Account Executive

We need to output HTML fragment with sections for headings that have content: About the role? The posting includes "About Our Client", "The Opportunity", "What You'll Do", "What We're Looking For", "Bonus Points", "What Success Looks Like", "Why This Opportunity". Also location, compensation, comp structure, employment type are metadata; we should fold minor metadata into a short

or drop it. 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." So we can include a

for location, compensation, comp structure, employment type. Probably combine them. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings if they match content? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we should use

for each section heading we include. So we will wrap each heading in

. For lists, use

• . For prose, use

  . We must not include sections with filler like "commensurate with experience". We have real content for About Our Client, The Opportunity, What You'll Do, What We're Looking For, Bonus Points, What Success Looks Like, Why This Opportunity. Also we could include a short metadata paragraph. We must not include navigation/legal/EEO etc. None present. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details. That's a lot; we need to include everything but can we summarize? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep all details, not omit any. That means we need to include all bullet points etc. However we can keep them as lists; we must not drop any bullet. Thus we need to output a fairly large HTML fragment with all content. We need to ensure we don't add extra sections like Pay, Schedule, Benefits unless present. Compensation is present: "$130K–$150K OTE Comp Structure: 50/50 Base + Variable with Accelerators". That's compensation info. Should we include a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation, so we could include a Pay section. However they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could add a

  Pay

  with the compensation details. But they also said "fold minor metadata into a short

  or drop it." The location, compensation, comp structure, employment type could be considered minor metadata. However they said we can include Pay section if posting actually states them. It does state compensation. So we could either include a Pay section or fold into a short

  . The instruction: "fold minor metadata into a short

  or drop it." That suggests we could treat location, compensation, etc as minor metadata and put them in a short

  . But also they say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since it does state compensation, we could create a Pay section. Which is preferable? The instruction says "Prefer a few substantive sections over many thin ones." So maybe better to fold metadata into a short

  rather than create a thin Pay section. So we will include a short

  with location, compensation, comp structure, employment type. Thus sections: About Our Client, The Opportunity, What You'll Do, What We're Looking For, Bonus Points, What Success Looks Like, Why This Opportunity. We need to ensure we use

  for each section heading. Now we need to convert the content into HTML preserving details. We'll need to turn paragraphs into

  . Lists into

  • . The posting includes bullet points like "Own the Sales Process Manage qualified opportunities from discovery through close." Actually it's a heading then sentences. We'll need to parse. Let's extract sections: - About Our Client: paragraph(s) describing client. - The Opportunity: paragraph(s) describing opportunity. - What You'll Do: includes several bullet-like paragraphs each starting with a bold heading? Actually the text: "What You'll Do Own the Sales Process Manage qualified opportunities from discovery through close.Run thoughtful discovery conversations that uncover customer pain, goals, impact, urgency, budget, stakeholders, and decision criteria.Diagnose the underlying business problem before jumping into a product demonstration.Develop a clear understanding of each customer's buying process and approval requirements.Create and maintain strong next steps throughout the sales cycle. Deliver Consultative Product Demonstrations Lead clear, engaging demonstrations of a technical SaaS platform.Tailor demos to each customer's specific challenges, workflows, priorities, and level of sophistication.Translate technical functionality into accessible business language.Connect product capabilities directly to insights uncovered during discovery.Avoid generic feature tours by focusing demonstrations on the outcomes that matter most to each buyer. Sell Value & Create Urgency Translate product capabilities into customer-specific business value.Help prospects understand why they should change, why now, and why our client's solution.Quantify customer pain and potential impact where possible.Create urgency through business value rather than relying on discounting or pressure tactics.Build credibility and trust with prospects who may not already be familiar with the company or its solutions. Navigate Complex Buying Cycles Manage a range of opportunities, from faster transactional sales to longer, multi-stakeholder buying processes.Identify decision-makers, influencers, approvers, blockers, and executive sponsors early.Navigate opportunities that may involve executive leadership, boards, committees, or multiple functional stakeholders.Build clear close plans and maintain momentum throughout longer evaluation cycles.Adjust your communication and business case based on the complexity of the opportunity. Sell Across Multiple Solutions Learn a portfolio of SaaS solutions supporting nonprofit finance, fundraising, donor management, CRM, and digital giving.Understand which solution or workflow best addresses the customer's immediate needs.Identify opportunities where customers may benefit from multiple solutions.Position our client as a broader technology partner rather than focusing exclusively on an individual product.Engage multiple buyer personas across finance, development, fundraising, operations, and executive leadership. Own Your Pipeline & Forecast Maintain accurate opportunity stages, close dates, next steps, risks, and forecast categories.Surface deal risk early and adjust forecasts when new information emerges.Maintain clear customer actions and next steps throughout the sales process.Take ownership of conversion and revenue outcomes, not simply sales activity.Operate with strong pipeline discipline and accountability. Leverage AI & Modern Sales Technology Use AI and automation as part of your daily sales workflow.Leverage technology to improve account research, call preparation, follow-up, discovery planning, deal strategy, and productivity.Use CRM, sales engagement, and conversation intelligence tools to improve execution.Incorporate coaching and feedback quickly into future calls and opportunities." Thus it's a series of headings (Own the Sales Process, Deliver Consultative Product Demonstrations, Sell Value & Create Urgency, Navigate Complex Buying Cycles, Sell Across Multiple Solutions, Own Your Pipeline & Forecast, Leverage AI & Modern Sales Technology) each followed by sentences. We need to represent these as maybe

    ? But instruction only says use

    for section headings. It didn't forbid other headings, but we could treat each of these as

    or we could make them within

    . However to preserve structure, we could make each heading as

    (though not specified). But maybe better to keep them as inside

    to avoid extra headings. The instruction only mandates use

    for section headings (like About the role etc). It doesn't say we cannot use other heading levels. Safer to use

    for subheadings. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies that the main sections should be h3. Subheadings could be h4 or strong. We'll use

    for subheadings inside What You'll Do. Similarly for What We're Looking For: list of bullet points each starting with bold? Actually it's a list of items separated by periods. We'll need to parse. What We're Looking For: "2–3+ years of quota-carrying closing experience, preferably within B2B SaaS.Proven experience owning a full-cycle or late-stage sales process.Strong consultative discovery skills with the ability to uncover pain, impact, urgency, stakeholders, and decision criteria.Ability to sell business value rather than relying primarily on product features.Experience delivering technical SaaS demonstrations and connecting functionality to customer outcomes.Experience managing opportunities involving multiple stakeholders and decision-makers.Strong business acumen and the ability to connect customer problems to measurable outcomes.Comfort selling to prospects who may not already have strong brand or product awareness.Strong pipeline management and forecasting discipline.High coachability and willingness to quickly incorporate feedback.Excellent written and verbal communication skills.Comfort working across multiple products, workflows, and buyer personas.Experience using CRM, sales engagement, call intelligence, and AI-enabled sales tools." Thus each item ends with a period. We'll make each as

    . Bonus Points: similar list. What Success Looks Like: includes a paragraph then bullet list after colon? Actually: "Success in this role goes beyond simply hitting activity metrics. You'll be expected to: Consistently own and achieve your revenue goals.Run high-quality discovery that uncovers meaningful customer challenges.Deliver tailored product demonstrations tied directly to business outcomes.Build strong business cases and create urgency without relying on discounting.Effectively navigate both straightforward and complex buying processes.Maintain accurate pipeline and forecasting discipline.Build credibility and trust with prospects regardless of existing brand awareness.Incorporate coaching quickly and continuously improve your sales approach.Use AI and modern sales technology to become a more efficient and effective seller." Thus after colon, items separated by periods. We'll make list. Why This Opportunity: paragraph(s). Now we need to ensure we don't miss any detail. Let's craft HTML. We'll start with a

    for metadata: "Location: Fully Remote | Compensation: $130K–$150K OTE | Comp Structure: 50/50 Base + Variable with Accelerators | Employment Type: Full-Time" Then sections. We'll need to escape any HTML special characters? Not needed. Let's write. We'll need to ensure proper nesting. We'll produce:

    Location: Fully Remote | Compensation: $130K–$150K OTE | Comp Structure: 50/50 Base + Variable with Accelerators | Employment Type: Full-Time

    About Our Client

    Our client is a growing B2B SaaS organization providing technology solutions that help nonprofit organizations manage critical finance, fundraising, donor management, CRM, and digital giving workflows. As the company continues to expand its product portfolio and evolve its go-to-market strategy, it is building a more consultative, value-driven sales organization focused on understanding customer challenges and connecting those challenges to meaningful business outcomes.

    The Opportunity

    This is an ideal opportunity for a SaaS seller who wants to move beyond transactional or demo-driven selling and develop into a highly consultative Account Executive. You'll own the sales process from qualified opportunity through close, working with prospects to uncover business challenges, demonstrate relevant solutions, build a compelling business case, and navigate the decision-making process. While this is not primarily a cold outbound or self-generated pipeline role, you'll need to be comfortable selling to prospects with varying levels of intent and brand awareness. Success requires creating credibility, uncovering problems, building urgency, and helping customers understand why making a change matters.

    What You'll Do

    Own