=iOS & Desktop Quality Engineer

About the company: Series B | 11-50 employees | Founded in 2021

Key Job Info

• Location: LATAM
• Employment: Full-Time
• Work Type: Remote
• Experience: 4-5 Years
• Salary Range: $5000-$7000 / per month

Job Description

About Us

We are building the voice layer for AI, a dictation and voice interface product that lets users speak naturally and have their words converted to polished, formatted text in any application.

Doubling revenue every two months, the company is on track to hit $30M ARR in the coming months and $150M by year's end. Raised $85M to date at a $700M valuation, with a secondary sale at a $1B valuation currently in progress. Month-12 consumer retention is 70%, B2B NRR is 250%, and 3,700+ companies have deployed our product, including Meta, Notion, Klarna, Yahoo, and Groupon, with 200 new companies added every single week. The team builds its own voice models in-house, currently 3x better than the second-best model on the market.

About the Role

We are hiring a QA Engineer to be the last line of defense before every iOS and Windows release. This is not a traditional manual QA role. You will pull feature branches directly from GitHub, build the app locally, verify fixes against specific commits, and read diffs to understand the blast radius of every change.

When something breaks, you will use Claude Code to trace through the codebase, narrow down root causes, and hand off precise context to engineering. This is product-minded QA with an engineering background, someone who has built software before and chose to focus on quality. Desktop is more fleshed out, so iOS domain knowledge is a slight preference. One hire covers both platforms for now, with a possible split as volume grows.

What You'll Own

• Own pre-release testing on every iOS and Windows build, running the manual regression suite on physical devices
• Pull branches directly from GitHub, build apps locally, and verify specific fixes against specific commits before packaged builds exist
• Read code diffs to understand the blast radius of each change and shape your test cases accordingly
• Use Claude Code and similar tools to trace root causes when bugs surface, producing bug reports that engineers can reproduce alone
• Test Flow across Notion, Gmail, Slack, WhatsApp, Cursor, VS Code, and critical text fields on each platform, with variation across accents, noise, whisper mode, long-form dictation, and language switching
• Maintain and evolve the device matrix across Windows versions (10, 11) and current iOS versions and devices
• Own the manual regression suite and keep it current as features ship and bugs close
• Identify which test cases should be automated and partner with engineering on that transition over time
• Monitor crash reports, user feedback, and support tickets, proactively reproducing and filing patterns before they spread

Requirements

Must-Have

1. Prior software engineering experience. You have built software before and understand how codebases work.
2. Comfort with Git workflows: branching, pulling, building from source, and reading diffs.
3. Code-reading ability in Swift and Windows-side code (C++, C#, or similar). Swift day-one fluency is not required; strong general code-reading ability with the ability to ramp into Swift quickly is fine.
4. Comfort in a terminal. None of Git, local builds, or log inspection should feel foreign.
5. Claude Code or equivalent AI-assisted tooling as a daily part of your workflow. Not optional; the team uses these to trace bugs and separate real issues from AI slop.
6. Hands-on manual testing experience across iOS and Windows. Strong in one, willing to learn the other.
7. Meticulous bug reporting reproduction steps, logs, recordings, device/OS details, and commit/branch references.
8. High ownership mindset. Shipped bugs are treated as personal failures.
9. Attention to detail that borders on obsessive.
10. Based in LATAM with C2-level English and US time zone overlap.

Nice-to-Have

• Swift day-one fluency
• SDET-level system-building experience
• Prior iOS developer who pivoted to QA
• Experience testing voice, audio, or ML-powered products
• Familiarity with accessibility testing and assistive technology
• Experience with crash reporting and analytics tools (Sentry, PostHog, or similar)
• Background in localization testing across multiple languages
• Experience with products that interact at the OS level (keyboard hooks, overlays, input method editors)