Account Executive

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - About Dust (intro) maybe "About the role"? Actually posting includes "About Dust Work is being rewritten..." That's company description. Could be "About the role"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for the intro describing role? But we have a summary: "Summary As an Account Executive at Dust, you’ll help shape..." That's role description. Could be "About the role". Or we could have "About the role" for the summary and responsibilities. We also have "What you'll do" list of duties. That's responsibilities. We have "Requirements" with subpoints Aptitude, Attitude, Agency. Those are requirements. We have "Compensation and Benefits" with details: Competitive compensation: $250K–$320K OTE (50/50 split, ramped quota of $1.3M annually) Significant equity package ... relocation support Health insurance ... New MacBook Pro ... Beautiful office ... Opportunity to travel ... Regular team events and offsite. Thus we can have Benefits section (list) and Pay section (maybe separate). The instruction says include Pay/Schedule/Benefits sections only if posting actually states them. Pay is stated: compensation range. Benefits are stated. Schedule not mentioned (no schedule). So we should not include Schedule. We also have Location section: "We're prioritizing building our team with an in-person culture at our offices in Paris, London, San Francisco, and New York..." That's location info. Could be a section? Not in the list of headings but we could maybe treat as "Location" but not in allowed headings list? 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? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create a Location heading; we could embed location info within About the role or maybe as a paragraph under About the role. But we need to preserve all substantive info. Could include location in About the role paragraph. Also there is "Why Dust" section at end. Could be part of About the role or maybe "About the company". Not in list. Could embed in About the role. We need to avoid boilerplate: "Even if you don't check every box..." etc. That's maybe part of encouragement but could be considered boilerplate? It's not cookie/navigation/legal/EEO etc. It's part of the posting encouraging applicants. Might be considered substantive? It's more like encouragement. Might be okay to keep but could be considered filler? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The encouragement lines are not those. Could keep. But we need to avoid filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  ... (intro + summary + why dust + location)

  Responsibilities

  • Own the full sales cycle for Enterprise and MidMarket accounts
  ...

  Requirements

  • Aptitude: ...
  ...
  Maybe break Aptitude, Attitude, Agency as sub-items? Could be separate
  under Requirements with each as
  • containing the bullet points. We need to preserve all substantive info from Requirements: Under Aptitude list of bullet points; Attitude list; Agency list. We could structure as:

    Requirements

    • Aptitude
      • 5+ years of B2B SaaS sales experience, with a consistent track record of meeting or exceeding quota
      ...
    • Attitude
      ...
    • Agency
      ...
    That preserves details. For Benefits and Pay: We could have:

    Pay

    Competitive compensation: $250K–$320K OTE (50/50 split, ramped quota of $1.3M annually)

    Benefits

    • Significant equity package in a Sequoia-backed startup
    • Relocation support
    • Health insurance for you and your dependents
    • New MacBook Pro or Linux machine, monitor, keyboard, etc.
    • Beautiful office in the heart of San Francisco
    • Opportunity to travel to Paris and work with the EU team multiple times a year
    • Regular team events and offsite
    We might also include "Competitive compensation" as Pay. We should not include Schedule. We need to ensure we don't duplicate content. The "Compensation and Benefits" section originally had both pay and benefits; we split. Now we need to check for any duplicated lines: The posting repeats some sentences? Not obvious. Now produce final HTML. Check that we didn't include any markdown fences. Let's craft the About the role paragraph: combine company description, summary, why dust, location. Company description: "About Dust Work is being rewritten, and the people holding the pen are the ones who actually run it. With enterprise-grade governance, flexible model choice, and a collaborative interface for humans and agents to work together, Dust empowers AI Operators at the world’s fastest-moving companies to rewire how work gets done. With 70%+ weekly active users, people stick with Dust as much as they do with Slack and Notion. We don't get piloted and shelved. We land once, and spread. We're at an exciting stage of our journey, and growing fast. We're serving great customers like Datadog, 1Password, Cursor, Clay, Vanta and Persona, and aim to x5 our growth by the end of 2026. Dust is backed by Sequoia with a determined team of optimists (coming from Stripe, OpenAI, and Stanford) who like to focus on users, ship fast, and don't take themselves too seriously while doing so. The Generalist named us among the Future 50." Summary: "Summary As an Account Executive at Dust, you’ll help shape how companies adopt AI at work by bringing our platform to digital-native startups and larger enterprises alike. You’ll drive new business across both Enterprise (six-figure+) and MidMarket ($50–75K) segments, working in a lean, fast-moving environment where you’ll own the full sales cycle from prospecting to close. This is an opportunity to help define how AI-native sales teams operate. As a GenAI-native company, Dust is rethinking not only what software can do for customers, but also how modern go-to-market teams work with AI at the core. You’ll partner closely with Solutions Engineering and Customer Success to help customers transform how work gets done through custom AI agents connected to their internal systems and knowledge. You’ll contribute to building a new category from the ground up in an environment that values ownership, curiosity, speed, and strong execution." Why Dust: "Why Dust The models are powerful enough. What's missing is the product layer where AI meets how companies actually work. That's what we're building: the infrastructure that lets any team turn scattered knowledge and tools into coordinated execution with agents they build, own, and run themselves. We use Dust ourselves every day. We get to shape how humans and agents collaborate while solving our own problems with the product we ship. That loop is rare, and it's why we move fast. If you're excited about defining a new category and want to join a determined team of optimists who focus on users, ship fast, and don't take themselves too seriously, we'd love to talk. Even if you don't check every box in our requirements, we encourage you to apply. We value diverse perspectives and backgrounds, and we're more interested in your potential and passion than a perfect match to our checklist. Learn how we think and work.Our product constitution, a story about our missionAgents at work - Latent Space, podcast with our cofounder, Stanislas Polu, 2024LLMs reasoning and agentic capabilities over time - dotAI, podcast with our cofounder, Stanislas Polu, 2024" Location: "We're prioritizing building our team with an in-person culture at our offices in Paris, London, San Francisco, and New York because we value the magic that happens when talented people work closely together. We have an office-first culture. Some of the best things about building at Dust are the energy, the fast decisions, and the unexpected conversations that unlock a hard problem, which happen because we are in the same room. Being together is not a formality, it is how we do our best work, and it is something we actively protect. That said, we hire people with strong judgement and we extend that trust to how they manage their time. When working from home makes more sense for what you need to get done that day, we trust you to make that call." We can combine all into a paragraph or multiple paragraphs. Use

    for prose. Could split into multiple

    under the heading. We need to avoid duplication: The "Learn how we think and work.Our product constitution, a story about our missionAgents at work - Latent Space, podcast with our cofounder, Stanislas Polu, 2024LLMs reasoning and agentic capabilities over time - dotAI, podcast with our cofounder, Stanislas Polu, 2024" seems garbled but it's part of the posting. We'll keep as is. Now responsibilities list: from "What you'll do" bullet points. List them: - Own the full sales cycle for Enterprise and MidMarket accounts - Prospect and qualify opportunities through self-generated outbound efforts and inbound demand - Navigate complex, multi-stakeholder buying committees across 2–6 month sales cycles - Close six-figure deals while maintaining strong pipeline coverage and forecasting discipline - Build strategic relationships with senior stakeholders and identify expansion opportunities within target accounts - Build and establish US sales motions - Contribute to repeatable sales playbooks, processes, and best practices as we scale the US business - Share learnings and market insights that help shape pricing, messaging, and go-to-market strategy - Explore creative approaches to customer acquisition, events, and market expansion - Operate effectively in a lean, fast-moving environment where experimentation and iteration are encouraged - Drive creative, resourceful selling in a lean environment - Master product positioning and deliver compelling demos independently - Design and run paid pilot programs alongside Solutions Engineers - Develop land-and-expand strategies and target account plans for large tech companies - Collaborate cross-function