Engineering Manager, App Primitives

We need to output HTML fragment with sections: About the role? Actually the posting includes description. We need headings for sections present: About the role? The text includes "At Vanta, our mission..." that's about company. Could be "About the role" maybe not. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content. We have content: description of role (What you’ll do as an Engineering Manager at Vanta) -> that's responsibilities. Also "How to be successful in this role:" -> qualifications/requirements. Also "What you can expect as a Vanta’n:" -> benefits. Also maybe "About Vanta" -> about the company, could be "About the role"? Not exactly. Could treat as "About the role" maybe not. But we can include a section "About the role" with the introductory paragraph about mission and team? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to preserve all substantive information; remove boilerplate like EEO, legal, referral instructions, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract sections: - About the role? Could include the introductory paragraph: "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. Vanta's App Primitives team owns the shared building blocks that span data structures to UI: comments, notifications, event logs, feature flags, and task management. We own the general infrastructure; product teams own the logic built on top. Getting this layer right unlocks velocity for every team at Vanta. As the Engineering Manager, App Primitives at Vanta, you'll lead the team building the shared product primitives that every Vanta product team depends on, owning the infrastructure layer that makes collaboration, communication, and core workflows possible across the entire platform. Our Engineering Managers develop and grow high-performing teams that deliver significant value to our customers and enable our business to scale. This role sits at the intersection of technical architecture and team development, with real authority to set direction and grow a world-class platform team. Visit our Vanta Engineering Blog to learn more about what our team is working on!" That's substantive. Could be under

About the role

with

... maybe multiple paragraphs. - Responsibilities: "What you’ll do as an Engineering Manager at Vanta:" followed by bullet list (though not bullet but sentences). We'll convert to

• . List items: - Lead and grow the App Primitives team, owning hiring, team health, delivery, and the development of senior engineers and technical leads - Own the strategy and roadmap for Vanta's shared product primitives: comments infrastructure, notifications platform, event log, feature flag system (Statsig), and task management - Define and steward the interface model between App Primitives systems and product teams, ensuring product teams can build on top of shared infrastructure quickly and safely, without owning the underlying systems themselves - Partner closely with product engineering leaders across Vanta to surface developer needs, identify friction in shared systems, and prioritize investments that unlock velocity at scale - Set technical direction for a full-stack team working across data models, backend services, and UI primitives, and earn the trust of senior engineers through strong technical judgment - Manage cross-team dependencies and stakeholder expectations across concurrent workstreams, operating with a high degree of autonomy - Requirements/Qualifications: "How to be successful in this role:" list. Items: - 5+ years of engineering experience with 2+ years managing engineering teams, including a track record of developing senior engineers and technical leads - Experience leading platform, shared services, or product infrastructure teams — where your team's output is what other teams build on - Technical fluency across the full stack, with enough depth in backend systems, shared data models, and API design to engage substantively with your team's technical decisions - Strong cross-functional collaborator: able to partner with product, design, and engineering leaders to define clear ownership boundaries and drive alignment across teams - Track record of hiring senior engineers in a competitive market and building a team culture people want to be part of - Experience managing multi-team dependencies and delivering across concurrent workstreams with limited oversight - Uses AI in day-to-day work to amplify their skills and strengthen their outcomes, applying it across routine workflows, actively building fluency through experimentation, and exercising sound judgment to ensure AI-assisted work meets a high quality bar. We could put under

  Requirements

  or

  Qualifications

  . The instruction list includes both Requirements and Qualifications as possible headings. We need to decide. Since the content is about qualifications/experience, we can use

  Qualifications

  . Or Requirements. Choose one. Probably Qualifications. - Benefits: "What you can expect as a Vanta’n:" list. Items: - Industry-competitive salary and equity - Comprehensive medical, dental, and vision coverage, with 100% of employee-only benefit premiums covered for most medical plans - 16 weeks paid Parental Leave for all new parents - Health & wellness stipend - Remote workspace, internet, and cellphone stipend - Commuter benefits for team members who report to the SF and NYC office - Family planning benefits - Matching 401(k) contribution with immediate vesting - Flexible PTO policy, plus 80 hours of Sick Time - 11 company-paid holidays - Virtual team building activities, lunch and learns, and other company-wide events! - Offices in SF, NYC, London, Dublin, Tel Aviv, and Sydney We should not include Pay or Schedule sections because not explicitly stated (though they mention industry-competitive salary and equity but not specific numbers). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated, so we include Benefits. Pay not specific numbers, so we omit Pay section. Schedule not mentioned. We also have "About Vanta" section after the benefits? Actually after benefits there is "To provide greater transparency to candidates..." that's about pay ranges, but we should drop as boilerplate? It's about pay ranges but not specific numbers; still it's generic. Might be considered boilerplate; we should drop. Then EEO etc drop. Then "About Vanta" paragraph about history. That's substantive about company; could be under

  About Vanta

  but instruction only lists certain headings; but we can still use

  About Vanta

  as a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. We could add About Vanta as a section. However they said "include a section ONLY when the posting has real, specific content for it". The About Vanta paragraph is specific. So we can include

  About Vanta

  . But maybe better to incorporate into About the role? The intro already includes mission etc. The About Vanta paragraph is separate history. Could be separate. We need to avoid duplication: The intro already mentions mission etc. The About Vanta paragraph is about founding etc. Keep both? Might be okay. We also need to drop referral instructions, EEO, equal-opportunity, scam-warning, etc. Now construct HTML:

  About the role

  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. Vanta's App Primitives team owns the shared building blocks that span data structures to UI: comments, notifications, event logs, feature flags, and task management. We own the general infrastructure; product teams own the logic built on top. Getting this layer right unlocks velocity for every team at Vanta. As the Engineering Manager, App Primitives at Vanta, you'll lead the team building the shared product primitives that every Vanta product team depends on, owning the infrastructure layer that makes collaboration, communication, and core workflows possible across the entire platform. Our Engineering Managers develop and grow high-performing teams that deliver significant value to our customers and enable our business to scale. This role sits at the intersection of technical architecture and team development, with real authority to set direction and grow a world-class platform team. Visit our Vanta Engineering Blog to learn more about what our team is working on!

  Responsibilities

  • Lead and grow the App Primitives team, owning hiring, team health, delivery, and the development of senior engineers and technical leads
  • Own the strategy and roadmap for Vanta's shared product primitives: comments infrastructure, notifications platform, event log, feature flag system (Statsig), and task management
  • Define and steward the interface model between App Primitives systems and product teams, ensuring product teams can build on top of shared infrastructure quickly and safely, without owning the underlying systems themselves
  • Partner closely with product engineering leaders across Vanta to surface developer needs, identify friction in shared systems, and prioritize investments that unlock velocity at scale
  • Set technical direction for a full-stack team working across data models, backend services, and UI primitives, and earn the trust of senior engineers through strong technical judgment
  • Manage cross-team dependencies and stakeholder expectations across concurrent workstreams, operating with a high degree of autonomy

  Qualifications

  • 5+ years of engineering experience with 2+ years managing engineering teams, including a track record of developing senior engineers and technical leads
  • Experience leading platform, shared services, or product infrastructure teams — where your team's output is what other teams build on
  • Technical fluency across the full stack, with enough depth in backend systems, shared data models, and API design to engage substantively with your team's technical decisions
  • Strong cross-functional collaborator: able to partner with product, design, and engineering leaders to define clear ownership boundaries and drive alignment across teams
  • Track record of hiring senior engineers in a competitive market and building a team culture people want to be part of
  • Experience managing multi-team dependencies and delivering across concurrent workstreams with limited oversight
  • Uses AI in day-to-day work to amplify their skills and strengthen their outcomes, applying it across routine workflows, actively building fluency through experimentation, and exercising sound judgment to ensure AI-assisted work meets a high quality bar

  Benefits

  • Industry-competitive salary and equity
  • Comprehensive medical, dental, and vision coverage, with 100% of employee-only benefit premiums covered for most medical plans
  • 16 weeks paid Parental Leave for all new parents
  • Health & wellness stipend
  • Remote workspace, internet, and cellphone stipend
  • Commuter benefits for team members who report to the SF and NYC office
  • Family planning benefits
  • Matching 401(k) contribution with immediate vesting
  • Flexible PTO policy, plus 80 hours of Sick Time
  • 11 company-paid holidays
  • Virtual team building