Operations Manager, Signal Systems

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 own the data Vanta's EPD organization actually runs on — bringing new signal sources online, standardizing them at the point of ingestion, and building the systems that make the underlying data trustworthy rather than merely stored.

The EPD Systems team is building the infrastructure Vanta's engineering, product, and design organization depends on to understand itself.

Not by asking teams to be more diligent but by going to the source, processing it, standardizing it, and pushing value back out so each source of truth earns its own adoption.

What you’ll do as a Operations Manager, Signal Systems at Vanta:

Bring new signal sources online end to end — from discovery and scoping through ingestion, standardization, and live operation

Identify the specific failure modes in each information source and build systems that mitigate them at the point of ingestion

Go to the teams that produce and consume a signal, understand what the information actually means and what they need back from it, and build accordingly

Replace human-diligence dependencies with engineering solutions: derive fields, pull from source systems, validate at write time

Build alongside teammates who are growing into building — raise their technical ceiling, not just your own output

Partner with the inference and systems layers to ensure what you produce is queryable, trustworthy, and ready to build on

How to be successful in this role:

You look at a data source and see its failure modes before its contents: where it lies, where it goes stale, where it's duplicated, where the schema won't hold at 10x

Your first move on an adherence problem is an engineering answer — derive it, pull it, or validate it at write time.

Better forms and nudges are your last resort

You've shipped something yourself in roughly the last 12–18 months — a pipeline, an internal tool, a working prototype, an agent — and you can walk through the code and defend your choices.

Specs handed to an engineer don't count for this bar

You've built something real with Claude, an LLM API, or agentic tooling — not "I use ChatGPT for drafts." You'll be asked what broke and how you worked around it