Fractional Chief Technology Officer | Head of Engineering

elevAID; San Francisco, Las Vegas, St. Louis (CA, NV, MO); Ibrido; USD 50.000 - 120.000; Part-time

Descrizione del lavoro

Go Fractional seeks a Chief Technology Officer to own the architecture and lead engineering for a TEFCA-aligned healthcare interoperability platform. This is a part-time role with a clear path to full-time, remote across the United States.

You will drive the technical strategy, build scalable FHIR-based integrations, and guide the team as we move from MVP to a production-ready product focused on physicians and payers.

Competenze

• Strong technical depth and architectural ownership in healthcare data environments.
• Experience building or scaling integrations across EHRs, payers, and health systems.
• Comfort as the sole technical voice early on and ability to grow a team.
• Demonstrated ability to design and implement scalable data pipelines and security controls.

Mansioni

• Own the platform's technical architecture end to end.
• Design and scale FHIR-based integrations with providers and health systems.
• Lead TEFCA-compliant data pipelines and data normalization/matching.
• End-to-end ownership as MVP evolves into product layer; set tech stack directions.

Conoscenze

Technical leadership

FHIR/HL7 knowledge

Healthcare data

Systems integration

Data pipelines

Cloud/infra decisions

Descrizione del lavoro

Chief Technology Officer | Head of Engineering - Part-time to start, clear path to full-time

Compensation: $50k – $120k 5.0% – 15.0%

Work arrangement: Remote (United States) San Francisco +2

• Remote Work Policy: Onsite or remote
• Hires remotely in: United States
• Visa Sponsorship: Not Available
• Preferred Timezones: Pacific Time
• Relocation Allowed

Experience: 5 years of exp

About the job

The short version

We've built a live, TEFCA-aligned healthcare interoperability platform with real physician users and customers signing on pre-launch. What we haven't done is find the person who wants to own the architecture as much as we own the business and clinical side. If that's you, keep reading.

Why this exists

Healthcare data is scattered across EHRs, payers, and providers who don't talk to each other, and the people who pay for that are patients waiting on delayed care and clinicians drowning in denials and prior-auth back-and-forth. One of our cofounders had a surgery delayed because a record sat in the wrong system. That's the problem. We're not guessing at it, one of us spent four years inside RCM watching it happen daily, and our other two cofounders are practicing physicians who live it from the clinical side.

What you'd actually be doing

• Owning the technical architecture of the platform end to end, not just shipping features on someone else's spec
• Building and scaling FHIR-based integrations (we're currently working with providers via Metriport/Fasten-style connectors) across EHRs, payers, and health systems
• Designing our TEFCA-compliant data pipelines, including how clinical and billing data gets normalized, matched, and moved securely between systems
• Leading us toward our own QHIN (Qualified Health Information Network) and Carequality Implementer designations, so we're not permanently dependent on intermediaries
• Setting up and eventually managing an engineering team as we grow past MVP into the product layer
• Making the calls on stack, infra, and technical tradeoffs that we currently make by best guess and want someone with real conviction on instead

What we're working with today

Early-stage but not from-scratch: a live product, real usage data from physician users, and a customer pipeline forming pre-launch. You wouldn't be starting from a whiteboard, you'd be inheriting something real and shaping where it goes next, including rebuilding or hardening pieces you think deserve it.

What we're looking for

• Real technical depth, ideally with exposure to healthcare data, FHIR, HL7, or complex data infrastructure at a similar level of regulatory weight
• Experience building or scaling integrations across third‑party systems, not just internal tooling
• Comfortable being the first and only technical voice in the room, then building the team under you as we grow
• Wants to be a partner in this, not a hire executing a roadmap someone else wrote

What you'd be walking into

Two cofounders who've spent their careers in medicine, one who's spent his figuring out how to survive and grow across industries he had no business being in. We move fast, we've already proven people will use and pay for this, and we're looking for someone who wants to build the hard, unglamorous infrastructure that makes healthcare data actually move the way it should.