Staff Product Security Engineer

Ready to be a Titan?

At ServiceTitan, we are transforming product security into a core part of how engineering delivers software. We are looking for a Staff Product Security Engineer to embed with one of our engineering portfolios and own its security outcomes end to end, across application security and cloud security, so that our 80 plus R&D teams build securely by default without slowing down innovation.

In this role, you will sit alongside engineering leaders in planning and design, threat model systems before they are built, own the portfolio's risk picture, and bring secure-by-default patterns to each team's architecture and workflow. You will be the security expert engineers know by name and the voice that carries their real-world context back into the program's strategy. This is an opportunity to shape how security is practiced where software actually gets built, turning security into an enabler of engineering velocity rather than a constraint.

What you'll do

Design Partnership

• •Standing Seat in Planning and Design: Join the portfolio's planning and design cadences as a permanent participant. Review roadmaps, architecture proposals, and technical designs early enough to shape them rather than gate them.
• •Threat Modeling: Lead and scale threat modeling across the portfolio using the program's standard and tooling. Prioritize top-tier systems, coach squads to run their own models, and make sure identified threats become tracked requirements in the findings flow.
• •Architecture Review: Provide secure architecture guidance for cloud-native services, microservices, multi-tenant data access, identity and secrets handling, and AI-enabled features. Translate the program's security requirements into concrete design decisions the squads can implement.

Portfolio Risk Ownership

• •Own the Risk Picture: Maintain a current, evidence-backed view of the portfolio's security risk across application findings, cloud posture, identity, and data exposure. Know what each squad builds, the data it touches, and where it is heading.
• •Drive Priorities with Engineering Leaders: Partner directly with the portfolio VP and their leaders to set remediation priorities, negotiate tradeoffs, and drive adherence to vulnerability remediation SLAs. Bring the data, own the follow through, and escalate with judgment.
• •Risk Acceptance and Exceptions: Guide squads through the program's risk acceptance process. Make sure exceptions are documented, time-bound, and visible to the right decision makers.

Paved-Road Adoption

• •Fit Central Patterns to Local Architecture: Take the paved roads built by the Platform and Programs team, including secure service templates, secrets management patterns, secure cloud configuration templates, CI/CD guardrails, and IaC policy sets, and adapt them to each squad's stack and workflow.
• •Drive Adoption in the Field: Get squads onto SAST, SCA, secrets scanning, IaC scanning, container scanning, and CSPM coverage, and keep them there. Tune signal quality with squads so findings are actionable, and close the loop on what is noise versus real risk.
• •Hands-On Remediation Support: Read the code, review the Terraform, and pair with engineers on fixes for the hard findings. Write reference implementations and fixes when that is the fastest way to unblock a squad.

Champion Coaching

• •Develop the Portfolio's Champions: Recruit, coach, and support the security champions across your squads. Be the technical expert they bring the hard questions to, and build them into the portfolio's first line of security response.
• •Contextual Enablement: Deliver just-in-time training, design reviews, and office hours tuned to what the portfolio is actually building. Help squads learn to fix their own code and configuration.

Strategy Feedback

• •Feed the Program Roadmap: Bring real engineering context back to the Director and the Platform and Programs team. Identify where central tooling, patterns, or standards fall short of what squads need, and shape what gets built next.
• •Metrics and Reporting: Contribute portfolio-level data to the program's metrics rhythm. Report on coverage, remediation velocity, and risk trends for your portfolio to security and engineering leadership.
• •Incident Support: Support triage and investigation of security incidents touching your portfolio, and turn lessons learned into design changes and paved-road improvements.

What you'll bring

• •Experience: 7-10+ years in product security, application security, cloud security, or a closely related security engineering role, with a strong software engineering foundation. Prior experience embedded with or partnering directly with engineering teams is strongly preferred.
• •Breadth Across AppSec and CloudSec: Demonstrated ability to work across the full stack of a modern SaaS product: secure code review, threat modeling, secure design, CI/CD and supply chain security, cloud identity and least privilege, IaC security, container and Kubernetes security, and cloud posture management. You do not need to be the deepest specialist in every area, but you must be credible in all of them.
• •Coding and Cloud Fluency: Proficiency reading and writing code in C#/.NET (preferred), Go, Java, or Python, and hands-on experience with Azure and/or AWS security services and IaC tooling such as Terraform or Bicep. You can review a pull request and a Terraform module with equal comfort.
• •Threat Modeling and Secure Design: Track record of leading threat modeling and architecture review at scale, and of turning the results into requirements engineering teams actually deliver.
• •Influence Without Authority: Proven ability to build trust with VP level engineering leaders and senior engineers, drive priorities through partnership rather than mandate, and hold the line on risk when it matters.
• •Automation Mindset: Preference for building repeatable patterns over one-off fixes. Comfortable scripting and automating security tasks, and comfortable using AI-assisted tooling to scale your own work.
• •AI Forward: Familiarity with securing AI-enabled features and AI coding agents, and with the emerging risks around non-human identities, MCP integrations, and data exposure in AI systems.
• •Certifications: CISSP, CCSP, CSSLP, AWS Security Specialty, Azure Security Engineer, OSCP, or similar are a plus, not a requirement.

Why this role?

Be in the Room: Most security engineers review what has already been decided. You will sit in portfolio planning and design as a standing member and shape what gets built before it is built.

Own a Portfolio, Not a Queue: You are accountable for the security posture of a defined set of squads and a named engineering leaders. Your success is measured in risk reduced, remediation velocity, and paved-road adoption across that portfolio, not in tickets closed.

Full-Stack Security Scope: This role deliberately spans application and cloud security. You will work across code, pipelines, identity, infrastructure, data, and AI systems, backed by specialists on the central team when you need depth.

Shape How Security Is Practiced: You will help define what embedded security partnership looks like at ServiceTitan, from how you engage with engineering leaders to how field learnings become platform patterns that scale across every team.

High Ownership, High Leverage: You will have the autonomy to identify problems, design solutions, and drive them to completion with your portfolio, and the backing of a central team that turns what you learn into patterns for everyone.

• Be Human With Us:
• Being human isn’t about checking every box on a list. It’s about the experiences we have, people we meet, and the perspectives we share. So, if you have the skills but are hesitant to apply because of your background, apply anyway. We need amazing people like you to help us challenge the conventional and think differently about the problems that we’re solving. We’re in this together. Come be human, with us.

Use of AI T