Associate Software Engineer

Radiology is the second most used healthcare service, used by over 51% of the workforce annually. Despite the critical role of radiology in healthcare, the process for undergoing a medical imaging exam has remained unchanged for decades. OneImaging is solving this with a concierge approach and a premium-quality radiology network of over 5,000 vetted providers across 48 states, which also reduces imaging costs by 60-80%. Our solution helps patients and families access essential radiology services at fair prices and without surprise bills, all while delivering immediate savings and ROI for employers and payers on every exam.

We're hiring Full Stack Software Engineers graduating between December 2026 and June 2027 to join our engineering team in Miami, starting May or June 2027. This is not a rotational program and it isn't a shadowing role. You'll join one of our product squads and work across the whole stack — from the data model through the API to the interface a patient or a care navigator actually uses. Our engineering team is around twenty people, which means the work you ship is visibly yours and the distance between your code and a patient getting a scan scheduled is very short.

It also means you'll be building alongside a team that has moved unusually early on AI-assisted engineering. We run a shared AI harness that every engineer's agent builds on, we have AI agents running in production behind guardrails and eval suites, and we're explicit internally that writing code is no longer the slow part of the job — the slow parts are deciding what to build and verifying what comes out. We'll expect you to use these tools heavily and to own everything they produce for you.

What you'll do:

• Build and ship full stack features across our React frontend and TypeScript/Node.js backend, with a senior engineer as your mentor and reviewer
• Work across every layer of a feature — the migration, the API, the interface, the tests — with guidance at first and increasing independence as you go. Owning whole features end to end is the next step up our ladder, and it's a short step from here
• Work with AI coding agents as a normal part of your workflow, and take full accountability for the output: you should be able to explain every file in your diff
• Write tests across the stack, and treat verification as part of shipping rather than a phase afterwards
• Participate in design reviews and code reviews from your first weeks — including reviewing other engineers' work, because a bare approval with no comment isn't a completed review here
• Ask why. We reason from first principles and we have an explicit norm that engineers are not implementation machines — if a requirement doesn't make sense, we want you to say so