Platforms I have tested
All seven projectsVrushali Patil
Software QA Engineer in Mumbai. I test FinTech platforms for Angel One, HDFC Sky, Smallcase, and IIFL, from requirements through production release.
Available for freelance and full-time work
- Manual QA
- API testing
- Automation
- Release QA
Mumbai, India
Release check
Angel One, sample run
1 / 5 checks
- Years in QA
- 3+
- Releases verified
- 40+
- Cases per sprint
- 200+
- FinTech platforms
- 4
Catch it before release.
The cheapest defect is the one found in a requirements doc, not in production.
QA Engineer with over three years of end-to-end testing across Angel One, HDFC Sky, Smallcase, IIFL, and Protecct Industrial Services. From trading platforms to consulting websites, I cover functional, regression, API, and automation testing.
Forty production releases verified, hundreds of test cases per sprint, and work across FinTech, safety consulting, and web applications.
The toolbox
- JiraDefects, boards, releases
- PostmanREST API validation
- BrowserStackCross-browser and devices
- FigmaDesign review before build
- Selenium + JUnitRegression automation
- Zoho ProjectsSprints and milestones
Review early
Read the PRD and the Figma file before the build starts.
Test the risk
Cover the workflows that move money, not only the happy path.
Verify the release
Check production after deploy, not only the staging build.
Selected work
Three releases I tested from the first build to production.
01HDFC Securities
HDFC Sky
Quality assurance for an investment platform: modules, multilingual content, calculators, and complex form workflows across monthly releases.
6 modules, 50+ Figma screens
Manual TestingAPI TestingFigma ReviewMobile Testing
Read the case
02Trading platform
Angel One
Primary QA for one of India’s largest trading platforms, covering IPO, mutual funds, ETFs, F&O, and portfolio management across eight modules.
200+ test cases per sprint
03Freelance
Protecct Industrial Services
Independent QA for a safety consulting site: cross-browser compatibility, responsive behaviour, forms, gallery, and every service page.
4 browsers, 10+ page types
How a release gets checked
Five gates between a build and production. Pick a stage to see the work.
01/ 05
Before build
Read the requirements before the build
The cheapest defect is the one found in a requirements doc. I read the PRD and the Figma file before development starts.
What I check
- Read the PRD end to end and list open questions
- Check every Figma state: empty, loading, error, success
- Confirm acceptance criteria with product and design
- Flag missing rules, conflicting logic, and undefined behaviour
Requirements reviewOpen questions logged
- PRD read end to end
- Figma states reviewed
- Acceptance criteria confirmed
- Edge cases and rules clarified
A question here saves a retest later.
Where I worked
Two roles, one through-line: ownership of the release.
Freelance QA Engineer
Self-employed
Independent QA consulting. Delivered full QA for Protecct Industrial Services, a safety consulting platform.
- Client project
- 1
- Browsers tested
- 4
- Page types
- 10+
Associate QA Engineer
KraftPixel
Primary QA for FinTech platforms including Angel One, HDFC Sky, Smallcase, and IIFL.
- Years
- 3.5
- Platforms
- 4
- Releases per month
- 3 to 5
- Interns mentored
- 4
Writing
Notes on testing, defects, and the process between them.
QA Process Manual, Index: 10 Articles
Complete QA process documentation split into 10 detailed articles. Start here and navigate through each phase.
Read the articleWhy Every Little Bug Matters: Stories That Show the Power of Testing
Real stories behind some of the biggest failures caused by overlooked bugs, and why thorough testing matters at every level.
Read the articleTester vs Developer Mindset: The Friendly Tug-of-War That Saves Your Product
It's not a war. It's a partnership, with just a little friendly fire. Exploring how both mindsets are essential for quality.
Read the articleWhat teams say
Four people I tested alongside, on four different releases.
01 / 01