Staff Software Engineer: Compute
for headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes "Annual Salary $320,000—$485,000 USD". That's pay. Also "Deadline to apply: None. Applications will be reviewed on a rolling basis." That's application instruction, should be removed. Also "Logistics Minimum education: Bachelor’s degree or an equivalent combination..." etc. That's requirements. Also "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? It's about location/hybrid. Could be schedule section? The instruction: include Schedule section only if posting actually states them. It does state location-based hybrid policy. Could treat as schedule. But we might combine into Requirements or Benefits? Probably schedule is separate. However, we need to decide if we want a Schedule section. The posting says: "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 info. So we can include a Schedule section with that content.
Benefits: The posting mentions "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. 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." So we can include Benefits section with those bullet points.
Qualifications/Skills: The posting includes "You may be a good fit if you Have 8+ years of experience building software, with strong full-stack skills and solid grounding in data modeling, APIs, and databases..." etc. Also "Strong candidates may also have Experience in datacenters..." etc. Also "Candidates need not have 100% of the skills listed above Formal certifications or education credentials Direct machine learning or AI research experience". Also "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". That's qualifications.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information. So we need to include all details from the posting, but we can reorganize into sections.
We must not include boilerplate like "We think AI systems like the ones we're building have enormous social and ethical implications..." That's maybe not boilerplate but it's about representation etc. Might be considered EEO/equal-opportunity boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove paragraphs about representation, imposter syndrome, safety, scam warnings, etc. Also remove "How We're Different" section? That might be considered boilerplate? It's about company culture but maybe not EEO. However it's somewhat generic. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The "How We're Different" is not exactly that, but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The "How We're Different" includes details about their research directions, collaborative group, etc. That might be substantive. But it's not directly about the role. Might be considered company overview. The instruction says we can include About the role section; we already have an "About The Role" paragraph earlier. The "How We're Different" might be considered extra company info, not required. But we could keep it under About the role? However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company info into About the role? But we already have About the role content. The "How We're Different" is separate. Might be considered boilerplate? Not sure. Safer to omit it as it's not directly about the role and could be considered fluff. However the instruction says do NOT invent or summarize away detail. If we omit it, we are summarizing away detail. But maybe it's considered boilerplate? It's not EEO, but it's about company culture. The instruction didn't explicitly say to remove company culture. But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep "How We're Different" if it's not those. However it's pretty generic. But we need to decide.
Given the instruction to prefer few substantive sections, we could include About the role (which already includes the mission and role description). The "How We're Different" could be considered part of About the role or maybe we could add a section "About Anthropic" but that's not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "About Anthropic". So we must fit content into those headings. The "How We're Different" could go under About the role (maybe as extra prose). But About the role already has a paragraph about the role. We could append that content there.
Similarly, the "Guidance on Candidates' AI Usage" is likely application instruction, remove.
Also "Come work with us! Anthropic is a public benefit corporation..." is benefits? Actually that's benefits and company info. We already have benefits.
Thus we will produce sections:
About the role
with prose summarizing the role description (the paragraphs under "About The Role").
Responsibilities
with - each bullet from Responsibilities list.
Requirements
maybe combine qualifications and skills? But we have separate headings for Requirements, Qualifications, Skills. The instruction: use headings for those if content exists. We have content for Requirements (minimum education, years of experience, location-based hybrid policy? Actually location-based hybrid is schedule). We have Qualifications (the "You may be a good fit if you" list). We have Skills (the "Strong candidates may also have" list). Also we have "Candidates need not have 100% of the skills listed above Formal certifications or education credentials Direct machine learning or AI research experience" - that's a note about qualifications.
We need to decide what to put where. Let's map:
- 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.
These could be under Requirements (or maybe Qualifications). The "You may be a good fit if you" list is more like Qualifications/Skills. The "Strong candidates may also have" list is Skills.
Thus we can have:
Requirements
with - for each of the bullet points: Bachelor's degree..., Field of study..., Minimum years of experience..., Location-based hybrid policy..., Visa sponsorship...
Qualifications
with - for the "You may be a good fit if you" bullet points.
Skills
with - for the "Strong candidates may also have" bullet points.
Benefits: bullet list.
Pay:
with the salary range.
Schedule: maybe we already included location-based hybrid policy under Requirements; but we could also have a Schedule section. However we already used that info. To avoid duplication, we should not duplicate. So we could put location-based hybrid policy under Schedule instead of Requirements. But we also have visa sponsorship etc. Which is more appropriate for Requirements? Visa sponsorship is not a requirement but a company offering. Could be under Benefits? Actually visa sponsorship is a benefit/condition. Could be under Benefits. But the instruction says include Benefits section only when posting has real, specific content for it. It does mention visa sponsorship. So we could include visa sponsorship under Benefits.
Thus we need to allocate:
Requirements: Minimum education, Field of study, Minimum years of experience.
Schedule: Location-based hybrid policy.
Benefits: Visa sponsorship, competitive compensation and benefits (but compensation already in Pay), optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space.
Pay: Annual Salary $320,000—$485,000 USD.
We also have "We offer competitive compensation and benefits" which is somewhat redundant with Pay and Benefits. We'll keep benefits as listed.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
We need to remove duplicated lines. Ensure we don't repeat same info.
Now craft HTML.
We'll start with
About the role
then containing the prose from "About The Role". Let's extract that paragraph:
"At Anthropic, we're building AI systems that are safe, beneficial, and transformative. Our mission is to develop AI that benefits humanity, and we believe the most powerful capabilities emerge when we thoughtfully bridge the gap between research breakthroughs and real-world applications. Frontier AI runs on datacenters, and the world is in the middle of the largest infrastructure buildout in a generation. The binding constraint on progress is increasingly everything around the chips: land, power, permits, equipment, and the design and construction of the buildings themselves. Bringing a single site online involves hundreds of people, thousands of components, and decisions that move enormous amounts of capital. Much of that work still runs on spreadsheets and handoffs. At Anthropic, we're building software and Claude-powered tools to help Anthropic scale out its compute, and we think there's an enormous opportunity to rethink how that work gets done. It's early, it's already having a real impact, and the engineers who join now will shape how one of the most consequential buildouts in the world gets done. We're looking for strong, versatile software engineers who love building for people doing real work in the physical world. You'll embed with the teams that source sites, design buildings, procure equipment, and manage construction, learn their work deeply, and build the tools and systems they rely on every day. Datacenter experience is a big plus, but what matters most is that you can earn the trust of expert operators, model a messy domain cleanly, and move fast."
We'll put that in
.
Now Responsibilities: list each bullet:
- Build the core systems that track a datacenter's lifecycle (sites, designs, bills of materials, equipment, and construction progress) in one trusted, permissioned source of truth
- Embed with datacenter, energy, and supply chain teams to understand how the work actually gets done, find
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes "Annual Salary $320,000—$485,000 USD". That's pay. Also "Deadline to apply: None. Applications will be reviewed on a rolling basis." That's application instruction, should be removed. Also "Logistics Minimum education: Bachelor’s degree or an equivalent combination..." etc. That's requirements. Also "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? It's about location/hybrid. Could be schedule section? The instruction: include Schedule section only if posting actually states them. It does state location-based hybrid policy. Could treat as schedule. But we might combine into Requirements or Benefits? Probably schedule is separate. However, we need to decide if we want a Schedule section. The posting says: "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 info. So we can include a Schedule section with that content. Benefits: The posting mentions "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. 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." So we can include Benefits section with those bullet points. Qualifications/Skills: The posting includes "You may be a good fit if you Have 8+ years of experience building software, with strong full-stack skills and solid grounding in data modeling, APIs, and databases..." etc. Also "Strong candidates may also have Experience in datacenters..." etc. Also "Candidates need not have 100% of the skills listed above Formal certifications or education credentials Direct machine learning or AI research experience". Also "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". That's qualifications. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information. So we need to include all details from the posting, but we can reorganize into sections. We must not include boilerplate like "We think AI systems like the ones we're building have enormous social and ethical implications..." That's maybe not boilerplate but it's about representation etc. Might be considered EEO/equal-opportunity boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove paragraphs about representation, imposter syndrome, safety, scam warnings, etc. Also remove "How We're Different" section? That might be considered boilerplate? It's about company culture but maybe not EEO. However it's somewhat generic. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The "How We're Different" is not exactly that, but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The "How We're Different" includes details about their research directions, collaborative group, etc. That might be substantive. But it's not directly about the role. Might be considered company overview. The instruction says we can include About the role section; we already have an "About The Role" paragraph earlier. The "How We're Different" might be considered extra company info, not required. But we could keep it under About the role? However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine company info into About the role? But we already have About the role content. The "How We're Different" is separate. Might be considered boilerplate? Not sure. Safer to omit it as it's not directly about the role and could be considered fluff. However the instruction says do NOT invent or summarize away detail. If we omit it, we are summarizing away detail. But maybe it's considered boilerplate? It's not EEO, but it's about company culture. The instruction didn't explicitly say to remove company culture. But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep "How We're Different" if it's not those. However it's pretty generic. But we need to decide. Given the instruction to prefer few substantive sections, we could include About the role (which already includes the mission and role description). The "How We're Different" could be considered part of About the role or maybe we could add a section "About Anthropic" but that's not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add a custom heading like "About Anthropic". So we must fit content into those headings. The "How We're Different" could go under About the role (maybe as extra prose). But About the role already has a paragraph about the role. We could append that content there. Similarly, the "Guidance on Candidates' AI Usage" is likely application instruction, remove. Also "Come work with us! Anthropic is a public benefit corporation..." is benefits? Actually that's benefits and company info. We already have benefits. Thus we will produce sections:
About the role
with prose summarizing the role description (the paragraphs under "About The Role").Responsibilities
with- each bullet from Responsibilities list.
Requirements
maybe combine qualifications and skills? But we have separate headings for Requirements, Qualifications, Skills. The instruction: use headings for those if content exists. We have content for Requirements (minimum education, years of experience, location-based hybrid policy? Actually location-based hybrid is schedule). We have Qualifications (the "You may be a good fit if you" list). We have Skills (the "Strong candidates may also have" list). Also we have "Candidates need not have 100% of the skills listed above Formal certifications or education credentials Direct machine learning or AI research experience" - that's a note about qualifications. We need to decide what to put where. Let's map: - 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. These could be under Requirements (or maybe Qualifications). The "You may be a good fit if you" list is more like Qualifications/Skills. The "Strong candidates may also have" list is Skills. Thus we can have:Requirements
with- for each of the bullet points: Bachelor's degree..., Field of study..., Minimum years of experience..., Location-based hybrid policy..., Visa sponsorship...
Qualifications
with- for the "You may be a good fit if you" bullet points.
Skills
with- for the "Strong candidates may also have" bullet points.
Benefits: bullet list.
Pay:
with the salary range. Schedule: maybe we already included location-based hybrid policy under Requirements; but we could also have a Schedule section. However we already used that info. To avoid duplication, we should not duplicate. So we could put location-based hybrid policy under Schedule instead of Requirements. But we also have visa sponsorship etc. Which is more appropriate for Requirements? Visa sponsorship is not a requirement but a company offering. Could be under Benefits? Actually visa sponsorship is a benefit/condition. Could be under Benefits. But the instruction says include Benefits section only when posting has real, specific content for it. It does mention visa sponsorship. So we could include visa sponsorship under Benefits. Thus we need to allocate: Requirements: Minimum education, Field of study, Minimum years of experience. Schedule: Location-based hybrid policy. Benefits: Visa sponsorship, competitive compensation and benefits (but compensation already in Pay), optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. Pay: Annual Salary $320,000—$485,000 USD. We also have "We offer competitive compensation and benefits" which is somewhat redundant with Pay and Benefits. We'll keep benefits as listed. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove duplicated lines. Ensure we don't repeat same info. Now craft HTML. We'll start with
About the role
thencontaining the prose from "About The Role". Let's extract that paragraph: "At Anthropic, we're building AI systems that are safe, beneficial, and transformative. Our mission is to develop AI that benefits humanity, and we believe the most powerful capabilities emerge when we thoughtfully bridge the gap between research breakthroughs and real-world applications. Frontier AI runs on datacenters, and the world is in the middle of the largest infrastructure buildout in a generation. The binding constraint on progress is increasingly everything around the chips: land, power, permits, equipment, and the design and construction of the buildings themselves. Bringing a single site online involves hundreds of people, thousands of components, and decisions that move enormous amounts of capital. Much of that work still runs on spreadsheets and handoffs. At Anthropic, we're building software and Claude-powered tools to help Anthropic scale out its compute, and we think there's an enormous opportunity to rethink how that work gets done. It's early, it's already having a real impact, and the engineers who join now will shape how one of the most consequential buildouts in the world gets done. We're looking for strong, versatile software engineers who love building for people doing real work in the physical world. You'll embed with the teams that source sites, design buildings, procure equipment, and manage construction, learn their work deeply, and build the tools and systems they rely on every day. Datacenter experience is a big plus, but what matters most is that you can earn the trust of expert operators, model a messy domain cleanly, and move fast." We'll put that in
. Now Responsibilities: list each bullet: - Build the core systems that track a datacenter's lifecycle (sites, designs, bills of materials, equipment, and construction progress) in one trusted, permissioned source of truth - Embed with datacenter, energy, and supply chain teams to understand how the work actually gets done, find
- for the "Strong candidates may also have" bullet points.
Benefits: bullet list.
Pay:
- for the "You may be a good fit if you" bullet points.
- for each of the bullet points: Bachelor's degree..., Field of study..., Minimum years of experience..., Location-based hybrid policy..., Visa sponsorship...