Senior Software Engineer, Test

About Tin Can

Tin Can is building a safer, simpler way for kids to connect — without smartphones. We’re creating screen-free, delightful devices and services that let families call the people who matter most, free from the noise of today’s digital world.

We’re building a bold, authentic, nostalgic, and kinda quirky brand that resonates with folks who want something simpler & better for their kids than the tech-infused lives we’re currently living (and who have a sense of humor about it). As we gear up to scale to thousands of families, we’re ready to bring on an engineer to help make it happen.

The Role

When a kid picks up a Tin Can, the call has to work the first time, every time — whether that’s a call to Grandma or a call to 911. That promise is only as good as our ability to prove it holds before a release goes out. We’re looking for a Senior Software Engineer, Test to own that proof: the automated testing that verifies every call path works, on every change, before it reaches a kid’s phone.

You’ll own our end-to-end and call-path test suites and the checks that gate a release. The surfaces are real: a staging environment where a change can place an actual SIP call before it merges; a Flutter app on iOS and Android; firmware on ESP32 devices; and a call-decision engine whose scenario suite you’ll grow into our strongest safety net. You’ll work alongside our voice, app, infrastructure and firmware engineers, and you’ll be the person who defines what “tested” means here.

What You’ll Do

• Own our end-to-end and call-path test suites — the automated checks that tell engineers a change is safe to ship

• Build automated SIP test calls that run in staging before every merge — real calls verified for connection, audio, voicemail, and the call record afterward

• Guarantee emergency calling with continuous, safe verification, so we can show that every Tin Can reaches 911

• Grow regression coverage across the paths families depend on most — voicemail, contact approval, missed calls — so every release protects them

• Automate the manual parts of our release process across mobile, backend, and firmware, so releases get faster and safer as the fleet grows

• Shape our CI/CD: what runs on every pull request, what gates a deploy, and what a failing check blocks

• Partner with firmware on repeatable release testing, and push on testability — device emulation, test hooks — so device behavior is verified automatically on every build

• Measure the suites themselves — coverage of the paths families use, signal engineers can trust, and defects caught before they ship