Senior Product Designer, Agent Experience

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. The posting includes: - Intro about Vanta mission, role description: "As a Senior Product Designer, Agent Experience at Vanta, you will define how AI agents help security and compliance teams..." That's about the role. - Then "What you’ll do as a Senior Product Designer, Agent Experience at Vanta:" list of duties (responsibilities). That's responsibilities. - Then "How to be successful in this role:" list of qualifications/experience/skills. That's qualifications/requirements/skills. - Then "What you can expect as a Vanta’n:" list of benefits (salary, equity, medical, parental leave, stipends, etc). Also includes "To provide greater transparency to candidates, we share base pay ranges for all US-based job postings regardless of state." That mentions pay ranges but not specific numbers. It says they share base pay ranges but not actual numbers. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention "Industry-competitive salary and equity" but not specific numbers. It does not give actual pay range numbers. It says they share base pay ranges but not give them. So we should not create a Pay section because no specific numbers given. Benefits: they list many benefits: medical, dental, vision, parental leave, stipends, commuter benefits, family planning, 401k matching, PTO, sick time, holidays, virtual events, offices. Those are benefits. So we can include Benefits section. Schedule: not mentioned. So no Schedule. We also need About the role section: we have introductory paragraph(s) describing role and mission. Could be "About the role". Use

About the role

with paragraphs. Responsibilities: list from "What you’ll do..." bullet points. Use

• . Requirements/Qualifications/Skills: The "How to be successful in this role:" includes experience, skills, abilities. Could be split into Requirements and Skills but we can combine into Qualifications or Requirements. The instruction: prefer few substantive sections over many thin ones. So we could have one section "Qualifications" covering all. Or we could have Requirements and Skills separate but that may be thin. Better to have one "Qualifications" section. We need to ensure we don't repeat job title as heading. Already not. We need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is "Referral Instructions ..." and "About Vanta" etc. Those are not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Vanta" section is not boilerplate; it's company description. Should we keep? It's substantive info about company. Might be considered part of "About the role"? Possibly we can include as part of About the role or separate? The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The "About Vanta" could go under About the role or maybe we could add a separate section but not in allowed list. Better to incorporate into About the role. Also there is "Referral Instructions" which is application instructions; remove. Also "To provide greater transparency..." is about pay ranges but not specific; we decided not to include Pay section. Now produce HTML fragment. Structure:

  About the role

  ... (mission description and role overview)

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...
  We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet point from responsibilities and qualifications exactly as in text (maybe slight rephrase? Must preserve detail, not invent or summarize away. We can copy the bullet points as they appear, but ensure they are in
• . Should we keep the exact phrasing? Probably yes. Let's extract responsibilities bullet points from "What you’ll do as a Senior Product Designer, Agent Experience at Vanta:" list: - Lead end-to-end design for projects across the agent harness, from problem framing and discovery through launch and iteration. - Define how agents, skills, tools, and memory are composed, surfaced, and understood by customers. - Design experiences that help customers delegate real security and compliance work while maintaining visibility, control, and confidence. - Create patterns for reviewing, correcting, approving, interrupting, and recovering from agent-generated work. - Design conversational and agent interaction models across Vanta, Slack, and other surfaces where our agents appear. - Establish product patterns and principles for trustworthy agent behavior, including transparency, permissions, uncertainty, explainability, and graceful failure. - Partner with Product and Engineering to evaluate when an agent is the right solution for a customer problem. - Conduct customer discovery and usability testing with security, compliance, and GRC users. - Translate customer insights, product requirements, technical constraints, and AI quality considerations into clear design direction. - Collaborate with Design Systems and product designers across Vanta to turn emerging AI patterns into reusable, high-quality experiences. - Create design briefs, workflow models, prototypes, specifications, and other artifacts that bring clarity to complex problems. - Communicate design rationale, tradeoffs, risks, and recommendations clearly to cross-functional partners and leadership. - Contribute to design critique and help raise the quality bar for interaction design, information architecture, UX writing, and visual craft. - Help shape how Vanta approaches responsible AI and human control across the product. - Identify opportunities to improve how the design organization and product teams work together. Now qualifications bullet points from "How to be successful in this role:" list: - 7+ years of product design experience, with depth in B2B SaaS, complex workflows, or other sophisticated software products. - Experience designing AI-powered products, automation, or systems where product behavior may be dynamic or uncertain. - Ability to design agent experiences beyond chat, including systems involving agents, skills, tools, memory, and multi-step workflows. - Experience designing products that require human judgment, including deciding when and how to bring a person into an automated workflow. - Experience designing across surfaces that a product team may not fully control, such as Slack, terminal environments, or other third-party interfaces. - Strong product thinking and discovery skills, including the ability to frame ambiguous problems and identify the right questions to answer. - High craft in interaction design, information architecture, UX writing, and visual design. - Strong cross-functional collaboration skills, particularly with Product, Engineering, Research, Data, and customer-facing teams. - A thoughtful approach to responsible AI, including transparency, data control, human review, explainability, and recovery from incorrect or incomplete outputs. - A portfolio that demonstrates shipped work, complex workflows, meaningful tradeoffs, and learning from customers or users. - Ability to move fluidly between systems-level thinking and detailed interaction design. - Clear communication skills and the ability to influence cross-functional partners without formal authority. - Curiosity, sound judgment, and comfort working in emerging product spaces where patterns and best practices are still taking shape. - 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. - Open to using AI to amplify their skills and strengthen their work - demonstrating curiosity, a willingness to learn, and sound judgment in applying AI responsibly to improve efficiency and impact. Now benefits bullet points from "What you can expect as a Vanta’n:" list: - 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 Also there is a sentence: "To provide greater transparency to candidates, we share base pay ranges for all US-based job postings regardless of state. We set standard base pay ranges for all roles based on function, level, and country location, benchmarked against similar-stage growth companies. Final offer amounts are determined by multiple factors and may vary based on candidate location, skills, depth of work experience, and relevant licenses/credentials." This is about pay but not specific numbers; we should not create Pay section. However we could incorporate that into Benefits? It's about pay transparency. But instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state they share base pay ranges, but not actual numbers. It's still about pay. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they share base pay ranges, which is about pay. But we might still avoid Pay section because no specific range. However we could include a short paragraph under Benefits about pay transparency? But Benefits section is for benefits; pay is separate. Safer to not include Pay section and maybe include that sentence in About the role? It's not about role. Could drop it as it's not substantive detail about role? It's about compensation transparency; maybe we can keep it in Benefits as a note about pay transparency. But the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they share base pay ranges, which is a statement about pay. So we could include a Benefits subsection about pay transparency? However they said "Prefer a few substantive sections over many thin ones." So we could incorporate that sentence into Benefits as a bullet: "Transparent base pay ranges shared for all US-based roles". That is substantive. Let's do that. Thus Benefits bullets include that line. Now About the role paragraph: combine the introductory paragraphs before "What you’ll do". The text includes: "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. As a Senior Product Designer, Agent Experience at Vanta, you will define how AI agents help security and compliance teams accomplish meaningful work with greater clarity, control, and trust across Vanta and the surfaces where our customers already work. The Agent Experience team builds agent-led experiences that help security and compliance teams achieve outcomes with less manual effort. The team owns the agent harness, including agents, skills, tools, and memory, as well as the patterns that help customers understand, guide, review, correct, and trust agent-generated work. Our goal is to make AI-powered workflows useful, transparent, and dependable in a product where clarity and correctness matter. As a Senior Product Designer on this team, you will shape both the underlying agent experience and the customer-facing workflows built on top of it. You will partner with Product, Engineering, Research, Data, AI Quality, and customer-facing teams to turn ambiguous problems into thoughtful, scalable, and trustworthy experiences. The patterns you establish will influence product teams across Vanta." We can put that in a

  (maybe multiple paragraphs). We'll keep as one paragraph. Now ensure we don't include duplicated lines. There