Full Stack Engineer

WellTheory

4d•$140,000 - $165,000•Remote

About The Position

WellTheory is hiring an engineer to own what happens when things break, and then make sure they break less. When a member or Care Team member hits an issue, you’re first on it. You size the impact, find the root cause, get people unblocked, and decide what deserves a permanent fix. Your real job is to shrink the queue, not just work through it: spot patterns, ship upstream fixes, write runbooks, and automate the repetitive stuff. You’ll work across our member app, Care Hub (our clinical tooling for care teams), and the internal tools and data pipelines behind them. You’ll partner closely with our Member Support Specialist and Care Team, join a small, senior, fully remote engineering team, and report to our Co-Founder & CPO. You likely have 4+ years as a software engineer and fluency in TypeScript. Our stack is TypeScript/JavaScript, React, React Native, Node, Postgres, and GCP, with Sentry, GCP logs, Linear, and Slack day to day. You don’t need every piece. We’re a team of generalists who learn fast and make good trade-offs.

Requirements

4+ years as a software engineer
Fluency in TypeScript
US-based
Current US work authorization
Access to protected health information

Nice To Haves

Play detective. You follow the thread, connecting logs, errors, and Slack history without needing the whole system mapped out first.
Size impact before acting. One member locked out and ten providers unable to submit charting notes are not a tie, and you know which comes first.
Stay calm in the chaos. You triage, communicate, and work the problem.
Say only what’s needed. Members and providers get the answer, not the investigation.
Scale yourself. You use AI to move faster, and you’d rather automate a fix than do it a third time.
Care about the person on the other end. It shows in how you prioritize and communicate.
Know your limits. You ask for help before you’re drowning, but not for every splash.
Stay curious. You ask questions without fear and welcome new approaches.
Worked as a support, sustaining, or forward-deployed engineer.
Built internal tools, dashboards, or bots that made a support process disappear.
Worked in healthcare, or you care deeply about autoimmune or women’s health outcomes.
Done something most people wouldn’t: run a marathon, started a company, earned a degree while working full time, or overcome serious adversity.

Responsibilities

Triage first. Size the impact, reproduce the issue, and decide the next move.
Find the root cause. Dig through Sentry, GCP logs, and the codebase, and ship the fix when it’s worth it.
Unblock, then fix. Get the reporter moving first, then decide if the problem earns a ticket.
Kill recurring issues. Maintain a prioritized backlog and use quieter stretches to ship durable fixes, improvements, and feature requests.
Make next week easier. Write runbooks, build meaningful alerts, and create automations and AI agents that cut ticket volume.
Protect the queue. A ticket means “worth doing,” not “someone mentioned it.”
Handle member data with care.