Executive Business Parter, Customer Success
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, but we can format as sections.
We have sections: About the role (the paragraph after "About The Role"). Then Responsibilities (the "What You'll Do" list). Then Requirements/Qualifications/Skills (the "What We're Looking For" list). Possibly we could split into Requirements and Skills, but we can combine into one section if we want fewer sections. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (covering experience, skills). We'll not create Benefits, Pay, Schedule.
We need to remove boilerplate like Company Overview, Company Operating Rhythm, etc? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview and operating rhythm are not boilerplate but they are substantive? They are about company, not role. The instruction says preserve ALL substantive information; but we are to reformat a job posting into clean HTML. Likely we should include company overview? The sections we can use are limited to those headings; we cannot add arbitrary headings like Company Overview. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we should not include company overview as a separate heading; maybe we can incorporate it into About the role? But About the role is specific to role description. The company overview could be placed in a
before any heading? The instruction says output ONLY the HTML fragment — no /. It didn't forbid extra paragraphs outside headings. It says use
for section headings (list). It didn't say we cannot have other elements like
outside headings. So we could include a brief company overview as a
before the first heading. However the instruction: "Prefer a few substantive sections over many thin ones." Might be okay to have a short intro paragraph.
But we need to preserve ALL substantive information. The company overview is substantive. So we should include it. Where? Could be a
before the first heading. Or we could treat it as "About the role" but that's not accurate. Better to include a
with company overview, then
About the role
etc.
Also need to remove duplicated lines, cookie/navigation/legal/EEO/scam-warning boilerplate. At the end there is a notice about impersonating recruiters. That's boilerplate/scam-warning; should be removed.
Also remove "Notice: We're aware of individuals impersonating Deepgram recruiters..." etc.
Also remove "How You'll Know You're Successful" maybe we could incorporate into Responsibilities or Qualifications? It's more about success metrics; could be omitted? But we need to preserve ALL substantive information. That section is substantive. Could we include it as a separate section? Not among allowed headings. Could we incorporate into Responsibilities or Qualifications? It's about success criteria, not duties or requirements. Could be placed as a after Qualifications maybe as a separate section with no heading? But instruction says use
for section headings (list). 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; other headings maybe not appropriate. Better to incorporate that info into existing sections: maybe as part of Responsibilities (outcomes) or Qualifications (what success looks like). But we risk losing nuance. However we can add a
after Qualifications titled "Success Indicators" but that would be a heading not in list. Might be considered adding a heading not allowed. Safer to incorporate into Qualifications as a paragraph.
Let's extract content.
Company Overview paragraph: "Deepgram is the leading platform underpinning the emerging trillion-dollar Voice AI economy, providing real-time APIs for speech-to-text (STT), text-to-speech (TTS), and building production-grade voice agents at scale. More than 200,000 developers and 1,300+ organizations build voice offerings that are ‘Powered by Deepgram’, including Twilio, Cloudflare, Sierra, Decagon, Vapi, Daily, Cresta, Granola, and Jack in the Box. Deepgram’s voice-native foundation models are accessed through cloud APIs or as self-hosted and on-premises software, with unmatched accuracy, low latency, and cost efficiency. Backed by a recent Series C led by leading global investors and strategic partners, Deepgram has processed over 50,000 years of audio and transcribed more than 1 trillion words. There is no organization in the world that understands voice better than Deepgram."
Company Operating Rhythm: "At Deepgram, we expect an AI-first mindset—AI use and comfort aren’t optional, they’re core to how we operate, innovate, and measure performance. Every team member who works at Deepgram is expected to actively use and experiment with advanced AI tools, and even build your own into your everyday work. We measure how effectively AI is applied to deliver results, and consistent, creative use of the latest AI capabilities is key to success here. Candidates should be comfortable adopting new models and modes quickly, integrating AI into their workflows, and continuously pushing the boundaries of what these technologies can do. Additionally, we move at the pace of AI. Change is rapid, and you can expect your day-to-day work to evolve just as quickly. This may not be the right role if you’re not excited to experiment, adapt, think on your feet, and learn constantly, or if you’re seeking something highly prescriptive with a traditional 9-to-5."
This is also substantive; could be included as a
before About the role.
Now About The Role paragraph: "We are looking for an Executive Business Partner (EBP) to partner closely with the SVP of Customer Success and increase the operating effectiveness of both the executive and the broader Customer Success organization. This is not a traditional Executive Assistant role. The ideal person combines exceptional executive support with strong business acumen, analytical thinking, operational judgment, project management, and follow-through. You will help create leverage for the SVP of Customer Success by managing priorities, bringing structure to complex work, driving cross-functional initiatives forward, and helping turn business data into insights, decisions, and executive-level narratives. You will sit alongside the SVP in key operating and forecasting conversations and develop a deep understanding of the health and performance of the Customer Success organization. You'll understand not only what the numbers are, but what they mean, where they come from, how they connect, and what questions we should be asking because of them. You should be equally comfortable managing a complex executive calendar, preparing for a leadership or board meeting, reviewing a renewal forecast, interrogating inconsistencies in business data, coordinating an offsite, building a project plan, or synthesizing information across multiple teams and systems into a clear executive narrative. The goal of this role is to increase the leverage of the SVP of Customer Success while strengthening the operating rigor, business visibility, and accountability of the Customer Success organization."
Now What You'll Do (list). It's a bunch of bullet points under headings: Executive Partnership, Business Analytics & Executive Insights, Functional Operating Rhythm & Accountability, Business & Customer Success Operations, Planning & Execution. Each has multiple bullet points. We need to output as
- for any list of duties/requirements/benefits. So we can combine all bullets into a single list, or we could keep subheadings? The instruction says use
- for any list. It doesn't forbid having headings inside list? Probably better to flatten all duties into a single
list. But we might lose grouping. However we can keep subheadings as before the list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we could have a
introducing the list, then
- items. That's fine.
We need to preserve all bullet points. Let's extract them.
Executive Partnership:
- Manage and strategically prioritize the SVP of Customer Success's calendar, meetings, and commitments.
- Ensure the SVP is prepared for key customer, executive, board, leadership, and cross-functional meetings with the appropriate context, data, materials, and outstanding decisions.
- Help prioritize incoming requests and determine what requires the SVP's direct involvement versus what can be delegated or resolved elsewhere.
- Track decisions, commitments, and follow-ups to ensure important work does not stall.
- Coordinate travel, leadership meetings, team events, offsites, and other executive logistics as needed.
- Help organize and prepare executive communications, presentations, agendas, and internal updates.
Business Analytics & Executive Insights:
- Participate in Customer Success forecasting, business reviews, and operating meetings alongside the SVP of Customer Success.
- Develop a strong understanding of the metrics that drive the Customer Success business, including retention, renewals, expansion, consumption, customer health, risk, capacity, and other key performance indicators.
- Understand where critical business data lives, how it is calculated, how different data sources connect, and where gaps or inconsistencies exist.
- Partner with CS functional leaders to ensure forecasts, metrics, and business updates are accurate, well-supported, and accompanied by meaningful insights.
- Ask the second- and third-level questions behind the data: Why did this change? What is driving it? Is this an isolated issue or a trend? What action should we take because of it?
- Identify inconsistencies, gaps, or unsupported assumptions in forecasts and operating metrics and work with the appropriate leaders to resolve them.
- Synthesize complex data and operational information into concise insights for the SVP of Customer Success and other executive audiences.
- Help translate detailed functional reporting into executive-level narratives focused on performance, drivers, risks, opportunities, and actions.
- Support preparation for executive leadership meetings, board meetings, quarterly business reviews, and strategic planning.
- Maintain continuity between reporting periods by tracking trends, prior commitments, forecast movement, and changes in key business drivers.
Functional Operating Rhythm & Accountability:
- Support weekly, monthly, and quarterly operating rhythms across the Customer Success leadership team.
- Partner with CS functional leaders to ensure they arrive at operating reviews prepared with the right data, insights, risks, and recommendations.
- Establish clear expectations for recurring reporting and business reviews across CS functions.
- Track commitments made during forecast reviews, leadership meetings, and operating reviews and ensure owners follow through.
- Help distinguish between reporting activity and actionable business insight, pushing teams to clearly articulate what the data means and what should happen next.
- Surface issues early when performance is off-track, ownership is unclear, data is unreliable, or executive intervention is required.
- Help create consistency in how the CS organization communicates performance internally and to executive audiences.
Business & Customer Success Operations:
- Support high-priority Customer Success initiatives from initial problem definition through execution.
- Build structure around ambiguous problems by identifying workstreams, owners, dependencies, timelines, data requirements, and decisions needed.
- Coordinate cross-functional initiatives involving Customer Success, Sales, Finance, RevOps, Product, Support, and other teams.
- Help maintain visibility into organizational priorities, customer and renewal risk, operational dependencies, and strategic initiatives.
- Develop lightweight operating mechanisms, dash
for prose. We need to preserve all substantive information, but we can format as sections. We have sections: About the role (the paragraph after "About The Role"). Then Responsibilities (the "What You'll Do" list). Then Requirements/Qualifications/Skills (the "What We're Looking For" list). Possibly we could split into Requirements and Skills, but we can combine into one section if we want fewer sections. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (covering experience, skills). We'll not create Benefits, Pay, Schedule. We need to remove boilerplate like Company Overview, Company Operating Rhythm, etc? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview and operating rhythm are not boilerplate but they are substantive? They are about company, not role. The instruction says preserve ALL substantive information; but we are to reformat a job posting into clean HTML. Likely we should include company overview? The sections we can use are limited to those headings; we cannot add arbitrary headings like Company Overview. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we should not include company overview as a separate heading; maybe we can incorporate it into About the role? But About the role is specific to role description. The company overview could be placed in a
before any heading? The instruction says output ONLY the HTML fragment — no /. It didn't forbid extra paragraphs outside headings. It says use
for section headings (list). It didn't say we cannot have other elements like
outside headings. So we could include a brief company overview as a
before the first heading. However the instruction: "Prefer a few substantive sections over many thin ones." Might be okay to have a short intro paragraph. But we need to preserve ALL substantive information. The company overview is substantive. So we should include it. Where? Could be a
before the first heading. Or we could treat it as "About the role" but that's not accurate. Better to include a
with company overview, then
About the role
etc. Also need to remove duplicated lines, cookie/navigation/legal/EEO/scam-warning boilerplate. At the end there is a notice about impersonating recruiters. That's boilerplate/scam-warning; should be removed. Also remove "Notice: We're aware of individuals impersonating Deepgram recruiters..." etc. Also remove "How You'll Know You're Successful" maybe we could incorporate into Responsibilities or Qualifications? It's more about success metrics; could be omitted? But we need to preserve ALL substantive information. That section is substantive. Could we include it as a separate section? Not among allowed headings. Could we incorporate into Responsibilities or Qualifications? It's about success criteria, not duties or requirements. Could be placed as aafter Qualifications maybe as a separate section with no heading? But instruction says use
for section headings (list). 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; other headings maybe not appropriate. Better to incorporate that info into existing sections: maybe as part of Responsibilities (outcomes) or Qualifications (what success looks like). But we risk losing nuance. However we can add a
after Qualifications titled "Success Indicators" but that would be a heading not in list. Might be considered adding a heading not allowed. Safer to incorporate into Qualifications as a paragraph. Let's extract content. Company Overview paragraph: "Deepgram is the leading platform underpinning the emerging trillion-dollar Voice AI economy, providing real-time APIs for speech-to-text (STT), text-to-speech (TTS), and building production-grade voice agents at scale. More than 200,000 developers and 1,300+ organizations build voice offerings that are ‘Powered by Deepgram’, including Twilio, Cloudflare, Sierra, Decagon, Vapi, Daily, Cresta, Granola, and Jack in the Box. Deepgram’s voice-native foundation models are accessed through cloud APIs or as self-hosted and on-premises software, with unmatched accuracy, low latency, and cost efficiency. Backed by a recent Series C led by leading global investors and strategic partners, Deepgram has processed over 50,000 years of audio and transcribed more than 1 trillion words. There is no organization in the world that understands voice better than Deepgram." Company Operating Rhythm: "At Deepgram, we expect an AI-first mindset—AI use and comfort aren’t optional, they’re core to how we operate, innovate, and measure performance. Every team member who works at Deepgram is expected to actively use and experiment with advanced AI tools, and even build your own into your everyday work. We measure how effectively AI is applied to deliver results, and consistent, creative use of the latest AI capabilities is key to success here. Candidates should be comfortable adopting new models and modes quickly, integrating AI into their workflows, and continuously pushing the boundaries of what these technologies can do. Additionally, we move at the pace of AI. Change is rapid, and you can expect your day-to-day work to evolve just as quickly. This may not be the right role if you’re not excited to experiment, adapt, think on your feet, and learn constantly, or if you’re seeking something highly prescriptive with a traditional 9-to-5." This is also substantive; could be included as a
before About the role. Now About The Role paragraph: "We are looking for an Executive Business Partner (EBP) to partner closely with the SVP of Customer Success and increase the operating effectiveness of both the executive and the broader Customer Success organization. This is not a traditional Executive Assistant role. The ideal person combines exceptional executive support with strong business acumen, analytical thinking, operational judgment, project management, and follow-through. You will help create leverage for the SVP of Customer Success by managing priorities, bringing structure to complex work, driving cross-functional initiatives forward, and helping turn business data into insights, decisions, and executive-level narratives. You will sit alongside the SVP in key operating and forecasting conversations and develop a deep understanding of the health and performance of the Customer Success organization. You'll understand not only what the numbers are, but what they mean, where they come from, how they connect, and what questions we should be asking because of them. You should be equally comfortable managing a complex executive calendar, preparing for a leadership or board meeting, reviewing a renewal forecast, interrogating inconsistencies in business data, coordinating an offsite, building a project plan, or synthesizing information across multiple teams and systems into a clear executive narrative. The goal of this role is to increase the leverage of the SVP of Customer Success while strengthening the operating rigor, business visibility, and accountability of the Customer Success organization." Now What You'll Do (list). It's a bunch of bullet points under headings: Executive Partnership, Business Analytics & Executive Insights, Functional Operating Rhythm & Accountability, Business & Customer Success Operations, Planning & Execution. Each has multiple bullet points. We need to output as
- for any list of duties/requirements/benefits. So we can combine all bullets into a single list, or we could keep subheadings? The instruction says use
- for any list. It doesn't forbid having headings inside list? Probably better to flatten all duties into a single
- list. But we might lose grouping. However we can keep subheadings as
- for any list of duties/requirements/benefits, and
for prose. So we could have a
introducing the list, then
- items. That's fine. We need to preserve all bullet points. Let's extract them. Executive Partnership: - Manage and strategically prioritize the SVP of Customer Success's calendar, meetings, and commitments. - Ensure the SVP is prepared for key customer, executive, board, leadership, and cross-functional meetings with the appropriate context, data, materials, and outstanding decisions. - Help prioritize incoming requests and determine what requires the SVP's direct involvement versus what can be delegated or resolved elsewhere. - Track decisions, commitments, and follow-ups to ensure important work does not stall. - Coordinate travel, leadership meetings, team events, offsites, and other executive logistics as needed. - Help organize and prepare executive communications, presentations, agendas, and internal updates. Business Analytics & Executive Insights: - Participate in Customer Success forecasting, business reviews, and operating meetings alongside the SVP of Customer Success. - Develop a strong understanding of the metrics that drive the Customer Success business, including retention, renewals, expansion, consumption, customer health, risk, capacity, and other key performance indicators. - Understand where critical business data lives, how it is calculated, how different data sources connect, and where gaps or inconsistencies exist. - Partner with CS functional leaders to ensure forecasts, metrics, and business updates are accurate, well-supported, and accompanied by meaningful insights. - Ask the second- and third-level questions behind the data: Why did this change? What is driving it? Is this an isolated issue or a trend? What action should we take because of it? - Identify inconsistencies, gaps, or unsupported assumptions in forecasts and operating metrics and work with the appropriate leaders to resolve them. - Synthesize complex data and operational information into concise insights for the SVP of Customer Success and other executive audiences. - Help translate detailed functional reporting into executive-level narratives focused on performance, drivers, risks, opportunities, and actions. - Support preparation for executive leadership meetings, board meetings, quarterly business reviews, and strategic planning. - Maintain continuity between reporting periods by tracking trends, prior commitments, forecast movement, and changes in key business drivers. Functional Operating Rhythm & Accountability: - Support weekly, monthly, and quarterly operating rhythms across the Customer Success leadership team. - Partner with CS functional leaders to ensure they arrive at operating reviews prepared with the right data, insights, risks, and recommendations. - Establish clear expectations for recurring reporting and business reviews across CS functions. - Track commitments made during forecast reviews, leadership meetings, and operating reviews and ensure owners follow through. - Help distinguish between reporting activity and actionable business insight, pushing teams to clearly articulate what the data means and what should happen next. - Surface issues early when performance is off-track, ownership is unclear, data is unreliable, or executive intervention is required. - Help create consistency in how the CS organization communicates performance internally and to executive audiences. Business & Customer Success Operations: - Support high-priority Customer Success initiatives from initial problem definition through execution. - Build structure around ambiguous problems by identifying workstreams, owners, dependencies, timelines, data requirements, and decisions needed. - Coordinate cross-functional initiatives involving Customer Success, Sales, Finance, RevOps, Product, Support, and other teams. - Help maintain visibility into organizational priorities, customer and renewal risk, operational dependencies, and strategic initiatives. - Develop lightweight operating mechanisms, dash
before the list? The instruction: Use
- for any list of duties/requirements/benefits, and
- for any list. It doesn't forbid having headings inside list? Probably better to flatten all duties into a single