
Lead Technical Architect
Added
1/9/2026
How Syndicated Job Posts Work
This Role is Closed
This is a Featured Job
Note: We've kept the name of the company private. If you'd like to know the company before requesting an intro, just email us at hello [at] fractionaljobs.io
About MedKey
MedKey Health is building a secure interoperability layer that unifies fragmented patient medical records across healthcare systems using standards-based integrations. We are intentionally starting with a FHIR R4 sandbox pilot to validate core infrastructure before scaling to production environments.
We are a founder-led, early stage company prioritizing correctness, auditability, and trust over speed or feature volume.
Role Overview
We are seeking a Fractional Lead Technical Architect to design and implement MedKey’s initial backend infrastructure. This role is ideal for a senior engineer who enjoys early stage problem solving, architectural ownership, and hands on building — without the pressure of full-time commitment.
You will lead the technical execution of our FHIR sandbox pilot and help define MedKey’s long term platform foundations.
What You Will Build (Initial Scope)
- Secure authentication to a FHIR R4 sandbox (SMART on FHIR / OAuth 2.0)
- Ingestion of core FHIR resources:
- Patient
- Encounter
- Observation
- MedicationRequest
- Condition
- AllergyIntolerance
- Dual-layer data storage:
- raw source records (immutable)
- normalized MedKey data models
- A unified patient timeline API
- Patient consent and role-based access controls
- Audit logging for data access and ingestion activity
- Baseline security practices (encryption, secrets management, environment separation)
This is a read-only, pilot-focused build. Production integrations, AI, and write-back workflows are explicitly out of scope for this phase.
Responsibilities
- Design MedKey’s system architecture and data flow
- Lead backend development and integration strategy
- Implement ingestion pipelines and background jobs
- Own data modeling and normalization logic
- Establish consent enforcement and auditability
- Document architectural decisions and pilot scope
- Participate in technical discussions with hospital IT and advisors
Required Experience
- 6+ years of backend or full-stack engineering experience
- Strong API design and data modeling skills
- Experience implementing OAuth 2.0–based integrations
- Familiarity with healthcare interoperability concepts (FHIR, HL7, CCD, etc.)
- Experience building systems on AWS or comparable cloud platforms
- Security-conscious approach to handling sensitive data
Nice to Have
- Prior healthtech or regulated-industry experience
- Direct experience with FHIR R4 or SMART on FHIR
- Early-stage startup or greenfield build experience
- Experience designing audit and compliance systems
Time Commitment & Engagement
- 15–20 hours per week (flexible scheduling)
- Initial engagement of 8–12 weeks, with the potential to expand scope or commitment based on pilot progress
What Success Looks Like (First 90 Days)
- Working FHIR sandbox integration
- Reliable ingestion of core FHIR resources
- Clear architecture and technical documentation
- Unified patient timeline API
- Pilot-ready backend with audit logging and consent enforcement
Hiring Timeline
We are intentionally taking a thoughtful approach to this hire. Our goal is to identify and onboard the right technical leader within the next 2–3 months.
Compensation:
This is a paid, fractional role. Compensation is competitive and commensurate with experience, with an expected range of $75–$120/hour for 15–20 hours per week. Equity participation may be discussed for the right long-term fit.
How to Apply
Note: This is a syndicated job post. Fractional Jobs found it on the web, but we are not working with the client directly, so we don't have control over or knowledge of the application process. To apply, click on the "View Application" button and follow the application's instructions. Let us know how it goes!
How to Get in Touch
Hit that "Request Intro" button below. Include any relevant links so we can get to know you better.
Your brief intro note should clearly address:
If we think there's a fit, we'll reach out to schedule an intro call. Looking forward!
MoreEngineeringJobs
Send fractional jobs,
playbooks, and more to
%20(1).webp)