At Vanta, our mission is to help businesses earn and prove trust.We believe that security should be monitored and verified continuously, and we empower companies to practice better security and prove it with ease. Vanta has a kind and talented team, and while some have prior security experience, many have been successful at Vanta without it.

You will build the operating system for EPD — the systems, agents, and practices that make engineering, product, and design unreasonably effective at delivery, with Jira as the substrate.

The EPD Systems team is building the infrastructure Vanta's engineering, product, and design organization depends on to understand itself and operate well. We're constructing three interlocking layers: sources of truth at the foundation, a shared interpretive layer that reasons across all of them, and the operating system that makes the work itself legible. This role owns the operating system.

This is not a traditional PMO or status-reporting role. You build — agents, automation, workflow design, and the practices that make teams want to use the system rather than route around it.

What you’ll do as a Senior Systems Designer at Vanta:

• Design and own workflow and hierarchy across engineering, product, and design in Jira
• Make sure Jira reflects real practice, and real practice reflects what needs to show up in Jira — in both directions
• Build the agents and automation that run the system yourself, with AI as part of how you work
• Drive adoption: go to the teams whose practice doesn't match the substrate today and change that — through conversation, well-built artifacts, or clear instruction that works without you in the room
• Understand delivery breakdowns at the mechanism level and build fixes that address the root cause, not the symptom
• Build alongside teammates who are growing into more technical work — raise their ceiling, not just your own output

How to be successful in this role:

• You build and ship, recently, with AI as part of how you work. "I'd ask an engineer to build that" is not a valid answer here
• You find the mechanism that's actually failing before you reach for a tool. Your default is to remove steps, not add them
• You move toward a solution now. You don't wait for a green light to start, and you can name a real decision you made and acted on without checking first
• You learn what's new before anyone tells you to — especially in AI tooling — and you share what you find with others
• You get things adopted without authority: through a conversation, a well-built artifact, or clear instruction that carries your message beyond you being in the room