Manual QA → SDET in 90 days
What to learn, what to skip, and what you should have to show at the end. Built for 30 minutes a day around a full-time job.
Read it →Test automation, written down properly
I interview SDET candidates for a living. Before that I was a manual tester trying to work out how to cross over. This is what I wish someone had written down.
Three things worth your time, in the order most people need them.
Fifteen questions about what you have actually built and done, scored the way I score candidates when I sit on the hiring panel. You get a number, the gaps that would sink you, and what to fix first.
Take the readiness checkWhat to learn, what to skip, and what you should have to show at the end. Built for 30 minutes a day around a full-time job.
Read it →The first test I write for any AI feature has nothing to do with AI. A schema assertion, and why it catches more than an eval suite.
Read it →Why the word exists, how it decays from a label into a budget line, and why development is growing its own version right now.
Read it →Most advice for manual testers moving into automation is either a tool tutorial or a motivational post. Neither tells you what a hiring panel is actually looking at.
I sit on that panel. I also made this exact transition, recently enough to remember which parts hurt — a Mechanical Engineering degree, manual testing on kiosk software, and now a Senior SDET role where the thing under test is an AI agent whose output changes every run.
Everything here is written from that seat. No affiliate links, no course funnel.