Forward Deployed Engineer – EHR

We need to output HTML fragment only, with sections for headings where content exists. Must not repeat job title as heading. Must not include Job ID etc. Must not include boilerplate like EEO. Must include only sections with real content. We have content: "W2 only, no C2C, must be authorized to work in the US (both now and in the forward)." That's a requirement. Also location: "Forward Deployed Engineer - EHR (Direct Hire) - Remote in New York City, New York." But we cannot repeat job title as heading. We can include location and work authorization in a short

maybe under a heading? The instructions: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can have a

containing the location and work auth etc. Then sections: About the role? The posting includes description: "Carex is partnering...". That's like About the role or Overview. Could be a section "About the role". Then Responsibilities (What You'll Do). Then Requirements/Qualifications/Skills (What You'll Bring). Also maybe Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned (though travel %). Travel is mentioned but not schedule. Should we include a Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Travel is not schedule; schedule is about hours? Not given. So we omit Schedule. Benefits not mentioned. Pay not mentioned. Thus we can have sections: About the role (overview), Responsibilities, Requirements (or Qualifications/Skills). Could combine Requirements and Skills into one section "Requirements". But we need to preserve all substantive info. We'll list bullet points under each. We must not include filler like "commensurate with experience". Not present. We need to remove EEO boilerplate at end. Let's extract content: Overview paragraph: "Carex is partnering with a fast-growing Series A healthtech partner to hire a Forward Deployed Engineer to help build an AI-native operating system. This is a highly technical, customer-facing engineering role for someone who wants to work directly with behavioral health providers, understand how their organizations actually operate, and rapidly build software that solves their hardest problems. Healthcare and EHR domain expertise is essential for this role. The ideal candidate combines deep technical ability with the communication and product instincts required to work directly with clinicians, billers, operators, and executives. This person will spend meaningful time in the field, turn complex healthcare workflows and legacy-system challenges into buildable product requirements, and ship production solutions in days rather than quarters. The role involves approximately 10–15 hours per week of direct customer interaction and 25–50% travel. There is flexibility for remote candidates given the travel requirements." That's overview. Responsibilities (What You'll Do) list: - Own complex data migrations from legacy EHRs, billing platforms, and other healthcare systems from discovery through production deployment. - Work directly with behavioral health providers to understand their workflows, operational challenges, and technical pain points. - Spend approximately 10–15 hours per week interacting directly with customers, including clinicians, billers, operational leaders, and executives. - Translate ambiguous and interconnected customer problems into clearly scoped, buildable technical solutions. - Write production software that solves real customer problems rather than limiting work to implementations, prototypes, specifications, or presentations. - Build solutions independently and partner closely with Product Engineering on larger or more complex product initiatives. - Navigate messy healthcare data, legacy systems, integrations, migrations, and operational workflows. - Apply healthcare and EHR expertise to determine what should be built, not simply how existing requirements should be implemented. - Work alongside Product Engineers on complex features spanning clinical, operational, billing, and data workflows. - Bring insights from customer engagements back into product development so field learnings directly inform the roadmap. - Travel approximately 25–50% to work closely with customers and understand their environments firsthand. - Help establish and scale the Forward Deployed Engineering function as the team grows. Requirements (What You'll Bring): - Strong software engineering skills and the ability to personally design, build, and ship production-quality software. - Significant healthcare and EHR domain expertise. - Experience working deeply with EHR platforms and healthcare technology ecosystems; substantial Epic experience is particularly valuable. - Experience with EHR migrations, healthcare data migrations, or migrations from similarly complex legacy enterprise systems. - The ability to work directly with customers while remaining a hands-on technical builder rather than functioning solely as an implementation or project-management resource. - Strong product instincts and the ability to determine what should be built based on customer needs, technical constraints, and business context. - Confidence communicating with clinicians, billers, operators, executives, and technical stakeholders. - Experience making sense of messy data, legacy systems, incomplete requirements, and highly ambiguous problems. - A bias toward shipping, rapid iteration, and getting working solutions in front of users. - High ownership, autonomy, and comfort operating with significant scope in a fast-moving startup environment. - Willingness to travel approximately 25–50%. - Founder, early-stage, or 0-to-1 startup experience is valuable. - New York City-based candidates are preferred, with greater flexibility for remote candidates due to the travel component. Also initial line: "W2 only, no C2C, must be authorized to work in the US (both now and in the future)." That's a requirement about employment type and work auth. Could be included in Requirements. We need to avoid duplication: The overview already mentions travel 25-50% and 10-15 hours per week. Responsibilities also repeats that. It's okay to keep as is; we must preserve all substantive info, not remove. Duplication is okay? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should avoid duplicate lines. The overview and responsibilities both have the 10-15 hours per week and travel 25-50% lines. Those are duplicated. We should keep only one occurrence. Probably keep in Responsibilities (since it's more specific) and remove from overview. Or we could keep overview but remove duplicate from responsibilities. Let's decide: Keep overview concise without those specifics, and keep them in Responsibilities. So overview will not include those lines. Thus overview paragraph: "Carex is partnering with a fast-growing Series A healthtech partner to hire a Forward Deployed Engineer to help build an AI-native operating system. This is a highly technical, customer-facing engineering role for someone who wants to work directly with behavioral health providers, understand how their organizations actually operate, and rapidly build software that solves their hardest problems. Healthcare and EHR domain expertise is essential for this role. The ideal candidate combines deep technical ability with the communication and product instincts required to work directly with clinicians, billers, operators, and executives. This person will spend meaningful time in the field, turn complex healthcare workflows and legacy-system challenges into buildable product requirements, and ship production solutions in days rather than quarters. Help establish and scale the Forward Deployed Engineering function as the team grows." Wait the last sentence about scaling is in responsibilities; maybe keep it there. We'll keep overview without duplication. Now responsibilities list: include all items, but we need to ensure we include the 10-15 hours per week and travel 25-50% lines. Also include "Own complex data migrations..." etc. We must not include application instructions like "Apply now for this opportunity at Carex!" That's boilerplate/application instruction; remove. Also remove "Forward Deployed Engineer - EHR (Direct Hire) - Remote in New York City, New York." as job title heading not needed; but we can include location and W2 etc in a short

at top. Let's craft HTML:

W2 only, no C2C, must be authorized to work in the US (both now and in the future). Remote role based in New York City, NY with travel flexibility.

Then sections:

About the role

Carex is partnering with a fast-growing Series A healthtech partner to hire a Forward Deployed Engineer to help build an AI-native operating system. This is a highly technical, customer-facing engineering role for someone who wants to work directly with behavioral health providers, understand how their organizations actually operate, and rapidly build software that solves their hardest problems. Healthcare and EHR domain expertise is essential for this role. The ideal candidate combines deep technical ability with the communication and product instincts required to work directly with clinicians, billers, operators, and executives. This person will spend meaningful time in the field, turn complex healthcare workflows and legacy-system challenges into buildable product requirements, and ship production solutions in days rather than quarters.

Responsibilities

• Own complex data migrations from legacy EHRs, billing platforms, and other healthcare systems from discovery through production deployment.
• Work directly with behavioral health providers to understand their workflows, operational challenges, and technical pain points.
• Spend approximately 10–15 hours per week interacting directly with customers, including clinicians, billers, operational leaders, and executives.
• Translate ambiguous and interconnected customer problems into clearly scoped, buildable technical solutions.
• Write production software that solves real customer problems rather than limiting work to implementations, prototypes, specifications, or presentations.
• Build solutions independently and partner closely with Product Engineering on larger or more complex product initiatives.
• Navigate messy healthcare data, legacy systems, integrations, migrations, and operational workflows.
• Apply healthcare and EHR expertise to determine what should be built, not simply how existing requirements should be implemented.
• Work alongside Product Engineers on complex features spanning clinical, operational, billing, and data workflows.
• Bring insights from customer engagements back into product development so field learnings directly inform the roadmap.
• Travel approximately 25–50% to work closely with customers and understand their environments firsthand.
• Help establish and scale the Forward Deployed Engineering function as the team grows.

Requirements

• Strong software engineering skills and the ability to personally design, build, and ship production-quality software.
• Significant healthcare and EHR domain expertise.
• Experience working deeply with EHR platforms and healthcare technology ecosystems; substantial Epic experience is particularly valuable.
• Experience with EHR migrations, healthcare data migrations, or migrations from similarly complex legacy enterprise systems.
• The ability to work directly with customers while remaining a hands-on technical builder rather than functioning solely as an implementation or project-management resource.
• Strong product instincts and the ability to determine what should be built based on customer needs, technical constraints, and business context.
• Confidence communicating with clinicians, billers, operators, executives, and technical stakeholders.
• Experience making sense of messy data, legacy systems, incomplete requirements, and highly ambiguous problems.
• A bias toward shipping, rapid iteration, and getting working solutions in front of users.
• High ownership, autonomy, and comfort operating with significant scope in a fast-moving startup environment.
• Willingness to travel approximately 25–50%.
• Founder, early-stage, or 0-to-1 startup experience is valuable.
• New York City-based candidates are preferred, with greater flexibility for remote candidates due to the travel component.

We should also include the W2 etc maybe as part of Requirements? Already we have a short p at top. Could also incorporate into Requirements but it's fine. Check for any duplicated lines: The overview didn't have the 10-15 hours or travel lines. Responsibilities has them. Requirements has willingness to travel line (duplicate with responsibilities travel line). That's duplicate: responsibilities includes travel approximately 25–50% to work closely... Requirements includes willingness to travel approximately