Account Executive - Enterprise - US

We need to output HTML fragment with sections: About the role? Actually the posting includes "A bit About Flosum" and "A bit About You". Those are about company and candidate. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly. We have sections: About Flosum (company description) could be "About the role"? Actually "About the role" is typical but we have company description. Could treat as "About the role" maybe not. But we can create sections: "About Flosum" maybe not in list but we can still use heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. We should include sections only when posting has real specific content. We have content for: About Flosum, About You (candidate profile), Within 1 Month, Within 3 Months, Within 6 Months, Within 12 Months (these could be under "Responsibilities" or "Expectations"? Might be better as "Responsibilities" or "Expectations". But we have explicit responsibilities list later: "In the role as an Enterprise Account Executive, you will:" then bullet list of duties. That's responsibilities. We also have Requirements section: list of requirements. We have Benefits section: list. We have no explicit Pay or Schedule info, so we should not create those sections. We need to avoid boilerplate like EEO etc. The posting includes "Join Us at Flosum ..." which includes benefits and some fluff. We'll keep benefits. We need to preserve all substantive information, not invent. We need to use

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

  for prose. We need to not repeat job title as heading (page already shows it). No Job ID. We need to output only HTML fragment. Let's structure:

  About Flosum

  maybe not standard but okay. Could use

  About the role

  and put Flosum description there. But "About the role" usually describes role, not company. However we have "A bit About Flosum" and "A bit About You". Could combine into "About the role" and "About you"? Might be confusing. Better to follow instruction: use headings from list when applicable. We have sections: Responsibilities, Requirements, Qualifications (maybe same as Requirements), Skills, Benefits. We have no explicit Qualifications separate from Requirements. We have "Requirements" section with bullet list. We have "Bonus Points for:" which could be considered Qualifications or Skills. We'll treat as "Qualifications" maybe. We have "Within 1 Month..." etc. Those are expectations/timeline; could be placed under "Responsibilities" as prose? Or we could create a section "Expectations" but not in list. Might be better to incorporate them into responsibilities as prose paragraphs. But we need to preserve all info. We could create a section "Onboarding & Milestones" but not in list. However instruction says prefer a few substantive sections over many thin ones. Could combine timeline into responsibilities. Let's decide sections: - About Flosum (company overview) maybe as

  About Flosum

  (though not in list but acceptable). Could also be

  About the role

  with company description. - About You (candidate profile) maybe as

  About the ideal candidate

  but not in list. But maybe we should stick to the given headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We can map: About the role: combine Flosum description and candidate profile? Might be too mixed. Better: Use About the role for Flosum description; Responsibilities for duties list; Requirements for mandatory requirements; Qualifications for bonus points/preferred; Skills maybe not needed; Benefits for benefits. We have no explicit Skills list; we could omit. Let's extract content: Flosum description: "A bit About Flosum: Flosum occupies the vanguard of technological innovation within the Salesforce DevOps arena, proffering a comprehensive solution that seamlessly integrates merge tools, version control, continuous deployment, and meticulous code analysis. In addition, Flosum boasts Enterprise-grade Disaster Recovery Solutions, complemented by a game-changing Cybersecurity framework meticulously tailored for Salesforce Programs. This framework has been astutely harnessed to amplify the DevSecOps paradigm in collaboration with our esteemed Partners. Our well curated suite of products harmonizes seamlessly within the expansive Salesforce ecosystem, catering to the needs of Developers, Administrators, Architects, and Chief Information Officers. If the notion of contributing to a progressive enterprise equipped with proven offerings within a rapidly evolving market beckons you, this extraordinary opportunity awaits your consideration" Candidate profile: "A bit About You: You're a dynamic, results-driven individual with a fervor for technical sales and an innate grasp of SaaS Customer Account Management. You have experience selling to technical buyers and working with resellers, VAR's, and channel partners. You're an ambitious Account Executive with a proven track record over 5+ years growing revenue within Enterprise customer accounts with a customer-centric approach. You thrive working remotely, cherish structured routines, and exemplify a professional demeanor. You are highly organized and thrive in a high-velocity environment that, although reasonable and respectful, often has ambiguities and competing prioritiesYou are internally driven by curiosity and continuous learning. You have proven that you can be entrusted with big decisions, and you strive to bring thoughtfulness and empathy to all of your workYou are humble, and collaborate well with other people. You thrive working within a team, and exhibit excellent communication and interpersonal skillsYou are self-motivated, reliable, and can function effectively in a distributed teamAvailable to travel up to 25%Multilingual proficiency to elevate global engagement is a distinct advantage. Bonus Points for: Certified Sales Certifications & demonstrated ability to consistently achieve $1mm+ quotas. Expertise in Salesforce platform support, development or CyberSecurityBackground in project or product management. Experience in process design and documentation. Prior exposure to DevOps solutions" Note: The "Bonus Points for:" appears within candidate profile but also separate. We'll treat as Qualifications. Then timeline sections: Within 1 Month, Within 3 Months, Within 6 Months, Within 12 Months. We'll incorporate into Responsibilities as prose paragraphs maybe under a heading "Expectations". But we could create a section "Onboarding & Milestones" but not in list. Might be okay to add a heading not in list? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We could put timeline under Responsibilities as prose paragraphs. Responsibilities list: after "In the role as an Enterprise Account Executive, you will:" then bullet list of duties. We'll capture those as

  • . We also have some prose before that list: "Build relationships with prospective enterprise-level clients" etc actually that's part of the bullet list? The text shows: "In the role as an Enterprise Account Executive, you will: Build relationships with prospective enterprise-level clientsLeverage the following strategic sales motions: Strategic Account Planning Account Based Sales (ABM)Tailored Sales Automation Drip Campaigns (Salesloft / Outreach.io) Embrace Enterprise GAP / Value / Solution Sales Methodologies Execute Upsell / Cross-Sell / Nurture / GTM / Awareness Sales CampaignsConstruct and Deliver Interactive Growth Presentations and Proposals Deliver exceptional Customer Experiences with new clients, ensuring their triumphant onboarding. Engage stakeholders proactively, addressing strategic, technical, and soft skill aspectsSustain value through structured cadences, encompassing business, process, onboarding, and technical discussions, alongside webinars and other communications. Convey the value of our products through innovative approaches. Drive the adoption of novel features and enhancements, perpetuating growth. Conduct Quarterly Business Reviews and interactions grounded in value with clients. Oversee the complete customer lifecycle, including escalations and touchpoints. Amass insights and recommendations from clients to inform product refinement. Exemplify thought leadership and orchestrate customer advocacy. Create client-facing materials, including support articles, FAQs, release notes, and contribute to customer / GTM webinars. Rigorously document and classify client interactions for valuable insights." This is a long sentence with no clear bullet separation. We need to split into list items logically. Could treat each sentence as a bullet. Let's parse: - Build relationships with prospective enterprise-level clients - Leverage the following strategic sales motions: Strategic Account Planning, Account Based Sales (ABM), Tailored Sales Automation Drip Campaigns (Salesloft / Outreach.io) - Embrace Enterprise GAP / Value / Solution Sales Methodologies - Execute Upsell / Cross-Sell / Nurture / GTM / Awareness Sales Campaigns - Construct and Deliver Interactive Growth Presentations and Proposals - Deliver exceptional Customer Experiences with new clients, ensuring their triumphant onboarding. - Engage stakeholders proactively, addressing strategic, technical, and soft skill aspects - Sustain value through structured cadences, encompassing business, process, onboarding, and technical discussions, alongside webinars and other communications. - Convey the value of our products through innovative approaches. - Drive the adoption of novel features and enhancements, perpetuating growth. - Conduct Quarterly Business Reviews and interactions grounded in value with clients. - Oversee the complete customer lifecycle, including escalations and touchpoints. - Amass insights and recommendations from clients to inform product refinement. - Exemplify thought leadership and orchestrate customer advocacy. - Create client-facing materials, including support articles, FAQs, release notes, and contribute to customer / GTM webinars. - Rigorously document and classify client interactions for valuable insights. That seems fine. Now Requirements: The section "Requirements In the role as an Enterprise Account Executive, you will:" Actually that's responsibilities. Wait the text: "Requirements In the role as an Enterprise Account Executive, you will:" seems misplaced; maybe they meant "Responsibilities". But after that they list duties. Then later there is a separate "Requirements" heading? Actually after the duties list, we see "Benefits Join Us at Flosum". There's no explicit "Requirements" heading besides the earlier "Requirements In the role..." which is likely a mistake. However earlier we have "Bonus Points for:" etc. The posting includes a "Requirements" section? Let's scan: After candidate profile, we have timeline, then "Requirements In the role as an Enterprise Account Executive, you will:" then duties. So the word "Requirements" appears incorrectly; but we should treat that as responsibilities. There's no separate explicit requirements list besides the candidate profile (which is more about ideal candidate). However we have "Bonus Points for:" which could be considered qualifications. Thus we may not have a distinct Requirements section beyond the candidate profile. But we need to include a Requirements section if there is real specific content. The candidate profile includes requirements (experience, skills). We could treat that as Requirements. Thus: - About Flosum (company description) -> maybe

    About Flosum

    or

    About the role

    with that content. - About You (candidate profile) -> maybe

    About the ideal candidate

    but not in list. Could treat as

    Requirements

    with that content. - Responsibilities: duties list. - Qualifications: Bonus Points for etc. - Benefits: list. We need to avoid creating sections with filler. Ensure each heading has substantive content. Let's craft HTML:

    About Flosum