Senior Director, Sales Development
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info.
We need to parse the posting.
Content:
- About The Position: description of role: leads 30-40 SDRs across multiple managers, covering outbound and inbound. second-line leadership role, seat at revenue table. Own pipeline number, partner with Marketing, RevOps, Sales leadership, lieutenant to VP of Sales delivering predictable pipeline. Looking for leader relentless about number, runs coaching standard, treats pipeline quality as seriously as volume.
- What You Will Do: list of duties (bulleted sentences). We'll need to turn into
- .
- What You Will Bring: requirements (experience, skills). Also list.
- You Will Get: benefits (flexibility, stock options, insurance, 401k, AI tools, opportunities, leadership, workspace). Also maybe schedule: flexibility of working from Austin office three days a week (Tue, Wed, Thu), option remote remainder. That's schedule info.
- Why Join Stampli?: company description, maybe not needed as a section? Could be "About the company" but not in required headings list. We could include as a
under maybe "About the company" but not required heading. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, but we should use those headings when appropriate. We can also add other headings if needed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. We have content that maps:
- About the role: The About The Position paragraph.
- Responsibilities: What You Will Do.
- Requirements: What You Will Bring (maybe split into Requirements and Qualifications? Could combine). Could have Requirements (experience) and Qualifications (skills). But we can just put Requirements.
- Benefits: You Will Get.
- Schedule: flexibility of working from office three days a week, option remote remainder.
- Pay: Not mentioned explicitly (no salary). So we should NOT create Pay section.
- Skills: maybe we could extract skills from requirements (HubSpot, Gong, etc.) but we could also put under Requirements. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have Requirements and Skills separate if we have distinct lists. But we have both experience and skills. Could split: Requirements (experience) and Skills (tools). However the instruction says "Prefer a few substantive sections over many thin ones." So maybe better to have one "Requirements" section that includes both experience and skills.
Thus sections:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Schedule
...
We must not include fluff like "commensurate with experience". Not present.
We need to preserve all substantive information. Let's extract.
About the role paragraph: "The Senior Director of Sales Development leads 30 to 40 SDRs across multiple managers, covering both outbound and inbound. This is a second-line leadership role and a seat at the revenue table. You will own Sales Development pipeline as a revenue number, partner closely with Marketing, RevOps, and Sales leadership, and act as a lieutenant to the VP of Sales on delivering predictable pipeline against the plan. We are looking for a leader who is relentless about the number, runs a coaching standard that never slips, and treats pipeline quality as seriously as pipeline volume."
We'll put that in .
Responsibilities: list from "What You Will Do". Let's extract each sentence as bullet.
- Own the pipeline number. Accountable for Sales Development-sourced pipeline and the Closed-Won revenue it produces. Forecast it, inspect it weekly, and close gaps before the month ends.
- Serve as a lieutenant of revenue. Participate in forecast calls, pipeline reviews, and annual planning. Flag where the plan is at risk early, with a recommendation attached.
- Lead leaders. Develop a bench of SDR managers who coach well. Raise the hiring bar, build a promotion path into AE roles, and manage performance with clarity and care.
- Build the talent engine. Own onboarding, ramp, enablement, and career progression, developing future AEs and leaders from within the SDR ranks.
- Run the coaching cadence. Film room, call review, and 1:1s on a schedule that holds for every manager and rep. Coach meeting quality and opportunity conversion as distinct skills.
- Stay hands-on. Personally inspect cadence performance and the quality of every meeting passed to Sales. Hold the qualification standard, retire what underperforms, and scale what works.
- Put AI to work on quality. Use AI to sharpen targeting, account research, and message relevance, so reps spend more time in better conversations.
- Hold partners to supply. Set explicit account and lead supply, data quality, and instrumentation requirements with Marketing and RevOps. Track delivery weekly and escalate early.
- Own the system end to end. Capacity planning, coverage by segment and ERP, targeting, messaging, and conversion from first touch to Closed-Won. Fix the constraint wherever it sits.
We'll make each bullet a
- . Might need to split long sentences but okay.
Requirements: from "What You Will Bring". Let's extract each bullet.
- 8+ years in B2B SaaS, with 5+ years leading Sales Development or Inside Sales teams, including 3+ years as a second-line leader of three or more managers.
- A track record of carrying a pipeline number tied to revenue, at a B2B SaaS company scaling through meaningful growth.
- Proof of improving pipeline quality by increasing meeting-to-opportunity or opportunity-to-close conversion rates.
- Experience selling to finance buyers (CFO, Controller, VP Finance) in the mid-market.
- Hands-on fluency with HubSpot, Gong, Nooks, LinkedIn Sales Navigator, and AI-powered sales engagement tools, and the habit of inspecting the data yourself.
- Experience applying AI to targeting, research, and messaging in a Sales Development org.
- A history of building strong partnerships with Marketing and RevOps on targeting, lead definitions, and capacity models.
- A coaching standard others notice, and managers and reps who grew under you.
We'll put each as
- .
Benefits: from "You Will Get". Let's extract.
- The flexibility of working from our Austin, TX office three days a week (Tuesday, Wednesday, and Thursday), with the option to work remotely for the remainder of the week.
- Stock Options
- Full medical, dental, and vision insurance
- 401(k) + employer match
- Access to cutting-edge AI tools, including ChatGPT Enterprise, to enhance productivity, support innovation, and streamline daily workflows
- Opportunities and development for career and personal growth
- Strong and experienced leadership that supports your growth and success
- An open-concept, modern workspace within an inclusive and dynamic scale-up culture
We'll put each as
- . Note that the first bullet includes schedule info; but we also have a separate Schedule section. Might duplicate. Better to separate schedule: The flexibility of working from our Austin, TX office three days a week (Tuesday, Wednesday, and Thursday), with the option to work remotely for the remainder of the week. That's schedule. So we can move that to Schedule section and not include in Benefits. Benefits then list the rest.
Thus Benefits:
- Stock Options
- Full medical, dental, and vision insurance
- 401(k) + employer match
- Access to cutting-edge AI tools, including ChatGPT Enterprise, to enhance productivity, support innovation, and streamline daily workflows
- Opportunities and development for career and personal growth
- Strong and experienced leadership that supports your growth and success
- An open-concept, modern workspace within an inclusive and dynamic scale-up culture
Schedule: The flexibility of working from our Austin, TX office three days a week (Tuesday, Wednesday, and Thursday), with the option to work remotely for the remainder of the week.
We'll put that in
under Schedule heading.
Now ensure we didn't miss any substantive info: The "Why Join Stampli?" paragraph includes company description. Should we include? It's substantive but not under given headings. Could we add a section "About the company"? The instruction says use headings e.g. About the role, Responsibilities... 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 where applicable, but we could also add other headings if needed. However they say "Prefer a few substantive sections over many thin ones." Adding another section may be thin. The company description is substantive but maybe we can incorporate into About the role? Not really. Could we add a
after the sections without a heading? The instruction says use headings for section headings; doesn't forbid stray
without heading. But better to keep structured. Perhaps we can include a section "About the company" as
About the company
...
. That seems reasonable.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are those. Safer to stick to those headings only. However the company description is substantive; we could incorporate it into About the role? Not ideal but we could add a sentence about company in About the role? The About the role currently is about the position. Could we extend About the role paragraph to include company description? That would be mixing role and company but still substantive. The instruction: "Preserve ALL substantive information". So we need to keep that company description somewhere. If we don't create a heading for it, we could just put a
after the sections without a heading. That might be acceptable. The instruction says "use
for section headings (e.g ...)". It doesn't say every
must be under a heading. So we can add a
for company description without a heading. That preserves info.
Thus final HTML:
About the role
The Senior Director of Sales Development leads 30 to 40 SDRs across multiple managers, covering both outbound and inbound. This is a second-line leadership role and a seat at the revenue table. You will own Sales Development pipeline as a revenue number, partner closely with Marketing, RevOps, and Sales leadership, and act as a lieutenant to the VP of Sales on delivering predictable pipeline against the plan. We are looking for a leader who is relentless about the number, runs a coaching standard that never slips, and treats pipeline quality as seriously as pipeline volume.
Responsibilities
- Own the pipeline number. Accountable for Sales Development-sourced pipeline and the Closed-Won revenue it produces. Forecast it, inspect it weekly, and close gaps before the month ends.
- Serve as a lieutenant of revenue. Participate in forecast calls, pipeline reviews, and annual planning. Flag where the plan
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Include sections only when posting has real specific content. Must preserve all substantive info. We need to parse the posting. Content: - About The Position: description of role: leads 30-40 SDRs across multiple managers, covering outbound and inbound. second-line leadership role, seat at revenue table. Own pipeline number, partner with Marketing, RevOps, Sales leadership, lieutenant to VP of Sales delivering predictable pipeline. Looking for leader relentless about number, runs coaching standard, treats pipeline quality as seriously as volume. - What You Will Do: list of duties (bulleted sentences). We'll need to turn into
- .
- What You Will Bring: requirements (experience, skills). Also list.
- You Will Get: benefits (flexibility, stock options, insurance, 401k, AI tools, opportunities, leadership, workspace). Also maybe schedule: flexibility of working from Austin office three days a week (Tue, Wed, Thu), option remote remainder. That's schedule info.
- Why Join Stampli?: company description, maybe not needed as a section? Could be "About the company" but not in required headings list. We could include as a
under maybe "About the company" but not required heading. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, but we should use those headings when appropriate. We can also add other headings if needed? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where applicable. We have content that maps: - About the role: The About The Position paragraph. - Responsibilities: What You Will Do. - Requirements: What You Will Bring (maybe split into Requirements and Qualifications? Could combine). Could have Requirements (experience) and Qualifications (skills). But we can just put Requirements. - Benefits: You Will Get. - Schedule: flexibility of working from office three days a week, option remote remainder. - Pay: Not mentioned explicitly (no salary). So we should NOT create Pay section. - Skills: maybe we could extract skills from requirements (HubSpot, Gong, etc.) but we could also put under Requirements. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". Or we could have Requirements and Skills separate if we have distinct lists. But we have both experience and skills. Could split: Requirements (experience) and Skills (tools). However the instruction says "Prefer a few substantive sections over many thin ones." So maybe better to have one "Requirements" section that includes both experience and skills. Thus sections:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Schedule
...
We must not include fluff like "commensurate with experience". Not present. We need to preserve all substantive information. Let's extract. About the role paragraph: "The Senior Director of Sales Development leads 30 to 40 SDRs across multiple managers, covering both outbound and inbound. This is a second-line leadership role and a seat at the revenue table. You will own Sales Development pipeline as a revenue number, partner closely with Marketing, RevOps, and Sales leadership, and act as a lieutenant to the VP of Sales on delivering predictable pipeline against the plan. We are looking for a leader who is relentless about the number, runs a coaching standard that never slips, and treats pipeline quality as seriously as pipeline volume." We'll put that in. Responsibilities: list from "What You Will Do". Let's extract each sentence as bullet. - Own the pipeline number. Accountable for Sales Development-sourced pipeline and the Closed-Won revenue it produces. Forecast it, inspect it weekly, and close gaps before the month ends. - Serve as a lieutenant of revenue. Participate in forecast calls, pipeline reviews, and annual planning. Flag where the plan is at risk early, with a recommendation attached. - Lead leaders. Develop a bench of SDR managers who coach well. Raise the hiring bar, build a promotion path into AE roles, and manage performance with clarity and care. - Build the talent engine. Own onboarding, ramp, enablement, and career progression, developing future AEs and leaders from within the SDR ranks. - Run the coaching cadence. Film room, call review, and 1:1s on a schedule that holds for every manager and rep. Coach meeting quality and opportunity conversion as distinct skills. - Stay hands-on. Personally inspect cadence performance and the quality of every meeting passed to Sales. Hold the qualification standard, retire what underperforms, and scale what works. - Put AI to work on quality. Use AI to sharpen targeting, account research, and message relevance, so reps spend more time in better conversations. - Hold partners to supply. Set explicit account and lead supply, data quality, and instrumentation requirements with Marketing and RevOps. Track delivery weekly and escalate early. - Own the system end to end. Capacity planning, coverage by segment and ERP, targeting, messaging, and conversion from first touch to Closed-Won. Fix the constraint wherever it sits. We'll make each bullet a
- . Might need to split long sentences but okay. Requirements: from "What You Will Bring". Let's extract each bullet. - 8+ years in B2B SaaS, with 5+ years leading Sales Development or Inside Sales teams, including 3+ years as a second-line leader of three or more managers. - A track record of carrying a pipeline number tied to revenue, at a B2B SaaS company scaling through meaningful growth. - Proof of improving pipeline quality by increasing meeting-to-opportunity or opportunity-to-close conversion rates. - Experience selling to finance buyers (CFO, Controller, VP Finance) in the mid-market. - Hands-on fluency with HubSpot, Gong, Nooks, LinkedIn Sales Navigator, and AI-powered sales engagement tools, and the habit of inspecting the data yourself. - Experience applying AI to targeting, research, and messaging in a Sales Development org. - A history of building strong partnerships with Marketing and RevOps on targeting, lead definitions, and capacity models. - A coaching standard others notice, and managers and reps who grew under you. We'll put each as
- . Benefits: from "You Will Get". Let's extract. - The flexibility of working from our Austin, TX office three days a week (Tuesday, Wednesday, and Thursday), with the option to work remotely for the remainder of the week. - Stock Options - Full medical, dental, and vision insurance - 401(k) + employer match - Access to cutting-edge AI tools, including ChatGPT Enterprise, to enhance productivity, support innovation, and streamline daily workflows - Opportunities and development for career and personal growth - Strong and experienced leadership that supports your growth and success - An open-concept, modern workspace within an inclusive and dynamic scale-up culture We'll put each as
- . Note that the first bullet includes schedule info; but we also have a separate Schedule section. Might duplicate. Better to separate schedule: The flexibility of working from our Austin, TX office three days a week (Tuesday, Wednesday, and Thursday), with the option to work remotely for the remainder of the week. That's schedule. So we can move that to Schedule section and not include in Benefits. Benefits then list the rest.
Thus Benefits:
- Stock Options
- Full medical, dental, and vision insurance
- 401(k) + employer match
- Access to cutting-edge AI tools, including ChatGPT Enterprise, to enhance productivity, support innovation, and streamline daily workflows
- Opportunities and development for career and personal growth
- Strong and experienced leadership that supports your growth and success
- An open-concept, modern workspace within an inclusive and dynamic scale-up culture
Schedule: The flexibility of working from our Austin, TX office three days a week (Tuesday, Wednesday, and Thursday), with the option to work remotely for the remainder of the week.
We'll put that in
under Schedule heading. Now ensure we didn't miss any substantive info: The "Why Join Stampli?" paragraph includes company description. Should we include? It's substantive but not under given headings. Could we add a section "About the company"? The instruction says use headings e.g. About the role, Responsibilities... 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 where applicable, but we could also add other headings if needed. However they say "Prefer a few substantive sections over many thin ones." Adding another section may be thin. The company description is substantive but maybe we can incorporate into About the role? Not really. Could we add a
after the sections without a heading? The instruction says use headings for section headings; doesn't forbid stray
without heading. But better to keep structured. Perhaps we can include a section "About the company" as
About the company
...
. That seems reasonable. But the instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are those. Safer to stick to those headings only. However the company description is substantive; we could incorporate it into About the role? Not ideal but we could add a sentence about company in About the role? The About the role currently is about the position. Could we extend About the role paragraph to include company description? That would be mixing role and company but still substantive. The instruction: "Preserve ALL substantive information". So we need to keep that company description somewhere. If we don't create a heading for it, we could just put a
after the sections without a heading. That might be acceptable. The instruction says "use
for section headings (e.g ...)". It doesn't say every
must be under a heading. So we can add a
for company description without a heading. That preserves info. Thus final HTML:
About the role
The Senior Director of Sales Development leads 30 to 40 SDRs across multiple managers, covering both outbound and inbound. This is a second-line leadership role and a seat at the revenue table. You will own Sales Development pipeline as a revenue number, partner closely with Marketing, RevOps, and Sales leadership, and act as a lieutenant to the VP of Sales on delivering predictable pipeline against the plan. We are looking for a leader who is relentless about the number, runs a coaching standard that never slips, and treats pipeline quality as seriously as pipeline volume.
Responsibilities
- Own the pipeline number. Accountable for Sales Development-sourced pipeline and the Closed-Won revenue it produces. Forecast it, inspect it weekly, and close gaps before the month ends.
- Serve as a lieutenant of revenue. Participate in forecast calls, pipeline reviews, and annual planning. Flag where the plan