Senior Software Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading (the page already shows it). Do not put Job ID etc. Remove boilerplate like EEO etc. We have "Leap is an equal opportunity employer..." that's boilerplate, remove. Also "Compensation Range: $200K - $250K" is pay info, so we need a Pay section with that content. Also maybe Benefits? Not present. Schedule? Not present. So only sections with real content: About Leap? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. But we can also have other headings? Probably we should map content to those headings where appropriate. The posting includes "About Leap" (company overview) maybe not needed? Could be considered "About the role"? Actually "About The Role" is a heading. We'll use About The Role
for that section. Then "What You'll Do" corresponds to Responsibilities. Use Responsibilities
. Then "What You Bring" corresponds to Requirements/Qualifications/Skills. Could split into Requirements and Skills. But we can combine? The instruction: prefer a few substantive sections over many thin ones. So maybe we have one section for Requirements (including what you bring and bonus points). Or we could have Requirements and Skills separate. But we need to avoid thin sections. Let's think: "What You Bring" includes 5+ years experience, TypeScript-native, track record, experience building 0-1, etc. That's qualifications. "Bonus Points For" includes healthcare/HIPAA experience, data pipelines, CRM integrations. That's skills/bonus. Could combine into Requirements section with subpoints? But we need to use - for any list. So we can have a
with items for requirements and another for bonus? Might be okay.
We also have "About Leap" company description. Could be considered "About the role"? Not exactly. But we could include a short about company under a heading like "About Leap"? Not in the list but maybe allowed. 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, but suggests those are typical. Safer to stick to those headings. So we need to map content to those headings. We have About Leap (company overview) maybe not needed; but we could omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Leap paragraph. Where to put it? Could be under a heading like "About Leap" but not in list. However we could treat it as a
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't say every paragraph must be under a heading, but we should use headings for sections. Could we have a leading
without heading? Probably okay. But to be safe, we could include a heading "About Leap" even though not in the list; risk of deviating? The instruction says use
for section headings (e.g. About the role, Responsibilities...). The "e.g." implies examples, not exhaustive. So we can use other headings as needed. So we can have About Leap
.
Then we have About The Role
(or maybe we combine with About Leap? But we have both). Then Responsibilities, Requirements, Pay.
We need to output only HTML fragment, no markdown fences.
Let's extract content:
About Leap paragraph:
"Leap is one of the fastest-growing benefits solutions and a category-defining pioneer in employer specialty pharmacy. We are reshaping how life-changing therapies are delivered and financed, ensuring patients get the treatment they need while employers finally get a fair deal. Specialty drugs and infusions represent nearly 10% of all healthcare spend and are the fastest-growing cost category for employers. Leap tackles this challenge with a novel approach: eliminating hidden markups, expanding access to high-quality infusion providers, and bringing clarity and fairness to how therapies are priced and paid for. We’re proud to partner with numerous Fortune 500 companies and leading TPAs. Each patient we serve creates immediate ROI: lower costs, improved access, and better care. Join us as we redefine what’s possible in specialty care."
About The Role heading content:
"As a Senior Software Engineer, you will build the AI and automation systems that power Leap’s clinical and business operations. You will own large surface areas across product, data, infrastructure, and automation, helping scale the company’s operational platform as the business grows. This role partners closely with Clinical Operations, Business Operations, and company leadership to identify high-value automation opportunities and ship systems that improve care delivery and internal efficiency. Engineers here have real input into what we build, not just how."
What You'll Do (Responsibilities):
We have bullet-like paragraphs:
- AI and Automation Build LLM agents and automation pipelines that replace manual operational workflows
- Design and ship AI-driven care orchestration systems that coordinate treatment journeys across patients, providers, pharmacies, and internal teams
- Identify high-value automation opportunities by working directly with clinical and business operations teams
- Product Development Own and ship both internal and external products used by clinical teams, growth teams, partners, and customers
- Talk to users (often internal teams), instrument what you ship, and use the data to decide what to build next
- Platform and Infrastructure Build and maintain shared services, identity/auth, and HIPAA-compliant data architecture
- Ship integrations across CRM and external healthcare systems
- Design PHI-safe LLM pipelines, agent orchestration frameworks, evaluation systems, and MCP integrations
These are sentences; we can treat each as
- .
What You Bring (Requirements):
- 5+ years of experience building with AI systems in production (LLM integrations, agents, AI-powered workflows)
- TypeScript-native, full-stack generalist comfortable across frontend, backend, data, and infrastructure
- Track record of shipping fast with high quality - your code, UI, and documentation hold up without a designer or QA team
- Experience building 0-1 at an early stage startup
- Use AI heavily in your own development workflow
Bonus Points For:
- Healthcare or HIPAA experience
- data pipelines (BigQuery, ETL)
- CRM integrations (Salesforce, HubSpot)
Compensation Range: $200K - $250K
We need to output sections: About Leap, About The Role, Responsibilities, Requirements (maybe combine What You Bring and Bonus Points For), Pay.
We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we need a
. For Requirements we need a . For Bonus Points maybe we could include as part of Requirements but separate list? Could be another under same heading? Might be thin. Better to combine Requirements and Bonus Points into one Requirements section with two sublists? But we need to preserve all detail; we can have a for requirements and another for bonus points under same heading, but that might be considered thin? However the instruction says prefer a few substantive sections over many thin ones. Having two lists under same heading is okay.
Alternatively we could have Requirements heading with a that includes both required and bonus items, maybe differentiate with text. But we need to keep the bonus points separate as they are optional. Could embed as - with "(Bonus)" note.
Let's do:
Requirements
then a with items: required items (first five) and then bonus items with note "(Bonus)".
But we need to preserve the exact phrasing. We'll include bullet points exactly as given.
Pay section: Pay
Compensation Range: $200K - $250K
Now ensure we don't include boilerplate like EEO etc.
Now produce HTML fragment:
About Leap
Leap is one of the fastest-growing benefits solutions and a category-defining pioneer in employer specialty pharmacy. We are reshaping how life-changing therapies are delivered and financed, ensuring patients get the treatment they need while employers finally get a fair deal. Specialty drugs and infusions represent nearly 10% of all healthcare spend and are the fastest-growing cost category for employers. Leap tackles this challenge with a novel approach: eliminating hidden markups, expanding access to high-quality infusion providers, and bringing clarity and fairness to how therapies are priced and paid for. We’re proud to partner with numerous Fortune 500 companies and leading TPAs. Each patient we serve creates immediate ROI: lower costs, improved access, and better care. Join us as we redefine what’s possible in specialty care.
About The Role
As a Senior Software Engineer, you will build the AI and automation systems that power Leap’s clinical and business operations. You will own large surface areas across product, data, infrastructure, and automation, helping scale the company’s operational platform as the business grows. This role partners closely with Clinical Operations, Business Operations, and company leadership to identify high-value automation opportunities and ship systems that improve care delivery and internal efficiency. Engineers here have real input into what we build, not just how.
Responsibilities
- AI and Automation Build LLM agents and automation pipelines that replace manual operational workflows
- Design and ship AI-driven care orchestration systems that coordinate treatment journeys across patients, providers, pharmacies, and internal teams
- Identify high-value automation opportunities by working directly with clinical and business operations teams
- Product Development Own and ship both internal and external products used by clinical teams, growth teams, partners, and customers
- Talk to users (often internal teams), instrument what you ship, and use the data to decide what to build next
- Platform and Infrastructure Build and maintain shared services, identity/auth, and HIPAA-compliant data architecture
- Ship integrations across CRM and external healthcare systems
- Design PHI-safe LLM pipelines, agent orchestration frameworks, evaluation systems, and MCP integrations
Requirements
- 5+ years of experience building with AI systems in production (LLM integrations, agents, AI-powered workflows)
- TypeScript-native, full-stack generalist comfortable across frontend, backend, data, and infrastructure
- Track record of shipping fast with high quality - your code, UI, and documentation hold up without a designer or QA team
- Experience building 0-1 at an early stage startup
- Use AI heavily in your own development workflow
- (Bonus) Healthcare or HIPAA experience
- (Bonus) data pipelines (BigQuery, ETL)
- (Bonus) CRM integrations (Salesforce, HubSpot)
Pay
Compensation Range: $200K - $250K
for prose. Do not repeat job title as heading (the page already shows it). Do not put Job ID etc. Remove boilerplate like EEO etc. We have "Leap is an equal opportunity employer..." that's boilerplate, remove. Also "Compensation Range: $200K - $250K" is pay info, so we need a Pay section with that content. Also maybe Benefits? Not present. Schedule? Not present. So only sections with real content: About Leap? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also have other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when applicable. But we can also have other headings? Probably we should map content to those headings where appropriate. The posting includes "About Leap" (company overview) maybe not needed? Could be considered "About the role"? Actually "About The Role" is a heading. We'll use About The Role
for that section. Then "What You'll Do" corresponds to Responsibilities. Use Responsibilities
. Then "What You Bring" corresponds to Requirements/Qualifications/Skills. Could split into Requirements and Skills. But we can combine? The instruction: prefer a few substantive sections over many thin ones. So maybe we have one section for Requirements (including what you bring and bonus points). Or we could have Requirements and Skills separate. But we need to avoid thin sections. Let's think: "What You Bring" includes 5+ years experience, TypeScript-native, track record, experience building 0-1, etc. That's qualifications. "Bonus Points For" includes healthcare/HIPAA experience, data pipelines, CRM integrations. That's skills/bonus. Could combine into Requirements section with subpoints? But we need to use - for any list. So we can have a
with items for requirements and another for bonus? Might be okay.
We also have "About Leap" company description. Could be considered "About the role"? Not exactly. But we could include a short about company under a heading like "About Leap"? Not in the list but maybe allowed. 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, but suggests those are typical. Safer to stick to those headings. So we need to map content to those headings. We have About Leap (company overview) maybe not needed; but we could omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Leap paragraph. Where to put it? Could be under a heading like "About Leap" but not in list. However we could treat it as a
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't say every paragraph must be under a heading, but we should use headings for sections. Could we have a leading
without heading? Probably okay. But to be safe, we could include a heading "About Leap" even though not in the list; risk of deviating? The instruction says use
for section headings (e.g. About the role, Responsibilities...). The "e.g." implies examples, not exhaustive. So we can use other headings as needed. So we can have About Leap
.
Then we have About The Role
(or maybe we combine with About Leap? But we have both). Then Responsibilities, Requirements, Pay.
We need to output only HTML fragment, no markdown fences.
Let's extract content:
About Leap paragraph:
"Leap is one of the fastest-growing benefits solutions and a category-defining pioneer in employer specialty pharmacy. We are reshaping how life-changing therapies are delivered and financed, ensuring patients get the treatment they need while employers finally get a fair deal. Specialty drugs and infusions represent nearly 10% of all healthcare spend and are the fastest-growing cost category for employers. Leap tackles this challenge with a novel approach: eliminating hidden markups, expanding access to high-quality infusion providers, and bringing clarity and fairness to how therapies are priced and paid for. We’re proud to partner with numerous Fortune 500 companies and leading TPAs. Each patient we serve creates immediate ROI: lower costs, improved access, and better care. Join us as we redefine what’s possible in specialty care."
About The Role heading content:
"As a Senior Software Engineer, you will build the AI and automation systems that power Leap’s clinical and business operations. You will own large surface areas across product, data, infrastructure, and automation, helping scale the company’s operational platform as the business grows. This role partners closely with Clinical Operations, Business Operations, and company leadership to identify high-value automation opportunities and ship systems that improve care delivery and internal efficiency. Engineers here have real input into what we build, not just how."
What You'll Do (Responsibilities):
We have bullet-like paragraphs:
- AI and Automation Build LLM agents and automation pipelines that replace manual operational workflows
- Design and ship AI-driven care orchestration systems that coordinate treatment journeys across patients, providers, pharmacies, and internal teams
- Identify high-value automation opportunities by working directly with clinical and business operations teams
- Product Development Own and ship both internal and external products used by clinical teams, growth teams, partners, and customers
- Talk to users (often internal teams), instrument what you ship, and use the data to decide what to build next
- Platform and Infrastructure Build and maintain shared services, identity/auth, and HIPAA-compliant data architecture
- Ship integrations across CRM and external healthcare systems
- Design PHI-safe LLM pipelines, agent orchestration frameworks, evaluation systems, and MCP integrations
These are sentences; we can treat each as
- .
What You Bring (Requirements):
- 5+ years of experience building with AI systems in production (LLM integrations, agents, AI-powered workflows)
- TypeScript-native, full-stack generalist comfortable across frontend, backend, data, and infrastructure
- Track record of shipping fast with high quality - your code, UI, and documentation hold up without a designer or QA team
- Experience building 0-1 at an early stage startup
- Use AI heavily in your own development workflow
Bonus Points For:
- Healthcare or HIPAA experience
- data pipelines (BigQuery, ETL)
- CRM integrations (Salesforce, HubSpot)
Compensation Range: $200K - $250K
We need to output sections: About Leap, About The Role, Responsibilities, Requirements (maybe combine What You Bring and Bonus Points For), Pay.
We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we need a
. For Requirements we need a . For Bonus Points maybe we could include as part of Requirements but separate list? Could be another under same heading? Might be thin. Better to combine Requirements and Bonus Points into one Requirements section with two sublists? But we need to preserve all detail; we can have a for requirements and another for bonus points under same heading, but that might be considered thin? However the instruction says prefer a few substantive sections over many thin ones. Having two lists under same heading is okay.
Alternatively we could have Requirements heading with a that includes both required and bonus items, maybe differentiate with text. But we need to keep the bonus points separate as they are optional. Could embed as - with "(Bonus)" note.
Let's do:
Requirements
then a with items: required items (first five) and then bonus items with note "(Bonus)".
But we need to preserve the exact phrasing. We'll include bullet points exactly as given.
Pay section: Pay
Compensation Range: $200K - $250K
Now ensure we don't include boilerplate like EEO etc.
Now produce HTML fragment:
About Leap
Leap is one of the fastest-growing benefits solutions and a category-defining pioneer in employer specialty pharmacy. We are reshaping how life-changing therapies are delivered and financed, ensuring patients get the treatment they need while employers finally get a fair deal. Specialty drugs and infusions represent nearly 10% of all healthcare spend and are the fastest-growing cost category for employers. Leap tackles this challenge with a novel approach: eliminating hidden markups, expanding access to high-quality infusion providers, and bringing clarity and fairness to how therapies are priced and paid for. We’re proud to partner with numerous Fortune 500 companies and leading TPAs. Each patient we serve creates immediate ROI: lower costs, improved access, and better care. Join us as we redefine what’s possible in specialty care.
About The Role
As a Senior Software Engineer, you will build the AI and automation systems that power Leap’s clinical and business operations. You will own large surface areas across product, data, infrastructure, and automation, helping scale the company’s operational platform as the business grows. This role partners closely with Clinical Operations, Business Operations, and company leadership to identify high-value automation opportunities and ship systems that improve care delivery and internal efficiency. Engineers here have real input into what we build, not just how.
Responsibilities
- AI and Automation Build LLM agents and automation pipelines that replace manual operational workflows
- Design and ship AI-driven care orchestration systems that coordinate treatment journeys across patients, providers, pharmacies, and internal teams
- Identify high-value automation opportunities by working directly with clinical and business operations teams
- Product Development Own and ship both internal and external products used by clinical teams, growth teams, partners, and customers
- Talk to users (often internal teams), instrument what you ship, and use the data to decide what to build next
- Platform and Infrastructure Build and maintain shared services, identity/auth, and HIPAA-compliant data architecture
- Ship integrations across CRM and external healthcare systems
- Design PHI-safe LLM pipelines, agent orchestration frameworks, evaluation systems, and MCP integrations
Requirements
- 5+ years of experience building with AI systems in production (LLM integrations, agents, AI-powered workflows)
- TypeScript-native, full-stack generalist comfortable across frontend, backend, data, and infrastructure
- Track record of shipping fast with high quality - your code, UI, and documentation hold up without a designer or QA team
- Experience building 0-1 at an early stage startup
- Use AI heavily in your own development workflow
- (Bonus) Healthcare or HIPAA experience
- (Bonus) data pipelines (BigQuery, ETL)
- (Bonus) CRM integrations (Salesforce, HubSpot)
Pay
Compensation Range: $200K - $250K
- with items for requirements and another for bonus? Might be okay.
We also have "About Leap" company description. Could be considered "About the role"? Not exactly. But we could include a short
- .
What You Bring (Requirements):
- 5+ years of experience building with AI systems in production (LLM integrations, agents, AI-powered workflows)
- TypeScript-native, full-stack generalist comfortable across frontend, backend, data, and infrastructure
- Track record of shipping fast with high quality - your code, UI, and documentation hold up without a designer or QA team
- Experience building 0-1 at an early stage startup
- Use AI heavily in your own development workflow
Bonus Points For:
- Healthcare or HIPAA experience
- data pipelines (BigQuery, ETL)
- CRM integrations (Salesforce, HubSpot)
Compensation Range: $200K - $250K
We need to output sections: About Leap, About The Role, Responsibilities, Requirements (maybe combine What You Bring and Bonus Points For), Pay.
We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we need a
- . For Requirements we need a
- with "(Bonus)" note.
Let's do:
Requirements
then a- with items: required items (first five) and then bonus items with note "(Bonus)".
But we need to preserve the exact phrasing. We'll include bullet points exactly as given.
Pay section:
- AI and Automation Build LLM agents and automation pipelines that replace manual operational workflows
- Design and ship AI-driven care orchestration systems that coordinate treatment journeys across patients, providers, pharmacies, and internal teams
- Identify high-value automation opportunities by working directly with clinical and business operations teams
- Product Development Own and ship both internal and external products used by clinical teams, growth teams, partners, and customers
- Talk to users (often internal teams), instrument what you ship, and use the data to decide what to build next
- Platform and Infrastructure Build and maintain shared services, identity/auth, and HIPAA-compliant data architecture
- Ship integrations across CRM and external healthcare systems
- Design PHI-safe LLM pipelines, agent orchestration frameworks, evaluation systems, and MCP integrations
- 5+ years of experience building with AI systems in production (LLM integrations, agents, AI-powered workflows)
- TypeScript-native, full-stack generalist comfortable across frontend, backend, data, and infrastructure
- Track record of shipping fast with high quality - your code, UI, and documentation hold up without a designer or QA team
- Experience building 0-1 at an early stage startup
- Use AI heavily in your own development workflow
- (Bonus) Healthcare or HIPAA experience
- (Bonus) data pipelines (BigQuery, ETL)
- (Bonus) CRM integrations (Salesforce, HubSpot)
Pay
Compensation Range: $200K - $250K
Now ensure we don't include boilerplate like EEO etc. Now produce HTML fragment:About Leap
Leap is one of the fastest-growing benefits solutions and a category-defining pioneer in employer specialty pharmacy. We are reshaping how life-changing therapies are delivered and financed, ensuring patients get the treatment they need while employers finally get a fair deal. Specialty drugs and infusions represent nearly 10% of all healthcare spend and are the fastest-growing cost category for employers. Leap tackles this challenge with a novel approach: eliminating hidden markups, expanding access to high-quality infusion providers, and bringing clarity and fairness to how therapies are priced and paid for. We’re proud to partner with numerous Fortune 500 companies and leading TPAs. Each patient we serve creates immediate ROI: lower costs, improved access, and better care. Join us as we redefine what’s possible in specialty care.
About The Role
As a Senior Software Engineer, you will build the AI and automation systems that power Leap’s clinical and business operations. You will own large surface areas across product, data, infrastructure, and automation, helping scale the company’s operational platform as the business grows. This role partners closely with Clinical Operations, Business Operations, and company leadership to identify high-value automation opportunities and ship systems that improve care delivery and internal efficiency. Engineers here have real input into what we build, not just how.
Responsibilities
Requirements
Pay
Compensation Range: $200K - $250K
- . For Bonus Points maybe we could include as part of Requirements but separate list? Could be another
- under same heading? Might be thin. Better to combine Requirements and Bonus Points into one Requirements section with two sublists? But we need to preserve all detail; we can have a
- for requirements and another
- for bonus points under same heading, but that might be considered thin? However the instruction says prefer a few substantive sections over many thin ones. Having two lists under same heading is okay.
Alternatively we could have Requirements heading with a
- that includes both required and bonus items, maybe differentiate with text. But we need to keep the bonus points separate as they are optional. Could embed as
- with "(Bonus)" note.
Let's do:
- for any list of duties/requirements/benefits. So for Responsibilities we need a
about company under a heading like "About Leap"? Not in the list but maybe allowed. 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, but suggests those are typical. Safer to stick to those headings. So we need to map content to those headings. We have About Leap (company overview) maybe not needed; but we could omit it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Leap paragraph. Where to put it? Could be under a heading like "About Leap" but not in list. However we could treat it as a
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't say every paragraph must be under a heading, but we should use headings for sections. Could we have a leading
without heading? Probably okay. But to be safe, we could include a heading "About Leap" even though not in the list; risk of deviating? The instruction says use