Blog
The blog is where we share what we're learning as we build the platform. New posts as we have something worth saying.
Exit code 137 means SIGKILL. The kernel OOM killer, a failed liveness probe, or an outside actor: a diagnosis path that tells the three apart, with a runnable repro.
Most DevOps job ads are requirement soup that repels the engineers they need. How to write a JD around provable capabilities: structure, wording, lines to delete.
No CS degree? Not the blocker you think. What actually filters candidates out, the signals that substitute for credentials, and a working plan.
Most portfolio advice produces identical toy projects nobody reads. What hiring managers actually look for, five projects worth building, and how to present them.
Question lists test recall, not operating skill. What each interview stage can honestly tell you, and how to build a scenario that predicts performance.
Practise diagnosing CrashLoopBackOff, ImagePullBackOff, Pending pods, unreachable Services and OOMKilled containers through real troubleshooting paths.
Dropping the degree requirement is the easy part. The evidence ladder, the process changes, and the honest costs nobody puts in the framework posts.
Support engineers already have production instincts most career switchers lack. Map support experience onto SRE competencies, close the real gaps, make the move.
Resumes reward prestige, not skill. SkillBricks replaces the CV with proof from real environments, so the people with the skills get the interviews.
Coding-puzzle screens filter for test-takers, not engineers. Here is what they miss, why senior candidates skip them, and what to measure instead.
The CKA is not the only way to show you can run Kubernetes in production. Here is what actually signals DevOps competence, and five things you can start doing this week.
The architecture behind browser-based Kubernetes labs: xterm.js, Socket.IO, an assessment gateway, gVisor-sandboxed pods, and tmux for disconnect survival.
What we are building, why we are building it, and how the blog will work during the launch build.
How DevOps and SRE profiles actually get screened: where the six seconds go, what hiring managers care about, and how to stop optimising for signals nobody reads.