Principal Software Engineer (Platform, Developer Experience)

• ServiceTitan is building the Developer Platform for enterprise-scale SaaS. DevEx is a newly formed, lean, highly agile team (3–4 people) building AI-enabled platform infrastructure — pioneering AI-assisted development tools and coding agent runtimes (like Codex) to help engineering teams operate at “AI speed.”
• This is a Principal Engineer role per ServiceTitan’s engineering leveling framework: 10+ years of experience, SME & Systems Design Expert level, with broad R&D impact and an 18-month planning horizon. You are not just building within DevEx — you’re setting technical direction that other teams and eventually the APEX platform build against
• AI-Native Tooling: Agent orchestration layers, harnesses, and LLM reasoning loops — infrastructure other engineers will treat as the reference implementation for how ServiceTitan builds with coding agents
• Environments, Build & CI/CD, Developer Portal, Guardrails & Compliance, Velocity Harness — the full DevEx platform surface, where your architectural calls set the pattern others follow
• Domain Expertise & Influence: Proactively identify where your expertise on coding-agent infrastructure could help teams across R&D, not just within DevEx — and contribute to the wider industry conversation on agent-runtime architecture
• Delivery: Deliver complete, comprehensive system designs and lead autonomous delivery of the projects that come from them, in partnership with R&D peers. Remove barriers that are widely felt across the engineering org, not just your pod
• Independence & Decision Making: Operate self-directed and unsupervised. Act as the key technical consultant on agent-runtime architecture across multiple teams; your judgment and timeliness on hard calls is what people rely on
• Complex System Understanding: Anticipate technical problems before they surface in major platform initiatives; identify ServiceTitan’s technology needs on a 1–3 year horizon for AI-native developer tooling and drive the milestones to get there
• Leading by Example: Your work (harness code, orchestration patterns, agent-safety guardrails) becomes the thing other engineers copy to hit the quality bar you’ve set
• Mentor and raise the technical bar for engineers at Staff level and below on the team

Benefits

• Flexible time off
• Fully paid individual medical, dental, and vision coverage
• Access to on-demand services like Ginger, Headspace, One Medical, Galileo, Aaptiv, and more
• Tax free savings via HSA, FSA, and Dependent Care FSA
• 401(k) match
• Medical plan with up to $20,000 in fertility coverage
• Up to 30 weeks of paid leave for birthing parents and up to 16 for non-birthing parents
• Adoption support including reimbursement of up to $20,000
• Bereavement leave for loss of a pregnancy or loved one
• Access to programs for new parents including Maven Maternity, Ready, Set, Food! Wellthy, SNOO Smart Sleeper, and more
• Personal development programs

• Deep experience with build systems, CI/CD, or internal developer platforms shipped and operated in production at real scale
• A track record consistent with Principal-level scope: technical decisions and architecture that other teams and orgs build on, not just your own team’s roadmap
• Comfort setting direction with minimal oversight — this is a small, high-trust team; you’re expected to define the plan, not receive it
• Strong instincts for environment safety (RBAC, secrets management, compliance gates) as applied to autonomous or semi-autonomous coding agents specifically
• 15-20+ years of software engineering experience, with recent (last 6–12 months) hands-on work building coding-agent-runtime infrastructure — agent orchestration, harnesses, or LLM reasoning loops. This is a hard filter: process automation or AI-assisted code review experience does not meet this bar
• If you have the skills but are hesitant to apply because of your background, apply anyway
• Prior experience where coding agents are already core to daily engineering workflow, not a pilot
• Experience representing engineering direction externally (blog posts, conference talks) or influencing practice change across an org