Confirmed on the employer's own hiring board on Nov 17, 2026. First seen by Alion on Nov 17, 2026. Sage scores A on the Alion truth index.
We're investing heavily in AI. Our AI Infrastructure team is building the platform that lets AI agents take engineering intent and carry it through the software development lifecycle end to end: planning, coding, testing, review and merge, with controls that let each team increase agent autonomy as trust builds.
The team designs and runs everything that makes that work: orchestration, isolated development environments, agent identity and access, model access and routing, context and memory, evaluation, and the feedback loops that make agents better over time. It's an unusual mix of distributed systems, systems engineering and applied AI, much of it not yet done at enterprise scale, and you'll be building it from the early stages with engineering teams across Sage as your first users.
The Role
You'll set the technical direction for major parts of the platform and stay close enough to the code to make sound calls. You'll turn the platform vision into an architecture teams across Sage can build on and rely on, and set the engineering bar across squads.
Responsibilities
- Own the architecture for one or more core platform areas, such as orchestration, execution environments, agent identity and access, or the model gateway, from design through production.
- Make and record key architecture decisions: service boundaries, contracts between components, technology choices and build-versus-buy, with options and trade-offs written down.
- Design the platform's trust model: isolation, least privilege, short-lived task-scoped access, evidence tied to exact code revisions, and safe failure handling, so autonomy can grow without growing risk.
- Lead the hardest technical problems hands-on: reliability, performance, security incidents, and scaling to many concurrent agent runs.
- Set engineering standards for testing, observability, security, deployment and recovery, and make sure they're adopted, not just documented.
- Work with architects and senior engineers from teams across Sage to turn their requirements into platform capabilities, and explain decisions back to them.
- Partner with ML engineers on evaluation and model strategy, so infrastructure and agent quality improve together.
- Mentor senior engineers and grow technical leadership across our distributed team.
What You'll Own
Technical direction and architecture for your platform areas, cross-squad technical trade-offs, and acceptance of engineering evidence before capabilities go live. You escalate product, security, legal or commercial policy questions with a clear recommendation.
What We're Looking For
Extensive engineering experience, including significant ownership of architecture and technical strategy for large-scale distributed or platform systems, and hands-on experience building LLM-powered or agent-based systems in production.
Technical Skills
- Expert in distributed systems design: durable workflows, queues and async processing, idempotency, consistency, failure recovery and operating at scale.
- Deep experience building cloud platforms (AWS preferred, or GCP/Azure): Kubernetes, containers, infrastructure as code, and multi-account or multi-tenant isolation.
- Strong security architecture judgement: identity and access management, short-lived credentials, secrets management, sandboxing, supply-chain security and auditability.
- Production experience with LLM systems: agents and tool use, context engineering, model routing, evaluation, and the ways they fail.
- Proficient in one or more of Python, TypeScript, Go, Java or Rust, and still able to write, review and debug production code.
- Experience defining API and event contracts, versioning and backward compatibility across teams.
Leadership & Ownership
- A track record of setting technical direction across multiple teams and seeing it through to production.
- Makes sound decisions under uncertainty, makes trade-offs visible, and changes course when the evidence says so.
- Exceptional written and verbal communication; can align engineers, architects, product and senior leaders around complex decisions.
- Raises the bar for senior engineers through design reviews, examples and pairing.
Mindset & Collaboration
- Growth mindset: curious, always learning and open to feedback.
- Works closely with the engineers who use these tools every day, helping the whole organization build software better and faster.
Nice to Have
- Experience with durable workflow engines such as Temporal, or similar.
- Experience with microVM or container sandboxing (for example Firecracker, Kata Containers or gVisor).
- Built developer platforms, CI/CD or code-review systems used across a large engineering organization.
- Experience with policy engines (for example OPA or Cedar) and fine-grained authorization.
- Open-source or public contributions in agent tooling or LLM infrastructure.
What Success Looks Like in Your First Year
- A small set of recorded architecture decisions guides the build without blocking teams.
- Your areas reach production with clear SLOs, passed security reviews and proven recovery drills.
- Teams onboarding to the platform adopt your capabilities with little custom work.
- Engineers around you make more decisions confidently because standards and examples are clear.
What to Expect
- We value humility and collaboration. We're looking for people who work as part of a team, not in silos.
- We expect engineers to take ownership beyond writing code, including tests, documentation and long-term system quality.
- We use AI tools heavily in our own work, and expect you to as well, with good judgement about when to trust them.

