SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 197,000 - 197,000 / annual
Kit is a creator-focused email marketing platform helping coaches, YouTubers, authors, podcasters, and other creatives grow audiences, automate email marketing, and sell digital products. The company is 100% independent and remote, with a mission to help creators earn $1 billion using their platform.
You'll own a large share of Kit's core infrastructure: databases, Kubernetes, version upgrades, platform tooling, and day-to-day support. You'll build the paved paths that enable engineers, non-engineers, and AI agents to 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.
This is a full-time individual contributor role reporting to Mojtaba Hosseini, VP of Engineering. You'll work closely with Kris Hamoud and Ivan Mora Perez on the infrastructure team.
First week: gain access to AWS accounts, Kubernetes clusters, monitoring, and CI/CD pipelines; review runbooks and architecture docs; meet the engineering teams.
First month: handle day-to-day infrastructure support requests with backup from Kris and Ivan; ship your first improvement (version upgrade, monitoring fix); shadow on-call shifts.
First six months: own core infrastructure areas end-to-end (databases, Kubernetes, version upgrades, platform tooling); take full on-call share; become the go-to person for infrastructure questions; eliminate one recurring source of pages; ship a paved path (e.g., sandbox environment for AI agents or non-engineers).
First year: be the primary owner of large infrastructure areas and lead projects independently; maintain 99.9%+ uptime; reduce page volume; achieve real cost savings; ensure paved paths are in regular use; build observability for AI agents to handle some on-call load; document decisions for others to build on.
You'll join a three-person on-call rotation (roughly one week in three). The team works mostly on East Coast time; if based on West Coast US, Europe, or Asia, expect some early mornings or late evenings. PTO always takes priority over on-call.
REQUIREMENTS:
Skills:
- Running production infrastructure on AWS at scale (managed relational databases, networking, load balancing)
- Operating Kubernetes in production (upgrades, capacity planning, troubleshooting)
- Managing infrastructure as code and maintaining CI/CD pipelines engineers trust
- Building monitoring and alerting that catches real problems early without noise
- Diagnosing complex multi-service incidents calmly and fixing underlying causes
- Cutting cloud costs through right-sizing and reserved capacity without hurting reliability
- Writing clear runbooks, docs, and decision write-ups
- Nice to have: Cloudflare, ephemeral/sandbox environments, or email sending infrastructure experience
Experiences:
- Around 7+ 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 on-call rotations quieter over time
- Leading a major upgrade or migration (database or Kubernetes version) with little or no customer impact
- Building self-service tooling or paved paths that other engineers adopted
- Working on a small infrastructure team where you couldn't hand problems off to a specialist
Traits:
- Own what you run; spot infrastructure debt and fix it without waiting to be asked
- Build quality into work; upgrades have rollback plans, maintenance windows planned around customers
- Leverage AI effectively; know when to delegate and when to dive in while holding accountability
- Make work easier for everyone else; build tools or write guides rather than answer the same question repeatedly
- Teach what you know; write things down so the next person or AI agent can build on your work
- Work in public; share context and tradeoffs openly, including during incidents
- Use AI thoughtfully as part of how you work; help others adopt it without creating new risks
- Remember who's on the other end; understand that outages mean creators' launch emails don't go out
