Build the defence that does not wait to be told
Most security work makes an analyst faster at a job they were already doing. We are building the platform that does the job: detecting, investigating and responding on its own, with its own reasoning model, inside environments that cannot call out for help.
Where the work sits
We hire continuously across these areas rather than posting a fixed list of requisitions. Tell us which one is yours and what you have built.
AI and ML engineering
Fine-tuning and evaluating SAGE, designing the agent architecture behind AuraXP, and building the evaluation harnesses that decide whether a change to reasoning was actually an improvement.
Security research and detection engineering
Detection content mapped to MITRE ATT&CK and ATT&CK for ICS, behavioural models, threat intelligence pipelines, and the adversary research that keeps all of it current.
Platform and data engineering
The ingestion path, normalisation across 250+ sources, the event store behind it, and the query layer that has to answer an investigation's questions in seconds rather than minutes.
Product engineering
The analyst surface: the investigation workbench, the case narrative, and the interfaces where an autonomous decision has to be explained well enough to be trusted or overruled.
Solutions and deployment engineering
Taking the platform into customer environments, including on-premises, sovereign and fully air-gapped deployments, and the OT estates where nothing may be sent to a controller.
Product management
Deciding what autonomous defence should do next, and holding the line between a capability that demonstrates well and one that survives a regulated customer's evaluation.
Hyderabad and Bangalore
A deep-tech company shipping a sovereign platform from India, recognised under DPIIT Startup India and a member of the NASSCOM DeepTech Club.
Hyderabad
Engineering, security research and product.
Bangalore
Engineering, security research and product.
Tell us what you have built
A CV and the discipline you are aiming at is enough to start. If something you have shipped is public, point us at it: we would rather read the work than a summary of it.
Prefer email? Write to [email protected].