Account Executive, SLED Government - South
Vanta · Austin, TX · 1 mo ago
RemoteRemoteSalesFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, job title: Account Executive, SLED Government at Vanta. Not to repeat as heading.
We need to extract sections.
Let's read the posting.
Paragraphs:
"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 an Account Executive, SLED Government at Vanta, you will be responsible for driving a significant share of revenue by guiding new business and growth with State, Local, and Education organizations. Reporting directly to the Head of Public Sector, this is a highly visible role that requires cross-functional collaboration, strategic vision, and operational execution. Vanta for Government is Vanta’s AI-powered platform that helps government agencies and vendors protect mission data, manage risk, streamline compliance, and build trust – faster and with less manual work. Vanta’s public sector efforts are growing quickly and this is an exciting opportunity to join a new team dedicated explicitly to public sector sales. We are looking for a passionate, results-oriented, and collaborative sales executive who has a proven track-record of closing complex, multi-stakeholder deals within SLED markets."
That's about the role.
Then "What you’ll do as an Account Executive, SLED Government at Vanta:" then bullet list (actually sentences separated by periods). Let's extract bullet points:
- In coordination with Vanta leadership, develop and execute a comprehensive strategy to build, maintain, and expand Vanta for Government business across the SLED market.
- As an individual contributor, proactively work to cultivate, pursue, and capture SLED sales opportunities.
- Work cross-functionally to drive the sales and implementation of complex contracts, services, and solutions, with the ability to close sales through effective sales and negotiation methods.
- Serve as the primary point of contact between Vanta and key SLED accounts, and represent Vanta’s Public Sector team at industry events and conferences.
- Establish and grow strategic relationships with SLED decision-makers, systems integrators, and technology partners to expand access and accelerate deals.
- Partner closely with SLED-specific resellers, distributors, MSPs, and channel partners to expand access and accelerate deals.
- Serve as a subject matter expert on the SLED market, helping inform Vanta’s product roadmap, pricing strategy, service delivery, and positioning to meet customer needs.
That's responsibilities.
Then "How to be successful in this role:" then list of requirements/qualifications/skills.
Let's extract:
- 8+ years of progressive enterprise sales experience, including at least 4 years selling to SLED agencies within a SaaS company.
- Experience working in government is a plus.
- Entrepreneurial mindset that biases to action and leads with resilience through a fast-moving, complex, and collaborative environment.
- Strong understanding of SLED sales cycles, SLED procurement landscape, including contract vehicles, compliance requirements (e.g., GovRAMP), acquisition regulations, and partner ecosystems.
- Strong verbal and written communications skills, with the ability to demonstrate Vanta’s vision and values to a variety of public sector audiences.
- Develop a deep familiarity with Vanta’s software platform and how it can be used by government agencies to support real-world challenges.
- The ability to establish rapport with highly technical prospects is essential.
- Strong collaboration with internal partners and external counterparts.
- A deep passion for Vanta’s mission, public sector innovation, and mission-driven work.
- A high level of empathy for customers, you are a consultative seller with a track record of long-term customer retention.
- Must be authorized to work in the U.S. without the need for current or future employer sponsorship.
- 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.
These are requirements/qualifications/skills. We need to decide which sections to output. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only when posting has real specific content.
We have About the role (intro paragraph). Responsibilities (the bullet list). Requirements (maybe years of experience, government experience plus). Qualifications (maybe education? none). Skills (communication, technical, etc). Benefits (list of benefits). Pay (they mention base pay ranges but not specific numbers; they say "Industry-competitive salary and equity" and later "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 generic, not specific numbers. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, they do not give a specific range; they talk about ranges but not actual numbers. Is that considered filler? It says "Industry-competitive salary and equity" which is vague but still a statement. However they also say they share base pay ranges but not give them. This might be considered not specific enough. The instruction: never create Pay section unless posting actually states them. It does state they share base pay ranges, but not the actual range. I'd argue it's not specific content; it's a statement about practice but not actual numbers. Safer to omit Pay section.
Schedule: Not mentioned. No schedule info.
Benefits: They list many benefits: "Industry-competitive salary and equityComprehensive medical, dental, and vision coverage, with 100% of employee-only benefit premiums covered for most medical plans16 weeks paid Parental Leave for all new parentsHealth & wellness stipendRemote workspace, internet, and cellphone stipendCommuter benefits for team members who report to the SF and NYC officeFamily planning benefitsMatching 401(k) contribution with immediate vestingFlexible PTO policy, plus 80 hours of Sick Time11 company-paid holidaysVirtual team building activities, lunch and learns, and other company-wide events!Offices in SF, NYC, London, Dublin, Tel Aviv, and Sydney". That's specific benefits. So we should include Benefits section.
Now we need to decide on sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Requirements" and "Qualifications" could be split but we can combine? The instruction: prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have content for both Requirements (years of experience, government experience, etc.) and Qualifications (maybe education? none). Skills: we have communication, technical rapport, collaboration, passion, empathy, AI usage. That's separate.
We could have:
- About the role (intro)
- Responsibilities (bullet list)
- Requirements (years of experience, government experience, understanding of SLED sales cycles, etc.)
- Skills (communication, technical rapport, collaboration, passion, empathy, AI usage)
- Benefits (list)
Qualifications maybe not needed if we covered in Requirements. But we could put some items under Qualifications like "Must be authorized to work in the U.S." maybe that's a requirement. However we can keep Qualifications empty? Better not to include empty heading.
Thus we will output:
About the role
... intro paragraph ...
Responsibilities
- ... each bullet ...
Requirements
- 8+ years of progressive enterprise sales experience, including at least 4 years selling to SLED agencies within a SaaS company.
- Experience working in government is a plus.
- Entrepreneurial mindset that biases to action and leads with resilience through a fast-moving, complex, and collaborative environment.
- Strong understanding of SLED sales cycles, SLED procurement landscape, including contract vehicles, compliance requirements (e.g., GovRAMP), acquisition regulations, and partner ecosystems.
- Strong verbal and written communications skills, with the ability to demonstrate Vanta’s vision and values to a variety of public sector audiences.
- Develop a deep familiarity with Vanta’s software platform and how it can be used by government agencies to support real-world challenges.
- The ability to establish rapport with highly technical prospects is essential.
- Strong collaboration with internal partners and external counterparts.
- A deep passion for Vanta’s mission, public sector innovation, and mission-driven work.
- A high level of empathy for customers, you are a consultative seller with a track record of long-term customer retention.
- Must be authorized to work in the U.S. without the need for current or future employer sponsorship.
- 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.
- . The benefits text is a run-on sentence; we need to split into items. Benefits list from posting: - Industry-competitive