Careers

Build software for work that cannot afford loose ends.

Early Intervention agencies carry regulated records, hard deadlines, and families waiting for services. The product work demands precision, restraint, and respect for the people using it.

  • No open roles are posted right now
  • Unsolicited introductions are welcome
  • No application portal or automated screening
  • Product judgment matters as much as execution
The work

The interesting problems are close to the ground.

The job is to understand how an agency runs, then make the correct action obvious without flattening the domain.

Find the real constraint

A deadline, permission boundary, audit requirement, or handoff often matters more than the screen someone first asks for.

Treat safety as product work

Agency isolation, least privilege, reliable recovery, and careful copy belong in the same design conversation as layout.

Stay close to the user

Owners, coordinators, evaluators, providers, and agency staff each see a different slice of the same child record.
How we judge the work

Clear thinking shows up in the details.

Strong work here joins product decisions, careful implementation, and plain writing. One without the others leaves the agency carrying the gap.

You learn the domain

You read the source material, follow the record through the agency, and use the language practitioners already know.
  • Trace the workflow before choosing the interface
  • Separate verified facts from assumptions
  • Write so an agency owner understands the consequence

You own the outcome

A feature includes its permissions, loading and error states, responsive behavior, and the final words a person reads.
  • Make the next action unmistakable
  • Prefer durable system fixes over local patches
  • Say when evidence is missing
A useful introduction

Send the work that explains how you think.

A short note is enough. Include the kind of role you want, one or two pieces of relevant work, and why this problem holds your attention. Please do not send child or family information.

What to include

Links to shipped product work, code, writing, research, or design are more useful than a long cover letter.
  • The role or craft area you care about
  • Work that shows your judgment
  • Your location and working hours
  • A plain-text resume, if it adds context
Email your introduction

What happens next

An introduction is not an application to an unposted job. We keep the exchange direct and will not pretend there is an opening when there is not.
  • No recruiter database
  • No speculative take-home exercise
  • No promise of a role or interview
Keep an eye on the product

The changelog is the best view of how we work.

Read the current build notes, then write if your work belongs beside it.

There are no posted openings at this time.