Governed
Nothing that commits the business happens without a named approver.
Shows up as: the approval gate, the proof record, the word “answerable” in our copy.
Careers
Build the part that says no.
elan1 hires people to build the part of AI systems that says no: the rule checks, approvals and proof records between AI agents and business records. The company is based in Chennai, Tamil Nadu. This page explains how elan1 hires, what it values and how to apply.
We work the way the product does: a named owner for every change, short sentences, plans we publish.
01Open roles
No open roles today.
Open roles: none listed
Checked 10 Oct 2026No open roles today. Write to us to hear when that changes.
We list a role only when it is funded and has a named hiring manager. Until then we will not collect CVs for roles that do not exist. You can also write to us with the subject “Careers”.
02How we work
The product's rules are our working rules.
The same discipline elan1 Govern asks of an agent, we ask of ourselves: a rule, an owner, a record.
A named owner for every change
Every change to the product, the site or a policy has one person who answers for it, written down before the work starts.
Decisions written down
A decision that changes how the system behaves gets a short record: what we chose, what we rejected, and why. New joiners read the trail, not the folklore.
Short sentences
We write the way the product speaks: what a thing does, what it costs, where it is weak. No adjectives doing the work of evidence.
Plans we publish
Our roadmap is public, and every item on it is a plan. When one changes, we change it in public and log why.
Limits stated up front
Every product page carries its limits at equal weight. We expect the same in a design review or a pull request.
Tests that can fail
A check that cannot fail proves nothing. We show a guard failing before we trust it passing.
03What we value
Governed. Exact. Composed. Plain.
Exact
One unit, one angle, one number.
Shows up as: a logo specified in three numbers; one meter per layer; plans written as plans, with their level.
Composed
Parts that hold together.
Shows up as: shared configuration, industry packs as configuration, no bespoke forks.
Plain
We say what a thing does, including what it costs and where it is weak.
Shows up as: a Limits section on every layer page, and a public list of the words we don't use.
04When a role opens
What every role page will tell you.
- The work, described as the problems you would own in your first six months
- Who you would work with, and who you report to
- Where the role is based (India first) and how remote work is arranged
- The hiring steps, how long each takes, and who you meet
- The pay band for the role
If a role page is missing any of these, tell us and we will fix it.
// MEANWHILE
See what you would be building.
One governed action, from intent to proof record, in eight steps. No sign-up.