Manager, Customer Success – Cyber
for each heading. Use - for lists. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content.
We need to parse the posting.
Key content:
- About Anthropic (mission) maybe not needed? The instruction: "About Anthropic" is not a required heading; we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have "About The Role" paragraph: description of role. That's "About the role". So we put that in
About the role
with content.
Responsibilities: list of bullet points under "Responsibilities". We'll output
- each.
Requirements/Qualifications: The posting has "You May Be a Good Fit If You Have ..." which is qualifications. Also "Minimum education: Bachelor’s degree..." etc. Also "Logistics" includes Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship. Those are qualifications/requirements. We'll combine into a Requirements section (or Qualifications). Since we have both headings possible, we need to decide. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we can also combine. Better to separate: Requirements could be the "You May Be a Good Fit If You Have ..." list (experience, skills). Qualifications could be the logistics: education, field of study, years of experience, location policy, visa sponsorship. However the instruction says prefer a few substantive sections over many thin ones. Might be better to have one Requirements section covering all. But we have both headings allowed; we could include both if they have substantive content. Let's see.
"You May Be a Good Fit If You Have" includes bullet-like sentences (though not bullet list). It's a paragraph with multiple criteria separated by line breaks? Actually it's a paragraph with sentences separated by line breaks? In the text it's a paragraph with line breaks? It appears as a block of sentences each starting with capital letter. We can turn each into
- . That would be a list of qualifications.
Then "Minimum education: Bachelor’s degree or an equivalent combination..." etc. That's also qualifications.
Thus we could have a single Requirements section with all those items as
- . That would be substantive.
Skills: maybe we can extract skills from the qualifications: technical fluency, executive presence, business acumen, etc. But those are already in qualifications. Could create Skills section but might be thin. Better to not create Skills if not distinct.
Benefits: The posting mentions at end: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." That's benefits. So we can create Benefits section with those items as list.
Pay: The posting includes "Annual Salary $265,000—$320,000 USD". Also mention OTE etc. So we can create Pay section with that info.
Schedule: The posting includes "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." That's schedule/hybrid expectation. So we can create Schedule section with that.
We should not include boilerplate like EEO, scam warning, etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We can paraphrase but must preserve all info. Safer to keep the sentences as is, maybe split into list items.
Let's extract each piece.
About the role paragraph:
"As Manager, Customer Success – Cyber, you'll lead the Customer Success Managers who cover our cybersecurity accounts: the security, identity, cloud, data protection and observability vendors building on Claude across API, Claude Code, Cowork and other surfaces, both inside their own engineering and security organizations and embedded in the products they sell to their customers. You'll directly coach and develop a team of 5-10 CSMs while keeping strategic oversight of the highest-impact engagements in the segment. This role demands exceptional people leadership combined with deep product knowledge, cybersecurity domain expertise and customer success acumen to guide your team in maximizing customer value, driving consumption, and expanding our footprint across enterprise accounts. You'll be instrumental in building scalable CS processes, methodologies, and playbooks that will define how we grow and mature as an organization."
We'll put that in
.
Responsibilities list: each bullet after "Responsibilities". Let's extract:
- Directly manage and develop a team of 5-10 Customer Success Managers supporting strategic cybersecurity accounts across all Anthropic products (API, Claude.ai, Claude Code)
- Coach team members on customer success best practices, including change management and adoption strategies, value realization, and expansion methodologies across our product suite
- Provide cybersecurity subject matter expertise to cyber customers and the CSMs supporting them: bring domain knowledge of security operations, detection and response, identity, cloud and data protection to customer engagements, and coach the team on how cyber vendors build, buy and embed AI so they can engage credibly with CISOs, CTOs and principal engineers
- Drive team accountability to core CS metrics: expansion (consumption growth, cross-sell/upsell opportunity identification), customer health scores, retention (NRR), and customer satisfaction (CSAT)
- Join strategic customer engagements and escalations, demonstrating executive presence with C-level stakeholders at leading cybersecurity companies
- Build and refine scalable CS processes including success planning frameworks, QBR templates, and expansion playbooks
- Partner closely with Sales to identify expansion opportunities, facilitate smooth handoffs, and ensure aligned account strategies
- Collaborate cross-functionally with Product, Engineering, and Marketing to advocate for customer needs and drive product adoption
- Contribute to hiring, onboarding, and training initiatives as the Customer Success organization scales
- Establish and nurture an AI-first, innovation-focused team culture, improving team processes and deepening team hands-on expertise
- Conduct regular 1:1s, performance reviews, and career development planning for direct reports
- Own portfolio-level planning and forecasting, including renewal risk mitigation and expansion pipeline development
- Serve as escalation point for at-risk accounts and complex customer situations within your team's portfolio
- Develop customer advocacy programs including case studies, testimonials, and reference architecture development
- Champion responsible AI deployment practices with customers and represent Anthropic's values in all customer interactions
We'll output each as
- .
Requirements/Qualifications: combine "You May Be a Good Fit If You Have" and logistics.
"You May Be a Good Fit If You Have" sentences:
- 7+ years of experience in customer success, account management, or customer-facing roles, with 2+ years of front-line management experience
- Proven track record of managing and building customer success teams in SaaS, API, or AI/ML companies
- Cybersecurity experience: time spent working with or inside cybersecurity companies, or in a security-adjacent domain (security operations, detection and response, identity, cloud or data security), with the fluency to act as a credible subject matter expert for cyber customers and your team
- Experience managing customer portfolios at enterprise scale, including accounts with $1M-$100M+ annual contract values
- Strong understanding of both consumption-based and seat-based business models, with proven ability to drive adoption, expansion, and value realization across different pricing structures
- Technical fluency to understand AI/ML products, navigate technical conversations, and coach teams on product capabilities across multiple offerings
- Strong executive presence and ability to represent Anthropic with customer technical and business leaders
- Strong business acumen with ability to articulate value, calculate ROI, and drive customer business outcomes
- Ability to balance strategic thinking with tactical execution and context-switch between coaching, customer engagement, and operational planning
- Experience building CS processes, playbooks and operational frameworks, using data to drive team and customer outcomes
- Demonstrated ability to coach customer success professionals and systematically improve team performance against KPIs
- Track record of achieving team targets for expansion, retention and customer satisfaction
- Passion for responsible AI development and helping customers transform their businesses with cutting-edge technology
Now logistics:
- Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience
- Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience
- Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position
- Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.
- Visa sponsorship: We do sponsor visas! However, we aren't able to successfully sponsor visas for every role and every candidate. But if we make you an offer, we will make every reasonable effort to get you a visa, and we retain an immigration lawyer to help with this.
We could include these as list items as well.
But note: "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position" is vague; but it's still substantive? It's basically saying experience required correlates with internal level. Might be considered filler? It's not a specific number. The instruction says do not emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Requirements section, we can include it if it's substantive. This line is somewhat vague but still conveys that experience required aligns with internal level. Might be okay.
We could omit that line if we think it's filler. But it's not exactly placeholder like "N/A". It's a statement. I'd keep it.
Now Benefits: list:
- competitive compensation and benefits
- optional equity donation matching
- generous vacation and parental leave
- flexible working hours
- lovely office space in which to collaborate with colleagues
We could phrase as list items.
Pay: "Annual Salary $265,000—$320,000 USD". Also note OTE explanation: "For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role." This role is not sales? It's Manager, Customer Success – Cyber. Might not be sales. But the note is generic. We can include the salary range and note about OTE if relevant. The instruction: preserve all substantive information. So include that note.
Thus Pay section:
Annual Salary $265,000—$320,000 USD. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role.
Schedule: from Location-based hybrid policy: "Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." Also maybe mention visa sponsorship? That's not schedule. So schedule section: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.
We should not include the "Visa sponsorship" line under schedule; maybe we could put under Requirements as a qualification? It's more about logistics. Could be part of Requirements. But we already have many items; we could add it as
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content. We need to parse the posting. Key content: - About Anthropic (mission) maybe not needed? The instruction: "About Anthropic" is not a required heading; we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "About The Role" paragraph: description of role. That's "About the role". So we put that in
About the role
withcontent. Responsibilities: list of bullet points under "Responsibilities". We'll output
- each. Requirements/Qualifications: The posting has "You May Be a Good Fit If You Have ..." which is qualifications. Also "Minimum education: Bachelor’s degree..." etc. Also "Logistics" includes Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship. Those are qualifications/requirements. We'll combine into a Requirements section (or Qualifications). Since we have both headings possible, we need to decide. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we can also combine. Better to separate: Requirements could be the "You May Be a Good Fit If You Have ..." list (experience, skills). Qualifications could be the logistics: education, field of study, years of experience, location policy, visa sponsorship. However the instruction says prefer a few substantive sections over many thin ones. Might be better to have one Requirements section covering all. But we have both headings allowed; we could include both if they have substantive content. Let's see. "You May Be a Good Fit If You Have" includes bullet-like sentences (though not bullet list). It's a paragraph with multiple criteria separated by line breaks? Actually it's a paragraph with sentences separated by line breaks? In the text it's a paragraph with line breaks? It appears as a block of sentences each starting with capital letter. We can turn each into
- . That would be a list of qualifications. Then "Minimum education: Bachelor’s degree or an equivalent combination..." etc. That's also qualifications. Thus we could have a single Requirements section with all those items as
- . That would be substantive.
Skills: maybe we can extract skills from the qualifications: technical fluency, executive presence, business acumen, etc. But those are already in qualifications. Could create Skills section but might be thin. Better to not create Skills if not distinct.
Benefits: The posting mentions at end: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." That's benefits. So we can create Benefits section with those items as list.
Pay: The posting includes "Annual Salary $265,000—$320,000 USD". Also mention OTE etc. So we can create Pay section with that info.
Schedule: The posting includes "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." That's schedule/hybrid expectation. So we can create Schedule section with that.
We should not include boilerplate like EEO, scam warning, etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We can paraphrase but must preserve all info. Safer to keep the sentences as is, maybe split into list items.
Let's extract each piece.
About the role paragraph:
"As Manager, Customer Success – Cyber, you'll lead the Customer Success Managers who cover our cybersecurity accounts: the security, identity, cloud, data protection and observability vendors building on Claude across API, Claude Code, Cowork and other surfaces, both inside their own engineering and security organizations and embedded in the products they sell to their customers. You'll directly coach and develop a team of 5-10 CSMs while keeping strategic oversight of the highest-impact engagements in the segment. This role demands exceptional people leadership combined with deep product knowledge, cybersecurity domain expertise and customer success acumen to guide your team in maximizing customer value, driving consumption, and expanding our footprint across enterprise accounts. You'll be instrumental in building scalable CS processes, methodologies, and playbooks that will define how we grow and mature as an organization."
We'll put that in
. Responsibilities list: each bullet after "Responsibilities". Let's extract: - Directly manage and develop a team of 5-10 Customer Success Managers supporting strategic cybersecurity accounts across all Anthropic products (API, Claude.ai, Claude Code) - Coach team members on customer success best practices, including change management and adoption strategies, value realization, and expansion methodologies across our product suite - Provide cybersecurity subject matter expertise to cyber customers and the CSMs supporting them: bring domain knowledge of security operations, detection and response, identity, cloud and data protection to customer engagements, and coach the team on how cyber vendors build, buy and embed AI so they can engage credibly with CISOs, CTOs and principal engineers - Drive team accountability to core CS metrics: expansion (consumption growth, cross-sell/upsell opportunity identification), customer health scores, retention (NRR), and customer satisfaction (CSAT) - Join strategic customer engagements and escalations, demonstrating executive presence with C-level stakeholders at leading cybersecurity companies - Build and refine scalable CS processes including success planning frameworks, QBR templates, and expansion playbooks - Partner closely with Sales to identify expansion opportunities, facilitate smooth handoffs, and ensure aligned account strategies - Collaborate cross-functionally with Product, Engineering, and Marketing to advocate for customer needs and drive product adoption - Contribute to hiring, onboarding, and training initiatives as the Customer Success organization scales - Establish and nurture an AI-first, innovation-focused team culture, improving team processes and deepening team hands-on expertise - Conduct regular 1:1s, performance reviews, and career development planning for direct reports - Own portfolio-level planning and forecasting, including renewal risk mitigation and expansion pipeline development - Serve as escalation point for at-risk accounts and complex customer situations within your team's portfolio - Develop customer advocacy programs including case studies, testimonials, and reference architecture development - Champion responsible AI deployment practices with customers and represent Anthropic's values in all customer interactions We'll output each as
- .
Requirements/Qualifications: combine "You May Be a Good Fit If You Have" and logistics.
"You May Be a Good Fit If You Have" sentences:
- 7+ years of experience in customer success, account management, or customer-facing roles, with 2+ years of front-line management experience
- Proven track record of managing and building customer success teams in SaaS, API, or AI/ML companies
- Cybersecurity experience: time spent working with or inside cybersecurity companies, or in a security-adjacent domain (security operations, detection and response, identity, cloud or data security), with the fluency to act as a credible subject matter expert for cyber customers and your team
- Experience managing customer portfolios at enterprise scale, including accounts with $1M-$100M+ annual contract values
- Strong understanding of both consumption-based and seat-based business models, with proven ability to drive adoption, expansion, and value realization across different pricing structures
- Technical fluency to understand AI/ML products, navigate technical conversations, and coach teams on product capabilities across multiple offerings
- Strong executive presence and ability to represent Anthropic with customer technical and business leaders
- Strong business acumen with ability to articulate value, calculate ROI, and drive customer business outcomes
- Ability to balance strategic thinking with tactical execution and context-switch between coaching, customer engagement, and operational planning
- Experience building CS processes, playbooks and operational frameworks, using data to drive team and customer outcomes
- Demonstrated ability to coach customer success professionals and systematically improve team performance against KPIs
- Track record of achieving team targets for expansion, retention and customer satisfaction
- Passion for responsible AI development and helping customers transform their businesses with cutting-edge technology
Now logistics:
- Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience
- Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience
- Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position
- Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.
- Visa sponsorship: We do sponsor visas! However, we aren't able to successfully sponsor visas for every role and every candidate. But if we make you an offer, we will make every reasonable effort to get you a visa, and we retain an immigration lawyer to help with this.
We could include these as list items as well.
But note: "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position" is vague; but it's still substantive? It's basically saying experience required correlates with internal level. Might be considered filler? It's not a specific number. The instruction says do not emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Requirements section, we can include it if it's substantive. This line is somewhat vague but still conveys that experience required aligns with internal level. Might be okay.
We could omit that line if we think it's filler. But it's not exactly placeholder like "N/A". It's a statement. I'd keep it.
Now Benefits: list:
- competitive compensation and benefits
- optional equity donation matching
- generous vacation and parental leave
- flexible working hours
- lovely office space in which to collaborate with colleagues
We could phrase as list items.
Pay: "Annual Salary $265,000—$320,000 USD". Also note OTE explanation: "For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role." This role is not sales? It's Manager, Customer Success – Cyber. Might not be sales. But the note is generic. We can include the salary range and note about OTE if relevant. The instruction: preserve all substantive information. So include that note.
Thus Pay section:
Annual Salary $265,000—$320,000 USD. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role.
Schedule: from Location-based hybrid policy: "Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." Also maybe mention visa sponsorship? That's not schedule. So schedule section:Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.
We should not include the "Visa sponsorship" line under schedule; maybe we could put under Requirements as a qualification? It's more about logistics. Could be part of Requirements. But we already have many items; we could add it as