Senior Infrastructure Engineer II

Kit 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.

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.

You'll report to Mojtaba Hosseini, VP of Engineering at Kit. Day to day, you'll work most closely with Kris Hamoud and Ivan Mora Perez.

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.

• →
  • →

    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

  We value diversity in all of its forms. Research tells us that applicants who are female or non-binary, as well as applicants who are people of color, are less likely to apply for roles they do not feel 100% qualified for. If you think you meet more than 50% of our requirements but fewer than 100% of them, please apply.

  We’re imperfect communicators, so think of our job postings as the starting point for discussion rather than proof that you shouldn’t apply.

  Kit does not discriminate on the basis of race, sex, color, religion, age, national origin, marital status, disability, veteran status, genetic information, sexual orientation, gender identity or any other reason prohibited by law in provision of employment opportunities and benefits.

• 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