Mid-Market Account Executive - Central

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 that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to parse the posting. Let's extract sections: - About Anaconda (company description) maybe "About the role"? Actually the posting starts with "About Anaconda". Then "Summary". Then "What You'll Do". Then "What 'Mid-Market' means at Anaconda". Then "What You Need". Then "What Will Make You Stand Out". Then "Why you'll like working here". Then salary info and deadline. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections correspond. - About the role: could be the summary and description of role (maybe "Summary" and "What You'll Do"). - Responsibilities: could be "What You'll Do" bullet list. - Requirements: could be "What You Need". - Qualifications: maybe "What Will Make You Stand Out" (preferred qualifications). Or could be separate. - Skills: maybe not explicit; could be derived from requirements. - Benefits: we have "Why you'll like working here" includes flexible hours, fully remote, culture, etc. Also salary info includes equity + benefits. So we can have Benefits section. - Pay: we have salary range $100,000-$135,000 + variable commission + equity + benefits. So Pay section. - Schedule: maybe not explicit; but we have flexible hours, fully remote. Could be schedule? Not explicit schedule like full-time, etc. The posting does not mention schedule specifics. So we should not create Schedule section unless there is real specific content. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Schedule, we have "flexible hours" and "fully remote setup". That could be considered schedule info. But is that specific enough? It says flexible hours, fully remote. That is schedule-related. Might be okay to include Schedule section with that content. However we need to see if we should include Schedule heading only if posting has real specific content for it. It does mention flexible hours and fully remote. That's schedule. So we can include Schedule. But we also have Benefits: "flexible hours, a fully remote setup, and a genuine commitment to your wellbeing and growth." Also earlier: "+ equity + benefits." So we can include Benefits. Pay: salary range. Now we need to avoid duplication and boilerplate. Remove application deadline line? The instruction: remove application instructions. The deadline is part of application instructions? It says "The application deadline for this role is 11/16/2026 applicants will be reviewed on an ongoing basis until the role is filled." That's application instruction; we should remove it. Also remove "Learn more at https://www.anaconda.com." maybe considered boilerplate? It's a link but not navigation/legal/EEO. Might be okay to keep? It's not required but could be considered company info. Might keep as part of About Anaconda? But we are not including About Anaconda as a heading; we could incorporate into About the role summary. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description? It's substantive about Anaconda. But we don't have a heading for company description; we could put it under About the role as a paragraph. That seems fine. We must not repeat job title as heading. The job title is Mid-Market Account Executive. Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

...

Then maybe

Responsibilities

with

• ...

Then

Requirements

with

• ...

Then

Qualifications

(preferred) with

• ...

Then

Skills

maybe not needed if covered; but we could combine skills into Requirements. The instruction: prefer a few substantive sections over many thin ones. So maybe we skip Skills if not distinct. Then

Benefits

with

• ...

Then

Pay

with

...

Then

Schedule

with

...

We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract content. Company description (About Anaconda): "Anaconda is built to advance AI with open source at scale, giving builders and organizations the confidence to increase productivity, and save time, spend and risk associated with open source. 95% of the Fortune 500 including Panasonic, AmTrust, Booz Allen Hamilton and over 50 million users rely on the value The Anaconda AI Platform delivers through a centralized approach to sourcing, securing, building, and deploying AI. With 21 billion downloads and growing, Anaconda has established itself as the gold standard for Python, data science, and AI and the enterprise-ready solution of choice for AI innovation. Anaconda is backed by world-class investors including Insight Partners. Learn more at https://www.anaconda.com." We can keep that as a paragraph under About the role. Summary: "We're looking for a driven Mid-Market Account Executive to join Anaconda's Sales team and build a strong pipeline across mid-market organizations. At Anaconda, we're transforming how enterprises harness open-source AI and data science to accelerate innovation. Our Sales team works with organizations already using open-source Python and AI to help them move from free adoption to governed, scalable solutions that drive business outcomes. In this role, you'll own the full sales cycle for mid-market opportunities, building relationships with both technical and business stakeholders. You'll partner closely with Sales Engineering, Customer Success, and Product to deliver real value at every stage. We value sellers who are curious first—understanding each customer's unique challenges before recommending solutions—collaborative in their approach, accountable for results, and courageous enough to think differently about how AI and open-source create competitive advantage." We can incorporate that into About the role paragraph as well, maybe after company description. But we need to avoid duplication. The summary repeats some of the responsibilities. We'll combine. Responsibilities: "What You'll Do" bullet list: - Build and manage a strong pipeline of net-new opportunities within your territory, combining warm leads from existing users with proactive outbound - Lead discovery conversations that uncover business value—productivity gains, cost reduction, risk mitigation—translating technical capabilities into outcomes that matter to customers - Navigate buying committees and multi-threaded deals with developers, platform teams, security, and procurement, adapting your communication style for each stakeholder - Leverage AI tools daily across the sales cycle for account planning and outreach, call summaries, and AI-synthesized Salesforce data for pipeline reviews - Support technical validation by coordinating with Sales Engineering on POCs and demos, ensuring customers understand how Anaconda's platform solves their specific problems - Own deals from first conversation through close, maintaining accurate forecasting and staying focused on velocity and deal progression - Partner cross-functionally with Customer Success and Product to identify expansion opportunities and ensure smooth handoff post-close - Your impact will be measured through Net-new pipeline created and ARR sourced within your territory - Win rate and deal velocity on qualified mid-market opportunities - Forecast accuracy and consistency in deal execution - Customer satisfaction and successful onboarding of new accounts We need to keep each as

. Now "What 'Mid-Market' means at Anaconda": This is description of the market. Could be part of Responsibilities or maybe a separate section like "About the role". Might be considered part of role description. We'll incorporate into About the role paragraph. Now Requirements: "What You Need": - 3+ years of B2B SaaS sales experience, with demonstrated success closing mid-market deals - Proven ability to sell to technical buyers—developers, data engineers, platform teams—and translate their technical needs into business outcomes - Experience navigating complex buying processes and working comfortably with multiple stakeholders across an organization - Actively uses AI tools for account research, outreach personalization, and deal prep. Not occasionally, but as a standard part of how you work. - A working knowledge of how developers think and operate (SDLC, cloud infrastructure, open-source ecosystems) without needing to code yourself - Comfort with ambiguity and strong pipeline creation skills—you proactively build your own opportunities, not just working inbound leads - Alignment with Anaconda's values: Curious by Default, Build Together, Own It, and Lead with Guts and Heart - Ability to work in CST time zone Now Qualifications (preferred): "What Will Make You Stand Out": - Experience selling developer tools, data platforms, AI infrastructure, or open-source-adjacent products - Experience working within structured AI workflows for territory management, such as maintaining account context in Claude Projects and building reusable prompt templates for pipeline reviews - Comfortable using Granola or Zoom AI to extract next steps and CRM updates from recorded calls - Time spent in a high-growth startup or scaling environment where you built your own playbook - Demonstrated success with land-and-expand strategies or growing existing accounts through proactive outreach - Familiarity with modern enterprise sales frameworks (MEDDPICC, Challenger, etc.) - A track record of consistently hitting quota or exceeding targets - Experience building credibility with engineering teams based on genuine knowledge and curiosity, not just relationships or brand recognition - You embody our values—"Curious by Default", "Build Together", "Own It", and "Lead with Guts and Heart"—and our behaviors: Clarity, Care and Candor - You care deeply about fostering an environment where people of all backgrounds and experiences can flourish Now Benefits: "Why you'll like working here": - You'll thrive in a high-performance environment where results are recognized and rewarded - Your work directly contributes to shaping the future of data science, machine learning, and AI in the enterprise. - You'll work alongside a collaborative team that values diverse, thoughtful discussion, clarity and candor. - You'll be supported by a culture that puts employees first - with flexible hours, a fully remote setup, and a genuine commitment to your wellbeing and growth. Also earlier: "+ equity + benefits." but we already have benefits. Now Pay: "The US base salary range for this role is $100,000-$135,000 + variable commission structure based on sales performance + equity + benefits. Our salary ranges are determined by role, level, and location. Within the range, individual compensation is determined by various factors, including work location, job-related skills, experience, and relevant education or training. Your recruiter will provide more specific details on the salary range for your preferred location during the hiring process." We should keep that as paragraph. Now Schedule: we have flexible hours, fully remote setup. Could be schedule. We'll put that as paragraph. Now we must remove application deadline line and maybe "Learn more at https://www.anaconda.com."? It's not boilerplate but could be considered navigation? It's a link to learn more; might be considered external reference. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not navigation per se (like site navigation). It's a reference to learn more about company. Might be okay to keep. But we could also drop it