Senior Infrastructure Engineer II
Kit · Remote
USD 197,000 to 197,000 per year
Kit https://kit.com/ is the email marketing platform experts choose to grow their audience, deepen their relationships, and build a business around the work they love. For coaches, YouTubers, authors, podcasters, and other creatives, there isn't a better marketing hub to rely on to grow audiences, automate email marketing, and sell digital products — all within one platform.
More importantly, there isn't a team more committed to helping creators earn a living. We're on a mission to help creators earn $1 billion using our creator marketing platform. We have always been 100% independent and 100% remote.
We are proud to have built a product that our customers love, and we look for people who have enthusiasm and belief in our mission, vision, and values to join our team. We're also embracing AI thoughtfully — both in how we build and how we hire to ensure our team is adaptable, innovative, and ready for what's next.
THE ROLE
We're looking for a Senior Infrastructure Engineer II to take ownership of a large share of Kit's core infrastructure: databases, Kubernetes, version upgrades, platform tooling, and day-to-day support. You'll also build the paved paths that let engineers, non-engineers, and AI agents test and ship changes safely.
The infrastructure supports creators who depend on Kit to reach their audiences and earn a living. When it's healthy, nobody notices. That's the job.
This is a full-time Individual Contributor role for an experienced infrastructure engineer who likes owning production systems end to end, takes on-call seriously, leans into automation and enjoys making other people's work easier.
YOUR SUPPORT SYSTEM
You'll report to Mojtaba Hosseini https://www.linkedin.com/in/mojtaba-hosseini-7a6666/, VP of Engineering at Kit. Day to day, you'll work most closely with Kris Hamoud https://www.linkedin.com/in/kristopher-hamoud-17b34665/ and Ivan Mora Perez https://www.linkedin.com/in/ivan-mora-p%C3%A9rez-ab460b45/.
You'll also partner with product engineers across Kit, and with teams outside engineering who rely on infrastructure to get their work done. Once you're ramped up, you'll join a three-person on-call rotation, which works out to roughly one week in three.
WHAT YOU'LL DO
- First Week: Get access to our AWS accounts, Kubernetes clusters, monitoring, and CI/CD pipelines. Read through our runbooks and architecture docs. Take part in Get To Know Yous (GTKYs) with Kris, Ivan, and the engineering teams you'll support.
- First Month: Pick up day-to-day infrastructure support requests and start working through them with Kris and Ivan as backup. Ship your first improvement, such as a version upgrade or a fix to a gap in monitoring. Shadow on-call shifts. Write down what you learn along the way, especially the parts that only lived in someone's head or those that can be automated or improved.
- First Six Months: Own core infrastructure areas end to end: databases, Kubernetes, version upgrades, and platform tooling. Take your full share of on-call, which you'll start by the end of your first quarter. Become the go-to person for day-to-day infrastructure questions. Find one recurring source of pages and make it go away. Ship a first paved path, such as a sandbox environment where AI agents or non-engineers can safely build and test changes.
- First Year: You're the primary owner of a large part of Kit's core infrastructure, and you lead projects in it without needing direction. Uptime stays at 99.9% or better, page volume is down, and you've found real cost savings. Your paved paths are in regular use by engineers, non-engineers, and AI agents. You've built observability good enough for AI agents to handle some on-call load. You've documented your decisions so others can build on your work.
WHAT WILL S.E.T. YOU UP FOR SUCCESS
Skills
- Running production infrastructure on AWS at scale, including managed relational databases, networking, and load balancing
- Operating Kubernetes in production: upgrades, capacity planning, and troubleshooting
- Managing infrastructure as code and maintaining CI/CD pipelines that engineers trust
- Building monitoring and alerting that catches real problems early and doesn't page people for noise
- Diagnosing complex, multi-service incidents calmly, then fixing the underlying cause
- Cutting cloud costs through right-sizing and reserved capacity without hurting reliability
- Writing clear runbooks, docs, and decision write-ups
- Nice to have: experience with Cloudflare, ephemeral or sandbox environments, or email sending infrastructure
Experiences
- Around 7 or more years in infrastructure, platform, DevOps, or SRE roles
- Owning production infrastructure for a product where downtime costs customers money
- Carrying a pager for systems you owned, and making that on-call rotation quieter over time
- Leading a major upgrade or migration, such as a database or Kubernetes version upgrade, with little or no customer impact
- Building self-service tooling or paved paths that other engineers actually adopted
- Working on a small infrastructure team where you couldn't hand problems off to a specialist
Traits
- You own what you run. You spot infrastructure debt and fix it without waiting to be asked, and you follow through until it's done.
- You build quality into the work. Upgrades have rollback plans, maintenance windows are planned around customers, and "good enough" is a decision, not a default.
- You leverage AI effectively. AI helps you increase quality and velocity where it matters most. You know when to delegate and when to dive in, while holding accountability.
- You make work easier for everyone else. You'd rather build a tool or write a guide once than answer the same question ten times.
- You teach what you know. You write things down so the next person, or the next AI agent, can build on your work.
- You work in public. You share context and tradeoffs openly, including during incidents and when things go wrong.
- You use AI thoughtfully. It's part of how you work, and you help others adopt it without creating new risks.
- You remember who's on the other end. An outage means a creator's launch email doesn't go out, and that shapes how you prioritize.
WHAT WON'T SET YOU UP FOR SUCCESS
- Wanting a well-defined backlog handed to you each week. Here, you'll find much of the work yourself and set priorities with Kris.
- Preferring not to be on call. On-call is a core part of this role, shared across a team of three.
- You are skeptical of AI’s capabilities, or conversely use AI without good judgement and accountability.
- Wanting mostly greenfield architecture. A lot of this work is running, upgrading, and improving systems that already exist.
- Needing layers of approval before acting.
WORKING HOURS AND LOCATION
We're 100% remote with team members across the globe. We work mostly on East Coast time—so if you're based on the West Coast of the United States, Europe, or Asia, you might have a few early mornings or late evenings. We do our best to keep things reasonable, but a little time zone juggling comes with the territory.
This role is part of a three-person on-call rotation, so during your on-call week you'll need to be able to respond to pages outside your usual working hours.
We believe PTO should always take priority over on-call. We schedule on-call around people's lives, not the other way around. On-call is a shared responsibility, but taking time off should never be a challenge
COMPENSATION + PERKS + BENEFITS
Kit has standardized salaries based on position, no matter where you live. For this role, we're hiring at our level 4 ($197,000). Level is determined based on experience and our interview process.
PERKS + BENEFITS INCLUDE:
- Profit Sharing https://www.linkedin.com/feed/update/urn:li:activity:7454911054947688448/
- Kit equity
- 401k with a 5% match
- We cover up to $2,100 per month towar