DirectJobHub
Jobs · Sales

Enterprise Account Executive - Florida

PagerDuty · United States · 2 days ago
RemoteRemoteSales$131k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: description of role, what they will do. The posting starts with "PagerDuty, Inc.... We are growing rapidly and hiring top talent... PagerDuty is seeking an Account Executive (AE) to join our high-performing, customer-focused team! As an Account Executive, you will drive growth and expansion within an established customer portfolio, combining strategic account management with consultative enterprise selling. You’ll partner with C-level executives and key stakeholders to deliver measurable outcomes through Operations Cloud conversions and multi-product adoption. This is an exciting opportunity to shape the customer’s journey, close high-value deals, and accelerate PagerDuty’s growth in the enterprise market. The ideal candidate is a relationship-driven sales professional who thrives in complex deal cycles, excels at executive engagement, and is passionate about delivering customer impact through innovative SaaS solutions." That's about the role. We'll put that in

About the role

with

paragraphs. - Responsibilities: list of key responsibilities bullet points. The posting has "Key Responsibilities" then bullet list lines. We'll capture each bullet as

  • . - Basic Qualifications: list of qualifications. Could be under Requirements or Qualifications. The posting has "Basic Qualifications" then bullet list. Also "Preferred Qualifications". We need to decide sections: Requirements, Qualifications, Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content accordingly. We have Basic Qualifications (8+ years experience, proven success managing quota, demonstrated experience selling to C-level, proficiency with Salesforce, Bachelor's degree). That's requirements/qualifications. Preferred Qualifications also. We could put Requirements heading for basic qualifications, and Qualifications heading for preferred? Or combine? The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Basic and Preferred under "Requirements" or "Qualifications". But we need to follow headings list; we can choose which to include. We have Pay: base salary range $131,000 - $170,500 USD, plus bonus, commission (50/50 split), benefits. So we can include Pay section. Benefits: The posting has "What We Offer" with list of benefits. That's substantive. So Benefits section. Schedule: Not explicitly mentioned; there is hybrid work model, offices list, location restrictions. That's about work location, not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting states it. It does not. So omit Schedule. Skills: Could be derived from qualifications but maybe not separate. We could include Skills if there is explicit skill list. Not really; we have proficiency with Salesforce, etc. Could go under Qualifications. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. We need to decide which heading to use for qualifications. The list includes Requirements, Qualifications, Skills. We could use "Requirements" for basic qualifications and "Qualifications" for preferred? But that may be thin. Better to combine into one section "Requirements" containing both basic and preferred qualifications. Or "Qualifications". The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require using all; we can pick those that have content. Thus we can have:

    About the role

    ...

    Responsibilities

      ...

    Requirements

      ...
    (including basic and preferred)

    Benefits

      ...

    Pay

    ...

    We must not include fluff like "commensurate with experience". The posting includes base salary range; we include that. We need to preserve all substantive info: include details about hybrid work model, offices list, location restrictions? That's under "Where we work". That is substantive but not covered by headings. Should we include it? Possibly under a section like "Work Location" but not in allowed headings. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also add other headings if needed? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings. So we cannot add a "Work Location" heading. Where to put location info? Could be folded into About the role or Benefits? Probably not. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Location info is not boilerplate; it's substantive. But we have no heading for it. Perhaps we can include it under About the role as a paragraph? The About the role section could include info about hybrid work model and offices. That seems plausible. Thus we will incorporate location/hybrid work info into About the role paragraph. Now let's extract content precisely. About the role: The paragraph after "PagerDuty is seeking an Account Executive (AE) to join our high-performing, customer-focused team!" includes description. Also later there is "We are growing rapidly and hiring top talent with leading AI skills across engineering, sales, product, marketing, and beyond as we build the leading digital operations platform." That's also about company but could be part of About the role. Also "Where we work" paragraph: "PagerDuty operates a hybrid work model with offices in 8 major cities: Atlanta, Lisbon, London, San Francisco, Santiago, Sydney, Tokyo, and Toronto. While we offer flexibility within our established locations, we cannot employ candidates residing in: Location restrictions: ..." That's location restrictions. We'll include that in About the role as well. We must not include the list of location restrictions? It's substantive; we should keep it. It's not boilerplate. So include. Now Responsibilities: bullet list under "Key Responsibilities". Let's capture each: - Own and grow a defined set of enterprise accounts by driving upsell, cross-sell, and expansion opportunities. - Build and maintain trusted executive relationships through regular in-person engagement and consultative selling. - Develop and execute strategic account plans to identify growth areas, expansion pathways, and competitive positioning. - Drive adoption of PagerDuty’s Operations Cloud by articulating clear business value and ROI. - Execute complex, multi-product sales motions and partner with Solution Consultants for technical validation and proof-of-concept activities. - Maintain accurate forecasts and a disciplined pipeline in Salesforce using the MEDDICC framework. - Collaborate with Customer Success, Product Management, and Renewals teams to ensure customer satisfaction and long-term retention. Now Requirements: combine Basic Qualifications and Preferred Qualifications. Basic Qualifications bullets: - 8+ years of experience in B2B sales, account management, or expansion roles within SaaS or cloud software. - Proven success managing a quota in complex, long-cycle enterprise sales. - Demonstrated experience selling to and influencing C-level executives. - Proficiency with Salesforce (SFDC) for pipeline management and forecasting. - Bachelor’s degree or equivalent experience. Preferred Qualifications bullets: - Prior enterprise sales expertise leveraging MEDDPICC & Value Selling - Experience managing high-value accounts - Track record of success with multi-product sales and solution-based selling models. - Strong understanding of enterprise software ecosystems, Operations Cloud, or DevOps environments. - Strategic thinker with exceptional communication, negotiation, and relationship-building skills. We'll combine into one list under Requirements. Now Benefits: Under "What We Offer". The list: - Competitive salary - Comprehensive benefits package - Flexible work arrangements - Company equity* - ESPP (Employee Stock Purchase Program)* - Retirement or pension plan* - Generous paid vacation time - Paid holidays and sick leave - Dutonian Wellness Days & Hibernation - Duty - companywide paid days off in addition to PTO - Paid parental leave: 22 weeks for pregnant parent, 12 weeks for non-pregnant parent (some countries have longer leave standards and we comply with local laws)* - Paid volunteer time off: 20 hours per year - Company-wide hack weeks - Mental wellness programs - Eligibility may vary by role, region, and tenure We need to preserve all substantive info. The asterisks maybe indicate notes; we keep them as part of text. Now Pay: The base salary range paragraph: "The base salary range for this position is $131,000.00 - $170,500.00 USD. This role may also be eligible for bonus, commission (50/50 split), and/or benefits. Our base salary ranges are determined by role, level, and location. The range, which is subject to change based on primary work location, reflects the minimum and maximum base salary we expect to pay newly hired employees for the position. Within the range, we determine pay for an individual based on a number of factors including market location, job-related knowledge, skills/competencies and experience. Your recruiter can share more about the specific offerings for this role, as well as the salary range for your primary work location during the hiring process." We should keep that as a paragraph under Pay. Now we must not include boilerplate like "Hesitant to apply? We encourage you to submit your resume even if you don't meet every requirement..." That's application encouragement; maybe considered boilerplate? It's not legal/EEO but it's encouraging to apply. The instruction says remove application instructions. This is more like encouragement; could be considered application instruction? It's not exactly instruction to apply but encouraging. Safer to remove it. Also remove "If this just isn’t the right role or time - sign up for job alerts!" That's also application instruction. Remove. Also remove "About PagerDuty" duplicate description; that's boilerplate? It's about company but repeated; we already have some company info in About the role. Might be considered duplicate. We'll remove the later "About PagerDuty" paragraph that repeats. Also remove "PagerDuty is Great Place to Work-certified™..." etc. That's boilerplate/legal? It's about awards; could be considered boilerplate but maybe substantive? It's not required; but we can keep if we want but it's not under any heading. Since we only have allowed headings, we could fold into About the role? It's about company accolades; could be included. But the instruction says remove duplicated lines. This is not duplicated elsewhere but it's about company. Might be considered not essential to role. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Awards are not those categories. Could keep. But we have limited sections; we could add to About the role. But we must not invent or summarize away detail. If we keep it, we need to include it somewhere. Could add a paragraph after the role description. Let's include it in About

    • Similar jobs