About the role
About Polymarket Polymarket is the world's largest prediction market platform. We enable individuals to express views on real-world events by trading on outcomes across politics, economics, sports, culture, and current affairs. Built as a peer-to-peer marketplace with no centralized "house," Polymarket aggregates diverse opinions into transparent, market-based probabilities that reflect collective expectations about the future. We're growing fast, both in terms of volume ($21B traded in 2025) and adoption as an alternative news source. Our ambition is to become a ubiquitous beacon of truth in global media and we need your help adding fuel to the fire.
About
the Role Our Mobile Platform Team ships fast. We're iterating constantly on a product that millions of people use to make real-money predictions on real-world events, and quality is not optional. This role exists because we need someone who can hold the line on quality without slowing us down, someone who sees every release as a responsibility, not a formality. You'll split your time roughly in half. Half is hands-on manual testing of new mobile features before each release cutoff. The other half is making that manual work increasingly unnecessary by improving our AI testing harness and extending automated coverage across our core flows. This isn't a role where you're just running scripts someone else wrote or checking boxes on a test plan. You'll have real ownership over how quality gets defined and verified on this team. The right person for this role has worked at a product company where the app was always evolving and where "we'll fix it later" wasn't an option. You've seen what it looks like when quality slips at scale, and you don't want to be the reason it happens here.
What You'll Do Manually test new mobile features end-to-end before each release cutoff, catching issues that matter to real users before they ship. Sign off on releases and communicate quality status clearly to engineers, product managers, and leadership, no ambiguity, no hedging. Improve our AI testing harness to reduce the volume of repetitive manual verification, using agentic tools to do the tedious work so you can focus on the hard calls. Extend automated test coverage across core trading and market resolution flows, identifying gaps and closing them systematically. Dig into product behavior with genuine curiosity, asking why things work the way they do and flagging when something feels off even if it technically passes. Adapt quickly when priorities shift, treating a last-minute scope change as a problem to solve rather than a reason to escalate. Work directly with mobile engineers to surface bugs early in the development cycle, not just at the end of it.
