// Senior QA Engineer · QA Team Lead

Nothing ships
until it's ready.

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.

  • Leading QA at Stellarsoft
  • Lahore, Pakistan
release-readiness.log Passed

$ run checks --candidate "Farwa Ramzan"

  • ✓experience5+ years · FinTech, web, desktop, mobile
  • ✓leadershipLeads & mentors a team of 3 QA engineers
  • ✓stability70% fewer post-release issues
  • ✓coverage95–100% of requirements traced (RTM)
  • ✓ownershipGo/no-go, deployments, post-release checks

5 passed · 0 failed Ready for release

Years in QA
5+
Fewer post-release issues
70%
Requirement coverage
95–100%
Products tested
9

01 — Approach

How I think about quality.

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.

01

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.

02

Requirements are the contract.

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.

03

A release is a decision, not a date.

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.

04

Good QA makes the team faster.

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

From writing test cases to leading the team.

  1. Jul 2024 — Present

    Stellarsoft

    Current

    Senior Software Quality Assurance Analyst

    I own quality on FinTech platforms, from planning a change request to signing off the release.

    Leading the team

    • Lead and mentor a team of 3 QA engineers, setting quality standards, enforcing code-of-practice and driving continuous improvement across projects
    • Estimate effort and timelines for new change requests (CRs)
    • Manage project risks and prioritise testing by business impact
    • Keep QA aligned with development through sprint ceremonies and day-to-day collaboration

    Protecting the product

    • Safeguard FinTech platforms with functional, API and database testing, with a focus on financial data accuracy
    • Write test plans and test cases for functional, regression and integration testing
    • Test APIs with Postman and Bruno, and validate data with SQL in SSMS

    Shipping it

    • Own release management: go/no-go decisions, deployments and post-release checks
    • Take clients through UAT to formal sign-off
    • Deploy and manage QA environments through CI/CD pipelines on Azure DevOps for faster, repeatable test cycles
    • FinTech
    • Release management
    • UAT
    • Postman
    • Bruno
    • SQL / SSMS
    • Azure DevOps
  2. May 2022 — Jul 2024

    Techverx

    SQA Engineer

    −70% post-release issues, by catching and resolving critical defects before deployment.
    • Ran functional, smoke, sanity, regression, integration and system testing across web and desktop applications
    • Built and maintained test cases and a Requirement Traceability Matrix (RTM) for 95–100% requirement coverage
    • Logged, prioritised and tracked defects in Jira, working with developers to cut average resolution time
    • Worked directly with clients in requirement sessions to clarify scope and define acceptance criteria
    • Validated APIs and databases to confirm end-to-end data accuracy across integrated systems
    • Web & desktop
    • RTM
    • Jira
    • API testing
    • Database testing
  3. Oct 2021 — Apr 2022

    G-Tek Solutions

    Associate Quality Assurance

    • Designed test plans, scenarios and procedures, and planned test schedules against scope and delivery dates
    • Reported defects and tracked them to resolution in Jira and ClickUp
    • Took part in product design reviews, flagging gaps in requirements, designs and schedules early
    • Tested system changes before release, including Android and iOS mobile apps
    • Android
    • iOS
    • Jira
    • ClickUp
  4. Aug 2021 — Oct 2021

    EventBuizz

    SQA Intern

    Where it started.

    • Wrote test cases from business requirements
    • Ran manual, black-box, system, integration, UI/UX, regression, smoke and sanity testing on web and mobile
    • Re-tested fixes and reported defects to developers
    • Manual testing
    • Black-box
    • Web & mobile

03 — Process

How a release earns its “go”.

Six stages I run on every project, from the first change request to the checks after it's live.

  1. 01

    Plan

    Estimate the change, map the risks, and decide what deserves the most attention.

  2. 02

    Design

    Test plans, scenarios and cases, each traced back to a requirement.

  3. 03

    Execute

    Functional, regression, integration, API, database and performance testing on web, desktop and mobile.

  4. 04

    Track

    Every defect logged, prioritised and followed through to a fix in Jira.

  5. 05

    Accept

    UAT with the client, taken through to formal sign-off.

  6. 06

    Release

    The go/no-go call, deployment through Azure DevOps, then verification in production.

04 — Expertise

Skills & toolkit.

Leadership & process

  • Release management
  • Test planning & case design
  • UAT coordination
  • Risk management & estimation
  • QA process & task management
  • Agile / Scrum

Testing

  • Web, desktop & mobile (Android / iOS)
  • Smoke, regression & re-testing
  • API testing
  • Performance testing
  • Database testing (SQL)
  • Defect management & reporting

Automation & CI/CD

  • Selenium with POM frameworks
  • Cypress
  • Python
  • CI/CD pipelines on Azure DevOps
  • QA environment management
  • Documentation
toolkit 17 tools
Automation
Selenium (POM)Cypress
API
PostmanBruno
Performance
JMeterLoadRunner
Database
SSMSSQL
CI/CD & environments
Azure DevOpsDockerPowerShellNetScalerOrcastrator
Tracking
JiraClickUp
Development
Visual StudioPython

05 — Projects

Products I've tested.

Nine products in FinTech, education, events and mobile, including financial platforms serving multiple clients.

  • P-01

    Orca

    • FinTech
    • Multi-client
  • P-02

    Light Point Financial Technology

    • FinTech
  • P-03

    SharkFin Technology

    • FinTech
  • P-04

    Orcastrator

    • P-05

      FrameSuite

      • P-06

        Engage Advisor

        • P-07

          HSP — Home School Panda

          • EdTech
        • P-08

          Pusic

          • Mobile app
        • P-09

          EventBuizz

          • Events
          • Web & mobile

        06 — Education

        BS Computer Science

        PMAS Arid Agriculture University

        CGPA 3.41 / 4.0 Sep 2017 — Sep 2021

        07 — Contact

        Shipping something that can't afford to break?

        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.

        Please add your name.

        Please enter a valid email.

        A short message helps me reply properly.