Skills this job asks for
LeadershipComplianceTypeScriptNode.jsJavaScriptPython
Add your CV (free) to see which of these your CV is missing.
Where you can work from
United States only
Based on the listing's location: Remote (USA).
The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.
Visa sponsorship, if you would relocate
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal: ask the recruiter.
-
?
No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
Before you apply
Sponsorship unknown
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →
About the role
Staff Software Engineer, AI-Native Systems
Location: Remote (US)
We are
Virtual care only works if the infrastructure behind it does. Wheel builds that infrastructure: the systems that let telehealth run at scale for the patients, clinicians, and companies that depend on it. We're not bolting AI onto old workflows; we're rebuilding how care gets delivered, with AI in the product and in how we build it.
We do this in a live, regulated healthcare environment where getting it right matters. This is the next architecture of virtual care, and we're building it now.
You are
A staff-level engineer who has built software in a regulated, high-stakes domain (ideally health tech; fintech and insurtech count too) and knows what that demands: sensitive data, regulatory constraints, and the cost of getting it wrong. You've designed and shipped AI and agentic systems in production, you know where they break, and you have opinions, held loosely and argued well, about building them safely.
You're a builder first, and you've done real work in small, scrappy teams. You still write the hard parts of the code yourself, and you've done it recently. You don't need a platform org, TPMs, or layers of review to move.
You operate as a domain owner, not a task owner. You take a problem that isn't well-formed, define it, tie it to what the business has committed to, and lead a group of engineers to a shipped, measured outcome. Your impact shows up in other people's work: the patterns they reuse and the ambiguity you removed before it cost the team a quarter.
You get things done. You have sharp judgment about what actually moves the outcome, you'd rather ship something useful this week than something perfect next quarter, and you know when good enough is good enough (and when, in healthcare, it isn't).
And you're good to work with. You're curious, generous with your time, quick to give credit, and you can disagree hard without making it personal. Smart matters here; kind matters just as much. Bonus points if people genuinely enjoy being on a team with you.
The Work
Technical Leadership & Direction
•
Own the technical direction for a significant AI-native area of the platform, such as patient and clinician experiences, care delivery, or the AI platform layer other teams build on.
•
Act as tech lead for a team or cross-team initiative: break down ambiguous problems, sequence delivery, clear blockers, and keep the team pointed at the outcome rather than the ticket.
•
Connect day-to-day engineering to quarterly commitments and company goals, and make those links visible to the team.
•
Write and review design docs. Make and document the load-bearing calls, including "not yet" and "buy, don't build."
AI & Agent Engineering
•
Design and build production AI features and agents: retrieval, orchestration, tool calling, guardrails, evaluation, and observability.
•
Define what "production-ready" means for AI here (testability, rollback safety, cost ceilings, failure modes, human-in-the-loop boundaries) and hold the bar in review.
•
Take on the hardest parts of the build yourself. This is a hands-on role; you are expected to be in the code every day.
Healthcare-Grade Engineering
•
Treat privacy, security, and responsible AI use on sensitive health data as hard engineering requirements, and turn compliance constraints into concrete architecture.
•
Partner with clinical, compliance, and legal stakeholders early, so safety and review are designed in rather than bolted on.
•
Build for the realities of healthcare: integrations with clinical systems, auditability, and high-reliability workflows.
Cloud-Native Delivery
•
Own full-stack delivery in TypeScript/Node.js and Python: services, APIs, data jobs, and the interfaces on top.
•
Own deployment, monit
View original listing ↗