Enterprise Account Executive

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. We need to parse the posting. First, we have "About Pantheon" description: that's company overview, not needed as a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections like About the role (maybe summarizing role description), Responsibilities (list of duties), Requirements (maybe experience needed), Qualifications (maybe similar), Skills (maybe specific abilities), Benefits (list), Pay (OTE), Schedule (maybe travel %). We must not repeat job title as heading. Also we should not include boilerplate like EEO, visa, etc. We need to preserve all substantive information, not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Posting sections: - About Pantheon (company description) – maybe not needed as a heading; but could be part of "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities...). So we likely need an "About the role" section that includes description of the role. The "About Pantheon" is company overview; maybe we can incorporate into About the role? But we should not invent content. However we can include company overview as part of About the role? 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 have a short paragraph about the role, maybe using the "The Role" paragraph. Thus:

About the role

Pantheon is seeking a driven, results-oriented Enterprise (CORE) Account Executive to focus on acquiring new business and driving revenue growth. This is a hunter role with a focus on net-new business, targeting mid-market accounts. As a critical member of our sales team, you'll develop and execute a strategic sales plan to close deals, build strong client relationships, and contribute to Pantheon's success.

That seems good. Next responsibilities: The "What you Need to Succeed" bullet list. Those are responsibilities/duties. So we can put under

Responsibilities

a

with each bullet. List items: - Drive net new business by generating a pipeline through outbound prospecting, partner collaboration, and strategic territory management. - Lead discovery calls and navigate technical sales conversations with CTOs, CIOs, CMOs, Directors, VPs, and other executive-level stakeholders, including technical and marketing buyers. - Deliver compelling value propositions, leveraging a methodology like Force Management's Command of Message. - Effectively qualify opportunities using frameworks like MEDDIC. - Own and exceed your annual quota by closing deals while identifying new opportunities. - Manage the entire sales process from lead generation to close, maintaining a focus on speed-to-value and customer success. - Maintain a disciplined approach to pipeline management and forecasting to ensure consistent revenue achievement. - Collaborate cross-functionally with Sales Development, Sales Engineering, Professional Services, and Customer Success to ensure a seamless and effective buyer's journey. Make sure we keep all details. Next "What you Bring to the Table" includes experience requirements, qualifications, skills. We need to split into Requirements, Qualifications, Skills perhaps. The instruction: prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have content for Requirements (experience), Qualifications (maybe methodologies), Skills (communication, etc). Could combine some. Let's decide: - Requirements: 7-10 years of experience in technical or MarTech SaaS sales, with a strong focus on outbound efforts and net new business acquisition. Comfortable selling to a developer persona. Willingness to travel approximately 20-30% of the time. - Qualifications: Experience with established sales methodologies like Force Management's Command of the Message or Winning by Design's SPICED. Familiarity with qualification frameworks like MEDDIC or SPICED. Proven ability to generate your pipeline through outbound calling, prospecting, and identifying top targets. Demonstrated success in closing deals consistently and achieving or exceeding quota. Resourceful, scrappy mindset, able to build pipeline and opportunities without heavy lead support or brand recognition. Strong ability to ramp quickly and adapt to a technical sale, often starting with technical stakeholders. - Skills: Exceptional communication, negotiation, and relationship-building skills. Polished, professional demeanor with the ability to engage effectively at all organizational levels. Familiarity with open-source technology is a significant advantage. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now Benefits: "What We Offer" paragraph includes list of benefits. We'll create

Benefits

with
. List: - Industry competitive compensation and equity plan - Flexible time off, sick days, and 13 paid holidays - Comprehensive medical insurance including Health, Dental and Vision - Paid parental leave (plus fertility, adoption and other family planning benefits) - In-office workspace (San Francisco & Chicago) - Monthly allowance for wellness, reading and access to LinkedIn Learning for continued development - Events and activities both team-based and company wide that inspire, educate and cultivate We should not include the fluff sentence "We have all the usual perks and benefits but what we can really offer you is a fantastic work environment powered by an amazing team." That's somewhat generic but still substantive? It's not a specific benefit; maybe we can include as a

before the list? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence as well. Could be a

before the list. Thus Benefits section:

We have all the usual perks and benefits but what we can really offer you is a fantastic work environment powered by an amazing team.

then
list. Pay: The OTE info: "The on-target earnings (OTE) for this position are: US: $246,200–$300,000 OTE, with a 50/50 base-to-variable compensation split Final compensation will be determined based on factors including role scope, relevant experience, and geographic location." We'll put under

Pay

a

with that. Schedule: Travel % maybe considered schedule. The posting mentions "Willingness to travel approximately 20-30% of the time". That's schedule/travel. So we can have

Schedule

Willingness to travel approximately 20-30% of the time.

We should not include sections like "About Pantheon" as heading; we could incorporate company overview into About the role? But we already have About the role with role description. Could also add a short paragraph about Pantheon as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." Might be okay to keep About the role as just role description; company overview could be omitted? But we must preserve ALL substantive information. The company overview is substantive; if we omit it, we lose info. Where to put it? Could add a

before About the role? But we cannot add extra headings not allowed? We could add a

before the first heading describing Pantheon. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside headings. So we can include a

about Pantheon before the first heading. Thus structure:

Pantheon WebOps Platform powers the open web, running more than 300,000 sites in the cloud for customers including Google, Princeton, Salesloft, and Doctors Without Borders. Every day, thousands of developers and marketers create, iterate, and scale WordPress and Drupal sites to reach billions of people globally. Pantheon's multitenant, container-based platform enables organizations to manage all of their websites from a single dashboard. Organizations, including Clorox and the United Nations, drive results through accelerated development and real-time publishing using Pantheon's collaborative workflows.

Then

About the role

etc. Now ensure we don't repeat job title. Not included. Check for duplicated lines: we have not duplicated. Check for boilerplate: we removed EEO, visa, etc. Now produce HTML. Let's craft. Be careful with proper escaping of apostrophes etc. Use straight quotes. We'll output:

Pantheon WebOps Platform powers the open web, running more than 300,000 sites in the cloud for customers including Google, Princeton, Salesloft, and Doctors Without Borders. Every day, thousands of developers and marketers create, iterate, and scale WordPress and Drupal sites to reach billions of people globally. Pantheon's multitenant, container-based platform enables organizations to manage all of their websites from a single dashboard. Organizations, including Clorox and the United Nations, drive results through accelerated development and real-time publishing using Pantheon's collaborative workflows.

About the role

Pantheon is seeking a driven, results-oriented Enterprise (CORE) Account Executive to focus on acquiring new business and driving revenue growth. This is a hunter role with a focus on net-new business, targeting mid-market accounts. As a critical member of our sales team, you'll develop and execute a strategic sales plan to close deals, build strong client relationships, and contribute to Pantheon's success.

Responsibilities

• Drive net new business by generating a pipeline through outbound prospecting, partner collaboration, and strategic territory management.
• Lead discovery calls and navigate technical sales conversations with CTOs, CIOs, CMOs, Directors, VPs, and other executive-level stakeholders, including technical and marketing buyers.
• Deliver compelling value propositions, leveraging a methodology like Force Management's Command of Message.
• Effectively qualify opportunities using frameworks like MEDDIC.
• Own and exceed your annual quota by closing deals while identifying new opportunities.
• Manage the entire sales process from lead generation to close, maintaining a focus on speed-to-value and customer success.
• Maintain a disciplined approach to pipeline management and forecasting to ensure consistent revenue achievement.
• Collaborate cross-functionally with Sales Development, Sales Engineering, Professional Services, and Customer Success to ensure a seamless and effective buyer's journey.

Requirements

• 7-10 years of experience in technical or MarTech SaaS sales, with a strong focus on outbound efforts and net new business acquisition.
• Comfortable selling to a developer persona.
• Willingness to travel approximately 20-30% of the time.

Qualifications

• Experience with established sales methodologies like Force Management's Command of the Message or Winning by Design's SPICED.
• Familiarity with qualification frameworks like MEDDIC or SPICED.
• Proven ability to generate your pipeline through outbound calling, prospecting, and identifying top targets.
• Demonstrated success in closing deals consistently and achieving or exceeding quota.
• Resourceful, scrappy mindset, able to build pipeline and opportunities without heavy lead support or brand recognition.
• Strong ability to ramp quickly and