Product Manager, Safeguards (Generalist)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings for sections that have real content. We should not repeat job title. We need to preserve all substantive info, remove boilerplate like cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. The posting includes many paragraphs; we need to extract relevant content. We need sections: - About the role: content from "About The Role" paragraph(s). Likely combine the paragraphs after "About The Role" up to before "Responsibilities". Let's extract: "Anthropic is dedicated to developing AI assistants that are helpful, harmless, and honest. As usage of our AI services grows, we need to ensure they are not misused. The Safeguards team is at the forefront of protecting our users from the risks of powerful AIs as well as ethical, technical, and social risks from the use of generative AI. The Safeguards team at Anthropic builds protections for new AI features enabled by the research teams and protects new products and surfaces developed by our product teams. As a Product Manager for the Safeguards team at Anthropic, you will own the ideation, design, development and deployment of Safeguards systems and relevant product UX to ensure we are advancing frontier models safely to users across various cloud platforms. You will work closely with our research and product teams to develop detections, evals, interventions, and tools to measure and mitigate deployment and user risks. We are looking for a product manager who is deeply committed to making AI safe and beneficial for humanity. You are aware of the risks and are committed to working with experts and coming up with ideas for Anthropic to implement. You have deep technical expertise in development, deployment and measurement of Safeguards systems. You thrive in rapidly moving and ambiguous environments." That's the About the role. - Responsibilities: list bullet points from "Responsibilities" section. The text after "Responsibilities" includes multiple sentences each starting with a capital letter, maybe each is a responsibility. We need to turn each into
- ...
explaining. But we must not include placeholder text. It's real info. We'll include. - Benefits: from "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 maybe earlier: "Anthropic is a public benefit corporation headquartered in San Francisco." That's not benefit. We'll include benefits as list. - 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 visa sponsorship? That's not schedule. We'll include schedule as that. We also need to maybe include "Visa sponsorship" but not a heading; could be placed in a
under maybe "Logistics"? But we are not required to have a Logistics heading; we could incorporate into Schedule or Benefits? Better to keep as a short paragraph under maybe "Logistics" but we don't have a heading for that. The instruction says only use those headings; we can embed other info in paragraphs under existing sections or as a general
before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra
not under headings. But we should prefer few substantive sections. We could add a
for logistics like visa sponsorship, location, etc. But maybe better to incorporate into Schedule section (since it's about location/time). Visa sponsorship could be a separate short paragraph under maybe "Benefits"? Not exactly. Could be its own section but not in allowed headings. Safer to add a
after the sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should follow that pattern. It says "Prefer a few substantive sections over many thin ones." So we can keep to those headings and put other info as paragraphs within those sections or as a general
before first heading? Probably okay to have a
for general info like "About Anthropic" maybe not needed. But we can include a brief intro paragraph before sections. We must not include boilerplate like EEO, scam warning, etc. Remove duplicated lines. Let's craft HTML:
About the role
Anthropic is dedicated to developing AI assistants that are helpful, harmless, and honest. As usage of our AI services grows, we need to ensure they are not misused. The Safeguards team is at the forefront of protecting our users from the risks of powerful AIs as well as ethical, technical, and social risks from the use of generative AI. The Safeguards team at Anthropic builds protections for new AI features enabled by the research teams and protects new products and surfaces developed by our product teams. As a Product Manager for the Safeguards team at Anthropic, you will own the ideation, design, development and deployment of Safeguards systems and relevant product UX to ensure we are advancing frontier models safely to users across various cloud platforms. You will work closely with our research and product teams to develop detections, evals, interventions, and tools to measure and mitigate deployment and user risks. We are looking for a product manager who is deeply committed to making AI safe and beneficial for humanity. You are aware of the risks and are committed to working with experts and coming up with ideas for Anthropic to implement. You have deep technical expertise in development, deployment and measurement of Safeguards systems. You thrive in rapidly moving and ambiguous environments.
Responsibilities
- Determine how to build in safety by design upstream and leverage downstream defenses for Anthropic’s frontier models, AI products, customers on different surfaces - Claude.ai, 1P API, external Cloud providers.
- Ability to write safety evals and communicate externally about safety.
- Drive impact via ruthless prioritization by clearly defining problems, solution options forward, clarity on both business & technical tradeoffs and accordingly clear requirements toward MVP vs. ideal state.
- Align & collaborate with policy, enforcement, research, engineering and cross functional stakeholders.
- Understand the AI landscape and ecosystem to plan for mitigation of deployment risks of increasingly powerful models and determined adversaries.
- Lead the development of metrics to understand the area, performance, blindspots to help inform future project planning.
Minimum Qualifications
- Ability to make technical tradeoff decisions; ideally with experience working across policy experts, AI/ML research engineers and software engineering teams to design and build state of the art safety systems.
- Strong user understanding of how our products are used, their Safeguards concerns and how we provide the best solutions.
- Demonstrated ability to build product and engineering strategy across multiple cross-functional teams for a rapidly changing space.
- Demonstrated experience in designing and building metrics to evaluate risks, system performance, user impact and making crisp tradeoffs
- Very strong ability to navigate, and prioritize amidst rapidly changing product specs, and to flex into different domains to bring clarity and execute.
- Evidence of exercising judgment and decision making in ambiguous situations.
- Planning, building, launching and measuring new products / systems in a zero to one environment.
- Ability to clearly articulate complex technical concepts to non-technical audiences in written and verbal communication.
- Think creatively about the risks and benefits of new technologies, and think beyond past checklists and playbooks.
Preferred Qualifications
- 5+ years in product management with a focus on fast problem understanding, building roadmaps with tractable progress, ability to get into the details on data, detection & interventions, infrastructure & tools, and/or evals.
Pay
The annual compensation range for this role is $385,000—$460,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.
Benefits
- Competitive compensation