The posting, in Polymarket's own words
archived Sep 4, 2026About 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
Polymarket is looking for a Mobile Infrastructure Engineer to own mobile infrastructure end-to-end: the release pipeline, CI, test infrastructure, stability, and observability that let a small mobile platform team ship a high-traffic trading product quickly and safely. You'll also help build our AI layer — the harnesses, evaluations, and developer tooling that make AI a first-class part of how we build and ship mobile software. This is a generalist, hands-on role. You'll build and operate the tooling behind how the team ships — release automation, CI, test infrastructure, observability — and extend that toolchain with AI. The work spans services and code: alongside the pipelines and dashboards, you'll go into the app itself to fix crash clusters and harden error paths. We're looking for someone who has kept a high-traffic consumer mobile product shipping reliably.
Read the full posting ↓
What You'll Do
Own the release tooling across iOS and Android: automated builds, code signing, store submission, phased rollouts, hotfix paths, and post-release health checks after every deployment Build and maintain CI infrastructure that earns trust: build-time budgets, flaky-test detection and quarantine, merge gates, and device and simulator infrastructure that keeps feedback loops short Build the quality tooling: regression gates and automated coverage that let the team set and defend crash-free and ANR targets — and go directly into app code to fix crash clusters and harden error paths when the tooling surfaces them Run the observability stack and alerting that surfaces problems before users feel them Build AI into the mobile toolchain: create evaluation harnesses for AI-assisted features, embed into developer workflows, and make AI a first-class part of how the team ships and tests Measure everything: set budgets, track them over time, and prove improvements with data rather than instinct