Infrastructure Engineer
block mbNew York (NY)
About the role
$220,000 - $320,000 + equity My client is a Series A company building a Platform as a Service that runs inside their customers' own cloud. Instead of asking companies to move workloads onto someone else's platform, they provision and operate battle-tested Kubernetes clusters directly in customer AWS, GCP and Azure accounts, then automate the day 2 operations. Startups get enterprise-grade reliability and scale without the DevOps overhead, and they never hit the graduation problem that forces teams off a platform as they grow. They are looking for an Infrastructure Engineer to own and evolve the infrastructure management system behind that platform. This is a pure IC role on a flat engineering team of around 20. You will be working on some of the hardest problems in cloud infrastructure: designing systems that work seamlessly across three clouds for hundreds of customers, from seed-stage startups to post-IPO companies. You will not just set up infrastructure. You will write the software that programmatically manages and rolls out changes across every customer environment. Unlike back-office infra at a larger company, here your work is the product. You will talk to top customers directly and help broker deals worth hundreds of thousands of dollars.
What you will be doing:
- Building and maintaining the software that provisions, manages and rolls out infrastructure changes across hundreds of customer cloud accounts on AWS, GCP and Azure
- Designing cloud-agnostic infrastructure architecture that scales from seed-stage companies to public enterprises, without breaking the bank
- Engineering reliable, automated systems to handle the complexity of multi-cloud Kubernetes deployments at scale
- Collaborating directly with customers on Slack and calls to understand their infrastructure needs and turn those into platform improvements
- Raising the bar on reliability and code quality so that any customer's DevOps team could look under the hood and say "there's no chance I'm doing this better"What they are looking for 4+ years as an infrastructure or platform engineer
- You currently write production application code as a software engineer, rather than working as a pure DevOps or SRE specialist
- You have built or contributed to core infrastructure at an infrastructure company (PaaS, IaaS, cloud platform or internal developer platform) or at a company with a very high engineering bar
- Strong proficiency in GoHands-on multi-cloud experience across AWS, GCP or AzureNice to have
- Built infrastructure at a VC-backed infrastructure startup
- Experience with RustBS in Computer Science or an equivalent technical degree
- Logistics5 days per week onsite in New York City, with 30 remote days and 30 days PTO per year
- Relocation support available
- Process: hiring manager call, technical screen, one-day onsite with some flexibility for remote components. Feedback within 24 hours at every stage
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
More like this