Test by risk, not by habit.
Not every feature carries the same weight. I put testing effort where a failure would hurt the business most.
In practiceRisk management and impact-based prioritisation on every CR.
// Senior QA Engineer · QA Team Lead
I'm Farwa. I lead QA on FinTech platforms at Stellarsoft, where one wrong number is a real problem. I set the test strategy, take clients through UAT, and make the go/no-go call on every release.
5+ years across web, desktop and mobile. Still the person who reads the requirements twice.
$ run checks --candidate "Farwa Ramzan"
5 passed · 0 failed Ready for release
01 — Approach
Finding bugs is the easy part. The real work is knowing which risks matter, proving the product does what was promised, and deciding when it's ready.
Not every feature carries the same weight. I put testing effort where a failure would hurt the business most.
In practiceRisk management and impact-based prioritisation on every CR.
If a requirement isn't traced to a test, nobody has actually checked it. I keep that link visible from start to finish.
In practiceA Requirement Traceability Matrix at 95–100% coverage.
Shipping on schedule only matters if what ships works. I make the call on evidence and stand behind it.
In practiceI own go/no-go decisions and post-release checks.
Done well, QA speeds the team up. Repeatable environments and a well-mentored team mean shorter cycles and fewer surprises.
In practiceQA environments on Azure DevOps CI/CD, and a team of 3 I mentor.
02 — Experience
I own quality on FinTech platforms, from planning a change request to signing off the release.
Leading the team
Protecting the product
Shipping it
Where it started.
03 — Process
Six stages I run on every project, from the first change request to the checks after it's live.
Estimate the change, map the risks, and decide what deserves the most attention.
Test plans, scenarios and cases, each traced back to a requirement.
Functional, regression, integration, API, database and performance testing on web, desktop and mobile.
Every defect logged, prioritised and followed through to a fix in Jira.
UAT with the client, taken through to formal sign-off.
The go/no-go call, deployment through Azure DevOps, then verification in production.
04 — Expertise
05 — Projects
Nine products in FinTech, education, events and mobile, including financial platforms serving multiple clients.
06 — Education
PMAS Arid Agriculture University
07 — Contact
I'm happy to talk about QA leadership roles, release processes, or a product that needs a second pair of eyes. Send a message and it comes straight to me.