Sr/Staff Software Engineer - COB & Subrogate
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Must preserve all substantive info.
We need to parse the posting and extract sections.
The posting includes:
- Intro about Machinify (company description). Could be "About the role"? Actually "About the role" maybe includes description of role and team. We'll need to decide.
We have sections: "The Role", "What You’ll Do", "What You Bring", "Nice to have", "What We Offer", "Pay range". Also "Our Culture @ Machinify". Also "We're hiring for a Staff and Senior Backend Engineer...". Also "Click here to learn more about our COB & Subrogation product lines." Might be considered a link but we can ignore as it's not substantive? It's a link; maybe we can keep as part of description? Probably we can keep as part of "About the role". But we need to preserve all substantive info; we can include that sentence as prose.
We must not include EEO boilerplate, legal, etc. Remove "Equal Employment Opportunity at Machinify ..." and "We are an employment at will employer..." etc.
Also remove "Click here to learn more about our COB (Coordination of Benefits) & Subrogation product lines." Might be considered a link but it's substantive? It's a call to action; maybe we can keep as part of description but it's not essential. However it's not boilerplate; it's a link to learn more. Might be considered navigation? Probably safe to keep as part of "About the role". But we can drop if we think it's not crucial. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The link is not navigation? It's a call to action but maybe considered navigation? It's a link to learn more; could be considered navigation. Safer to remove it.
Also "Does this sound like the right opportunity for you? Let’s connect!" is application instruction? Might be considered call to action; could be removed as application instruction. Probably remove.
Now we need to decide sections.
Potential sections:
- About the role (or maybe "About the team"): includes company description, culture, role overview.
- Responsibilities: from "What You’ll Do".
- Requirements: from "What You Bring" (mandatory). Could split into Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use based on content.
We have "What You Bring" includes mandatory qualifications: 10+ years experience etc. Also "Nice to have" includes optional qualifications.
We could map:
- Requirements: mandatory qualifications (What You Bring).
- Qualifications: maybe education (BS/MS) etc. Could be part of Requirements.
- Skills: maybe technical skills list (Rust, Java, Go, Scala, Docker, Kubernetes, CI/CD, SQL, NoSQL, agentic engineering tools). Could be separate.
But we must not create sections with filler. If we don't have distinct content for a heading, we should omit it.
We have content for:
- About the role: company description, culture, role overview.
- Responsibilities: bullet list from "What You’ll Do".
- Requirements: bullet list from "What You Bring" (mandatory).
- Skills: maybe we can extract technical skills from Requirements and Nice to have.
- Benefits: from "What We Offer": Work from anywhere, medical/dental/vision, FSA/HSA, tuition reimbursement, competitive salary, 401(k) match, unlimited PTO, additional health and wellness benefits, flexible environment.
- Pay: salary range $200,000 - $250,000.
- Schedule: not mentioned; we should not create Schedule section if not present.
We also have "Nice to have" which could be part of Qualifications or Skills. Could create a "Qualifications" section for nice-to-have? But we already have Requirements for mandatory. Could put nice-to-have under Qualifications.
But we need to avoid filler like "commensurate with experience". Not present.
We need to ensure we preserve all substantive info. Let's extract.
Company description paragraph:
"Machinify is a leading healthcare intelligence company with expertise across the payment continuum, delivering unmatched value, transparency, and efficiency to health plan clients across the country. Deployed by over 85 health plans, including many of the top 20, and representing more than 270 million lives, Machinify brings together a fully configurable and content-rich, AI-powered platform along with best-in-class expertise. We’re constantly reimagining what’s possible in our industry, creating disruptively simple, powerfully clear ways to maximize financial outcomes and drive down healthcare costs."
Culture paragraph:
"Our Culture @ Machinify We embrace complex challenges with curiosity — a genuine interest in understanding the hard problems at hand and how to move the needle forward. Our engineers empower each other to take action, learn deeply about our customers' needs, and unlock innovation with a strong sense of product ownership. We build with our users in mind, thoughtfully shipping outcomes, not just features. The technology we build shapes real healthcare decisions, demanding a high bar for engineering excellence — what we ship carries real weight. We pressure-test new AI tools, shape how they're used, and set the example for what disciplined, AI-driven engineering looks like: fast, but always under structured human oversight."
Role overview paragraph:
"We're hiring for a Staff and Senior Backend Engineer to join our expanding Right Payer Solutions product team across Subrogate and COB product lines. Our Culture @ Machinify ... (already used). Actually the role overview: "We're hiring a Staff / Senior Backend Engineer to join our expanding engineering team spanning the Subrogation and Coordination of Benefits (COB) product lines. This is a joint posting for both lines — you'll join one of them, matched on your background and team need. You'll set technical direction for backend development and use your deep programming expertise to design, build, and operate scalable, reliable cloud-native services and distributed systems that run at scale on AWS, GCP, or Azure. You'll work alongside AI coding agents as a core part of how you deliver — directing and reviewing their output while holding the bar on quality. The ideal candidate has strong experience in application design, system architecture, and cloud development, plus a proven ability to drive adoption of new languages, tools, and agentic development practices across a team. You'll join a highly visible engineering team trusted to solve complex, high-stakes problems using the best of AI, data, and software systems. Partnering cross-functionally, you'll influence product direction, work directly with customers, and own systems that positively impact millions of lives — where your technical decisions truly matter. We develop in Rust; strong Java, Go, or Scala engineers are a great fit and we'll help you adopt Rust effectively. This is hands-on product engineering — building and owning production services and features, not a DevOps, Platform, or SRE role."
That's a lot; we can split into About the role (company + culture + role overview) and Responsibilities.
Now Responsibilities bullet list from "What You’ll Do":
- Set the architecture and technical direction for backend systems on your product line
- Ship cloud-native services that power accurate, high-stakes payment-integrity decisions
- Turn ambiguous product intent into concrete, well-sequenced backend design
- Own your services in production — reliability, observability, and performance at scale
- Raise the engineering bar and grow the team's programming maturity as we scale Rust
- Set the standard for AI-driven delivery, keeping delivery fast and under human oversight
- Simplify labor-intensive workflows by applying ML techniques to large volumes of data
- Balance new customer value with technical-debt cleanup to keep the product sustainable
- Partner with PM, ML/DS, QA and UX to shape product direction and outcomes
- Mentor engineers and act as the backend voice in cross-team planning
- Work directly with customers on systems that impact millions of lives
Now Requirements (mandatory) from "What You Bring":
- 10+ years of backend engineering for Staff, 6+ years for Senior (full-stack experience a plus)
- Strong application design and system architecture across complex backend systems
- Proven ability to author technical design documents that satisfy engineers and product partners alike
- Substantial production experience in Rust, Java, Go, or Scala; Rust highly desired
- Proven experience designing, building, and operating distributed systems at scale
- Hands-on with containers and orchestration (Docker, Kubernetes) in production
- Ownership of CI/CD pipelines for your own services — building them, not just consuming them
- Production experience on at least one major cloud — AWS, GCP, or Azure
- Strong SQL and relational database skills; comfort across NoSQL and caching layers
- Hands-on experience with agentic engineering tools and workflows in production
- Proven ability to read complex code and own and continually improve code quality
- Strong cross-functional collaboration with engineering, PM, ML/DS, and leadership
- A pragmatic default and strong systems instinct — you find root causes, not symptoms
- Comfort with complexity and curiosity to define the path forward, not wait for one
- BS or MS in Computer Science, or equivalent experience
Now Nice to have (optional):
- Technical leadership on Rust best practices — idioms, safety, and performance — as the team scales adoption across greenfield projects
- Healthcare, payer, or insurance domain experience; claims or payment-integrity workflows
- Experience shipping ML/AI-driven features in production and earning the business's trust in them
Now Benefits from "What We Offer":
- Work from anywhere in the US! Machinify is digital-first.
- Top Medical/Dental/Vision offerings
- FSA/HSA
- Tuition reimbursement
- Competitive salary, 401(k) with company match
- Unlimited PTO
- Additional health and wellness benefits and perks
- Flexible and trusting environment where you’ll feel empowered to do your best work
Now Pay: "Pay range: $200,000 - $250,000". Also earlier: "The salary for this position is based on an array of factors unique to each candidate: Such as years and depth of experience, set skills, certifications, etc. We are hiring for different levels, and our Recruiting team will let you know if you qualify for a different role/range. Salary is one component of the total compensation package, which includes meaningful equity, excellent healthcare, flexible time off, and other benefits and perks." We should preserve that substantive info. So we can include a paragraph about salary determination plus the range.
Now Schedule: not mentioned, so omit.
Now we need to output HTML fragment with headings
for each section we include.
We must not repeat job title as heading. So no Staff and Senior Backend Engineer
.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to decide which sections to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We have content for About the role (company description, culture, role overview). Could be one
or multiple
. We'll combine into maybe two paragraphs: company description and culture+role overview.
Responsibilities: list.
Requirements: list (mandatory). Could be
Requirements
with .
Qualifications: maybe we can put nice-to-have here.
Skills: maybe we can
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Must preserve all substantive info. We need to parse the posting and extract sections. The posting includes: - Intro about Machinify (company description). Could be "About the role"? Actually "About the role" maybe includes description of role and team. We'll need to decide. We have sections: "The Role", "What You’ll Do", "What You Bring", "Nice to have", "What We Offer", "Pay range". Also "Our Culture @ Machinify". Also "We're hiring for a Staff and Senior Backend Engineer...". Also "Click here to learn more about our COB & Subrogation product lines." Might be considered a link but we can ignore as it's not substantive? It's a link; maybe we can keep as part of description? Probably we can keep as part of "About the role". But we need to preserve all substantive info; we can include that sentence as prose. We must not include EEO boilerplate, legal, etc. Remove "Equal Employment Opportunity at Machinify ..." and "We are an employment at will employer..." etc. Also remove "Click here to learn more about our COB (Coordination of Benefits) & Subrogation product lines." Might be considered a link but it's substantive? It's a call to action; maybe we can keep as part of description but it's not essential. However it's not boilerplate; it's a link to learn more. Might be considered navigation? Probably safe to keep as part of "About the role". But we can drop if we think it's not crucial. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The link is not navigation? It's a call to action but maybe considered navigation? It's a link to learn more; could be considered navigation. Safer to remove it. Also "Does this sound like the right opportunity for you? Let’s connect!" is application instruction? Might be considered call to action; could be removed as application instruction. Probably remove. Now we need to decide sections. Potential sections: - About the role (or maybe "About the team"): includes company description, culture, role overview. - Responsibilities: from "What You’ll Do". - Requirements: from "What You Bring" (mandatory). Could split into Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use based on content. We have "What You Bring" includes mandatory qualifications: 10+ years experience etc. Also "Nice to have" includes optional qualifications. We could map: - Requirements: mandatory qualifications (What You Bring). - Qualifications: maybe education (BS/MS) etc. Could be part of Requirements. - Skills: maybe technical skills list (Rust, Java, Go, Scala, Docker, Kubernetes, CI/CD, SQL, NoSQL, agentic engineering tools). Could be separate. But we must not create sections with filler. If we don't have distinct content for a heading, we should omit it. We have content for: - About the role: company description, culture, role overview. - Responsibilities: bullet list from "What You’ll Do". - Requirements: bullet list from "What You Bring" (mandatory). - Skills: maybe we can extract technical skills from Requirements and Nice to have. - Benefits: from "What We Offer": Work from anywhere, medical/dental/vision, FSA/HSA, tuition reimbursement, competitive salary, 401(k) match, unlimited PTO, additional health and wellness benefits, flexible environment. - Pay: salary range $200,000 - $250,000. - Schedule: not mentioned; we should not create Schedule section if not present. We also have "Nice to have" which could be part of Qualifications or Skills. Could create a "Qualifications" section for nice-to-have? But we already have Requirements for mandatory. Could put nice-to-have under Qualifications. But we need to avoid filler like "commensurate with experience". Not present. We need to ensure we preserve all substantive info. Let's extract. Company description paragraph: "Machinify is a leading healthcare intelligence company with expertise across the payment continuum, delivering unmatched value, transparency, and efficiency to health plan clients across the country. Deployed by over 85 health plans, including many of the top 20, and representing more than 270 million lives, Machinify brings together a fully configurable and content-rich, AI-powered platform along with best-in-class expertise. We’re constantly reimagining what’s possible in our industry, creating disruptively simple, powerfully clear ways to maximize financial outcomes and drive down healthcare costs." Culture paragraph: "Our Culture @ Machinify We embrace complex challenges with curiosity — a genuine interest in understanding the hard problems at hand and how to move the needle forward. Our engineers empower each other to take action, learn deeply about our customers' needs, and unlock innovation with a strong sense of product ownership. We build with our users in mind, thoughtfully shipping outcomes, not just features. The technology we build shapes real healthcare decisions, demanding a high bar for engineering excellence — what we ship carries real weight. We pressure-test new AI tools, shape how they're used, and set the example for what disciplined, AI-driven engineering looks like: fast, but always under structured human oversight." Role overview paragraph: "We're hiring for a Staff and Senior Backend Engineer to join our expanding Right Payer Solutions product team across Subrogate and COB product lines. Our Culture @ Machinify ... (already used). Actually the role overview: "We're hiring a Staff / Senior Backend Engineer to join our expanding engineering team spanning the Subrogation and Coordination of Benefits (COB) product lines. This is a joint posting for both lines — you'll join one of them, matched on your background and team need. You'll set technical direction for backend development and use your deep programming expertise to design, build, and operate scalable, reliable cloud-native services and distributed systems that run at scale on AWS, GCP, or Azure. You'll work alongside AI coding agents as a core part of how you deliver — directing and reviewing their output while holding the bar on quality. The ideal candidate has strong experience in application design, system architecture, and cloud development, plus a proven ability to drive adoption of new languages, tools, and agentic development practices across a team. You'll join a highly visible engineering team trusted to solve complex, high-stakes problems using the best of AI, data, and software systems. Partnering cross-functionally, you'll influence product direction, work directly with customers, and own systems that positively impact millions of lives — where your technical decisions truly matter. We develop in Rust; strong Java, Go, or Scala engineers are a great fit and we'll help you adopt Rust effectively. This is hands-on product engineering — building and owning production services and features, not a DevOps, Platform, or SRE role." That's a lot; we can split into About the role (company + culture + role overview) and Responsibilities. Now Responsibilities bullet list from "What You’ll Do": - Set the architecture and technical direction for backend systems on your product line - Ship cloud-native services that power accurate, high-stakes payment-integrity decisions - Turn ambiguous product intent into concrete, well-sequenced backend design - Own your services in production — reliability, observability, and performance at scale - Raise the engineering bar and grow the team's programming maturity as we scale Rust - Set the standard for AI-driven delivery, keeping delivery fast and under human oversight - Simplify labor-intensive workflows by applying ML techniques to large volumes of data - Balance new customer value with technical-debt cleanup to keep the product sustainable - Partner with PM, ML/DS, QA and UX to shape product direction and outcomes - Mentor engineers and act as the backend voice in cross-team planning - Work directly with customers on systems that impact millions of lives Now Requirements (mandatory) from "What You Bring": - 10+ years of backend engineering for Staff, 6+ years for Senior (full-stack experience a plus) - Strong application design and system architecture across complex backend systems - Proven ability to author technical design documents that satisfy engineers and product partners alike - Substantial production experience in Rust, Java, Go, or Scala; Rust highly desired - Proven experience designing, building, and operating distributed systems at scale - Hands-on with containers and orchestration (Docker, Kubernetes) in production - Ownership of CI/CD pipelines for your own services — building them, not just consuming them - Production experience on at least one major cloud — AWS, GCP, or Azure - Strong SQL and relational database skills; comfort across NoSQL and caching layers - Hands-on experience with agentic engineering tools and workflows in production - Proven ability to read complex code and own and continually improve code quality - Strong cross-functional collaboration with engineering, PM, ML/DS, and leadership - A pragmatic default and strong systems instinct — you find root causes, not symptoms - Comfort with complexity and curiosity to define the path forward, not wait for one - BS or MS in Computer Science, or equivalent experience Now Nice to have (optional): - Technical leadership on Rust best practices — idioms, safety, and performance — as the team scales adoption across greenfield projects - Healthcare, payer, or insurance domain experience; claims or payment-integrity workflows - Experience shipping ML/AI-driven features in production and earning the business's trust in them Now Benefits from "What We Offer": - Work from anywhere in the US! Machinify is digital-first. - Top Medical/Dental/Vision offerings - FSA/HSA - Tuition reimbursement - Competitive salary, 401(k) with company match - Unlimited PTO - Additional health and wellness benefits and perks - Flexible and trusting environment where you’ll feel empowered to do your best work Now Pay: "Pay range: $200,000 - $250,000". Also earlier: "The salary for this position is based on an array of factors unique to each candidate: Such as years and depth of experience, set skills, certifications, etc. We are hiring for different levels, and our Recruiting team will let you know if you qualify for a different role/range. Salary is one component of the total compensation package, which includes meaningful equity, excellent healthcare, flexible time off, and other benefits and perks." We should preserve that substantive info. So we can include a paragraph about salary determination plus the range. Now Schedule: not mentioned, so omit. Now we need to output HTML fragment with headings
for each section we include.
We must not repeat job title as heading. So no Staff and Senior Backend Engineer
.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to decide which sections to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We have content for About the role (company description, culture, role overview). Could be one
or multiple
. We'll combine into maybe two paragraphs: company description and culture+role overview.
Responsibilities: list.
Requirements: list (mandatory). Could be
Requirements
with .
Qualifications: maybe we can put nice-to-have here.
Skills: maybe we can
. We need to decide which sections to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We have content for About the role (company description, culture, role overview). Could be one
or multiple
. We'll combine into maybe two paragraphs: company description and culture+role overview. Responsibilities: list. Requirements: list (mandatory). Could be
Requirements
with- .
Qualifications: maybe we can put nice-to-have here.
Skills: maybe we can