About the Project

VoiceOS (voiceos.com) is the Siri for Productivity, a desktop application that turns speech into action across your apps. Instead of just transcribing what you say, VoiceOS interprets your intent and executes real actions in external applications via MCP (Model Context Protocol): send a Slack message, create a calendar event, update a doc, all by voice. The app works system-wide across macOS and Windows. We are a Y Combinator (S25) company based in San Francisco.

Who We Are Looking For

We are looking for a detail-oriented QA tester to join our team and ensure the highest quality of our product. This is a manual, user-focused testing role with no automation required. Your job is to use the app as a real user would, explore every feature on staging before it ships, and surface bugs, UX inconsistencies, and anything that feels off or uncomfortable in the user experience.

You should be comfortable working with desktop applications (macOS and/or Windows), have a good intuition for what makes a product feel polished, and be able to clearly communicate issues you find. Familiarity with voice-based products or AI tools is a plus but not required.

Responsibilities

  1. Manual / Exploratory Testing: Thoroughly test all app functionality on staging builds, including transcription, voice commands, MCP actions (Slack, Calendar, and future integrations), custom vocabulary, history and re-transcription, settings, authentication, and localization (Japanese, French, etc.).
  2. User Experience Review: Go beyond pure bugs. Identify friction points, confusing flows, visual inconsistencies, and anything that would make a real user uncomfortable or confused. Think like a power user who relies on VoiceOS all day.
  3. Cross-Platform Testing: Test on macOS and Windows, paying attention to platform-specific behaviors, edge cases (e.g., Windows key interactions, clipboard behavior), and ensuring feature parity.
  4. Design Verification: Check that the implemented UI matches design intent, including correct elements, spacing, animations, and overall visual polish.
  5. Bug Documentation: Follow our established process for reporting issues in Linear, including clear reproduction steps, expected vs. actual behavior, screenshots/recordings, and environment details.

Requirements