The Problem: Healthcare Software That Actually Matters
Most telehealth platforms are digital band-aids on a fundamentally broken system. Patients wait weeks for appointments, navigate confusing interfaces, and often can't even get their medications delivered reliably. Meanwhile, healthcare providers are stuck with clunky EMRs that feel like they were designed in 2005.
At Rimo, we're building something different: telehealth infrastructure that actually ships medication to real patients. Not another SaaS dashboard that sits in a folder — software that directly impacts people's health outcomes.
The Technical Challenge: Multi-Tenant Healthcare at Scale
Here's what makes this interesting from an engineering perspective: we're not building one app. We're building a multi-tenant platform that powers multiple healthcare brands, each with their own workflows, branding, and regulatory requirements.
Our Stack: Type Safety All the Way Down
We've built our entire platform on a foundation of type safety:
- Next.js 14 with App Router for our frontend applications
- tRPC for end-to-end type-safe APIs (no more runtime API errors)
- Prisma with PostgreSQL for our data layer
- TypeScript everywhere — because runtime errors in healthcare software aren't just annoying, they're dangerous
The beauty of tRPC is that when a doctor updates a prescription on the frontend, TypeScript ensures that change propagates correctly through every layer of our stack. No manual API documentation. No wondering if the backend actually expects that field to be optional.
Multi-Brand Architecture: The Real Engineering Problem
The hardest part isn't the individual features — it's building them in a way that scales across multiple healthcare brands with different:
- Branding and UI customization (white-labeled experiences that don't feel generic)
- Prescription workflows (some brands focus on dermatology, others on hormone therapy)
- Pharmacy partnerships (different fulfillment networks, shipping requirements)
- Regulatory requirements (HIPAA compliance that doesn't slow down development)
Our multi-tenant architecture uses a combination of database-level tenant isolation and runtime configuration that lets us deploy new brands in hours, not months.
HIPAA-Compliant Development: Not Just a Checkbox
Healthcare compliance isn't just about encrypting data at rest (though we do that). It's about building systems where patient data can never accidentally leak between tenants, where audit logs capture every access, and where our entire deployment pipeline maintains compliance.
We've solved this with:
- Row-level security in PostgreSQL that makes cross-tenant data access impossible
- Audit logging built into our Prisma layer
- Encrypted communication for all pharmacy integrations
- SOC 2 Type II infrastructure (because trust isn't negotiable in healthcare)
Pharmacy Fulfillment: The Hardest Integration Problem
The most technically interesting challenge? Integrating with pharmacy fulfillment networks. Each pharmacy has different APIs, different data formats, and different ways of handling everything from insurance verification to shipping notifications.
We've built an abstraction layer that normalizes these differences, but pharmacy integrations are still one of our biggest engineering challenges. When a patient clicks "order," that triggers:
- Insurance verification (real-time API calls to multiple providers)
- Prescription routing (finding the right pharmacy based on medication, location, insurance)
- Fulfillment tracking (parsing shipping data from 5+ different formats)
- Patient notifications (SMS, email, push — all coordinated)
All of this happens behind a simple loading spinner, but the engineering complexity is enormous.
Why This Work Matters
I've worked on fintech apps, social media platforms, and e-commerce sites. This is different. Every feature we ship directly impacts someone's health. The prescription workflow we optimized last month? It helped a thousand patients get their medication two days faster. The pharmacy integration we debugged? It prevented insurance rejections that would have cost patients hundreds of dollars.
This isn't abstract software engineering — it's infrastructure that ships real medication to real people.
The Team: Small, Focused, High-Impact
We're a small engineering team (currently 4 people) building software that processes thousands of prescriptions per month. Every engineer here has massive scope and direct impact on the product.
Our current challenges include:
- Scaling our pharmacy network (integrating with 10+ new fulfillment partners)
- Building provider tools (giving doctors better prescription management interfaces)
- Expanding into new therapeutic areas (each one has unique regulatory requirements)
- Optimizing our checkout conversion (healthcare e-commerce is fascinating and weird)
The Role: Lead Engineer ($150K-$200K+, Remote US)
We need someone who can:
- Own large parts of the codebase (this isn't a narrow specialist role)
- Make architecture decisions that scale across multiple brands
- Mentor other engineers (we're growing the team)
- Ship features that directly impact patients (not just internal tools)
You should have experience with:
- TypeScript/Node.js (our entire stack is TS)
- Modern React patterns (hooks, context, server components)
- Database design (preferably PostgreSQL)
- API design (REST or tRPC experience preferred)
- Healthcare/compliance experience is nice but not required
More importantly, you should be excited about:
- Building systems that scale across multiple use cases
- Working in a domain where software quality directly impacts people's lives
- Being one of the first engineers at a company that's going to transform healthcare
What You'd Work On (First 90 Days)
- Prescription workflow optimization: Making our doctor-to-pharmacy handoff faster and more reliable
- New pharmacy integrations: Adding 3-4 new fulfillment partners to expand our coverage
- Multi-brand checkout flows: Building reusable components that work across different healthcare verticals
- Patient communication system: Improving how we keep patients informed throughout the fulfillment process
Ready to Build Healthcare Infrastructure That Actually Ships?
Healthcare software has been broken for decades. We're building the infrastructure to fix it, one prescription at a time.
If you're tired of building features that get buried in some corporate dashboard, come help us build software that gets medication to patients faster, cheaper, and more reliably.
Apply here — we review applications weekly and move fast with qualified candidates.
Rimo is building the future of healthcare delivery. Learn more at rimo.co.
Top comments (0)