About the role
Somebody has to read the Customs Act, the Foreign Trade Policy, the IRDAI broker regulations and a stack of notifications, and turn what they say into something software can evaluate without lying about it. That is this job.
If you have worked in regulatory content, statutory compliance libraries, indirect tax content, patent drafting or trade compliance at a manufacturer, you have done a version of this already — reading a primary instrument and producing a structured obligation with a trigger, a date and an evidence requirement. We are asking you to do it with more precision than anyone has asked before, and to stop paraphrasing.
What this job entails. You work from primary text, never a summary or a commentary. Each rule you produce carries the exact span it came from, the dates between which it applies, what evidence would satisfy it, and what it supersedes. When a provision genuinely cannot be resolved on the facts a system will ever hold, you say so and it becomes a state the software surfaces — not a footnote nobody reads. And you keep all of it correct through amendment cycles, which is the part that is invisible when it works.
You do not need to write code and we will not test you on it. You do need to be comfortable with structure: decision tables, if-then conditions, typed fields.
We are not filtering on the prestige of your degree, and we are not looking for policy writing. This is not a role about how trade ought to be regulated. It is a role about what the rule currently says, exactly, and what it would take to prove it.
What you’ll do
- Read primary instruments and produce structured, executable rules with span-level citation.
- Get the dates right — when a rule took effect, when it stopped, and what replaced it.
- Define evidence requirements: which document, issued by whom, bearing which field, would satisfy an auditor.
- Flag genuinely unresolvable provisions rather than picking an interpretation.
- Keep the rule base correct as notifications amend it, and know what changed and why.
What we look for
- Two to six years working with primary legal, regulatory, tax or standards text.
- You work from the source. If your instinct on an unfamiliar provision is to find a good summary of it, this is the wrong role.
- You are comfortable with structure — decision tables, conditions, schemas, typed fields.
- You can recognise when a provision cannot be decided on the available facts, and say so.
- You will hold a position under pressure from a founder who disagrees with you.
Nice to have
- Regulatory or trade content work — compliance libraries, tax content, legal publishing, XBRL taxonomies, or a regtech content team.
- Registered patent agent, or a law degree taken after an engineering or science degree.
- Customs, DGFT, foreign trade policy, HSN classification, SCOMET or marine insurance regulation specifically.
- Indirect tax or GST content, especially where you owned what happens when a notification lands mid-year.
- Any exposure to rules-as-code, decision modelling or knowledge representation.