Where I’ve been
The journey
Not a career summary, but a map of the beliefs that formed. Each company here left me with a conviction I didn’t arrive with.
Image sourced from the web
2014–2016
Foundations
Ness Technologies · Software Engineer
My assumption
Quality is a checkpoint at the end of the process, not something woven into it.
The reality
Started here as a functional tester, where quality was a phase at the end rather than a culture woven through.
Lesson learned
I thought testing was about validating finished software. I learned that every bug found late was a decision made without enough information.
This became
2016–2018
Automation at Scale
Zycus Infotech · Automation Test Lead
My assumption
The highest-leverage QA skill is writing more test cases and covering more scenarios.
The reality
Rebuilt 5,000 end-to-end cases, took automation success from 60% to 98%, and grew from engineer into leading a team of 12.
Lesson learned
Writing more tests seemed like the highest-leverage skill. Leading 12 engineers taught me that the real leverage comes from helping others think about quality, not doing the thinking for them.
Outcomes delivered
60→98% Automation success rate
5,000 Cases revamped end-to-end
12 Engineers led
This became
2018–2019
Fast Feedback
Gracenote · Senior Software Engineer
My assumption
Comprehensive coverage justifies long feedback cycles, because thoroughness takes time.
The reality
Rebuilt the test suite so engineers got feedback in 15 minutes instead of overnight, and designed the reporting tool that closed the loop.
Lesson learned
I assumed long test runs were the price of thoroughness. Reducing them from 3 hours to 15 minutes showed me that feedback only changes behavior when it arrives fast enough to act on.
Outcomes delivered
3h → 15m UI suite execution time
200k+ API calls in 30 minutes
This became
2019–2020
Visibility
Works Applications · Senior Quality Assurance Engineer
My assumption
One well-executed test run per product is enough to understand system health.
The reality
Replaced scattered product-by-product performance tests with one shared framework that gave every ERP team real-time visibility.
Lesson learned
I believed every product needed its own testing strategy. Building a shared quality dashboard showed me that visibility changes how entire engineering teams make decisions, not just QA.
Outcomes delivered
1 → All ERP products on the framework
Real-time Live quality visibility across every QA team
This became
2020–2024
Enablement
Xendit · Senior Quality Assurance Engineer
My assumption
A central QA team that writes great tests is what scales quality across an org.
The reality
Built the shared QA library that cut team onboarding from 14 days to 1, and sat on the architecture council to bring quality into design decisions.
Lesson learned
I believed quality scaled with a stronger QA team. Experience taught me it scales when every engineering team owns it, supported by the right tools and practices.
Outcomes delivered
14d → 1 Team onboarding to automation
100+ Managers & devs coached
This became
2024–Now
Quality Leadership
8x8 International · Senior Test Automation Engineer
My assumption
A quality framework, adopted and enforced, is itself the achievement.
The reality
Designed the quality strategy, maturity framework, and AI tooling for an entire communications platform, and measured it across 6 teams.
Lesson learned
Building a framework felt like the achievement. Watching six teams change how they approached quality showed me that the framework was simply the enabler.
Outcomes delivered
↓40% Escaped defects / prod incidents
11.8→7.1 Release lead time · days
~8 h/wk Saved per engineer
>95% AI-generated tests across the pyramid
6 teams On the Quality Maturity Framework
This became
The through-line
Every experience reinforced the same belief.
Quality isn’t a phase or a gate. It’s a way of thinking.