Back to jobs
FamilyWell

Software Engineer, Full Stack

Remote$140,000 – $155,000Posted 20h ago

Immigration summary

Visa sponsorship

UnclearInsufficient evidence

We could not match this company to a verified filing entity.

View visa evidence

Green card sponsorship

UnknownInsufficient evidence

Employer filing history could not be verified.

View green card evidence

Job description

Key Responsibilities & Duties

  • Design, build, and ship full stack features across our Registry platform — frontend, backend, and database.
  • Build and maintain integrations with our core platforms, including Healthie (EMR), Candid (RCM), Spruce (messaging), and HubSpot.
  • Write and maintain APIs and webhooks that connect FamilyWell’s systems, with attention to idempotency, retries, and data reconciliation.
  • Design and evolve database schemas and queries (Postgres), balancing performance, data integrity, and clarity.
  • Partner with Product, Data, and Clinical Operations to translate requirements into technical designs and shipped software.
  • Write unit, integration, and end-to-end tests; participate in code review and uphold engineering quality standards.
  • Support CI/CD pipelines, deployments, and monitoring/observability for the systems you build.
  • Follow HIPAA and security best practices for handling protected health information (PHI).
  • Troubleshoot and resolve production issues, working cross-functionally to identify root causes.

Minimum Qualifications

  • 3–6+ years of professional software engineering experience as a full stack developer.
  • Proficiency with a modern JavaScript/TypeScript stack (e.g., React/Next.js on the frontend; Node.js or Python on the backend).
  • Strong SQL skills and experience working with relational databases (Postgres preferred).
  • Experience building and consuming REST APIs and integrating with third-party platforms/SaaS tools.
  • Comfort working across the full stack — from UI to backend services to data layer — rather than specializing in one layer only.
  • Strong testing discipline and code quality habits (unit/integration testing, code review, documentation).
  • Ability to work independently in a fast-paced, remote startup environment and communicate clearly with cross-functional partners.
  • Experience using AI-powered development tools (e.g., Claude Code, GitHub Copilot, Cursor) to accelerate coding, testing, and debugging workflows.

Nice-to-Haves

  • Experience in healthcare or another regulated industry, with familiarity with HIPAA and PHI handling.
  • Hands-on experience with healthcare platforms such as Healthie, Spruce, Candid, athenahealth, or similar EMR/RCM systems.
  • Healthcare data experience — working with clinical, claims, or operational data in a warehouse/BI environment (e.g., Snowflake, dbt, Sigma).
  • Familiarity with healthcare data standards and interoperability (FHIR, HL7, X12/837-835).
  • Experience with cloud infrastructure (AWS/GCP), containerization (Docker), and CI/CD tooling (GitHub Actions).
  • Prior experience at an early-stage startup, comfortable with ambiguity and shifting priorities.

Compensation

$140,000-$155,000. While the anticipated range is within this band, flexibility may be limited based on the candidate’s experience and overall fit.

Sponsorship evidence

Why Openbound reached the conclusions above.

Visa sponsorship evidence

Current posting

Silent on sponsorship

Employer filing history

Unavailable

We couldn't confidently match this employer to a verified U.S. filing entity, so reliable H-1B and PERM history isn't available yet.

Filing history reflects past employer behavior; it isn't a promise for this opening.

All open roles at FamilyWell
How Openbound evaluates sponsorship

Visa history uses official U.S. Department of Labor H-1B LCA disclosure data and USCIS H-1B petition history. Green card history uses DOL PERM disclosure data. Each is read for the employer as a whole, for roles like this one, and for this location, weighted toward the most recent fiscal years.

An employer is matched to its filing entities by verified legal name and reviewed aliases; a match is never made on a name resemblance alone. Where no verified entity can be matched, the page says so and draws no conclusion from the absence.

What this posting states outranks history in both directions, and an employer's published policy outranks past filings. Filing history reflects past behavior; it is not a promise of sponsorship for this opening, and none of this is legal advice.