Complied AI is one place to see what changed across Indian statutory and regulatory sources, with the official document and the law it changes sitting right next to the update. You would build the parts people touch every day: the Act reader, the updates desk, and the pipelines that keep both fed.
Our stack is TypeScript, Next.js on the App Router, and Postgres through Supabase. Most of the interesting work is not in the framework. It is in the data. We pull from government sites that were not built to be read by machines, change their markup without notice, and sometimes sit behind rate limits or block scrapers outright. The code has to keep working when the source moves under it, fail in a way we can see, and never quietly publish something wrong.
A normal week might mean adding a new source to the updates pipeline, tightening a slow query behind the updates feed, improving how a section of an Act renders on a phone, or fixing the one edge case in a scraper that only shows up on Fridays. You would own a feature from the schema to the screen. We keep process light: no standup theatre, no tickets for the sake of tickets. We care that it works, that it is tested where testing earns its keep, and that the next person can read it.
This suits someone who has shipped real web software and is comfortable being the person who decides how a thing should work, not just how it should look. You do not need a compliance background. You do need to care that the numbers and the text are right, because people make decisions off this.
The role is freelance, fully remote, and paid. Hours are flexible and we are honest that the workload rises and falls. If you want a title and a big team, this is not it yet. If you want to build the core of a small product and see it used, it is.
Apply for Software Engineer
No CV upload. A few questions about you, then a few about the work. Write as much or as little as you like.