Jatin Vora — Operations Associate

Most production issues are not caused by bad code. They happen because risk is discovered too late. Many teams have good developers, automated tests, and CI/CD pipelines, yet releases still bring uncertainty, hotfixes, and late-night debugging. The problem is rarely effort or the number of tests. It is unclear ownership, delayed feedback, and quality treated as a phase instead of part of delivery. I work at the intersection of delivery, risk, and reliability. I’m a Senior SDET focused on release confidence , building practices that prevent defects from reaching production rather than detecting them after deployment. My work includes API and UI automation strategy, introducing CI/CD quality gates, improving test reliability, reducing flaky tests, defining clear acceptance criteria, and connecting quality signals with real business impact. Over the years in FinTech and Insurance domains, I’ve built scalable automation frameworks using Selenium, Playwright, and REST Assured, integrated automated checks into pipelines, supported release readiness decisions, improved regression stability, and mentored engineers on practical quality practices. I don’t see QA as testing. I see it as a predictability function , the mechanism that allows teams to release faster while still trusting their deployments. I’m increasingly working in areas where quality acts as a delivery capability: stable releases, earlier risk visibility, and reliable deployments. If your team values dependable releases, faster feedback, and fewer production surprises, I’m always open to exchanging ideas with engineering leaders and teams.

Stackforce AI infers this person is a Senior Quality Engineer specializing in FinTech and Insurance automation.

Location: Maharashtra, India

Experience: 10 yrs 4 mos