Platform and DevOps

Our customers' regulatory posture -- their ability to demonstrate compliance to auditors, regulators, and their own boards -- depends on what our systems output. Every obligation we extract, every answer our AI gives, every change we ship has real-world consequences for the companies that trust us. We treat that responsibility as the product, not as a constraint on the product.\n\nHOW WE WORK\nA few honest specifics about the team you'd join:\n- Lean by design, impact visible.\n- Merit-driven, not tenure-driven.\n- We grow people from within first.\n\nCORE REQUIREMENTS -- EVERY MEMBER OF TECHNICAL STAFF\nThese are non-negotiable.

Specialist depth requirements stack on top of these; they do not substitute.\n\n1. AI-native engineering practice (mandatory)\nYou have already made the transition. We are not training you on how to use agents -- we are hiring you because you have already internalized it and have opinions about where the current generation of tools is weak.

Concretely, you can show us:\n- A shipped artifact -\n- A specs-and-evals practice.\n- Autonomy-slider fluency.\n\nWe follow Karpathy's framing: vibe coding raises the floor; agentic engineering raises the ceiling without lowering the quality bar. Regulatory product is the second one, full stop.\n\n2. Spec discipline\nYou can write a spec that an agent can act on and a second Member of Technical Staff can sign off on.A spec that an agent misinterprets is a spec problem, not an agent problem.

You own the diagnosis.\n\nA spec that an agent misinterprets is a spec problem, not an agent problem. You own the diagnosis.\n\nYOUR DEPTH: DEVOPS & PLATFORM\nDevOps & Platform at Tracfox is not the role that gets paged when builds fail. It's the role that builds the harness which makes those pages unnecessary.

You own the substrate that every other Member of Technical Staff -- and every agent on the team -- depends on: our managed compute, the data-layer fleet across environments, the IaC tree, the CI/CD pipeline, the observability stack, and the secrets and identity surface that ties them together.\n\nRequired depth\n\n- Cloud platform depth.\n- Kubernetes operational fluency.\n- Terraform / IaC at scale.\n- CI/CD pipeline design.\n- Observability fluency.\n- Secrets and identity surface.\n- Developer-experience instincts.\n\nHOW TO APPLY\nShow us what you have built that you are proud of. A live URL, a repo, a demo, a write-up -- whatever shows it best. We care about what it tells us about how you work, not about the medium.\n\nApply at: