Software Engineer; Backend

Axiomatic AI is building a new class of AI systems designed to reason with the rigor of the scientific method. By combining deep learning with formal logic and physics-based modeling, we create verifiable, interpretable AI systems that collaborate with and support human researchers in high‑stakes scientific and engineering workflows.

Our mission, 30×30, is to deliver a 30× improvement in the speed, accessibility, and cost of semiconductor and photonic hardware development by 2030.

We aim to revolutionize hardware design and simulation in these industries and are building a team of highly motivated professionals to bring these innovations from research into commercial products.

As a Staff Software Engineer (Backend), you will set the technical direction for our backend platform and drive the systems that power an AI‑native product s is a hands‑on, T‑shaped role with a deep backend specialization: you’ll spend roughly 70% of your time writing and reviewing backend code,
20% on architecture and technical strategy
, and 10% contributing to frontend work when needed.

You operate at the intersection of backend engineering, AI infrastructure, and platform reliability, making the foundational decisions that let every other engineer ship faster, safer, and cheaper.

• Write and ship backend code daily — this is first and foremost a hands‑on engineering role
• Own the technical strategy for backend systems and AI infrastructure
• Lead cross‑functional initiatives spanning backend, AI, infra, and frontend
• Design and evolve foundational platforms (model routing, agent runtime, persistence, observability)
• Drive engineering excellence through RFCs, standards, and architecture reviews
• Contribute to frontend development when needed, collaborating with frontend engineers on integration points
• Multiply the team through mentorship and force‑multiplier code (frameworks, internal libraries, shared patterns)
• Be the technical owner of production reliability
  : incident response, performance, cost, security

• Set the 12–24 month technical roadmap for backend systems with the Head of Engineering / Lead Software Engineer
• Author RFCs and design documents that shape the engineering organization
• Make build‑vs‑buy decisions on critical platform components (model routing, vector DBs, queues, eval pipelines)
• Design for scale, multi‑tenancy, and compliance readiness
• Drive architecture reviews and ensure technical consistency across squads

• Own foundational systems: conversation persistence, observability stack, and core platform services
• Lead cost‑optimization initiatives (caching strategies, batching, resource budgets)
• Establish SLOs and drive incident response, postmortems, and durable fixes
• Partner with infra on the deployment story (Cloud Run, Cloud SQL, VPCs, multi‑region)
• Drive security and compliance (auth, secrets, data residency, audit trails)

• Collaborate with the AI team to integrate LLM‑powered features into backend services
• Design clean abstraction layers for model providers, enabling routing and fallback
• Contribute to patterns for prompt management, evaluation, and regression testing
• Stay informed on emerging AI infrastructure trends and help evaluate build‑vs‑buy decisions
• Set and enforce coding standards, review templates, and testing practices
• Drive measurable quality improvements (p95 latency, error budgets, test coverage, infra cost)
• Identify systemic issues and design durable fixes, never one‑off patches
• Build internal frameworks and libraries that raise the velocity of every other engineer
• Mentor senior engineers and help them grow toward staff
• Lead technical interviews and define the engineering bar
• Represent backend engineering in cross‑functional planning
• Communicate trade‑offs clearly to product, leadership, and external stakeholders
• Coach the team on debugging, performance work, and incident response

• 10+ years of backend development experience
  , with 2+ in a staff/principal/lead role
• Documented technical leadership
  : led architecture for multi‑team systems, authored RFCs adopted org‑wide
• Distributed systems intuition
  :…