Job Description
About the job We’re hiring someone who treats infra like product , not a ticket queue. We’re a startup shipping a multi-service platform (web portals +mobile + APIs + workers). Containers and Kubernetes are already in play — what we need now is an owner who makes deploys boring, environments trustworthy, and 3am pages rare. If your idea of fun is turning “works on my machine” into “green pipeline -> tagged image -> rolled out with a rollback plan,” keep reading. You might be our person if you: Have 3+ years owning cloud + containers in production (startup or product team beats pure ticket-ops) Have shipped microservices (many images, many deployables), not only a single monolith VM Can read a failing CI log and a CrashLoop pod without waiting for someone else to translate Prefer automation and guardrails over heroics (“I’ll SSH and fix it”) Write docs/runbooks like the next engineer is hungover and on call Are opinionated about reproducible builds, environment drift, and secret sprawl and willing to fix them Thrive in a small team where you talk to backend + frontend engineers daily, not only “raise a CRQ” How to apply Send: A short note on the nastiest production incident you owned (what broke, what you changed so it can’t happen the same way) Links / bullets: pipelines, Kubernetes, or “before/after” DX wins you’re proud of CV / LinkedIn
Required Skills
['Docker Kubernetes Facets']
Additional Information
NA
