Back to jobs

Senior Applied AI Engineer, AI Platform

Reads like a Data Engineer role: pipelines and data infrastructure.

Remote · San Francisco, CA · Seattle, WA · New York, NY · United States

Actively hiring, first seen by us 10 days ago
Pay
Pay not listedSimilar roles state $127K–$189K
Work setting
Remote — work setting source
Location type: Remote
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
All Cost Centers › Research & Development › Engineering & Technology › Engineering — team source
Department: All Cost Centers › Research & Development › Engineering & Technology › Engineering
From the employer’s posting

What you’ll work on

Full posting

Self-serve gets a function most of the way.

Legal still reads every provider contract and payer amendment by hand, because what would help isn't a chat window.

  • Design for PHI from the start.

From the employer’s posting
Self-serve gets a function most of the way. It doesn't get them all the way.
Legal still reads every provider contract and payer amendment by hand, because what would help isn't a chat window. It's a system that knows what a redline means here, what gets escalated, and what our position was the last four times. Credentialing, claims exceptions, and CX triage each have their own version: work that is obviously automatable but full of enough domain-specific detail that nobody outside the function can build it, and nobody inside can build it alone.
Kill work that shouldn't exist. Some requests are better answered by a workaround, a config change, a process change, or nothing. Finding those is worth as much as building. Design for PHI from the start. Eddy operates inside HIPAA. This is not solutions or sales engineering. There's no deal cycle, and your users are colleagues. It's not a pure platform role either: you'll spend real time inside other teams' problems.

Before you apply

Sponsorship
Visa sponsorship not confirmed — sponsorship source
Will you now, or in the future, require visa sponsorship for employment visa status (e.g. H-1B visa status)?
From the employer’s application form

What you’ll bring

All qualifications

Core experience

  • Experience we're seeking:
  • 5+ years shipping production software end to end.
  • Experience as a forward deployed engineer, solutions engineer, internal platform engineer, or founder is a plus, as is work on agent frameworks or developer platforms.
Qualification wording
Experience we're seeking:
5+ years shipping production software end to end.
Experience as a forward deployed engineer, solutions engineer, internal platform engineer, or founder is a plus, as is work on agent frameworks or developer platforms. Healthcare experience is not required, but you should be able to dive into an exception-heavy domain and build a working mental model fast, several times a year.

About Headway

Eddy is Headway's in-house AI agent platform and the highest-leverage internal product we've shipped.

In the employer’s words · Read in context · Company website ↗

Apply at Headway

Posting record

Report an error

Actively hiringFirst seen by us 10 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 12, 202610 days ago
Recorded sightings
10
Last seen by us
Nov 21, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$189K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,448 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 10

Similar jobs usually come down between day 6 and day 56.

At Headway, jobs usually come down by about day 84.

From 14,767 similar postings that came down, and 7 of Headway’s. Coming down is not always a hire.

Headway is hiring

7 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring is picking up
  • Its jobs tend to stay up a long time
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • TypeScript
  • AWS
  • Datadog
  • DynamoDB
  • Kafka
  • Redis
  • Snowflake
  • FastAPI
  • React
  • SQLAlchemy
  • PostgreSQL
Where the posting names them
Tools we use: Languages: Python 3, TypeScript Frontend: React 19, React Router 7, Tailwind, Radix, TanStack Query
AI: Claude Agent SDK, Anthropic API, Bedrock, LangSmith Infrastructure: AWS, EKS (a hardened pod per session), EC2 + CodeDeploy blue/green, Temporal, Kafka, Cloudflare Ops: Datadog, Sentry, PagerDuty, GitHub Actions
Infrastructure: AWS, EKS (a hardened pod per session), EC2 + CodeDeploy blue/green, Temporal, Kafka, Cloudflare Ops: Datadog, Sentry, PagerDuty, GitHub Actions AI tools: Cursor, Claude Code, and Eddy itself. We build Eddy with Eddy.
Frontend: React 19, React Router 7, Tailwind, Radix, TanStack Query Backend & Storage: FastAPI, SQLAlchemy 2.0 (async), Alembic, Postgres, Redis, DynamoDB, Snowflake AI: Claude Agent SDK, Anthropic API, Bedrock, LangSmith
Who you are: - An end-to-end product builder who moves between a React surface, a FastAPI service, and a container image without a handoff. - Serious about AI as engineering: tool use, agent loops, evals, context management, and cost and latency at volume.
Languages: Python 3, TypeScript Frontend: React 19, React Router 7, Tailwind, Radix, TanStack Query Backend & Storage: FastAPI, SQLAlchemy 2.0 (async), Alembic, Postgres, Redis, DynamoDB, Snowflake

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

1 in 4 people in the US have a treatable mental health condition, but most providers don't accept insurance, making therapy too expensive for most people. Headway’s mission is to fix this by building a new mental healthcare system everyone can access. We started by solving the biggest barrier to care: insurance. The admin work - credentialing, claims, payment reconciliation - is a nightmare. We've automated that.

But we're going further. Over 90,000 providers across all 50 states run their practice on our software, serving over 2.6 million patients. We are building the best tools for therapists to run their entire practice, reimagining the experience of finding a therapist, and investing in the platform foundations to enable this at scale, and building much of it with AI. We aren't just a billing layer; we are becoming the platform where care actually happens.

We're a Series D company with $325M+ in funding (a16z, Accel, Spark Capital, etc.), looking for exceptional people to help us achieve this mission. We want your time here to be the most meaningful experience of your career. Join us, and help change mental healthcare for the better.

About Eddy at Headway:

Eddy is Headway's in-house AI agent platform and the highest-leverage internal product we've shipped. It gives every Headwegian an agent harness pointed at Headway's own systems: an isolated sandbox per conversation, tool access to the third parties we depend on, and the ability to turn any of it into something durable, like a shareable interactive app, a workflow, a scheduled agent, a Slack teammate, or a webhook-triggered automation. Today 850+ Headwegians use Eddy daily, and 40k+ scheduled agents and workflows run every week with no one in the loop.

We sit in Engineering Foundations and own all of it: the chat product, the agent loop, the sandboxed runtime, the tool and integration layer, the artifact and app platform, the workflow engine, the eval harness, and the safety and access-control model that lets this touch real production and healthcare data without causing incidents. We're a small team with a very large surface area.

About this role:

Self-serve gets a function most of the way. It doesn't get them all the way.

Legal still reads every provider contract and payer amendment by hand, because what would help isn't a chat window. It's a system that knows what a redline means here, what gets escalated, and what our position was the last four times. Credentialing, claims exceptions, and CX triage each have their own version: work that is obviously automatable but full of enough domain-specific detail that nobody outside the function can build it, and nobody inside can build it alone.

That's this role. You'll embed with one function at a time and build them a real product on top of Eddy. Then you'll do the harder half: work out which parts are specific to that function and which are primitives that belong in the platform, and land the primitives in Eddy so the next function gets them for free. Most quarters should end with a function measurably better off and a new capability in the platform.

What you'll do:

- Find the real bottleneck. Sit with a function long enough to see the work, and define success in their terms: turnaround time, escalation volume, error rate, headcount avoided.

- Build the vertical. Skills, MCP integrations against their systems of record, subagents, scheduled and event-driven agents, artifact apps, and whatever product surface the workflow needs. You own it end to end.

- Ship in days, harden over weeks. Get a rough v1 in front of real users fast, then do the unglamorous work of making it dependable.

- Own it in production. Evals, tracing, cost and latency, failure modes. If a function depends on it, you're on the hook for it.

- Extract the primitives. Land the generalizable half in Eddy as a first-class capability, with tests and docs.

- Kill work that shouldn't exist. Some requests are better answered by a workaround, a config change, a process change, or nothing. Finding those is worth as much as building.

- Design for PHI from the start. Eddy operates inside HIPAA.

This is not solutions or sales engineering. There's no deal cycle, and your users are colleagues. It's not a pure platform role either: you'll spend real time inside other teams' problems.

Tools we use:

Languages: Python 3, TypeScript

Frontend: React 19, React Router 7, Tailwind, Radix, TanStack Query

Backend & Storage: FastAPI, SQLAlchemy 2.0 (async), Alembic, Postgres, Redis, DynamoDB, Snowflake

AI: Claude Agent SDK, Anthropic API, Bedrock, LangSmith

Infrastructure: AWS, EKS (a hardened pod per session), EC2 + CodeDeploy blue/green, Temporal, Kafka, Cloudflare

Ops: Datadog, Sentry, PagerDuty, GitHub Actions

AI tools: Cursor, Claude Code, and Eddy itself. We build Eddy with Eddy.

Who you are:

- An end-to-end product builder who moves between a React surface, a FastAPI service, and a container image without a handoff.

- Serious about AI as engineering: tool use, agent loops, evals, context management, and cost and latency at volume.

- Someone who likes users you can see. You've gravitated toward internal platform or developer tooling work, or taught something and enjoyed it.

- Able to hold a scope conversation: push back, renegotiate, say no, and leave people wanting to work with you again.

- A platform thinker who starts specific, and has the judgment to tell which half of a build is which.

- Comfortable owning outcomes with no spec and no backlog.

- Guardrails by instinct, and precise in communication with people who don't write code.

Experience we're seeking:

- 5+ years shipping production software end to end.

- Has built and shipped LLM/agent-powered products to real users.

- Experience as a forward deployed engineer, solutions engineer, internal platform engineer, or founder is a plus, as is work on agent frameworks or developer platforms. Healthcare experience is not required, but you should be able to dive into an exception-heavy domain and build a working mental model fast, several times a year.

You'll love this role if you want to:

- See a real business problem through to a shipped product your colleagues depend on.

- Shape an AI platform from the outside in.

- Have the most cross-functional engineering role at Headway.

Comprehensive benefits:

Medical, dental, vision, HSA/FSA, 401(k) including match for 2027!, Carrot Fertility reimbursement, and paid parental, medical and caregiver leave.

We believe a team's strength is in its people, and we cannot achieve this mission without a team that reflects the diversity of this problem – across race, ethnicity, gender, sexuality, age, national origin, religion, family status, disability, military status, and experience. Headway is committed to the full inclusion of all qualified individuals. As part of this commitment, Headway will ensure that persons with disabilities are provided with reasonable accommodations. If reasonable accommodation is needed to participate in the job application or interview process, to perform essential job functions, and/or receive other benefits and privileges of employment, please inform the recruiter when they contact you to schedule your interview.

Headway participates in E-Verify. To learn more, click here.

A notice to Headway applicants: To protect yourself against phishing and recruitment fraud, please note that Headway only accepts applications through our official careers page at https://headway.co/careers. Headway will never refer you to external websites, ask for payment or personal information, or conduct interviews via messaging apps. All official communication will come from a @findheadway.com email address. If you are contacted by someone claiming to be from Headway via an unofficial channel, please do not share any information and report it as spam.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.