> Markdown version of [/jobs/ext/2727914-staff-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/2727914-staff-infrastructure-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Staff Infrastructure Engineer

- **Company:** POLYMARKET CLEARING LLC
- **Location:** New York, United States
- **Experience:** Expert
- **Salary:** $250,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Software Debugging, Data Pipelines
- **Published:** September 5, 2026
- **Apply:** https://startup.jobs/staff-infrastructure-engineer-polymarket-9925550

## About the Role

* 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
 * (Plus) Prior experience building growth-specific infrastructure such as referral systems, onboarding flows, or user acquisition tooling
 * (Plus) Experience working in small, high-autonomy engineering teams where the scope of your role is defined by what needs to get done

## Description

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.

What You'll Do

 * 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


## Related Videos

- [Throwing off the burdens of scale in engineering](https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering)
- [Why and when should we consider Stream Processing frameworks in our solutions](https://www.wearedevelopers.com/videos/1085-why-and-when-should-we-consider-stream-processing-frameworks-in-our-solutions)
- [Using AI Without Losing Your Skills](https://www.wearedevelopers.com/videos/2045-using-ai-without-losing-your-skills)
- [Rest API Antipatterns](https://www.wearedevelopers.com/videos/100208-rest-api-antipatterns)
- [Platform Engineering vs. DevOps Why not both?](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both)
- [Python-Based Data Streaming Pipelines Within Minutes](https://www.wearedevelopers.com/videos/1233-python-based-data-streaming-pipelines-within-minutes)

## Related Articles

- [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)
- [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)
- [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated)
- [The Best X (Twitter) Accounts for Developers](https://www.wearedevelopers.com/magazine/294-the-best-x-twitter-accounts-for-developers)