Join our team and build your career with us
Why this role matters
Healthcare decisions today are often made with missing context.
Incomplete records. Delayed data. Fragmented systems.
At DIME, we’re building something different.
A clinical memory and intelligence backbone — where every patient has a complete, longitudinal story, and every doctor can make decisions with clarity and confidence.
This role sits at the center of that mission.
You won’t just be building APIs.
You’ll be shaping how medical data flows, connects, and becomes usable in real clinical moments.
Responsibilities
Design and build scalable backend systems for EMR, CDSS, and healthcare intelligence modules
Own core services handling patient records, encounters, clinical data pipelines
Develop secure, high-performance APIs (REST / GraphQL where needed)
Work with structured and unstructured clinical data (labs, imaging, notes, medications)
Contribute to clinical logic systems (rule-based engines, workflows, validations)
Support interoperability (FHIR, HL7, integrations with hospital systems)
Ensure systems are stable under real clinical load
Optimize database queries and system performance
Build for offline-first sync and real-world constraints (low connectivity environments)
Implement strict data protection practices (HIPAA-like standards, GDPR-aligned thinking)
Design role-based access and secure data handling
Work closely with product and security on safe data flows
Work closely with product, AI, and frontend teams
Translate clinical and operational needs into backend systems
Support rapid iteration without compromising system integrity
Requirements
4–7+ years of backend development experience
Strong experience with Node.js (or similar backend frameworks)
Solid understanding of databases (PostgreSQL preferred)
Experience designing production-grade APIs
Worked on EMR/EHR, healthtech platforms, or clinical systems
Familiarity with FHIR / HL7 / medical data standards
Understanding of clinical workflows is a strong advantage
Able to design systems, not just write endpoints
Thinks in data flows, edge cases, and real-world constraints
Balances speed with long-term maintainability
Takes ownership
Comfortable working in ambiguity and building from scratch
Cares about impact — not just code
Node.js (core backend)
PostgreSQL + Supabase
REST APIs (with evolving architecture toward modular services)
FHIR-based interoperability layer
Offline-first sync architecture (IndexedDB + background sync)
Cloud: AWS / Edge Functions
You’ve taken ownership of one core backend domain (e.g., encounters, patient records, CDSS logic)
You’ve improved performance or reliability of a critical system
You’ve contributed to at least one clinical workflow or intelligence feature
The team relies on your judgment for backend decisions
