Senior Client Services Director
Further · New York, NY · 1 mo ago
HybridBusiness DevelopmentFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No metadata like Job ID. Remove boilerplate: "WE’RE HIRING!", "Further is a data, cloud, and AI company..."? That's about the company; could be part of About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content.
Let's parse the posting:
- Intro: "WE’RE HIRING! If you love data and are looking for unlimited growth opportunities, we want to talk with you about joining Further. Further is a data, cloud, and AI company whose focus is helping companies turn raw data into the right decisions. We have an award winning culture of extraordinary people. Our purpose is to enable people to thrive so that businesses can thrive. We believe that the work you do should matter - it should be meaningful to you professionally and personally, and it should have a positive impact on both you and our clients. If this sounds exciting to you, let’s chat!" This is about the company and role; could be "About the role" or maybe "About the company". We'll put under "About the role".
- Then "Senior Client Services Lead" is the job title (not to be used as heading). Then description: "We’re hiring a client services leader who grows accounts through value creation. This person leads a portfolio of enterprise customers by translating strategy into measurable outcomes, shaping multi-quarter transformation roadmaps across data, cloud, and AI, and coaching account teams to consistently deliver (and prove) business impact. You bring executive presence, a consulting mindset, and a track record of driving multi-million-dollar YoY growth by building trusted relationships, identifying high-impact use cases, and operationalizing value realization." This is also about the role.
- Then "What Experience Should You Have" with bullet list (actually numbered list). This is Requirements/Qualifications/Skills. We need to decide sections: maybe "Requirements" for required experience, "Qualifications" for nice-to-have, "Skills" for specific skills? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to include only if there is real specific content.
We have required experience bullet points (starting with "10–15+ years managing enterprise client relationships..." etc). Then "Nice-to-have Experience building account plans..." etc.
Thus we can have:
- Requirements: the required experience bullet list.
- Qualifications: the nice-to-have bullet list.
- Skills: maybe we can extract skills like "executive presence, consulting mindset, commercial fluency, AI/data fluency". But those are already in required. Could combine.
Better: Use "Requirements" for required, "Qualifications" for nice-to-have, and maybe "Skills" not needed if overlapping. But we could still include Skills if we have distinct content: maybe "executive presence, consulting mindset, commercial fluency, enough fluency in AI and data concepts". Those are in required. Might be redundant.
We also have "What You’ll Be Doing In This Role" bullet list (actually paragraph with bullet-like sentences). That's Responsibilities.
Then "What You'll Need To Accomplish In Your First Year" bullet list (specific goals). That could be also Responsibilities or maybe "Objectives". Could be part of Responsibilities or a separate section like "First Year Goals". But we only have allowed headings; we could put under Responsibilities.
Then benefits paragraph: "Our total rewards program is designed for your protection, peace of mind, and overall well-being. In addition to our outstanding basics, we offer a net-zero cost medical option, company contributions to your HSA, fertility support, fully-paid parental leave, a monthly stipend for your lifestyle spending account, and much more." That's Benefits.
Pay and Schedule: not mentioned, so we should NOT include those sections.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content.
Let's parse the posting:
- Intro: "WE’RE HIRING! If you love data and are looking for unlimited growth opportunities, we want to talk with you about joining Further. Further is a data, cloud, and AI company whose focus is helping companies turn raw data into the right decisions. We have an award winning culture of extraordinary people. Our purpose is to enable people to thrive so that businesses can thrive. We believe that the work you do should matter - it should be meaningful to you professionally and personally, and it should have a positive impact on both you and our clients. If this sounds exciting to you, let’s chat!" This is about the company and role; could be "About the role" or maybe "About the company". We'll put under "About the role".
- Then "Senior Client Services Lead" is the job title (not to be used as heading). Then description: "We’re hiring a client services leader who grows accounts through value creation. This person leads a portfolio of enterprise customers by translating strategy into measurable outcomes, shaping multi-quarter transformation roadmaps across data, cloud, and AI, and coaching account teams to consistently deliver (and prove) business impact. You bring executive presence, a consulting mindset, and a track record of driving multi-million-dollar YoY growth by building trusted relationships, identifying high-impact use cases, and operationalizing value realization." This is also about the role.
- Then "What Experience Should You Have" with bullet list (actually numbered list). This is Requirements/Qualifications/Skills. We need to decide sections: maybe "Requirements" for required experience, "Qualifications" for nice-to-have, "Skills" for specific skills? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to include only if there is real specific content.
We have required experience bullet points (starting with "10–15+ years managing enterprise client relationships..." etc). Then "Nice-to-have Experience building account plans..." etc.
Thus we can have:
- Requirements: the required experience bullet list.
- Qualifications: the nice-to-have bullet list.
- Skills: maybe we can extract skills like "executive presence, consulting mindset, commercial fluency, AI/data fluency". But those are already in required. Could combine.
Better: Use "Requirements" for required, "Qualifications" for nice-to-have, and maybe "Skills" not needed if overlapping. But we could still include Skills if we have distinct content: maybe "executive presence, consulting mindset, commercial fluency, enough fluency in AI and data concepts". Those are in required. Might be redundant.
We also have "What You’ll Be Doing In This Role" bullet list (actually paragraph with bullet-like sentences). That's Responsibilities.
Then "What You'll Need To Accomplish In Your First Year" bullet list (specific goals). That could be also Responsibilities or maybe "Objectives". Could be part of Responsibilities or a separate section like "First Year Goals". But we only have allowed headings; we could put under Responsibilities.
Then benefits paragraph: "Our total rewards program is designed for your protection, peace of mind, and overall well-being. In addition to our outstanding basics, we offer a net-zero cost medical option, company contributions to your HSA, fertility support, fully-paid parental leave, a monthly stipend for your lifestyle spending account, and much more." That's Benefits.
Pay and Schedule: not mentioned, so we should NOT include those sections.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits.
We need to use for each section heading. Then content: use
for prose,
- for lists.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can reformat.
Let's extract content precisely.
About the role: combine the intro paragraphs and the role description before "What Experience Should You Have". Let's capture:
- "WE’RE HIRING! If you love data and are looking for unlimited growth opportunities, we want to talk with you about joining Further. Further is a data, cloud, and AI company whose focus is helping companies turn raw data into the right decisions. We have an award winning culture of extraordinary people. Our purpose is to enable people to thrive so that businesses can thrive. We believe that the work you do should matter - it should be meaningful to you professionally and personally, and it should have a positive impact on both you and our clients. If this sounds exciting to you, let’s chat!"
- Then after job title: "We’re hiring a client services leader who grows accounts through value creation. This person leads a portfolio of enterprise customers by translating strategy into measurable outcomes, shaping multi-quarter transformation roadmaps across data, cloud, and AI, and coaching account teams to consistently deliver (and prove) business impact. You bring executive presence, a consulting mindset, and a track record of driving multi-million-dollar YoY growth by building trusted relationships, identifying high-impact use cases, and operationalizing value realization."
We should keep that as prose. Could be two paragraphs.
Responsibilities: from "What You’ll Be Doing In This Role" paragraph:
"Own the commercial health, growth, and executive relationships for a portfolio of enterprise accounts
Run QBRs/EBRs that prove financial ROI, not just adoption — quantify value in terms a CFO cares about
Identify and close expansion opportunities independently, without waiting for GTM to prompt it
Coach and hold accountable the CS/PM/delivery talent supporting your accounts"
These are bullet points; we can make
- .
Also "What You'll Need To Accomplish In Your First Year" could be considered responsibilities or objectives. It includes:
"Own $2–3M account portfolio and grow it by 20%, including leading at least one renewal negotiation independently
Deliver Executive Business Reviews that quantify ROI
Build a 12-month account growth plan for each account in your portfolio, tied to the client's fiscal year budget and goals"
We could include these under Responsibilities as additional bullet points, or maybe under a separate section like "Goals". But we only have allowed headings; we could add them to Responsibilities as they are also responsibilities. That seems fine.
Thus Responsibilities list will combine both sets.
Requirements: the required experience bullet list (the numbered list). Let's capture exactly:
"10–15+ years managing enterprise client relationships in consulting, professional services, or technology/data services, with direct ownership of account revenue and growth targets (not just relationship management)
Demonstrated track record growing a $2M+ portfolio at 20%+ YoY, including leading renewal and expansion negotiations
Experience owning executive relationships at VP/SVP/C-suite level — including running Executive Business Reviews you set the agenda for, not just attend
Commercial fluency: deal structuring, margin/pricing tradeoffs, and revenue forecasting you're accountable for
Enough fluency in AI and data concepts to hold a credible strategic conversation with a client's CDO or VP Analytics without a technical lead in the room"
We need to preserve the bullet points; we can turn into
- .
Qualifications: nice-to-have list:
"Experience building account plans tied to NRR/expansion (not just satisfaction scores)
Exposure to cloud ecosystems (Adobe, Google Cloud, etc.)
Experience partnering with engineering/solution teams on adoption, not just technical delivery"
We'll put as
- .
Benefits: the paragraph about total rewards program.
"Our total rewards program is designed for your protection, peace of mind, and overall well-being. In addition to our outstanding basics, we offer a net-zero cost medical option, company contributions to your HSA, fertility support, fully-paid parental leave, a monthly stipend for your lifestyle spending account, and much more."
We'll put as
. We must not include any boilerplate like "Apply today or check out all our opportunities!" or data privacy statements. Remove those. Now produce HTML fragment. We need to ensure we don't include any extra text outside HTML. No markdown fences. Let's craft:
About the role
WE’RE HIRING! If you love data and are looking for unlimited growth opportunities, we want to talk with you about joining Further. Further is a data, cloud, and AI company whose focus is helping companies turn raw data into the right decisions. We have an award winning culture of extraordinary people. Our purpose is to enable people to thrive so that businesses can thrive. We believe that the work you do should matter - it should be meaningful to you professionally and personally, and it should have a positive impact on both you and our clients. If this sounds exciting to you, let’s chat!
We’re hiring a client services leader who grows accounts through value creation. This person leads a portfolio of enterprise customers by translating strategy into measurable outcomes, shaping multi-quarter transformation roadmaps across data, cloud, and AI, and coaching account teams to consistently deliver (and prove) business impact. You bring executive presence, a consulting mindset, and a track record of driving multi-million-dollar YoY growth by building trusted relationships, identifying high-impact use cases, and operationalizing value realization.
Responsibilities
- Own the commercial health, growth, and executive relationships for a portfolio of enterprise accounts
- Run QBRs/EBRs that prove financial ROI, not just adoption — quantify value in terms a CFO cares about
- Identify and close expansion opportunities independently, without waiting for GTM to prompt it
- Coach and hold accountable the CS/PM/delivery talent supporting your accounts
- Own $2–3M account portfolio and grow it by 20%, including leading at least one renewal negotiation independently
- Deliver Executive Business Reviews that quantify ROI
- Build a 12-month account growth plan for each account in your portfolio, tied to the client's fiscal year budget and goals
Requirements
- 10–15+ years managing enterprise client relationships in consulting, professional services, or technology/data services, with direct ownership of account revenue and growth targets (not just relationship management)
- Demonstrated track record growing a $2M+ portfolio at 20%+ YoY, including leading renewal and expansion negotiations
- Experience owning executive relationships at VP/SVP/C-suite level — including running Executive Business Reviews you set the agenda for, not just attend
- Commercial fluency: deal structuring, margin/pricing tradeoffs, and revenue forecasting you're accountable for
- Enough fluency in AI and data concepts to hold a credible strategic conversation with a client's CDO or VP Analytics without a technical lead in the room
Qualifications
- Experience building account plans tied to NRR/expansion (not just satisfaction scores)
- Exposure to cloud ecosystems (Adobe, Google Cloud, etc.)
- Experience partnering with engineering/solution teams on adoption, not just technical delivery
Benefits
Our total rewards program is designed for your protection, peace of mind, and overall well-being. In addition to our outstanding basics, we offer a net-zero cost medical option, company contributions to your HSA
- .
Benefits: the paragraph about total rewards program.
"Our total rewards program is designed for your protection, peace of mind, and overall well-being. In addition to our outstanding basics, we offer a net-zero cost medical option, company contributions to your HSA, fertility support, fully-paid parental leave, a monthly stipend for your lifestyle spending account, and much more."
We'll put as
- .
Qualifications: nice-to-have list:
"Experience building account plans tied to NRR/expansion (not just satisfaction scores)
Exposure to cloud ecosystems (Adobe, Google Cloud, etc.)
Experience partnering with engineering/solution teams on adoption, not just technical delivery"
We'll put as
- .
Also "What You'll Need To Accomplish In Your First Year" could be considered responsibilities or objectives. It includes:
"Own $2–3M account portfolio and grow it by 20%, including leading at least one renewal negotiation independently
Deliver Executive Business Reviews that quantify ROI
Build a 12-month account growth plan for each account in your portfolio, tied to the client's fiscal year budget and goals"
We could include these under Responsibilities as additional bullet points, or maybe under a separate section like "Goals". But we only have allowed headings; we could add them to Responsibilities as they are also responsibilities. That seems fine.
Thus Responsibilities list will combine both sets.
Requirements: the required experience bullet list (the numbered list). Let's capture exactly:
"10–15+ years managing enterprise client relationships in consulting, professional services, or technology/data services, with direct ownership of account revenue and growth targets (not just relationship management)
Demonstrated track record growing a $2M+ portfolio at 20%+ YoY, including leading renewal and expansion negotiations
Experience owning executive relationships at VP/SVP/C-suite level — including running Executive Business Reviews you set the agenda for, not just attend
Commercial fluency: deal structuring, margin/pricing tradeoffs, and revenue forecasting you're accountable for
Enough fluency in AI and data concepts to hold a credible strategic conversation with a client's CDO or VP Analytics without a technical lead in the room"
We need to preserve the bullet points; we can turn into