Member of Technical Staff

✨ Flexpa is hiring! Join us in building the future of healthcare data →We're hiring · Flexpal #7Member of Technical StaffFlexpa helps patients get access to their own health records. Every modern health app, AI care navigator, and patient-facing product needs access to actual records and we are the API that gets it for them.Our customers include apps, brands, and wearable devices you've definitely heard of, and a growing share of the companies leading the federal Patient Access push. We are six people. We have over ten years of runway. We are looking for our seventh Flexpal.Apply via the API →Read the role6people on the team10+ yrsof runway#7we're hiring nextUS/CAtime zones, US preferredWho we're looking forAn operator, not a stack.Someone who is unreasonably good at narrowing problems until they can be solved by an agent, and then building the agent that solves them.We are not hiring for a stack. We are not hiring for a title. We are not hiring for a specific years-of-experience number. We are hiring for a particular kind of operator: someone who can pick up a customer integration on Monday, ship a fix Tuesday, run a Claude Code loop overnight, get on a call with a payer's identity team Wednesday, and post a working prototype by Friday.The technical surface area at Flexpa is wide — FHIR, OAuth, identity verification, QHIN integrations, consent UX, agent orchestration, customer success — and our team is small enough that nobody owns one slice of it.We don't believe traditional hiring criteria predict success at Flexpa. Years in a particular language don't matter. Brand-name companies on a resume don't matter. What matters is whether you can read a problem, narrow it, and build the smallest possible thing that solves it, with an agent doing most of the work.MonPick up a customer integration.TueShip the fix.WedHop on a call with a payer's identity team.ThuRun a Claude Code loop overnight.FriPost a working prototype.What you'll actually doFour jobs, all at once. None of them optional.Agents01Build and operate agentsA meaningful share of our engineering work now happens through agent SDKs running in coding harnesses. You'll write less code by hand than you used to, and you'll architect more workflows than you ever have. If the phrase “Ralph Wiggum loop” doesn't immediately mean something to you, you'll learn what it means in your first week.Customers02Talk to customersEveryone at Flexpa takes customer calls. Not as backup. If this part doesn't excite you, this isn't the role.Pattern recognition03Find and fix product gaps before customers doOur most valuable engineers are the ones who notice that users are dropping off at step 4 of the consent flow, dig into why, and ship a fix without anyone asking. Pattern recognition matters more than ticket-taking.CTO04Work directly with our Cofounder and CTOYou'll take ownership of the things he's currently single-threaded on. You'll un-bottleneck PR review, vendor coordination, and integration debugging.What we're looking for in youFive things we will be honest about.01Demonstrated agentic capabilityNot “I use ChatGPT.” Not “I'm AI-curious.” Specifically: you have built and operated agents that do real work. You have used a coding harness (Claude Code, Cursor agent mode, Aider, Codex, equivalent) as a serious tool. Ideally you have shipped end-to-end automation using an agent SDK. You will be asked to walk us through specific things you've built.02US-based preferredPractical reason: you need to be a real user of US healthcare to use Flexpa. You'll need to test our consent flows on your own insurance, your own Clear account, your own Epic MyChart. Canada works if you're exceptional. Anywhere else is a much higher bar.03A chip on your shoulderYou think you’re better than your current title or scope reflects. You are tired of asking permission. You move faster than the org around you and it frustrates you. We want that.04You’ve worked a job where you had to talk to humansWaiting tables, retail,...