Outcomes Engineer

Moonfire; United States; Remote; USD 100,000 - 180,000; Full time

Job summary

Awell is seeking an Outcomes Engineer to own real customer outcomes end-to-end within healthcare workflows. You will engage with clinical, operations, and IT teams to understand how work is actually done, map pain points, and translate realities into practical platform integrations.

You’ll prototype with customers, decide when to build bespoke solutions or reuse components, and push for measurable impact. The role requires comfort with ambiguity and strong technical judgment.

Qualifications

• Experience shipping dependable systems and workflows.
• Ability to translate complex healthcare realities into platform solutions.
• Comfort handling ambiguous requirements without heavy processes.

Responsibilities

• Own a set of critical customers and their outcomes from signal to adoption.
• Work with clinical, ops, IT, and leadership to map real work.
• Build, configure, and iterate on workflows, data flows, and integrations.
• Prototype live with customers; learn fast and ship small increments.
• Decide when to build bespoke versus reusable components.
• Turn ambiguity into decisions and momentum; provide actionable insights to product.

Skills

Builder DNA

Outcome obsession

Pattern recognition

Comfort with ambiguity

Technical judgment

Narrative execution

Accountability

Job description

About the job

Location: Global (Remote) - US timezone hours

Compensation: $100K - $180K plus equity

Why this role exists

Awell operates inside messy, high‑stakes healthcare workflows where outcomes matter more than features. The Outcomes Engineer exists to own real customer outcomes end-to‑to‑end: deeply understanding how care is delivered, where value is created or lost, and translating that reality into systems, workflows, and product leverage.

This role sits at the intersection of our customers, our product, and our engineering team - not as a coordinator, but as an owner.

What you’ll own

• Own a set of critical customers and their outcomes from signal → solution → adoption → impact.
• Work directly with customers (clinical, ops, IT, leadership) to understand how work actually gets done, not how it’s described.
• Build, configure, and iterate on workflows, data flows, and integrations with our platform with the goal to unblock real operational pain.
• Prototype live with customers; learn fast; ship small; adjust based on reality.
• Decide when to build something bespoke and when to push for reuse - consciously and explicitly.
• Act as a forcing function: turning ambiguity into decisions and momentum.
• Feed sharp, grounded insights back into product to turn local learning into systemic leverage.

What makes you great at this

• Builder DNA: You’ve shipped things people depend on. “Broken” means someone can’t do their job.
• Outcome obsession: You don’t stop at “it works” - you care whether it actually changes behavior or results.
• Pattern recognition: You can spot the 2–3 interventions that remove 80% of friction in a messy workflow.
• Comfort with ambiguity: You don’t need perfect specs; you know how to move forward without hiding behind process.
• Technical judgment (not perfectionism): You can reason about APIs, data models, workflows, and reliability - and you know what needs to be bulletproof vs. good enough.
• Narrative + execution: You can explain why something matters to an exec and how it works to an operator.
• Accountability: When something doesn’t work, you fix it — you don’t deflect, elevate, or hide behind roles.

How you operate

• Customer outcomes are the only scoreboard.
• Reality outside the cave beats internal assumptions.
• You protect leverage: one-offs are conscious, documented tradeoffs — not accidents.
• You move fast and leave things better than you found them.
• You’re comfortable being the person who “just handles it.”

Bonus (not required)

• Experience in healthcare.
• Familiarity with FHIR or clinical data.
• Experience with workflow engines.
• Prior experience as a forward‑deployed engineer, solutions engineer, or deeply technical operator.

This role is not for you if

• You are not comfortable building systems, workflows and processes
• You want tickets, guardrails, or narrowly defined scope.
• You optimize for shipping artifacts instead of outcomes.
• You avoid customer‑facing ambiguity.
• You build local solutions and call them product.

At Awell

We expect you to hold narrative, technical truth, and execution - not because it’s easy, but because that’s how leverage is created. Outcomes Engineers are how we win with 1/100th the headcount.