I've spent 13 years in the gap between what gets built and what was meant. Vague requirements, rushed designs, untested edge cases — I find them before they cost you.
Practical guides and engineering perspectives — written for teams who take quality seriously.
Most teams bolt quality on at the end. The highest-performing engineering orgs bake it into the very first conversation. Here's how to make that shift.
If your UI is hard to automate, that's a design problem. A deep look at how product and design teams can build testability into every screen from day one.
A complete walkthrough of setting up a CI/CD pipeline with quality gates at every stage — lint, unit, integration, E2E, and performance checks before every deploy.
Step-by-step guide to setting up a production-ready Playwright framework using TypeScript, Page Object Model, fixtures, and custom reporters.
How I use Claude Code to generate, review, and refactor Playwright tests — cutting test authoring time by 60% without sacrificing quality or coverage.
A practical guide to visual snapshot testing with Playwright — how to set baselines, handle dynamic content, and integrate visual checks into your CI pipeline.
How to set up Allure Reporter with Playwright for rich, interactive test reports — with screenshots, traces, step-level breakdowns, and CI integration.
How to configure GitHub Actions workflows with strict quality gates — fail fast on test failures, coverage thresholds, and performance budgets.
Quality culture doesn't come from tools — it comes from how your team thinks. A management playbook for embedding quality mindset across product, dev, and QA.
AI won't replace QA engineers — but it will change everything they do. A clear-eyed look at what shifts, what stays, and how to future-proof your QA career.
Testing before deployment isn't enough. Here's how to extend your quality strategy into production with monitoring, alerting, and real-user feedback loops.
A practical framework for assessing your team's quality maturity — from ad-hoc manual testing to fully automated, AI-assisted continuous quality engineering.
Quality is not a department. It's not a phase. It's a shared responsibility — engineered into every decision, every line of code, every deployment.
Catch defects where they're cheapest to fix — in requirements, design, and architecture — not in production.
Use AI to generate, review, and maintain tests faster — freeing engineers to focus on strategy and exploration.
Quality signals must flow in real time — from CI pipelines, production monitors, and user behaviour data.
System design decisions determine 80% of your defect rate. Quality engineers must have a seat at the architecture table.
The tools I use daily to build, automate, and maintain quality across the full software lifecycle.
Bengaluru, India
I've spent 13 years in QA, most of it building things other people inherit — automation frameworks, pipeline gates, the standards a team runs on years after you've moved on.
Quality is a leadership decision. The bugs that reach production aren't random — they reflect what the team was allowed to skip and what the manager chose to prioritise. I work with engineering leaders to change those defaults before they become incidents.
If you're an engineering manager or CTO tired of treating QA as a final checkpoint, the writing and work here are for you.
Consulting, speaking, or just a conversation about building better engineering cultures — I'm open to it all.