Medical Technician

THE ROLE

You'll provide the operational ground-truth that healthcare AI projects fail without — the daily rhythm of how labs flow, how specimens get handled, how charge capture actually happens, where the manual workarounds live, why the same scan gets ordered twice. We need someone who has done the work, knows where the system breaks, and can sit with our engineering teams to make sure what we build helps technicians instead of adding documentation burden on top of them.

WHAT YOU'LL DO

• Embed with client technical staff during discovery — shadow shifts, document workflows, surface the unwritten rules of the lab or clinic floor
• Review automation designs against operational reality — flag where they'll break, where they'll create burden, where the workaround is already better
• Co-design clinical operations dashboards and reporting tools from the user side, not the architect side
• Help build evaluation scenarios that test AI features against real edge cases — the busy Friday afternoons, the staffing-short mornings, the seasonal surges
• Translate technician-floor knowledge into specifications engineering can build to
• Support training, change management, and rollout from the operational side as clients adopt new systems

WHAT WE LOOK FOR

• Active certification as a Medical Technician (MT, MLT, RT, surgical tech, or equivalent depending on specialty). Minimum 3 years floor experience
• Deep familiarity with at least one major operational system — LIS, RIS, EHR specimen workflows, charge capture, instrument interfaces
• Comfort with ambiguity. You'll be observing and translating more than executing standard protocols
• Curiosity about how technology gets designed — you've thought about how the system you use every day could be better, and you can articulate it
• Strong written communication. Operational documentation is half the deliverable
• Bonus: prior implementation, training, or consulting role; cross-departmental experience; experience with workflow design tools

HOW TO APPLY

Send a résumé and a short note (3–5 sentences is plenty) about a problem you've solved that sounded easy on paper and turned out to be hard.