Senior Full-Stack Developer / Technical Lead — Healthcare Marketplace

We are looking for an experienced full-stack developer, technical lead, or small development team to build a modern healthcare/pharmacy technology platform — similar in concept to Ironsail Pharma / ImpetusOne and VITL Rx. This will be a multi-tenant B2B healthcare SaaS platform connecting medical practices, providers, pharmacies, and eventually patients through one centralized system. We are not building a pharmacy. We are building the technology and marketplace layer that connects healthcare organizations with multiple independent pharmacy partners. What We Want to Build The goal is to create one platform where a clinic or provider can: Create and manage patients Select medications/formulations Compare available pharmacy partners View pharmacy pricing See which pharmacies can service a patient's state Submit prescription/order information Route prescriptions/orders to the appropriate pharmacy Track prescription status Track fulfillment Receive shipment/tracking information Manage refills Communicate regarding prescription issues View all pharmacy activity from one dashboard Instead of a clinic having separate accounts and portals with 5–20 different pharmacies, we want them to have one account, one interface, and one workflow. Pharmacy Marketplace The platform should support multiple pharmacy partners. Each pharmacy should have configurable information including: States serviced Pharmacy type (503A / 503B / retail / specialty) Medication catalog Formulations Strengths Dosage forms Pharmacy cost Shipping costs Estimated turnaround time Fulfillment capabilities API/integration method Active/inactive medications Active/inactive states When a provider selects a medication, the system should be able to display eligible pharmacies based on criteria such as: Patient State + Medication + Formulation + Pharmacy Licensure + Availability Eventually we would like intelligent routing and preferred pharmacy rules. Initial Integration Strategy We do NOT need every pharmacy fully API-integrated on day one. We want an architecture that allows multiple connection methods: API Pharmacy — Order and patient data transmitted through REST API, with status updates returned automatically. Portal / Manual Pharmacy — Our administrative team processes orders through the pharmacy's existing portal while the clinic still sees everything through our platform. Secure Fax / eRx Pharmacy — The provider sends the legal prescription through an existing e-prescribing solution while our system manages the patient/order/fulfillment workflow. CSV / Batch Pharmacy — Our system generates structured files that can be uploaded to a pharmacy partner. The objective is to launch quickly and automate progressively, rather than spending months integrating every pharmacy before going live. Provider / Clinic Dashboard Clinics should be able to: Create/manage patients Manage providers Search medications Browse pharmacy options Compare pricing Create prescription/order workflows Select pharmacy View current orders, status, and tracking Manage refills View patient history Receive alerts when an order has an issue Manage billing/account settings We want a very modern, simple UI. Think: Stripe + Shopify + modern telehealth software — not a traditional, outdated pharmacy system. Pharmacy Dashboard Participating pharmacies should eventually have their own portal, where pharmacy users can: View and accept incoming orders Review patient/order information Flag an order/problem Update order status Enter or automatically provide tracking Manage supported medications, pricing, and states serviced View order history and reporting Possible statuses: Pending Prescription → Received → Pharmacist Review → Processing → Ready for Shipment → Shipped → Delivered → Issue/Action Required Admin / Marketplace Dashboard Our internal team needs a powerful admin interface to manage: Clinics, providers, patients, pharmacies Pharmacy credentials, states, medication catalog, formulations, pricing Orders, prescription status, shipping/tracking Support issues, pharmacy performance, user permissions Agreements/documents, financial reporting, platform fees, analytics We also want the ability to configure which clinics can see which pharmacies, products, and pricing. Medication Catalog We need a centralized master medication/product catalog: Medication → formulation → strength → dosage form → pharmacy → pharmacy SKU → pharmacy cost → shipping → states available The same medication may be offered by multiple pharmacies at different prices and formulations. The architecture needs to support this cleanly. E-Prescribing We eventually want integrated e-prescribing. Experience with any of the following is highly valuable: Surescripts, DrFirst, DoseSpot, Photon, Rcopia, SureScripts-certified vendors, EPCS, NCPDP SCRIPT, pharmacy management systems. For V1, we are open to integrating an established e-prescribing vendor rather than attempting to build an e-prescribing network ourselves. We specifically want someone who understands the difference between the prescription and the pharmacy order/fulfillment workflow. APIs & Integrations The platform should be built API-first. We expect future integrations with: pharmacy APIs, EHRs, telehealth platforms, e-prescribing vendors, Stripe, shipping/tracking providers, SMS, email, webhook systems, potentially Shopify/WooCommerce, potentially laboratory platforms. We will also eventually expose our own API so outside telehealth companies can use our pharmacy network without using our full user interface: Telehealth Platform → Our API → Pharmacy Network White-Label Capability Long term, we want the platform to support white labeling — a healthcare organization should potentially be able to use pharmacy.theirbrand.com with their own logo, colors, pharmacy marketplace configuration, users, and preferred pharmacy network. This means the system should be designed as a proper multi-tenant SaaS architecture from the beginning. HIPAA / Security Because this system will handle PHI, experience building HIPAA-compliant healthcare software is strongly preferred. We expect proper implementation of: Role-based access control Encryption in transit and at rest Audit logs Secure authentication and MFA capability Session security Proper cloud architecture Database access controls Backups and logging Business Associate Agreement-compatible vendors Please do not apply if your only experience is building basic WordPress sites or simple consumer applications. Suggested Technical Architecture We are open to recommendations. Possible stack: Frontend: React, Next.js, TypeScript Backend: Node.js/NestJS, Python/FastAPI, Laravel, or other modern scalable architecture Database: PostgreSQL Cloud: AWS, Azure, or Google Cloud We care more about clean architecture and speed of execution than a particular programming language. Phase 1 / MVP We do NOT want to overbuild V1. The first version should focus on: Authentication and multi-tenant organizations Clinic dashboard Patient management Provider management Pharmacy management Medication/catalog management Pharmacy/state eligibility rules Pharmacy pricing Creating orders Assigning/routing orders to pharmacies Order status management Shipment/tracking information Admin dashboard Basic pharmacy dashboard Notifications Audit logging Initial payment integration Architecture for future APIs If a pharmacy does not initially have an API, our staff should be able to manually process that order while maintaining the exact same user experience for the clinic. We want to get V1 into production quickly instead of waiting for every outside integration. Phase 2 After proving the workflow: pharmacy API integrations, automated status updates, integrated e-prescribing, pharmacy comparison engine, advanced pricing rules, automated routing, patient portal, patient payments, automated refills, advanced reporting, external API, webhooks, white-label deployments. Phase 3 Eventually we envision this becoming a significant healthcare infrastructure platform connecting: Healthcare Practices → Our Technology/Marketplace → 503A/503B/Retail/Specialty Pharmacies → Patients Who We Want We would strongly prefer someone who has previously built or integrated: healthcare SaaS, pharmacy software, EHR software, telehealth platforms, prescription workflows, healthcare marketplaces, multi-vendor marketplaces, HIPAA systems, Surescripts, DrFirst, DoseSpot, Photon, pharmacy APIs, healthcare interoperability, HL7/FHIR, NCPDP, multi-tenant SaaS. You do NOT necessarily need pharmacy experience if you are an exceptional SaaS architect with strong API and healthcare experience. When Applying Please start your proposal with the words: PHARMACY PLATFORM (This lets us know you actually read the posting.) Then answer these questions: Have you built healthcare, pharmacy, EHR, telehealth, or e-prescribing software before? Please share links, live product URLs, GitHub, or case studies. Have you integrated with Surescripts, DrFirst, DoseSpot, Photon, or another eRx provider? Have you integrated directly with pharmacies or pharmacy management systems? Have you built a multi-vendor marketplace? Have you built multi-tenant SaaS software? What technology stack would you recommend for this project, and why? If we intentionally keep the first version lean, how would you architect the MVP? What features would you leave OUT of V1 so we can launch faster? Are you an individual developer, technical lead, or agency? Who will actually write the code? Are you available for ongoing development after the MVP? What is your estimated MVP budget range and timeline, based on the scope above? Important We are looking for someone who thinks like a technical co-founder / product architect, not simply someone waiting for us to provide detailed instructions for every screen. We understand the healthcare business and pharmacy workflow. We want someone who can help us determine: What needs to be built now vs. what can be integrated later vs. what should not be built ourselves at all. If you have already worked on a pharmacy marketplace, healthcare marketplace, prescription platform, telehealth infrastructure product, or pharmacy API integration, we especially want to speak with you. Please include your estimated MVP budget range, proposed team, recommended architecture, and examples of the most relevant work you have completed.