Hi, I’m Ajmal Khan
Quality Engineering leader, 15 years across QA, test strategy, and now AI systems testing.
I’ve spent 15 years in Quality Engineering across companies ranging from large MNCs to early-stage startups, which means I’ve worked both ends of the release-cadence spectrum: three-month release cycles where every change was a ceremony, and continuous deployment pipelines shipping 100+ changes to production in a day. That range is where most of what I actually know about test strategy comes from.
Test strategy is the discipline of turning “we shipped and nothing broke” from luck into a guarantee: deciding what actually needs coverage, at which layer, and what’s safe to leave untested. Fifteen years of doing that across both three-month release trains and 100-deploys-a-day pipelines is where most of what’s on this blog comes from.
Contract tests at the API boundary, integration tests where services actually talk to each other, and knowing which of the two catches a given class of bug. Most production incidents I’ve debugged trace back to a boundary nobody tested, not a unit that was undertested.
The newest focus: applying that same discipline (know what you’re actually verifying, test at the right layer, don’t trust a green check you can’t explain) to systems where the thing under test doesn’t return the same answer twice. Currently formalizing it through a degree in AI Engineering and MLOps at BITS Pilani. TestEnigma is where it gets written up.
Outside of work, I’m in the gym more often than not. Same principle as testing, honestly: consistency beats intensity.
Have feedback, a correction, or an idea for a post? Reach out on LinkedIn, or leave a comment on any post here.