blog / sre
SRE practice and incident response
On-call, incident review, blast radius, and the judgment calls that do not fit in a runbook.
13 posts
Posts
From developer to SRE: the skill bridge that matters
How to become an SRE from a developer background: the skills that actually transfer, the gaps to close, and how to get incident reps without the title.
Kubernetes NetworkPolicy debugging: when pods can't talk
Kubernetes NetworkPolicy not working - or working too well? A test method for silent packet drops: default-deny surprises, selector typos, DNS egress.
What hiring can learn from incident reviews
Your engineering hiring process could learn a lot from your incident reviews: blameless analysis, process evidence, and a bias for how over whether.
Requests and limits: the misconfigurations that page you
Kubernetes resource limits and requests, minus the folklore: CPU throttling, limit=request tradeoffs, missing requests, and the LimitRange safety net.
How to practice Linux troubleshooting deliberately
Practice Linux troubleshooting the deliberate way: break-it-yourself drills, a skill ladder from beginner to on-call ready, and feedback loops that stick.
Evicted pods: node pressure and who gets killed first
Kubernetes pod evicted? How node-pressure eviction works, what the eviction message means, why QoS class decides who dies first, and how to clean up.
Why we log commands, not screen video
Interview recording doesn't need a camera. A timestamped command log is searchable, costs kilobytes, and can't capture anything outside the lab.
How to grade an incident: process over outcome
Incident response evaluation should grade process, not luck. How to score diagnosis quality, wrong-turn recovery, verification, and blast radius.
Debugging under pressure: staying methodical on the clock
Debugging under pressure is a trainable skill: hypothesis discipline, timeboxing, note-taking, and panic recovery for interviews and 3 AM incidents alike.
HPA not scaling: metrics-server and the usual suspects
HPA not scaling? The ordered checklist: metrics-server health, missing resource requests, misread targets, behavior windows, and what the conditions mean.
SRE interview prep: a 4-week plan built on practice
SRE interview preparation as a 4-week training plan: Linux fundamentals, Kubernetes debugging, incident scenarios, and communication - with drills for each.
SRE interview questions: scenarios beat trivia
SRE interview questions built as scenarios beat trivia every time. Real prompts, what strong and weak answers look like, and how to score them fairly.
Blast radius: measuring what you broke while fixing
Blast radius is what a candidate broke or risked while fixing the fault. Why it's the most predictive hiring signal that nobody is measuring today.