Job Opportunities API

ABOUT WISPR We're building the first voice interface a billion people use every day. Our first product, Flow, lets you talk instead of type anywhere on your computer or phone, and turns messy speech into polished text that is ready to send. It's scaled from $2M → $50M in ARR in under 12 months with millions of users and thousands of enterprise customers. Read the master plan → https://wisprflow.ai/post/the-master-plan The team is still small enough that every person shapes what gets built. ABOUT THE ROLE Flow ships fast across Windows and iOS. Before every release, someone needs to put their hands on real devices and make sure the product works the way our users expect. That person is you. This isn't a traditional manual QA role. You'll pull feature branches directly from GitHub, build the app locally, and verify fixes against specific commits. When something breaks, you won't just file a ticket saying "it's broken" - you'll read the diff, trace the issue through the codebase using tools like Claude Code, and tell engineers exactly where things went wrong. You care about quality the way engineers care about their code. We're looking for someone with an engineering background who chose to focus on quality. You're comfortable in a terminal, you can read Swift and C++/C#, and you've built software before. You understand how the product works under the hood, and that knowledge makes you a significantly better tester. If you have high ownership, an obsessive eye for detail, and want to be the last line of defense for a product that millions of people rely on every day, this role is for you. WHAT YOU'LL DO Own pre-release testing on every build. Before each Windows and iOS release, you run the manual regression suite on physical devices. Verify every bug fix and new feature that went into the build. Pull, build, and test from source. You check out branches from GitHub, build the app locally, and test specific changes in isolation. When an engineer opens a PR, you can pull that branch, reproduce the reported issue on the previous build, and confirm the fix on the new one. You don't wait for packaged builds. Read code to test smarter. You look at diffs to understand the blast radius of a change. If a PR touches the audio session handling on iOS, you know to stress-test background/foreground transitions, Bluetooth audio switching, and long dictation sessions. Your test cases are informed by what the code actually changed. Use AI tools to debug and investigate. When you find a bug, you use Claude Code and similar tools to trace through the codebase, understand call paths, and narrow down root causes. Your bug reports include precise context: the relevant code path, the device/OS combo, logs, screen recordings, and the branch/commit SHA. Engineers can reproduce from your report alone. Test across apps, devices, and conditions. Flow works inside Notion, Gmail, Slack, WhatsApp, Cursor, VS Code, and hundreds more. You systematically test dictation across the most critical text fields on each platform. You test with different accents, background noise, whisper mode, long-form dictation, and language switching. You maintain and evolve the device matrix across Windows versions (10, 11) and iOS versions/devices. Maintain and grow the test case library. Every new feature and every fixed bug gets a test case. You own the manual regression suite and keep it current. Over time, you identify which test cases should be automated and work with engineering to make that happen. Monitor quality in the wild. You watch crash reports, user feedback, and support tickets. When patterns emerge, you reproduce and file them before they become widespread. You proactively test edge cases that nobody asked you to cover. WHAT WE'RE LOOKING FOR - Prior engineering experience - you've built software before and understand how codebases work - Comfort with Git workflows: branching, pulling, building from source, reading diffs - Ab