Senior Software Engineer, Perpetuals at Polymarket

<h2><strong>About Polymarket</strong></h2><p style="min-height:1.5em">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.</p><p style="min-height:1.5em">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.</p><h2><br /><strong>About the Role</strong></h2><p style="min-height:1.5em">Polymarket is launching perpetual futures and we're looking for Senior Backend Engineers to own the core systems that make it run. This is backend exchange engineering in the truest sense: low-latency order matching, high-throughput order state management, and the infrastructure that keeps an exchange operating correctly under load.</p><p style="min-height:1.5em">Ownership here is real and broad. We're looking for engineers who have built and operated order-book-based exchange systems before and can step in with deep context, take meaningful ownership of critical backend components, and raise the reliability and performance of the platform as we scale. If you've worked on the backend of a serious exchange and want to do it again somewhere with momentum, this is the role.</p><h2><br /><strong>What You'll Do</strong></h2><ul style="min-height:1.5em"><li><p style="min-height:1.5em"><strong>Own core exchange backend systems.</strong> Take deep ownership of the systems that power order matching, position management, and order state across perpetual futures.</p></li><li><p style="min-height:1.5em"><strong>Build and optimize the matching engine.</strong> Profile hot paths, reduce lock contention, and drive improvements to latency and throughput backed by benchmarks and production-grade evidence.</p></li><li><p style="min-height:1.5em"><strong>Design for correctness at scale.</strong> Build queueing and backpressure mechanisms that keep the orderbook consistent and reliable under high load, without crossing books, creating ghost fills, or introducing stale order state.</p></li><li><p style="min-height:1.5em"><strong>Build for observability.</strong> Instrument systems with metrics, logs, and traces. Establish rollback guarantees and narrow critical paths that make production incidents faster to detect, diagnose, and resolve.</p></li><li><p style="min-height:1.5em"><strong>Improve runtime performance.</strong> Optimize CPU, memory, and allocation behavior to meet the demands of a high-throughput exchange in production.</p></li><li><p style="min-height:1.5em"><strong>Own production incidents end-to-end.</strong> Debug latency and correctness issues di