Staff Infrastructure Engineer

Polymarket•New York, NY

3d•$250,000 - $500,000

About The Position

The growth engineering team at Polymarket owns the systems that bring new users in and keep them moving through the product — onboarding, referrals, user acquisition flows. These are high-stakes surfaces where a broken pipeline or a slow API doesn't just generate an incident ticket; it costs us real users at real scale. This is a senior IC role with a lot of autonomy and very little hand-holding. You'll design, build, and maintain the infrastructure layer that gives the growth team a stable, scalable surface to work on — so they can move quickly without stepping on landmines. You'll define what needs to be hardened, when to push back on shipping velocity in favor of correctness, and how to instrument systems before problems reach production.

Requirements

7+ years of infrastructure or platform engineering experience, with meaningful time spent owning systems in production
Track record of shipping systems under real user-growth pressure, not just maintaining inherited infrastructure
Comfortable owning systems end-to-end without close oversight, including making judgment calls when there's no obvious right answer
Experience reducing incidents proactively, finding bottlenecks in data pipelines or user-facing flows before they become outages
Strong instincts for the tradeoff between shipping velocity and correctness in a fast-moving team environment

Nice To Haves

Prior experience building growth-specific infrastructure such as referral systems, onboarding flows, or user acquisition tooling
Experience working in small, high-autonomy engineering teams where the scope of your role is defined by what needs to get done

Responsibilities

Design and maintain the infrastructure layer that growth engineers build on top of, including onboarding flows, referral systems, and user acquisition pipelines
Debug reliability incidents affecting growth surfaces, own the investigation end-to-end, and make sure the same failure mode doesn't repeat
Review growth team pull requests for infrastructure soundness, scalability concerns, and anything that could cause problems at higher traffic volumes
Instrument data pipelines to surface bottlenecks and failure points before they hit production
Coordinate with growth engineering to make clear calls about when to harden existing systems versus when to ship new ones
Set the standards and patterns that the growth team builds against, so individual engineers aren't making the same infrastructure decisions from scratch on every project
Identify the ambiguous systems that sit between teams, define their boundaries, and drive improvements without waiting for someone to assign them to you