Senior AI Software Engineer
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map sections accordingly. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings? Probably we should use those headings where appropriate. The posting has sections: About XCures (company description) maybe map to "About the role"? But they said do NOT repeat the job title as a heading (the page already shows it). The job title is Senior AI Software Engineer. So we can have "About the role" heading describing the role and impact. Then "Responsibilities" for Key Responsibilities. Then "Requirements" or "Qualifications" for qualifications. They also have "Skills" maybe not needed. "Benefits" for Benefits. "Pay" for Compensation (salary range). "Schedule" maybe not present; we should not create Schedule unless posting actually states it. There's no schedule info, so omit Schedule. Also "Location" maybe not a standard heading but we could include as a short p under About the role or separate? The instruction says only include a section when posting has real, specific content for it. Location is present: "Location xCures operates in a distributed, remote-first environment..." So we could include a section maybe "Location" but not in the list of headings given. The list is examples; we can use other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. Safer to stick to those headings and incorporate location info into About the role or maybe a short p after About the role. Additional Considerations could be part of Qualifications or maybe a separate section like "Additional Considerations" but not in list; we could incorporate into Qualifications or maybe a separate "Additional Considerations" heading but risk deviating. Probably better to keep to the given headings and place relevant info accordingly.
Thus sections:
- About the role: include company description (About XCures) and impact description (Here’s Where You’ll Make An Impact) plus location info maybe.
- Responsibilities: list from Key Responsibilities.
- Qualifications: list from Qualifications (Required and Bonus Points). Could separate Required and Bonus but still under Qualifications.
- Benefits: list from Benefits.
- Pay: compensation range.
We should not include Schedule.
We must preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits. Use
for prose.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Agency Notice:" etc. That's legal boilerplate; should remove. Also "All candidate information will be held in confidence and in accordance with EEOC guidelines." That's EEO boilerplate; remove. Also "Additional Considerations" includes diversity statement; that's not boilerplate? It's about encouraging diverse candidates; might be considered EEO but it's part of the posting's inclusive language. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that paragraph. Also "We recognize that people bring a wealth of experience..." that's also EEO-ish; remove. Also "xCures is an equal opportunity employer..." remove.
Also "Agency Notice:" remove.
Also "At this time, xCures does not offer sponsorship." That's maybe relevant to location/authorization; keep? It's about work authorization. Might be considered part of Location or Requirements. It's substantive: must already have authorization to work in US, no sponsorship. Keep that.
Also "Candidates may be located anywhere in the United States." Keep.
Also "The successful candidate must already have authorization to work in the United States." Keep.
Also "All candidate information will be held in confidence and in accordance with EEOC guidelines." Remove.
Also "We believe our people are our greatest asset..." that's benefits intro; keep.
Also "Great work deserves great support." keep.
Also "Our goal is to be a place where people genuinely want to build their careers..." keep.
Also "And more!" maybe vague; but it's part of benefits list; we can keep as part of benefits prose.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now craft HTML.
Structure:
About the role
About XCures ... (company description) ... Here’s Where You’ll Make An Impact ... (impact description) ... Location: xCures operates in a distributed, remote-first environment, with occasional travel to company offsites or key meetings throughout the year. Candidates may be located anywhere in the United States. The successful candidate must already have authorization to work in the United States. At this time, xCures does not offer sponsorship.
But we need to keep the location info as prose; maybe separate for location.
Better:
About the role
About XCures: The best of medicine should belong to everyone.... (full company description).
Here’s Where You’ll Make An Impact: xCures is looking for a Senior AI Software Engineer to help pioneer how AI gets used in one of the most regulated industries there is: healthcare.... (impact description).
Location: xCures operates in a distributed, remote-first environment, with occasional travel to company offsites or key meetings throughout the year. Candidates may be located anywhere in the United States. The successful candidate must already have authorization to work in the United States. At this time, xCures does not offer sponsorship.
Now Responsibilities:
Responsibilities
- Own software design and architecture, making technical decisions that hold up as we scale
- Write and ship production code across features and bug fixes, moving quickly without sacrificing quality
- Identify and clear roadblocks, technical or cross-team, that slow down delivery
- Partner with stakeholders across teams to land on solutions that serve company priorities, driving initiatives from idea to completion with minimal oversight
- Champion adoption of AI-forward development workflows across the engineering org, measured by increased velocity and reduced backlog
- Contribute to new platform and product deliverables as our architecture evolves
Qualifications:
We have Required and Bonus Points. Could combine into one list with subheadings? But we must use - for any list. Could have two separate
with headings Required:
etc. But headings must be only for section headings; we can use
for subheadings. That's fine.
Thus:
Qualifications
Required:
- 6+ years of professional software engineering experience
- Hands-on experience building AI-powered workflows and software
- Experience with AWS and GCP
- Strong proficiency in an object-oriented programming language
- Experience with database design and scaling
- Demonstrated experience with software performance and optimization
- Experience working in a highly regulated industry (e.g., healthcare, finance)
- Experience with event-driven architecture or CQRS
- Strong foundation in core computer science fundamentals and algorithmic thinking
- An agile, systems-level thinker who can diagnose ambiguous problems and drive to a solution using first-principles reasoning
- Self-directed: able to figure out what a task requires, identify who to loop in for missing details, and execute end to end
Bonus Points:
- Experience with data science or data engineering work
- A metrics-driven approach to evaluating your own and your team's output
Benefits:
Benefits
Great work deserves great support. We believe our people are our greatest asset, and we’re committed to supporting them with a strong, competitive benefits package. Our goal is to be a place where people genuinely want to build their careers, and our benefits are designed to support our team in the ways that matter most.
- Remote‑First
- Unlimited Paid Time Off and 13 Company Holidays
- Equity Package
- Paid Parental Leave
- Medical, Vision, and Dental
- Employer HSA Contribution
- Employer 401(k) Match
- STD, LTD, Life Insurance and Critical Illness Plans
- Employee Assistance Program
- Adoption Assistance
- Company Offsites
- Monthly Internet Allowance
- Professional Development Funds
- And more!
Pay:
Pay
The anticipated salary range for this role is $150,000 to $220,000.
We should not include Schedule.
Make sure no extra whitespace or markdown. Output only HTML fragment.
Check for any leftover boilerplate: removed EEO, diversity statement, agency notice, etc.
Check for duplicated lines: none.
Check for any mention of "Additional Considerations" removed.
Check for "Location" we included as a paragraph under About the role.
Check for "About XCures" description: we need to preserve all substantive information. Let's copy the About XCures paragraph exactly:
"About XCures The best of medicine should belong to everyone. Nobody dreams of becoming good at being a patient. We have people to love, things we want to do, and plans we hope to keep. Illness already asks enough of us. xCures® exists to give healthcare the capacity to care for everyone. Healthcare has more to give. Too much of its time, money, and talent goes into unnecessary work that keeps people waiting and drives up the cost of care. Freeing those resources can make excellent care possible for far more people. xCures understands a patient’s history across the places they receive care and keeps that understanding current. It puts trusted information in the hands of the people who need it, when they need it, and uses that knowledge to take on more of the administrative work around care. Every extracted data point traces back to the exact document and page it came from. Our ambition is to empower doctors to make better decisions, enable researchers to develop better treatments faster, and help healthcare organizations serve more people with fewer errors and lower costs. We work with diagnostic labs, providers, telehealth companies, health systems, payers, and consumer health platforms. We are a fully remote, venture-backed team that holds itself to the same standard as our product: trustworthy, precise, and purposeful. We are building for the lives people want to live."
We need to keep that exactly. Ensure we preserve line breaks? Not needed; just as a paragraph.
Now "Here’s Where You’ll Make An Impact" paragraph:
"xCures is looking for a Senior AI Software Engineer to help pioneer how AI gets used in one of the most regulated industries there is: healthcare. You will report directly to our Head of AI Engineering, designing and building systems that let us deliver more, faster, without giving up quality. You will help scale our technical foundation and performance as we grow. This is a chance to shape how AI-driven engineering
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. Safer to stick to those headings and incorporate location info into About the role or maybe a short p after About the role. Additional Considerations could be part of Qualifications or maybe a separate section like "Additional Considerations" but not in list; we could incorporate into Qualifications or maybe a separate "Additional Considerations" heading but risk deviating. Probably better to keep to the given headings and place relevant info accordingly.
Thus sections:
- About the role: include company description (About XCures) and impact description (Here’s Where You’ll Make An Impact) plus location info maybe.
- Responsibilities: list from Key Responsibilities.
- Qualifications: list from Qualifications (Required and Bonus Points). Could separate Required and Bonus but still under Qualifications.
- Benefits: list from Benefits.
- Pay: compensation range.
We should not include Schedule.
We must preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits. Use
for prose.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Agency Notice:" etc. That's legal boilerplate; should remove. Also "All candidate information will be held in confidence and in accordance with EEOC guidelines." That's EEO boilerplate; remove. Also "Additional Considerations" includes diversity statement; that's not boilerplate? It's about encouraging diverse candidates; might be considered EEO but it's part of the posting's inclusive language. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that paragraph. Also "We recognize that people bring a wealth of experience..." that's also EEO-ish; remove. Also "xCures is an equal opportunity employer..." remove.
Also "Agency Notice:" remove.
Also "At this time, xCures does not offer sponsorship." That's maybe relevant to location/authorization; keep? It's about work authorization. Might be considered part of Location or Requirements. It's substantive: must already have authorization to work in US, no sponsorship. Keep that.
Also "Candidates may be located anywhere in the United States." Keep.
Also "The successful candidate must already have authorization to work in the United States." Keep.
Also "All candidate information will be held in confidence and in accordance with EEOC guidelines." Remove.
Also "We believe our people are our greatest asset..." that's benefits intro; keep.
Also "Great work deserves great support." keep.
Also "Our goal is to be a place where people genuinely want to build their careers..." keep.
Also "And more!" maybe vague; but it's part of benefits list; we can keep as part of benefits prose.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now craft HTML.
Structure:
About the role
About XCures ... (company description) ... Here’s Where You’ll Make An Impact ... (impact description) ... Location: xCures operates in a distributed, remote-first environment, with occasional travel to company offsites or key meetings throughout the year. Candidates may be located anywhere in the United States. The successful candidate must already have authorization to work in the United States. At this time, xCures does not offer sponsorship.
But we need to keep the location info as prose; maybe separate for location.
Better:
About the role
About XCures: The best of medicine should belong to everyone.... (full company description).
Here’s Where You’ll Make An Impact: xCures is looking for a Senior AI Software Engineer to help pioneer how AI gets used in one of the most regulated industries there is: healthcare.... (impact description).
Location: xCures operates in a distributed, remote-first environment, with occasional travel to company offsites or key meetings throughout the year. Candidates may be located anywhere in the United States. The successful candidate must already have authorization to work in the United States. At this time, xCures does not offer sponsorship.
Now Responsibilities:
Responsibilities
- Own software design and architecture, making technical decisions that hold up as we scale
- Write and ship production code across features and bug fixes, moving quickly without sacrificing quality
- Identify and clear roadblocks, technical or cross-team, that slow down delivery
- Partner with stakeholders across teams to land on solutions that serve company priorities, driving initiatives from idea to completion with minimal oversight
- Champion adoption of AI-forward development workflows across the engineering org, measured by increased velocity and reduced backlog
- Contribute to new platform and product deliverables as our architecture evolves
Qualifications:
We have Required and Bonus Points. Could combine into one list with subheadings? But we must use - for any list. Could have two separate
with headings Required:
etc. But headings must be only for section headings; we can use
for subheadings. That's fine.
Thus:
Qualifications
Required:
- 6+ years of professional software engineering experience
- Hands-on experience building AI-powered workflows and software
- Experience with AWS and GCP
- Strong proficiency in an object-oriented programming language
- Experience with database design and scaling
- Demonstrated experience with software performance and optimization
- Experience working in a highly regulated industry (e.g., healthcare, finance)
- Experience with event-driven architecture or CQRS
- Strong foundation in core computer science fundamentals and algorithmic thinking
- An agile, systems-level thinker who can diagnose ambiguous problems and drive to a solution using first-principles reasoning
- Self-directed: able to figure out what a task requires, identify who to loop in for missing details, and execute end to end
Bonus Points:
- Experience with data science or data engineering work
- A metrics-driven approach to evaluating your own and your team's output
Benefits:
Benefits
Great work deserves great support. We believe our people are our greatest asset, and we’re committed to supporting them with a strong, competitive benefits package. Our goal is to be a place where people genuinely want to build their careers, and our benefits are designed to support our team in the ways that matter most.
- Remote‑First
- Unlimited Paid Time Off and 13 Company Holidays
- Equity Package
- Paid Parental Leave
- Medical, Vision, and Dental
- Employer HSA Contribution
- Employer 401(k) Match
- STD, LTD, Life Insurance and Critical Illness Plans
- Employee Assistance Program
- Adoption Assistance
- Company Offsites
- Monthly Internet Allowance
- Professional Development Funds
- And more!
Pay:
Pay
The anticipated salary range for this role is $150,000 to $220,000.
We should not include Schedule.
Make sure no extra whitespace or markdown. Output only HTML fragment.
Check for any leftover boilerplate: removed EEO, diversity statement, agency notice, etc.
Check for duplicated lines: none.
Check for any mention of "Additional Considerations" removed.
Check for "Location" we included as a paragraph under About the role.
Check for "About XCures" description: we need to preserve all substantive information. Let's copy the About XCures paragraph exactly:
"About XCures The best of medicine should belong to everyone. Nobody dreams of becoming good at being a patient. We have people to love, things we want to do, and plans we hope to keep. Illness already asks enough of us. xCures® exists to give healthcare the capacity to care for everyone. Healthcare has more to give. Too much of its time, money, and talent goes into unnecessary work that keeps people waiting and drives up the cost of care. Freeing those resources can make excellent care possible for far more people. xCures understands a patient’s history across the places they receive care and keeps that understanding current. It puts trusted information in the hands of the people who need it, when they need it, and uses that knowledge to take on more of the administrative work around care. Every extracted data point traces back to the exact document and page it came from. Our ambition is to empower doctors to make better decisions, enable researchers to develop better treatments faster, and help healthcare organizations serve more people with fewer errors and lower costs. We work with diagnostic labs, providers, telehealth companies, health systems, payers, and consumer health platforms. We are a fully remote, venture-backed team that holds itself to the same standard as our product: trustworthy, precise, and purposeful. We are building for the lives people want to live."
We need to keep that exactly. Ensure we preserve line breaks? Not needed; just as a paragraph.
Now "Here’s Where You’ll Make An Impact" paragraph:
"xCures is looking for a Senior AI Software Engineer to help pioneer how AI gets used in one of the most regulated industries there is: healthcare. You will report directly to our Head of AI Engineering, designing and building systems that let us deliver more, faster, without giving up quality. You will help scale our technical foundation and performance as we grow. This is a chance to shape how AI-driven engineering
for prose. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Agency Notice:" etc. That's legal boilerplate; should remove. Also "All candidate information will be held in confidence and in accordance with EEOC guidelines." That's EEO boilerplate; remove. Also "Additional Considerations" includes diversity statement; that's not boilerplate? It's about encouraging diverse candidates; might be considered EEO but it's part of the posting's inclusive language. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that paragraph. Also "We recognize that people bring a wealth of experience..." that's also EEO-ish; remove. Also "xCures is an equal opportunity employer..." remove. Also "Agency Notice:" remove. Also "At this time, xCures does not offer sponsorship." That's maybe relevant to location/authorization; keep? It's about work authorization. Might be considered part of Location or Requirements. It's substantive: must already have authorization to work in US, no sponsorship. Keep that. Also "Candidates may be located anywhere in the United States." Keep. Also "The successful candidate must already have authorization to work in the United States." Keep. Also "All candidate information will be held in confidence and in accordance with EEOC guidelines." Remove. Also "We believe our people are our greatest asset..." that's benefits intro; keep. Also "Great work deserves great support." keep. Also "Our goal is to be a place where people genuinely want to build their careers..." keep. Also "And more!" maybe vague; but it's part of benefits list; we can keep as part of benefits prose. We need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now craft HTML. Structure:
About the role
About XCures ... (company description) ... Here’s Where You’ll Make An Impact ... (impact description) ... Location: xCures operates in a distributed, remote-first environment, with occasional travel to company offsites or key meetings throughout the year. Candidates may be located anywhere in the United States. The successful candidate must already have authorization to work in the United States. At this time, xCures does not offer sponsorship.
But we need to keep the location info as prose; maybe separatefor location. Better:
About the role
About XCures: The best of medicine should belong to everyone.... (full company description).
Here’s Where You’ll Make An Impact: xCures is looking for a Senior AI Software Engineer to help pioneer how AI gets used in one of the most regulated industries there is: healthcare.... (impact description).
Location: xCures operates in a distributed, remote-first environment, with occasional travel to company offsites or key meetings throughout the year. Candidates may be located anywhere in the United States. The successful candidate must already have authorization to work in the United States. At this time, xCures does not offer sponsorship.
Now Responsibilities:Responsibilities
- Own software design and architecture, making technical decisions that hold up as we scale
- Write and ship production code across features and bug fixes, moving quickly without sacrificing quality
- Identify and clear roadblocks, technical or cross-team, that slow down delivery
- Partner with stakeholders across teams to land on solutions that serve company priorities, driving initiatives from idea to completion with minimal oversight
- Champion adoption of AI-forward development workflows across the engineering org, measured by increased velocity and reduced backlog
- Contribute to new platform and product deliverables as our architecture evolves
- for any list. Could have two separate
- with headings
- 6+ years of professional software engineering experience
- Hands-on experience building AI-powered workflows and software
- Experience with AWS and GCP
- Strong proficiency in an object-oriented programming language
- Experience with database design and scaling
- Demonstrated experience with software performance and optimization
- Experience working in a highly regulated industry (e.g., healthcare, finance)
- Experience with event-driven architecture or CQRS
- Strong foundation in core computer science fundamentals and algorithmic thinking
- An agile, systems-level thinker who can diagnose ambiguous problems and drive to a solution using first-principles reasoning
- Self-directed: able to figure out what a task requires, identify who to loop in for missing details, and execute end to end
- Experience with data science or data engineering work
- A metrics-driven approach to evaluating your own and your team's output
- Remote‑First
- Unlimited Paid Time Off and 13 Company Holidays
- Equity Package
- Paid Parental Leave
- Medical, Vision, and Dental
- Employer HSA Contribution
- Employer 401(k) Match
- STD, LTD, Life Insurance and Critical Illness Plans
- Employee Assistance Program
- Adoption Assistance
- Company Offsites
- Monthly Internet Allowance
- Professional Development Funds
- And more!
Required:
etc. But headings must beonly for section headings; we can use
for subheadings. That's fine. Thus:
Qualifications
Required:
Bonus Points:
Benefits
Great work deserves great support. We believe our people are our greatest asset, and we’re committed to supporting them with a strong, competitive benefits package. Our goal is to be a place where people genuinely want to build their careers, and our benefits are designed to support our team in the ways that matter most.
Pay
The anticipated salary range for this role is $150,000 to $220,000.
We should not include Schedule. Make sure no extra whitespace or markdown. Output only HTML fragment. Check for any leftover boilerplate: removed EEO, diversity statement, agency notice, etc. Check for duplicated lines: none. Check for any mention of "Additional Considerations" removed. Check for "Location" we included as a paragraph under About the role. Check for "About XCures" description: we need to preserve all substantive information. Let's copy the About XCures paragraph exactly: "About XCures The best of medicine should belong to everyone. Nobody dreams of becoming good at being a patient. We have people to love, things we want to do, and plans we hope to keep. Illness already asks enough of us. xCures® exists to give healthcare the capacity to care for everyone. Healthcare has more to give. Too much of its time, money, and talent goes into unnecessary work that keeps people waiting and drives up the cost of care. Freeing those resources can make excellent care possible for far more people. xCures understands a patient’s history across the places they receive care and keeps that understanding current. It puts trusted information in the hands of the people who need it, when they need it, and uses that knowledge to take on more of the administrative work around care. Every extracted data point traces back to the exact document and page it came from. Our ambition is to empower doctors to make better decisions, enable researchers to develop better treatments faster, and help healthcare organizations serve more people with fewer errors and lower costs. We work with diagnostic labs, providers, telehealth companies, health systems, payers, and consumer health platforms. We are a fully remote, venture-backed team that holds itself to the same standard as our product: trustworthy, precise, and purposeful. We are building for the lives people want to live." We need to keep that exactly. Ensure we preserve line breaks? Not needed; just as a paragraph. Now "Here’s Where You’ll Make An Impact" paragraph: "xCures is looking for a Senior AI Software Engineer to help pioneer how AI gets used in one of the most regulated industries there is: healthcare. You will report directly to our Head of AI Engineering, designing and building systems that let us deliver more, faster, without giving up quality. You will help scale our technical foundation and performance as we grow. This is a chance to shape how AI-driven engineering