Engineering-first is a working practice, not a slogan.
Every claim carries its evidence
Internal documents follow the same rule as the product: assertions state their source, and uncertainty is quantified rather than smoothed over. Design reviews are argued, minuted and revisited.
Engineers go to site
Everyone who builds the platform spends time in plant rooms with the people who will use it. Software written about industrial assets by people who have never stood next to one is how the last decade went wrong.
Correctness sets the pace
We ship deliberately. A physics gate that is right 98% of the time is not a feature, it is a liability, and the schedule bends around that fact rather than the other way round.
Small teams, long ownership
Layers of the platform are owned end to end by small groups who stay with them. The ontology, the solver and the constraint gate each have a named owner accountable for their correctness.
Open roles
6 OPEN · BENGALURU / REMOTE-INPrincipal Engineer — Physics Validation
Own the constraint gate: modelling, tolerance, and the block/allow decision
Ontology Architect
Govern the EIO canonical entities, relationships and amendment process
Reliability Engineer — Deployment
Reconcile asset records on site; turn FMEA and RCM studies into constraint sets
Senior Backend Engineer — Graph
Build the EIG traversal and versioning layer at plant scale
Applied AI Engineer — Agents
Graph-grounded retrieval and diagnosis with node-level citation and calibrated confidence
Product Designer — Engineering Interfaces
Design for provenance: make measured, calculated and predicted visibly different
How we hire
Fixed stages, stated durations, a decision deadline. No unpaid take-home projects.