Manager, Customer Success – Cyber
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. The posting includes "About The Role" then "Responsibilities", then "You May Be a Good Fit If You Have" (which is qualifications/requirements). Also there is "The annual compensation range for this role is listed below." That's Pay. Also "Logistics" includes education, location, visa sponsorship etc. That could be considered Requirements or Qualifications? The instruction: Use headings for sections only when posting has real, specific content. We need to include sections: About the role, Responsibilities, Requirements (or Qualifications), Pay. Possibly Benefits? The posting mentions benefits in "How We're Different" section: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". That's benefits content. So we can include Benefits section. Schedule? Not explicitly stated besides location-based hybrid policy: "Currently, we expect all staff to be in one of our offices at least 25% of the time." That's schedule/hybrid expectation. Could be Schedule section. But we should only include if real specific content. It says location-based hybrid policy: expect staff to be in office at least 25% of the time. That's specific enough. So we can include Schedule.
We must not include boilerplate like EEO, scam warning, etc. Remove those.
We need to preserve all substantive information. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to avoid creating sections with filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About the role: The paragraph after "About The Role". It includes multiple sentences. We'll put that in
under
About the role
.
Responsibilities: list after "Responsibilities". It's a bullet list but not marked with bullets in text; each line starts with a verb. We'll convert to - items.
Requirements/Qualifications: The "You May Be a Good Fit If You Have" section lists qualifications. We'll treat as Requirements (or Qualifications). Use
- .
Pay: The compensation range: "Annual Salary $265,000—$320,000 USD". Also note about OTE for sales roles but this is not sales? It's manager CS. Still we include the range. We'll put in
.
Benefits: From "How We're Different": "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." Also earlier: "Anthropic is a public benefit corporation headquartered in San Francisco. 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. We'll put in
- items? It's a list separated by commas. Could make
- each item. But we need to preserve all substantive information; we can split.
Schedule: 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 logistics but not schedule. Visa sponsorship is not schedule; maybe we could include under Requirements? But it's not a requirement; it's logistics. The instruction says we can include Schedule only if posting actually states them. It does state hybrid policy. We'll include Schedule section with that info.
We should also maybe include "Logistics" like minimum education, visa sponsorship. Could be part of Requirements or Qualifications? The instruction: Use headings for sections only when posting has real, specific content. We could include a "Qualifications" section that includes education, experience, etc. But we already have Requirements from "You May Be a Good Fit". However the posting also includes "Minimum education: Bachelor’s degree or an equivalent combination..." and "Required field of study: A field relevant to the role..." and "Minimum years of experience: Years of experience required will correlate with the internal job level requirements". That's also qualifications. We could merge them into Requirements/Qualifications section. But we must not invent headings; we can use either Requirements or Qualifications. The instruction list includes both as possible headings. We need to decide which to use. Since we have both experience/skills and education, we could use "Qualifications" heading to cover education, field of study, years of experience, plus the "You May Be a Good Fit" list. Or we could use "Requirements". Either is fine. Let's pick "Qualifications". We'll include all qualification-related content under that.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits, Schedule.
Now we need to ensure we don't include any boilerplate like "We encourage you to apply even if you do not believe you meet every single qualification." That's more of a motivational note; it's still substantive? It's not a requirement but it's part of posting. Should we keep? It's not boilerplate; it's a encouragement. Might be considered part of the posting but not a list. Could be included as a
under Qualifications or About the role? It appears after the qualifications list. It's a paragraph encouraging applications. We'll keep it as a
under Qualifications maybe after the list.
Also "We think AI systems like the ones we're building have enormous social and ethical implications..." etc. That's more about company values; could be considered part of About Anthropic? Already we have About Anthropic at top but we are not to repeat job title as heading; but we could include an "About Anthropic" section? Not in the allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says use those for section headings. Likely we should only use those headings. The "About Anthropic" is not in list; we could drop it or incorporate into About the role? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings like About Anthropic, but the list of examples suggests we should stick to those. Safer to only use those headings. So we will omit the initial "About Anthropic" paragraph. However we need to preserve ALL substantive information. If we drop it, we lose info about Anthropic's mission etc. That is substantive. But maybe we can incorporate that into About the role section? The About the role section already includes description of role; we could prepend the mission etc. But that might be mixing. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have an "About the role" section that includes both the role description and maybe company mission? But the heading is About the role, not About Anthropic. Could still include mission as part of role context. It's not violating.
Thus we will include the Anthropic mission paragraph inside About the role
before the role description.
Now let's extract exact text.
Anthropic’s mission: "Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems."
Then "About The Role 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 combine mission + role description into one
maybe two
s? Could be separate paragraphs. We'll put mission in one
, then role description in another
under same heading.
Now Responsibilities list: each line starts with a verb. We'll extract each bullet.
List:
- 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
Now Qualifications: includes education, field of study, minimum years of experience (correlates with internal job level), plus the "You May Be a Good Fit If You Have" list, plus the encouragement paragraph.
Let's extract education etc:
- 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
Now "You May Be a Good Fit If You Have" list:
- 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
for prose. We need to avoid creating sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About the role: The paragraph after "About The Role". It includes multiple sentences. We'll put that in
under
About the role
. Responsibilities: list after "Responsibilities". It's a bullet list but not marked with bullets in text; each line starts with a verb. We'll convert to- items.
Requirements/Qualifications: The "You May Be a Good Fit If You Have" section lists qualifications. We'll treat as Requirements (or Qualifications). Use
- .
Pay: The compensation range: "Annual Salary $265,000—$320,000 USD". Also note about OTE for sales roles but this is not sales? It's manager CS. Still we include the range. We'll put in
. Benefits: From "How We're Different": "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." Also earlier: "Anthropic is a public benefit corporation headquartered in San Francisco. 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. We'll put in
- items? It's a list separated by commas. Could make
- each item. But we need to preserve all substantive information; we can split.
Schedule: 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 logistics but not schedule. Visa sponsorship is not schedule; maybe we could include under Requirements? But it's not a requirement; it's logistics. The instruction says we can include Schedule only if posting actually states them. It does state hybrid policy. We'll include Schedule section with that info.
We should also maybe include "Logistics" like minimum education, visa sponsorship. Could be part of Requirements or Qualifications? The instruction: Use headings for sections only when posting has real, specific content. We could include a "Qualifications" section that includes education, experience, etc. But we already have Requirements from "You May Be a Good Fit". However the posting also includes "Minimum education: Bachelor’s degree or an equivalent combination..." and "Required field of study: A field relevant to the role..." and "Minimum years of experience: Years of experience required will correlate with the internal job level requirements". That's also qualifications. We could merge them into Requirements/Qualifications section. But we must not invent headings; we can use either Requirements or Qualifications. The instruction list includes both as possible headings. We need to decide which to use. Since we have both experience/skills and education, we could use "Qualifications" heading to cover education, field of study, years of experience, plus the "You May Be a Good Fit" list. Or we could use "Requirements". Either is fine. Let's pick "Qualifications". We'll include all qualification-related content under that.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits, Schedule.
Now we need to ensure we don't include any boilerplate like "We encourage you to apply even if you do not believe you meet every single qualification." That's more of a motivational note; it's still substantive? It's not a requirement but it's part of posting. Should we keep? It's not boilerplate; it's a encouragement. Might be considered part of the posting but not a list. Could be included as a
under Qualifications or About the role? It appears after the qualifications list. It's a paragraph encouraging applications. We'll keep it as a
under Qualifications maybe after the list. Also "We think AI systems like the ones we're building have enormous social and ethical implications..." etc. That's more about company values; could be considered part of About Anthropic? Already we have About Anthropic at top but we are not to repeat job title as heading; but we could include an "About Anthropic" section? Not in the allowed headings list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says use those for section headings. Likely we should only use those headings. The "About Anthropic" is not in list; we could drop it or incorporate into About the role? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings like About Anthropic, but the list of examples suggests we should stick to those. Safer to only use those headings. So we will omit the initial "About Anthropic" paragraph. However we need to preserve ALL substantive information. If we drop it, we lose info about Anthropic's mission etc. That is substantive. But maybe we can incorporate that into About the role section? The About the role section already includes description of role; we could prepend the mission etc. But that might be mixing. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have an "About the role" section that includes both the role description and maybe company mission? But the heading is About the role, not About Anthropic. Could still include mission as part of role context. It's not violating. Thus we will include the Anthropic mission paragraph inside About the role
before the role description. Now let's extract exact text. Anthropic’s mission: "Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems." Then "About The Role 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 combine mission + role description into one
maybe two
s? Could be separate paragraphs. We'll put mission in one
, then role description in another
under same heading. Now Responsibilities list: each line starts with a verb. We'll extract each bullet. List: - 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 Now Qualifications: includes education, field of study, minimum years of experience (correlates with internal job level), plus the "You May Be a Good Fit If You Have" list, plus the encouragement paragraph. Let's extract education etc: - 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 Now "You May Be a Good Fit If You Have" list: - 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
- each item. But we need to preserve all substantive information; we can split.
Schedule: 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 logistics but not schedule. Visa sponsorship is not schedule; maybe we could include under Requirements? But it's not a requirement; it's logistics. The instruction says we can include Schedule only if posting actually states them. It does state hybrid policy. We'll include Schedule section with that info.
We should also maybe include "Logistics" like minimum education, visa sponsorship. Could be part of Requirements or Qualifications? The instruction: Use headings for sections only when posting has real, specific content. We could include a "Qualifications" section that includes education, experience, etc. But we already have Requirements from "You May Be a Good Fit". However the posting also includes "Minimum education: Bachelor’s degree or an equivalent combination..." and "Required field of study: A field relevant to the role..." and "Minimum years of experience: Years of experience required will correlate with the internal job level requirements". That's also qualifications. We could merge them into Requirements/Qualifications section. But we must not invent headings; we can use either Requirements or Qualifications. The instruction list includes both as possible headings. We need to decide which to use. Since we have both experience/skills and education, we could use "Qualifications" heading to cover education, field of study, years of experience, plus the "You May Be a Good Fit" list. Or we could use "Requirements". Either is fine. Let's pick "Qualifications". We'll include all qualification-related content under that.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits, Schedule.
Now we need to ensure we don't include any boilerplate like "We encourage you to apply even if you do not believe you meet every single qualification." That's more of a motivational note; it's still substantive? It's not a requirement but it's part of posting. Should we keep? It's not boilerplate; it's a encouragement. Might be considered part of the posting but not a list. Could be included as a
- items? It's a list separated by commas. Could make
- .
Pay: The compensation range: "Annual Salary $265,000—$320,000 USD". Also note about OTE for sales roles but this is not sales? It's manager CS. Still we include the range. We'll put in