Compliance is broken.
Help us fix it.
We're a small team building the document-compliance platform we wish we'd had when we were on the other side of the audit. Every rejection cites the rulebook clause. Every decision is on an immutable, chained log. If you've ever stayed up the night before an audit reconciling spreadsheets, you already know why we're here.
Why work here
No mission slides. Just six things we actually believe - and which shape every decision from hire #1 to the next 12 phases.
Compliance, made boring
Every audit failure costs real money and, in food and pharma, real safety. Making compliance dull and automatic is a serious craft. We treat it as one.
Real prod, not a demo
HA Postgres, autoscaled workers, real Vertex AI calls, real S3 Object Lock retention. The thing you ship to main goes to paying customers - not a sandbox.
Small team, real ownership
You will own systems end-to-end - schema, API, worker, UI, on-call. Twelve phases shipped with a tiny team. You'll do the same kind of work, not be slotted into a 30-person feature pod.
AI where it earns its keep
Gemini and Textract sit behind a deterministic pipeline with confidence-band routing and human queues. No magic. Every model decision is logged and reviewable.
Phases, not stories
We ship in phases with a hard acceptance bar - 177 acceptance tests today. No Jira theatre. Once a phase passes, it's done; we move to the next one.
You'll see the auditor's face
Engineers sit in on audit calls. Customer-success people commit code. The artificial wall between "build" and "use" doesn't exist here - and the product is better for it.
How we work
Remote-first, async by default, with one short live sync a day for whoever needs it. We write more than we meet - design notes, postmortems, phase plans - because clarity beats velocity in a system that gets cited in regulatory filings. We deploy multiple times a day from main; every change is gated by acceptance tests and an append-only audit log. On-call is shared and humane; alerts only page on user-visible breakage. We're remote-friendly across India, the US, and the EU, with timezone overlap (10:00–14:00 IST) treated as the precious resource it is.
- 177acceptance tests gating
main - 12phases shipped, top-to-bottom
- ~$0.40infra cost per user / month
Open roles
A short list, intentionally. We post a role when there's actual capacity to mentor and onboard well - not before.
Full-Stack Python Developer
EngineeringJob ID JOB-236DE6E4
Build features end-to-end across our Django backend and Angular frontend, from document intake and AI extraction down through the dashboards food-safety teams use every day.
View details →IT Infrastructure Engineer
EngineeringJob ID JOB-6C9FFCAF
Own how Tracegence runs in production: GCP infra, Cloud Run, Cloud SQL, the CI/CD pipeline, and the cost and observability story that keeps it healthy.
View details →ML / AI Engineer
EngineeringJob ID JOB-2D3CE0E0
Own how Tracegence reads, validates, and reasons over compliance documents - from Document AI OCR through Vertex AI classification to the predictive scoring that flags risk before audits do.
View details →Security Engineer
EngineeringJob ID JOB-A4E72F63
Own the security posture of a multi-tenant SaaS handling food-safety compliance data - Postgres RLS, JWT auth, HMAC-signed workflows, immutable audit logs, and everything between them.
View details →Test Engineer (QA / SDET)
EngineeringJob ID JOB-4A7D26C3
Own how Tracegence catches regressions before customers do - test infrastructure, end-to-end coverage across the Django backend and Angular SPA, and the contract tests that keep the AI pipeline honest.
View details →UI / UX Designer
DesignJob ID JOB-DBB1D9F1
Design the screens compliance teams live in every day - dashboards, document workflows, recall investigations, audit portals - in a domain where "simple" is a feature, not a default.
View details →Don't see your role?
GeneralIf you've spent real years close to a document audit - as an engineer, auditor, supplier QA, or compliance manager - and the rest of this page made you nod, we'd like to hear from you regardless of what we have posted today.
Reach out →How hiring works here
Short, two weeks end-to-end, no whiteboard puzzles. We pay for take-home work past the first conversation.
- 01
30-min intro
You and the founder. Why us, why you, why now. We answer every question on the table - comp range, runway, customer count, what's broken.
- 02
Paid take-home
A small, scoped slice of real work - 4 to 6 hours, paid at a fair rate. You keep the code. Engineering roles ship a feature; domain roles draft a rule pack.
- 03
Working session
90 minutes pairing on your take-home, then on a problem we're currently stuck on. We want to see how you think when the answer isn't pre-baked.
- 04
References & offer
Two reference calls - your pick, plus one we ask for. Offer follows within 48 hours. We tell you the comp band before you ever invest a minute in step 02.
What you get
Honest about the early-stage parts - and honest about the parts that already work.
Don't see your role?
Send us a note - we read every email, and a good fit beats a posted req.