Technical Program Manager, Public Sector
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all specifics: responsibilities bullet points, qualifications bullet points, benefits details, pay range, schedule (location-based hybrid policy: at least 25% time in office), minimum education, field of study, years of experience (correlates with internal job level - not specific number; but we should keep as is? It says "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position". That's vague; maybe we should not include if it's not specific? It's still substantive but vague. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar: "Years of experience required will correlate with the internal job level requirements". That's somewhat vague but not placeholder like TBD. Might be okay to include. However we could combine into Requirements paragraph.
We also have "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience". That's specific.
"Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience". That's vague but okay.
"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.
"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." That's maybe part of Benefits or Requirements? Could be under Benefits? It's more about logistics. Could be under Requirements? Not exactly. Could be its own section? Not listed as allowed headings; we have Benefits, Pay, Schedule. Visa sponsorship could be under Benefits? Might be considered part of Benefits. But we could include it under Benefits as a bullet.
We must not include application instructions like "We encourage you to apply..." etc. Also "Not all strong candidates will meet every single qualification..." etc. That's boilerplate encouraging underrepresented groups; could be considered EEO? Might be considered boilerplate; better to remove.
Also "We think AI systems..." etc. That's mission statement; could be part of About Anthropic but we already have About the role? Actually we have About Anthropic mission at top. 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 should have About the role heading, not About Anthropic. The About Anthropic description could be considered part of About the role? Might be considered company overview; but we could include it under About the role as prose. The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can have About the role heading and include the mission description there.
Thus structure:
About the role
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. About The Role Claude is used across government, from US federal civilian agencies to national security, state and local, and allied international governments, and nearly every model and product Anthropic ships has public sector work on the end of it. Each of those segments runs under its own regulatory and deployment constraints, so delivering Claude to them means standing up compliant infrastructure with cloud partners, landing new models in restricted environments, bringing our application suite to parity with commercial, and clearing frameworks like FedRAMP, repeated for every segment. We're hiring a Technical Program Manager to own that program. Today that coordination is spread across the public sector product and engineering leads and the many teams they pull in: research, infrastructure, security, compliance, and product engineering. You'll become the single owner of that program, the person who knows where every workstream stands, what it is waiting on, and who needs to decide. Over time, government customers get new models and products on a predictable cadence, authorizations like FedRAMP run as a steady program rather than a one-off push, and each new segment takes less bespoke effort than the last.
Then Responsibilities:
Responsibilities
- Own the program for delivering new Claude models into public sector environments: sequencing, dependencies, and tradeoffs across research, inference and capacity, cloud partners, safeguards, and compliance teams
- Drive FedRAMP and similar authorization programs for Anthropic's public sector offerings, working with privacy, security, compliance, and platform engineering
- Plan and sequence work across public sector segments, from model and API availability to application parity and segment-specific product work
- Represent public sector requirements in model launch planning alongside the launch TPMs
- Establish the operating rhythm: a single view of workstreams, owners, dependencies, risks, and status, with planning, escalation paths, and launch coordination across orgs
- Convert recurring efforts into documented, repeatable processes so that each new segment or model requires less bespoke coordination
Then Requirements/Qualifications: we can combine as Requirements.
Requirements
- Several years of experience in technical program management, with a track record of successfully delivering complex, cross-functional programs
- Have shipped software or infrastructure into regulated or restricted environments (government clouds, air-gapped deployments, FedRAMP or similar authorization frameworks) and can engage meaningfully with the infrastructure, ML, and security engineers doing the work
- Experience coordinating across multiple engineering teams and organizations simultaneously, including research, security, and compliance partners
- Highly organized and can manage multiple parallel workstreams effectively across distributed teams
- Thrive in unstructured environments with a knack for bringing order to chaos and creating clarity in ambiguous situations
- Excellent written and verbal communication skills, with the ability to influence without authority
- Have worked on public sector, defense, or government cloud programs, or hold or are eligible for a US security clearance (preferred but not required)
- Are passionate about Anthropic's mission and interested in the challenges of bringing AI capabilities to public institutions safely and reliably
- Are a US person. We have agreements with the US Government that mandate this for these roles.
- 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
But note: "Are a US person..." is a requirement; we keep.
We might also include visa sponsorship under Benefits? Could be under Benefits as bullet: "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."
But we already have a Benefits section; we can add that.
Benefits:
Benefits
- 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
- 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.
Pay:
Pay
Annual Salary $365,000—$435,000 USD
Schedule:
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.
We should not include any other sections like Skills.
Check for any duplicated lines: we have not duplicated.
We removed boilerplate: safety scam warning, guidance on AI usage, "We encourage you to apply...", "Not all strong candidates will meet every single qualification...", "We think AI systems..." etc. Also removed "How We're Different" section.
Check that we preserved all substantive information: mission, about the role description, responsibilities list, qualifications list (including US person requirement, education, field of study, years of experience), benefits list (including visa sponsorship), pay, schedule. Did we miss any? The "Logistics" section also includes Minimum education, field of study, years of experience, location-based hybrid policy, visa sponsorship. We covered those. Also we missed "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" (included). "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience" (included). "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all specifics: responsibilities bullet points, qualifications bullet points, benefits details, pay range, schedule (location-based hybrid policy: at least 25% time in office), minimum education, field of study, years of experience (correlates with internal job level - not specific number; but we should keep as is? It says "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position". That's vague; maybe we should not include if it's not specific? It's still substantive but vague. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar: "Years of experience required will correlate with the internal job level requirements". That's somewhat vague but not placeholder like TBD. Might be okay to include. However we could combine into Requirements paragraph. We also have "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience". That's specific. "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience". That's vague but okay. "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. "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." That's maybe part of Benefits or Requirements? Could be under Benefits? It's more about logistics. Could be under Requirements? Not exactly. Could be its own section? Not listed as allowed headings; we have Benefits, Pay, Schedule. Visa sponsorship could be under Benefits? Might be considered part of Benefits. But we could include it under Benefits as a bullet. We must not include application instructions like "We encourage you to apply..." etc. Also "Not all strong candidates will meet every single qualification..." etc. That's boilerplate encouraging underrepresented groups; could be considered EEO? Might be considered boilerplate; better to remove. Also "We think AI systems..." etc. That's mission statement; could be part of About Anthropic but we already have About the role? Actually we have About Anthropic mission at top. 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 should have About the role heading, not About Anthropic. The About Anthropic description could be considered part of About the role? Might be considered company overview; but we could include it under About the role as prose. The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can have About the role heading and include the mission description there.
Thus structure:
About the role
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. About The Role Claude is used across government, from US federal civilian agencies to national security, state and local, and allied international governments, and nearly every model and product Anthropic ships has public sector work on the end of it. Each of those segments runs under its own regulatory and deployment constraints, so delivering Claude to them means standing up compliant infrastructure with cloud partners, landing new models in restricted environments, bringing our application suite to parity with commercial, and clearing frameworks like FedRAMP, repeated for every segment. We're hiring a Technical Program Manager to own that program. Today that coordination is spread across the public sector product and engineering leads and the many teams they pull in: research, infrastructure, security, compliance, and product engineering. You'll become the single owner of that program, the person who knows where every workstream stands, what it is waiting on, and who needs to decide. Over time, government customers get new models and products on a predictable cadence, authorizations like FedRAMP run as a steady program rather than a one-off push, and each new segment takes less bespoke effort than the last.
Then Responsibilities:Responsibilities
- Own the program for delivering new Claude models into public sector environments: sequencing, dependencies, and tradeoffs across research, inference and capacity, cloud partners, safeguards, and compliance teams
- Drive FedRAMP and similar authorization programs for Anthropic's public sector offerings, working with privacy, security, compliance, and platform engineering
- Plan and sequence work across public sector segments, from model and API availability to application parity and segment-specific product work
- Represent public sector requirements in model launch planning alongside the launch TPMs
- Establish the operating rhythm: a single view of workstreams, owners, dependencies, risks, and status, with planning, escalation paths, and launch coordination across orgs
- Convert recurring efforts into documented, repeatable processes so that each new segment or model requires less bespoke coordination
Requirements
- Several years of experience in technical program management, with a track record of successfully delivering complex, cross-functional programs
- Have shipped software or infrastructure into regulated or restricted environments (government clouds, air-gapped deployments, FedRAMP or similar authorization frameworks) and can engage meaningfully with the infrastructure, ML, and security engineers doing the work
- Experience coordinating across multiple engineering teams and organizations simultaneously, including research, security, and compliance partners
- Highly organized and can manage multiple parallel workstreams effectively across distributed teams
- Thrive in unstructured environments with a knack for bringing order to chaos and creating clarity in ambiguous situations
- Excellent written and verbal communication skills, with the ability to influence without authority
- Have worked on public sector, defense, or government cloud programs, or hold or are eligible for a US security clearance (preferred but not required)
- Are passionate about Anthropic's mission and interested in the challenges of bringing AI capabilities to public institutions safely and reliably
- Are a US person. We have agreements with the US Government that mandate this for these roles.
- 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
Benefits
- 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
- 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.
Pay
Annual Salary $365,000—$435,000 USD
Schedule: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.
We should not include any other sections like Skills. Check for any duplicated lines: we have not duplicated. We removed boilerplate: safety scam warning, guidance on AI usage, "We encourage you to apply...", "Not all strong candidates will meet every single qualification...", "We think AI systems..." etc. Also removed "How We're Different" section. Check that we preserved all substantive information: mission, about the role description, responsibilities list, qualifications list (including US person requirement, education, field of study, years of experience), benefits list (including visa sponsorship), pay, schedule. Did we miss any? The "Logistics" section also includes Minimum education, field of study, years of experience, location-based hybrid policy, visa sponsorship. We covered those. Also we missed "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience" (included). "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience" (included). "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position