Applied AI Engineer, Beneficial Deployments (Life Sciences)
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Guidance on Candidates' AI Usage" maybe considered boilerplate? It's about policy for using AI in application process - maybe considered application instructions? Might be considered boilerplate; but it's not exactly scam warning. However it's about application process; likely we should remove as it's application instructions. Also "We encourage you to apply even if you do not believe you meet every single qualification." That's application encouragement; maybe considered application instructions? Might be considered boilerplate; but it's substantive encouragement? The instruction says remove application instructions. So we should remove that paragraph.
Also "We think AI systems like the ones we're building have enormous social and ethical implications..." that's maybe part of mission; keep? It's not boilerplate; it's about representation. Might be okay.
We need to include sections: About the role (maybe combine About Anthropic and About Beneficial Deployments? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings like About the role, Responsibilities, Requirements (maybe "You Might Be a Good Fit If" corresponds to Requirements/Qualifications/Skills), Benefits, Pay, Schedule.
We need to decide what content goes where.
We have:
- About Anthropic (mission, team)
- About Beneficial Deployments (mission)
- About The Role (description)
- Responsibilities (list)
- You Might Be a Good Fit If You Have ... (list of qualifications/skills)
- The annual compensation range ... (Pay)
- Logistics (Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship) - could be considered Requirements or maybe separate but we can embed in Requirements? The instruction says include a section only when posting has real specific content. We have content for Pay (salary range). We have content for Schedule? Not explicit schedule besides location-based hybrid policy (office at least 25% of time). That's schedule-ish. Could be Schedule section.
We have Benefits? Not explicitly listed except later: "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. So we can include Benefits section.
We have Requirements? Could be from "You Might Be a Good Fit If You Have ..." plus logistics (education, experience). We'll put those under Requirements (or Qualifications/Skills). The instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide which to use. Probably combine into Requirements (or Qualifications). We'll make a Requirements section containing education, experience, field of study, and the "You Might Be a Good Fit If" bullet list.
We also have Skills? Could be separate but we can incorporate.
We must not repeat job title as heading. Not include Job ID.
We must output only HTML fragment, no /, no markdown fences.
We need to use 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 keep all details from the sections we keep.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to identify duplicated lines: maybe some sentences repeated? Not obvious.
We need to remove "Guidance on Candidates' AI Usage: Learn about our policy for using AI in our application process." That's application instructions.
Also remove "We encourage you to apply even if you do not believe you meet every single qualification." etc.
Also remove "Not all strong candidates will meet every single qualification as listed." etc.
Also remove "Your safety matters to us. To protect yourself from potential scams, remember that Anthropic recruiters only contact you from @anthropic.com email addresses...." That's scam-warning boilerplate; remove.
Also remove "How We're Different ..."? That's maybe not boilerplate but could be considered generic; but it's substantive about company culture. Might keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We're Different" is not those; it's about company values. Could keep as maybe a section? But we only have headings for specific categories; we could incorporate into About the role or maybe a separate section like "About Anthropic" already covers mission. "How We're Different" could be considered part of About Anthropic. We could merge.
We also have "Come work with us! 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 and location; we already have Benefits section; we can incorporate location maybe in Benefits or Schedule? Not needed.
We need to ensure we don't create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (salary range). We have Benefits (explicit). We have Schedule? The posting mentions 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-ish; we can treat as Schedule section.
We also have Visa sponsorship info; could be part of Requirements or Logistics but we might include under Requirements as a note.
We must not create sections with filler like "commensurate with experience". We have specific salary range, so Pay section is valid.
Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? But we can combine.
We must not repeat job title as heading.
We need to preserve all substantive info from sections we keep.
Let's extract content:
About Anthropic:
- 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 Beneficial Deployments:
- Beneficial Deployments ensures AI reaches and benefits the communities that need it most. We partner with nonprofits, foundations, and mission-driven organizations to deploy Claude in education, global health, economic mobility, and life sciences — focusing on raising the floor for those who need it most.
About The Role:
- We're looking for an Applied AI Engineer to join our Beneficial Deployments team, focused on maximizing the impact of Claude in the life sciences. Our goal is ambitious: accelerate scientific progress from R&D through translation by an order of magnitude. That means making Claude the go-to tool for the life sciences ecosystem from early discovery in academia to paradigm shifting biotech to reimaging pharma pipelines — and building the technical infrastructure to back that up. You'll work directly with flagship research partners like The Howard Hughes Medical Institute (HHMI) and The Allen Institute, embedded in their scientific workflows. This isn't consulting from the outside — you'll be building alongside their engineers, prototyping agents that fit into real research pipelines, and developing the ecosystem-level tooling (MCP servers, benchmarks, reusable agent skills) that extends Claude's usefulness across the broader life sciences community. This role will be part of the founding Beneficial Deployments Applied AI team focused on bringing life sciences closer to the frontier.
Responsibilities (list):
- Partner deeply with flagship life sciences research institutions — understand their scientific workflows end-to-end, build hands-on with their engineering teams, and help take projects from early exploration to production systems integrated into how they do science day-to-day.
- Develop reusable ecosystem infrastructure, like MCP servers for domain-specific data sources (genomics platforms, literature databases, experimental repositories), instruments, scientifically-grounded benchmarks, and agent skills that other institutions can adopt without starting from scratch.
- Identify what's actually hard about deploying AI in life sciences (heterogeneous data, auditability requirements, the prototype-to-trust gap) and feed those findings back to product, engineering, and research.
- Create technical content and documentation that lets partners self-serve, so what works for one institution can scale globally without the same level of hand-holding.
You Might Be a Good Fit If You Have (list):
- Deep research experience in life sciences, biomedical research, or scientific computing. Bonus if you've studied genomics, neuroscience, or drug discovery specifically and are comfortable getting deeply technical with academics.
- Experience building LLM-powered tools or applications: prompting, context engineering, agent architectures, evaluation frameworks.
- Builder credibility from shipping production code as a software engineer, forward-deployed engineer, or technical founder.
- A scrappy mentality–comfortable wearing multiple hats, building from scratch, driving clarity in ambiguous situations, and doing whatever it takes to further the mission.
Logistics (details):
- 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.
Benefits (from later):
- 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.
Pay:
- Annual Salary $280,000—$320,000 USD
Schedule: we have location-based hybrid policy (office at least 25% of time). Could be Schedule.
We also have "The annual compensation range for this role is listed below. 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 is extra clarification about Pay; we should include that in Pay section.
Now we need to format.
We'll produce:
About the role
... combine About Anthropic, About Beneficial Deployments, About The Role? Actually About the role heading should contain description of role. Could include the three paragraphs: About Anthropic, About Beneficial Deployments, About The Role. But maybe better to have About the role just the role description; but we have no heading for About Anthropic or Beneficial Deployments. 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Lik
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 keep all details from the sections we keep.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to identify duplicated lines: maybe some sentences repeated? Not obvious.
We need to remove "Guidance on Candidates' AI Usage: Learn about our policy for using AI in our application process." That's application instructions.
Also remove "We encourage you to apply even if you do not believe you meet every single qualification." etc.
Also remove "Not all strong candidates will meet every single qualification as listed." etc.
Also remove "Your safety matters to us. To protect yourself from potential scams, remember that Anthropic recruiters only contact you from @anthropic.com email addresses...." That's scam-warning boilerplate; remove.
Also remove "How We're Different ..."? That's maybe not boilerplate but could be considered generic; but it's substantive about company culture. Might keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We're Different" is not those; it's about company values. Could keep as maybe a section? But we only have headings for specific categories; we could incorporate into About the role or maybe a separate section like "About Anthropic" already covers mission. "How We're Different" could be considered part of About Anthropic. We could merge.
We also have "Come work with us! 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 and location; we already have Benefits section; we can incorporate location maybe in Benefits or Schedule? Not needed.
We need to ensure we don't create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (salary range). We have Benefits (explicit). We have Schedule? The posting mentions 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-ish; we can treat as Schedule section.
We also have Visa sponsorship info; could be part of Requirements or Logistics but we might include under Requirements as a note.
We must not create sections with filler like "commensurate with experience". We have specific salary range, so Pay section is valid.
Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? But we can combine.
We must not repeat job title as heading.
We need to preserve all substantive info from sections we keep.
Let's extract content:
About Anthropic:
- 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 Beneficial Deployments:
- Beneficial Deployments ensures AI reaches and benefits the communities that need it most. We partner with nonprofits, foundations, and mission-driven organizations to deploy Claude in education, global health, economic mobility, and life sciences — focusing on raising the floor for those who need it most.
About The Role:
- We're looking for an Applied AI Engineer to join our Beneficial Deployments team, focused on maximizing the impact of Claude in the life sciences. Our goal is ambitious: accelerate scientific progress from R&D through translation by an order of magnitude. That means making Claude the go-to tool for the life sciences ecosystem from early discovery in academia to paradigm shifting biotech to reimaging pharma pipelines — and building the technical infrastructure to back that up. You'll work directly with flagship research partners like The Howard Hughes Medical Institute (HHMI) and The Allen Institute, embedded in their scientific workflows. This isn't consulting from the outside — you'll be building alongside their engineers, prototyping agents that fit into real research pipelines, and developing the ecosystem-level tooling (MCP servers, benchmarks, reusable agent skills) that extends Claude's usefulness across the broader life sciences community. This role will be part of the founding Beneficial Deployments Applied AI team focused on bringing life sciences closer to the frontier.
Responsibilities (list):
- Partner deeply with flagship life sciences research institutions — understand their scientific workflows end-to-end, build hands-on with their engineering teams, and help take projects from early exploration to production systems integrated into how they do science day-to-day.
- Develop reusable ecosystem infrastructure, like MCP servers for domain-specific data sources (genomics platforms, literature databases, experimental repositories), instruments, scientifically-grounded benchmarks, and agent skills that other institutions can adopt without starting from scratch.
- Identify what's actually hard about deploying AI in life sciences (heterogeneous data, auditability requirements, the prototype-to-trust gap) and feed those findings back to product, engineering, and research.
- Create technical content and documentation that lets partners self-serve, so what works for one institution can scale globally without the same level of hand-holding.
You Might Be a Good Fit If You Have (list):
- Deep research experience in life sciences, biomedical research, or scientific computing. Bonus if you've studied genomics, neuroscience, or drug discovery specifically and are comfortable getting deeply technical with academics.
- Experience building LLM-powered tools or applications: prompting, context engineering, agent architectures, evaluation frameworks.
- Builder credibility from shipping production code as a software engineer, forward-deployed engineer, or technical founder.
- A scrappy mentality–comfortable wearing multiple hats, building from scratch, driving clarity in ambiguous situations, and doing whatever it takes to further the mission.
Logistics (details):
- 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.
Benefits (from later):
- 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.
Pay:
- Annual Salary $280,000—$320,000 USD
Schedule: we have location-based hybrid policy (office at least 25% of time). Could be Schedule.
We also have "The annual compensation range for this role is listed below. 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 is extra clarification about Pay; we should include that in Pay section.
Now we need to format.
We'll produce:
About the role
... combine About Anthropic, About Beneficial Deployments, About The Role? Actually About the role heading should contain description of role. Could include the three paragraphs: About Anthropic, About Beneficial Deployments, About The Role. But maybe better to have About the role just the role description; but we have no heading for About Anthropic or Beneficial Deployments. 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? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Lik
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we keep. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to identify duplicated lines: maybe some sentences repeated? Not obvious. We need to remove "Guidance on Candidates' AI Usage: Learn about our policy for using AI in our application process." That's application instructions. Also remove "We encourage you to apply even if you do not believe you meet every single qualification." etc. Also remove "Not all strong candidates will meet every single qualification as listed." etc. Also remove "Your safety matters to us. To protect yourself from potential scams, remember that Anthropic recruiters only contact you from @anthropic.com email addresses...." That's scam-warning boilerplate; remove. Also remove "How We're Different ..."? That's maybe not boilerplate but could be considered generic; but it's substantive about company culture. Might keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "How We're Different" is not those; it's about company values. Could keep as maybe a section? But we only have headings for specific categories; we could incorporate into About the role or maybe a separate section like "About Anthropic" already covers mission. "How We're Different" could be considered part of About Anthropic. We could merge. We also have "Come work with us! 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 and location; we already have Benefits section; we can incorporate location maybe in Benefits or Schedule? Not needed. We need to ensure we don't create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (salary range). We have Benefits (explicit). We have Schedule? The posting mentions 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-ish; we can treat as Schedule section. We also have Visa sponsorship info; could be part of Requirements or Logistics but we might include under Requirements as a note. We must not create sections with filler like "commensurate with experience". We have specific salary range, so Pay section is valid. Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? But we can combine. We must not repeat job title as heading. We need to preserve all substantive info from sections we keep. Let's extract content: About Anthropic: - 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 Beneficial Deployments: - Beneficial Deployments ensures AI reaches and benefits the communities that need it most. We partner with nonprofits, foundations, and mission-driven organizations to deploy Claude in education, global health, economic mobility, and life sciences — focusing on raising the floor for those who need it most. About The Role: - We're looking for an Applied AI Engineer to join our Beneficial Deployments team, focused on maximizing the impact of Claude in the life sciences. Our goal is ambitious: accelerate scientific progress from R&D through translation by an order of magnitude. That means making Claude the go-to tool for the life sciences ecosystem from early discovery in academia to paradigm shifting biotech to reimaging pharma pipelines — and building the technical infrastructure to back that up. You'll work directly with flagship research partners like The Howard Hughes Medical Institute (HHMI) and The Allen Institute, embedded in their scientific workflows. This isn't consulting from the outside — you'll be building alongside their engineers, prototyping agents that fit into real research pipelines, and developing the ecosystem-level tooling (MCP servers, benchmarks, reusable agent skills) that extends Claude's usefulness across the broader life sciences community. This role will be part of the founding Beneficial Deployments Applied AI team focused on bringing life sciences closer to the frontier. Responsibilities (list): - Partner deeply with flagship life sciences research institutions — understand their scientific workflows end-to-end, build hands-on with their engineering teams, and help take projects from early exploration to production systems integrated into how they do science day-to-day. - Develop reusable ecosystem infrastructure, like MCP servers for domain-specific data sources (genomics platforms, literature databases, experimental repositories), instruments, scientifically-grounded benchmarks, and agent skills that other institutions can adopt without starting from scratch. - Identify what's actually hard about deploying AI in life sciences (heterogeneous data, auditability requirements, the prototype-to-trust gap) and feed those findings back to product, engineering, and research. - Create technical content and documentation that lets partners self-serve, so what works for one institution can scale globally without the same level of hand-holding. You Might Be a Good Fit If You Have (list): - Deep research experience in life sciences, biomedical research, or scientific computing. Bonus if you've studied genomics, neuroscience, or drug discovery specifically and are comfortable getting deeply technical with academics. - Experience building LLM-powered tools or applications: prompting, context engineering, agent architectures, evaluation frameworks. - Builder credibility from shipping production code as a software engineer, forward-deployed engineer, or technical founder. - A scrappy mentality–comfortable wearing multiple hats, building from scratch, driving clarity in ambiguous situations, and doing whatever it takes to further the mission. Logistics (details): - 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. Benefits (from later): - 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. Pay: - Annual Salary $280,000—$320,000 USD Schedule: we have location-based hybrid policy (office at least 25% of time). Could be Schedule. We also have "The annual compensation range for this role is listed below. 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 is extra clarification about Pay; we should include that in Pay section. Now we need to format. We'll produce:
About the role
... combine About Anthropic, About Beneficial Deployments, About The Role? Actually About the role heading should contain description of role. Could include the three paragraphs: About Anthropic, About Beneficial Deployments, About The Role. But maybe better to have About the role just the role description; but we have no heading for About Anthropic or Beneficial Deployments. The instruction says use