Serious healthcare infrastructure.
We build healthcare technology businesses on a single Azure tenant and one compliance program. We hire when we need to. Most roles end up broader than the title suggests.
Location
US-based
Stack
100% Microsoft Azure
Compliance
HIPAA
Working at ApiVoc, in plain language.
We build real healthcare infrastructure: systems that process protected health information for actual customers under actual regulatory obligations. Everyone's work is visible and consequential.
We work in Microsoft 365 and Teams, build in Azure DevOps, monitor compliance through Drata, and operate everything on a single Azure tenant. The tooling is intentional and consistent.
Roles tend to be broader than their titles. An engineer here will touch claims processing, real-time pharmacy benefits, and ambient documentation surfaces, sometimes in the same week. Compliance work isn't a separate department; it's part of the operating fabric.
We hire when we need to, not on a schedule. We don't add seats to look bigger. When you join, you're joining because the work needed someone who could do it.
Location
Headquartered in Scottsdale, Arizona.
Schedule
Real meetings when needed, not by default.
Travel
Occasional team gatherings. Customer site visits per role.
Tooling
M365, Teams, Azure, Azure DevOps, Drata.
Four traits that translate.
Independent of role, the people who do well at ApiVoc tend to share a few things. None of these are deal-breakers if missing, but having them makes the team work.
Comfortable with compliance.
Healthcare technology runs on HIPAA, BAAs, and audits. You don't need to be a compliance expert on day one, but you should be willing to take the program seriously rather than treat it as overhead.
Self-directed.
Roles here are defined by outcomes, not activity. You should be able to identify what needs doing, prioritize, and ship, with the autonomy and responsibility that comes with it.
Plain-language thinker.
We avoid the language of healthcare technology marketing internally and externally. People who write and speak clearly, without buzzwords or dressing up the work, tend to fit.
Bias toward shipping.
We prefer working systems over polished plans. Iteration over architecture astronomy. If you find yourself drawn to building over discussing, you'll find others here who do too.
What we're hiring for now.
We're not actively hiring — but we'd still like to know about you.
This page is honest. If we had open roles, they'd be listed here. Right now we don't.
That said, we hire occasionally and often in narrow windows. If your background fits the kinds of work below and you'd be interested when something opens, send us a note. We keep candidate context for when roles emerge. We read every email.
Areas where we hire
- Backend engineering · API and platform
- Healthcare data integration
- Security & compliance engineering
- Site reliability & cloud operations
- Healthcare operations & subject-matter expertise
- Product · across multiple subsidiaries
A short, honest process.
No take-home assignments designed to extract free labor. No twelve-round panels. Four steps, paced respectfully, scoped to the role.
Initial conversation
About you, about us, about whether the role is a real fit before either side invests further. 30–45 minutes with a leader on the team.
Skills conversation
Role-specific. Could be a coding session, a system design walkthrough, a security review walkthrough, or a domain conversation depending on the role.
Team meets
Conversations with the people you'd work with day to day. This part of the process matters.
References & offer
Reference checks against candidates' suggested contacts. Background check where required. Offer extended directly by the hiring leader.
If your background fits, don't wait for a posting.
Roles open in narrow windows. Most of our hires came in through people who reached out before there was a job listing. If that's you, send a note. We'll read it.
What to include
A few sentences about your background, what you're looking for, and why ApiVoc specifically. Even a single line works. Resume or LinkedIn welcome but not required.
We won't add you to a recruiting drip campaign. Real human reads it, replies when there's reason to, and keeps your context for when something opens.