Full-stack Engineer
Posted
Summary
Full-stack/backend engineer at PathwAI builds the HTTP APIs, queues/webhooks, and integrations (CRMs, scheduling, analytics, payments-adjacent flows) powering its HIPAA-minded funnel builder that handles sensitive health data. Core stack is TypeScript/Node with PostgreSQL and Cloudflare Workers, plus observability and security-minded design.
Build the APIs, integrations, and builder backend that power HIPAA-minded funnels—from submission pipelines to CRM and billing hooks.
PathwAI sits between
sensitive health data ,
third-party tools , and
operator workflows . You’ll own services and integrations that ingest submissions, route leads, enforce guardrails, and keep observability honest—so our customers can trust the pipe as much as the UI. What you’ll do
Design and implement
HTTP APIs
and background work (queues, webhooks, retries) for the builder and runtime. Build and maintain
integrations
(CRMs, scheduling, analytics, payments-adjacent flows) with clear failure modes and idempotency. Collaborate with frontend engineers on
contract shape , pagination, and real-time or near-real-time updates where needed. Improve
observability : structured logs, tracing hooks, and alerts that help us catch issues before customers do. Participate in
security-minded design
reviews—least privilege, secret handling, and safe handling of PHI-adjacent payloads. What we’re looking for
5+ years
building production backend or full-stack systems; comfortable owning a feature end-to-end. Strong
TypeScript
or
Node
ecosystem experience, plus a solid database mental model (transactions, migrations, indexing basics). Experience with
REST
and/or
RPC
APIs, auth patterns, and integration testing against external vendors. Pragmatism about
reliability : retries, backoff, deduplication, and clear operator-facing errors. Nice to have
PostgreSQL
(or similar) at scale; familiarity with migration tooling. Cloudflare Workers ,
Durable Objects , or edge-style runtimes. Prior work in
health tech ,
HIPAA , or other regulated environments. Exposure to
event-driven
architectures and workflow or job systems. How we work
Engineers work closely with product and design; we prefer
thin vertical slices
over long-lived branches. You’ll have room to propose architecture, but we value
simple systems
that the next person can operate.
sensitive health data ,
third-party tools , and
operator workflows . You’ll own services and integrations that ingest submissions, route leads, enforce guardrails, and keep observability honest—so our customers can trust the pipe as much as the UI. What you’ll do
Design and implement
HTTP APIs
and background work (queues, webhooks, retries) for the builder and runtime. Build and maintain
integrations
(CRMs, scheduling, analytics, payments-adjacent flows) with clear failure modes and idempotency. Collaborate with frontend engineers on
contract shape , pagination, and real-time or near-real-time updates where needed. Improve
observability : structured logs, tracing hooks, and alerts that help us catch issues before customers do. Participate in
security-minded design
reviews—least privilege, secret handling, and safe handling of PHI-adjacent payloads. What we’re looking for
5+ years
building production backend or full-stack systems; comfortable owning a feature end-to-end. Strong
TypeScript
or
Node
ecosystem experience, plus a solid database mental model (transactions, migrations, indexing basics). Experience with
REST
and/or
RPC
APIs, auth patterns, and integration testing against external vendors. Pragmatism about
reliability : retries, backoff, deduplication, and clear operator-facing errors. Nice to have
PostgreSQL
(or similar) at scale; familiarity with migration tooling. Cloudflare Workers ,
Durable Objects , or edge-style runtimes. Prior work in
health tech ,
HIPAA , or other regulated environments. Exposure to
event-driven
architectures and workflow or job systems. How we work
Engineers work closely with product and design; we prefer
thin vertical slices
over long-lived branches. You’ll have room to propose architecture, but we value
simple systems
that the next person can operate.