Skip to main content
Tiny Solutions
  • Demo
  • Pricing
  • What's new
  • Contact
Log inCreate agency
Create agency

Product

  • Intake
  • Services
  • Tiny Agent
  • Billing
  • Pricing
  • Security

Features

  • Referral forms
  • Authorizations
  • Session notes
  • EI Hub claim files
  • Integrations
  • Changelog

Company

  • About
  • Careers
  • What's new
  • Contact

Resources

  • Switch from ProviderSoft
  • Start an agency
  • Early Intervention guide
  • Help center
  • Developers
  • Roles

Connect

  • Explore the demo
  • Contact us
  • Help center
PrivacySecurity

© 2026 Tiny Solutions, Inc. · Each agency sees only its own records · Audit history is never rewritten · Email carries no PHI

Careers

Build software for work where small mistakes matter

Early Intervention agencies keep regulated records, meet hard deadlines, and serve families who wait for services. This work needs care, accuracy, and respect for the people who use the product.

Introduce yourselfWhy Tiny Solutions exists

There are no open roles right now. This page lists a role only when a real opening exists. You can still send a short introduction.

The work

The hard problems come from daily agency work

The job is to learn how an agency runs. Then you make the right next step clear, and you keep the details that Early Intervention needs.

Find the real limit

A deadline, a rule about who can see what, or a handoff between staff often matters more than the screen someone first asks for.

Treat safety as product work

Keeping agencies apart, giving each person only the access they need, recovering from failures, and careful wording are as important as layout.

Stay close to the people who use it

Admins, service coordinators, evaluators, providers, and billing staff each see a different part of the same child record.

How we judge the work

Clear thinking shows in the details

Good work here combines product decisions, careful code, and plain writing. If one is missing, the agency has to make up for it.

You learn the domain

You read the source material, follow the record through the agency, and use the words EI staff already know.

  • Follow the work before you design the screen
  • Separate verified facts from assumptions
  • Write so an agency owner understands the result

You own the outcome

A feature includes who can use it, what it shows while loading or after an error, how it fits a phone screen, and the words a person reads.

  • Make the next action clear
  • Fix the cause of a problem as well as the symptom
  • Say when evidence is missing

A useful introduction

Send the work that shows how you think

A short note is enough. Do not send child or family information.

What to include

Links to released product work, code, writing, research, or design help more than a long cover letter.

  • The role or craft you care about
  • Work that shows your judgment
  • Your location and working hours
Email your introduction

What happens next

An introduction is not an application for a job we have not posted. The conversation stays between you and us.

  • No recruiter database
  • No speculative take-home exercise
  • No promise of a role or an interview

The changelog shows how we work

Read the recent changes. Then write to us if your work fits beside them.

Read the changelogIntroduce yourself