Platform Engineer

What I do

I’m a Platform Engineer with a deep focus on site reliability. I build and maintain the infrastructure, tooling, and automation that teams depend on — systems that recover on their own, fail loudly when they can’t, and stay boring to operate day to day.

Platform engineering is the umbrella: internal tools, CI/CD, Kubernetes, observability, and the glue between application teams and production. SRE is how I specialize within that — reducing toil, improving visibility, and designing for resilience instead of heroics.

How I approach the work

Reliability isn’t a dashboard or an on-call rotation; it’s a set of design choices. I look for friction in manual workflows, gaps in visibility, and places where a small amount of code or infrastructure change prevents a whole class of incidents. Self-healing behavior, clear alerting, and documentation that outlives any single person on the team all serve the same goal.

Background

My path runs through operations, test engineering, and application support before moving into platform and reliability work. That mix shaped how I debug production issues, how I collaborate with application teams, and why I default to automation when a task shows up more than twice. Today I work on large-scale e-commerce infrastructure — automating deployments, improving observability at the edge and in the cluster, and building internal tools that keep CI/CD and monitoring dependable.

What I’m looking for

Teams that treat the platform as a product — reliable, documented, and built for the people who use it every day. I want to keep shipping high-impact automation, learn from strong engineers, and grow further into ML operations without losing the operational discipline that makes systems trustworthy.