Senior Director, Solutions Consulting
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. Let's extract.
Job title: Senior Director, Solutions Consulting (but we don't repeat as heading). We'll have About the role: maybe a paragraph summarizing role purpose.
From posting:
"Why We Need You Solution Consulting (Presales) is a critical part of the sales engine at PagerDuty - driving revenue and successful customers. As we continue to scale, the North America Solution Consulting leader will help raise the bar on our execution as a sales team, adapting to new product go to market motions, providing technical expertise to impact net revenue retention and expansion, and bringing creative ideas to improve our effectiveness and efficiency."
That's about role.
"How You Contribute to Our Vision You define the vision for our North America Solution Consulting & Value Engineering organization – spanning solutions architects, demo engineers, and value engineers across Strategic, Enterprise, Commercial, and Architecture segments – building on our strengths and setting us up for accelerated growth well into the future. You represent the Customer Engineering team, partnering with key executives across Sales, Product, and Customer Revenue leadership to help drive product direction, customer success, net revenue retention, and sales results. Collaborating with regional Solutions Consulting peers and team, you build scalable systems and playbooks – establishing a Global Center of Excellence that codifies demo engineering standards, POC/POV methodology, and repeatable customer engagement frameworks adopted across the entire field organization. You hire outstanding people who will help us execute where we are today and lead us well into the future You inspire your team to bring their best every day, providing coaching and mentorship to support their career development. Partnering with our sales and customer success leaders, you constantly challenge the way things are done, looking for creative solutions to optimize for both effectiveness and efficiency. You have a great handle on the business. You know the deals in flight, where there’s risk and opportunity in the deals and you actively sell. You prioritize to ensure we’re focusing our limited bandwidth and resources on what will make the biggest difference. You manage our most expensive activities, Proofs of Value (POVs), closely with a focus on setting them up for success and communicating the value proven. You design reference architecture programs and POC infrastructure for strategic and named account pursuits, and serve as executive technical sponsor in competitive evaluations for our highest-value enterprise deals. You own the full customer journey – partnering with Customer Revenue leadership to protect and grow net revenue retention, surface expansion opportunities, and drive executive-level QBRs and business reviews well past the point of sale. You bring an innovation mindset – as a curious and critical-thinker, you will lead the team in developing AI-powered tools and automation that scale repeatable technical sales motions, improve team productivity, and drive down operating costs."
That's responsibilities.
"Basic Qualifications Experience: 10+ years of progressive growth in technical sales roles with at least 3 years in a senior-level people management role. Strategic Leadership: Proven track record of successfully partnering with sales leadership to drive revenue generation across a wide range of customers and their technologies. Technical Proficiency: Previous experience with SaaS and Cloud technologies as well as selling into technology organizations (IT Operations, Engineering, and/or office of the CTO). Working knowledge of cloud infrastructure (AWS, Azure, or GCP), modern DevOps/SRE workflows, APIs and system integrations, and observability or incident management tooling, Problem Solver: Exceptional analytical skills and the ability to use rigorous logic to solve complex problems in a fast-moving, sometimes ambiguous environment. Communication: Excellent written and oral communication skills with the ability to represent a complex organization at the senior executive level and speak credibly to technical architecture in front of engineering and IT audiences. Metrics Driven: Track record of managing key SC leadership metrics, including SC-influenced win rate, POV-to-close conversion rate, net new ARR and net revenue retention (NRR) influenced by the Customer Success organization."
That's qualifications/requirements.
"Preferred Experience Industry Experience: Experience selling into or supporting ITSM, Observability, or Incident Management technology categories. Sales Methodology: Familiarity with MEDDPICC or similar value-selling and qualification frameworks. Global Team Leadership: Experience building and leading globally distributed technical sales teams across multiple go-to-market segments. Executive Presence: Comfortable presenting to and influencing C-level stakeholders in both customer and internal settings."
That's preferred experience, could be Skills or Qualifications.
We need to separate Requirements vs Qualifications vs Skills. The instruction: use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
Typically: Requirements = basic qualifications (must have). Qualifications = maybe preferred? Skills = specific skills. But we can map as we see fit, as long as we include all substantive info.
We must not create sections with filler. So we need to ensure each section has real content.
Let's assign:
- About the role: short paragraph summarizing role purpose (the "Why We Need You" paragraph).
- Responsibilities: the "How You Contribute to Our Vision" paragraph (multiple sentences). Could be broken into bullet list? It's prose; we can keep as
.
- Requirements: Basic Qualifications list (the bullet points). We'll make
- for each.
- Qualifications: Preferred Experience list (the bullet points). Could be considered qualifications.
- Skills: maybe we can extract specific skills from the requirements: cloud infrastructure, DevOps/SRE, APIs, observability, incident management, analytical, communication, metrics-driven, etc. But we already have those in Requirements. To avoid duplication, maybe we put Skills as a separate list of technical and soft skills: e.g., "SaaS and Cloud technologies, AWS/Azure/GCP, DevOps/SRE, APIs, system integrations, observability/incident management, analytical, communication, MEDDPICC, etc." But we risk duplicating. However instruction says preserve ALL substantive information; we can keep them in Requirements and Qualifications; Skills could be omitted if no distinct content. But we must include a section only when posting has real specific content for it. If we don't have distinct skills beyond those already captured, we could omit Skills section. However we might still include Skills if we can extract from the text: "Experience selling into or supporting ITSM, Observability, or Incident Management technology categories." That's industry experience, not skill. "Familiarity with MEDDPICC or similar value-selling and qualification frameworks." That's a skill. "Experience building and leading globally distributed technical sales teams across multiple go-to-market segments." That's leadership skill. "Comfortable presenting to and influencing C-level stakeholders." That's a skill.
Thus we can create Skills section with those items.
But we must avoid duplication; but it's okay if some overlap as long as we preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we can split: Requirements = basic qualifications (must have). Qualifications = preferred experience (nice to have). Skills = specific abilities (technical and soft). We'll list them.
Now Benefits: The posting lists many benefits under "What We Offer". We'll capture them as list.
Pay: base salary range and mention bonus, commission, equity, benefits. We'll include that.
Now we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out sections like "Where we work", "How We Work", "Our values", "Manager Expectations", "About PagerDuty", "Additional Information", etc. Also remove location restrictions? That's substantive? It's about eligibility; maybe it's considered substantive but not a section heading we have. Could be included in About the role? Probably not needed. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Location restrictions might be considered substantive but not a heading we have; we could incorporate into a short paragraph under About the role or maybe not include at all? It's about where candidates must reside; it's important info. However we don't have a heading for Location. Could we put it under About the role as a note? The instruction says preserve ALL substantive information. So we need to include location restrictions somewhere. Since we don't have a heading for Location, we could add a paragraph under About the role or maybe under Responsibilities? Better to add a short paragraph under About the role after the summary, mentioning hybrid work model and location restrictions. That would preserve info.
Similarly, "Where we work" includes hybrid work model and offices list. We'll incorporate that.
We must not include sections like "How We Work", "Our values", "Manager Expectations", "About PagerDuty", "Additional Information", EEO statements, etc.
Now let's craft HTML.
Structure:
About the role
...
Responsibilities
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
We must not include Schedule.
Now extract content precisely.
About the role: combine "Why We Need You" paragraph plus maybe mention hybrid work model and location restrictions.
Why We Need You: "Solution Consulting (Presales) is a critical part of the sales engine at PagerDuty - driving revenue and successful customers. As we continue to scale, the North America Solution Consulting leader will help raise the bar on our execution as a sales team, adapting to new product go to market motions, providing technical expertise to impact net revenue retention and expansion, and bringing creative ideas to improve our effectiveness and efficiency."
We can also add: "PagerDuty operates a hybrid work model with offices in Atlanta, Lisbon, London, San Francisco, Santiago, Sydney, Tokyo, and Toronto. Candidates must reside in eligible locations (see location restrictions)." But we should not invent; we can include that as factual.
Location restrictions list: many states/provinces. We'll include them as a sentence: "Candidates must reside in eligible locations; restrictions apply to certain U.S. states (Alaska, Hawaii, Iowa, Louisiana, Mississippi, Nebraska, New Mexico, Oklahoma, Rhode Island, South Dakota, West Virginia, Wyoming), Canadian provinces (Alberta, Manitoba, Newfoundland, Northwest Territories, Nunavut, PEI, Quebec, Saskatchewan, Yukon), and Australian territories/states (Northern Territory, Queensland, South Australia, Tasmania, Western Australia)." That's preserving.
Now Responsibilities
for prose. We need to preserve all substantive information. Let's extract. Job title: Senior Director, Solutions Consulting (but we don't repeat as heading). We'll have About the role: maybe a paragraph summarizing role purpose. From posting: "Why We Need You Solution Consulting (Presales) is a critical part of the sales engine at PagerDuty - driving revenue and successful customers. As we continue to scale, the North America Solution Consulting leader will help raise the bar on our execution as a sales team, adapting to new product go to market motions, providing technical expertise to impact net revenue retention and expansion, and bringing creative ideas to improve our effectiveness and efficiency." That's about role. "How You Contribute to Our Vision You define the vision for our North America Solution Consulting & Value Engineering organization – spanning solutions architects, demo engineers, and value engineers across Strategic, Enterprise, Commercial, and Architecture segments – building on our strengths and setting us up for accelerated growth well into the future. You represent the Customer Engineering team, partnering with key executives across Sales, Product, and Customer Revenue leadership to help drive product direction, customer success, net revenue retention, and sales results. Collaborating with regional Solutions Consulting peers and team, you build scalable systems and playbooks – establishing a Global Center of Excellence that codifies demo engineering standards, POC/POV methodology, and repeatable customer engagement frameworks adopted across the entire field organization. You hire outstanding people who will help us execute where we are today and lead us well into the future You inspire your team to bring their best every day, providing coaching and mentorship to support their career development. Partnering with our sales and customer success leaders, you constantly challenge the way things are done, looking for creative solutions to optimize for both effectiveness and efficiency. You have a great handle on the business. You know the deals in flight, where there’s risk and opportunity in the deals and you actively sell. You prioritize to ensure we’re focusing our limited bandwidth and resources on what will make the biggest difference. You manage our most expensive activities, Proofs of Value (POVs), closely with a focus on setting them up for success and communicating the value proven. You design reference architecture programs and POC infrastructure for strategic and named account pursuits, and serve as executive technical sponsor in competitive evaluations for our highest-value enterprise deals. You own the full customer journey – partnering with Customer Revenue leadership to protect and grow net revenue retention, surface expansion opportunities, and drive executive-level QBRs and business reviews well past the point of sale. You bring an innovation mindset – as a curious and critical-thinker, you will lead the team in developing AI-powered tools and automation that scale repeatable technical sales motions, improve team productivity, and drive down operating costs." That's responsibilities. "Basic Qualifications Experience: 10+ years of progressive growth in technical sales roles with at least 3 years in a senior-level people management role. Strategic Leadership: Proven track record of successfully partnering with sales leadership to drive revenue generation across a wide range of customers and their technologies. Technical Proficiency: Previous experience with SaaS and Cloud technologies as well as selling into technology organizations (IT Operations, Engineering, and/or office of the CTO). Working knowledge of cloud infrastructure (AWS, Azure, or GCP), modern DevOps/SRE workflows, APIs and system integrations, and observability or incident management tooling, Problem Solver: Exceptional analytical skills and the ability to use rigorous logic to solve complex problems in a fast-moving, sometimes ambiguous environment. Communication: Excellent written and oral communication skills with the ability to represent a complex organization at the senior executive level and speak credibly to technical architecture in front of engineering and IT audiences. Metrics Driven: Track record of managing key SC leadership metrics, including SC-influenced win rate, POV-to-close conversion rate, net new ARR and net revenue retention (NRR) influenced by the Customer Success organization." That's qualifications/requirements. "Preferred Experience Industry Experience: Experience selling into or supporting ITSM, Observability, or Incident Management technology categories. Sales Methodology: Familiarity with MEDDPICC or similar value-selling and qualification frameworks. Global Team Leadership: Experience building and leading globally distributed technical sales teams across multiple go-to-market segments. Executive Presence: Comfortable presenting to and influencing C-level stakeholders in both customer and internal settings." That's preferred experience, could be Skills or Qualifications. We need to separate Requirements vs Qualifications vs Skills. The instruction: use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically: Requirements = basic qualifications (must have). Qualifications = maybe preferred? Skills = specific skills. But we can map as we see fit, as long as we include all substantive info. We must not create sections with filler. So we need to ensure each section has real content. Let's assign: - About the role: short paragraph summarizing role purpose (the "Why We Need You" paragraph). - Responsibilities: the "How You Contribute to Our Vision" paragraph (multiple sentences). Could be broken into bullet list? It's prose; we can keep as
. - Requirements: Basic Qualifications list (the bullet points). We'll make
- for each.
- Qualifications: Preferred Experience list (the bullet points). Could be considered qualifications.
- Skills: maybe we can extract specific skills from the requirements: cloud infrastructure, DevOps/SRE, APIs, observability, incident management, analytical, communication, metrics-driven, etc. But we already have those in Requirements. To avoid duplication, maybe we put Skills as a separate list of technical and soft skills: e.g., "SaaS and Cloud technologies, AWS/Azure/GCP, DevOps/SRE, APIs, system integrations, observability/incident management, analytical, communication, MEDDPICC, etc." But we risk duplicating. However instruction says preserve ALL substantive information; we can keep them in Requirements and Qualifications; Skills could be omitted if no distinct content. But we must include a section only when posting has real specific content for it. If we don't have distinct skills beyond those already captured, we could omit Skills section. However we might still include Skills if we can extract from the text: "Experience selling into or supporting ITSM, Observability, or Incident Management technology categories." That's industry experience, not skill. "Familiarity with MEDDPICC or similar value-selling and qualification frameworks." That's a skill. "Experience building and leading globally distributed technical sales teams across multiple go-to-market segments." That's leadership skill. "Comfortable presenting to and influencing C-level stakeholders." That's a skill.
Thus we can create Skills section with those items.
But we must avoid duplication; but it's okay if some overlap as long as we preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we can split: Requirements = basic qualifications (must have). Qualifications = preferred experience (nice to have). Skills = specific abilities (technical and soft). We'll list them.
Now Benefits: The posting lists many benefits under "What We Offer". We'll capture them as list.
Pay: base salary range and mention bonus, commission, equity, benefits. We'll include that.
Now we must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out sections like "Where we work", "How We Work", "Our values", "Manager Expectations", "About PagerDuty", "Additional Information", etc. Also remove location restrictions? That's substantive? It's about eligibility; maybe it's considered substantive but not a section heading we have. Could be included in About the role? Probably not needed. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Location restrictions might be considered substantive but not a heading we have; we could incorporate into a short paragraph under About the role or maybe not include at all? It's about where candidates must reside; it's important info. However we don't have a heading for Location. Could we put it under About the role as a note? The instruction says preserve ALL substantive information. So we need to include location restrictions somewhere. Since we don't have a heading for Location, we could add a paragraph under About the role or maybe under Responsibilities? Better to add a short paragraph under About the role after the summary, mentioning hybrid work model and location restrictions. That would preserve info.
Similarly, "Where we work" includes hybrid work model and offices list. We'll incorporate that.
We must not include sections like "How We Work", "Our values", "Manager Expectations", "About PagerDuty", "Additional Information", EEO statements, etc.
Now let's craft HTML.
Structure:
About the role
...
Responsibilities
...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
We must not include Schedule. Now extract content precisely. About the role: combine "Why We Need You" paragraph plus maybe mention hybrid work model and location restrictions. Why We Need You: "Solution Consulting (Presales) is a critical part of the sales engine at PagerDuty - driving revenue and successful customers. As we continue to scale, the North America Solution Consulting leader will help raise the bar on our execution as a sales team, adapting to new product go to market motions, providing technical expertise to impact net revenue retention and expansion, and bringing creative ideas to improve our effectiveness and efficiency." We can also add: "PagerDuty operates a hybrid work model with offices in Atlanta, Lisbon, London, San Francisco, Santiago, Sydney, Tokyo, and Toronto. Candidates must reside in eligible locations (see location restrictions)." But we should not invent; we can include that as factual. Location restrictions list: many states/provinces. We'll include them as a sentence: "Candidates must reside in eligible locations; restrictions apply to certain U.S. states (Alaska, Hawaii, Iowa, Louisiana, Mississippi, Nebraska, New Mexico, Oklahoma, Rhode Island, South Dakota, West Virginia, Wyoming), Canadian provinces (Alberta, Manitoba, Newfoundland, Northwest Territories, Nunavut, PEI, Quebec, Saskatchewan, Yukon), and Australian territories/states (Northern Territory, Queensland, South Australia, Tasmania, Western Australia)." That's preserving. Now Responsibilities