Software QA Engineer

Software that ships without surprises.

2+ years owning end-to-end quality assurance across web, mobile, and blockchain. Full STLC, from test planning to release sign-off, on Web3, DeFi, and AI products.

  • 2+ yrs experience
  • 8+ live products shipped
  • Web3 · DeFi · AI
  • Full STLC ownership
2+ Years of QA experience
8+ Live products shipped
Web3 DeFi & AI platforms
STLC Owned end to end

Attention to Detail

I catch the edge cases others walk past, cross-referencing Figma against live builds across hundreds of screens.

Quality Mindset

I think in risk, coverage, and prevention. Quality is planned into the STLC, not inspected in at the end.

Technical Depth

API validation in Postman, on-chain flow checks, and smart-contract testing, not just clicking through happy paths.

Reliability

Independent ownership of the full STLC, shipping secure, high-quality software on schedule across 8+ products.

About

Quality isn't a phase. It's a mindset.

I'm a Software QA Engineer based in Islamabad with 2+ years delivering end-to-end quality assurance across web, mobile, and blockchain platforms. I've independently owned the full STLC, from test planning and execution to defect management and release sign-off, across 8+ live products in the Web3, DeFi, and AI sectors.

My work spans API testing, performance testing, and cross-platform validation. A dual background in project management means I collaborate closely with developers, designers, and stakeholders to ship secure, high-quality software on schedule, not just to log bugs after the fact.

Skills

The full quality stack.

QA Methodologies

  • STLC
  • SDLC
  • Agile / Scrum
  • Test Planning
  • Test Case Design
  • Bug Reporting

Testing Types

  • Functional
  • Regression
  • Smoke / Sanity
  • Performance / Load
  • UI / UX
  • API
  • Security

Testing Tools

  • Postman
  • TestRail
  • Jira
  • Trello
  • Asana
  • Chrome DevTools
  • Remix (Smart Contracts)

API Testing

  • RESTful APIs
  • Request/Response Validation
  • Authentication Testing
  • Error Handling

Blockchain / Web3

  • Smart Contract Testing
  • On-chain Flow Validation
  • Wallet & DeFi Platform QA

AI Tools

  • Claude
  • Gemini
  • Cursor

AI-assisted test planning, debugging & workflow automation.

Frontend Awareness

  • React
  • JavaScript
  • C#

Database

  • SQL
  • Data Validation
  • Joins
  • Select Queries

Case Studies

Problem, approach, result.

Four products where full-STLC QA turned into shipped, dependable releases across web, mobile, and Web3. Each one carries an artifact from the actual work.

CS-01

JONI — Personal AI Computer

Quecko Inc. · Web & Mobile · QA Lead

10+ modules · 50+ screens verified

Problem

An ambitious AI platform spanning web and mobile, with 10+ feature modules, multi-step auth, a multi-chain payment system, and an AI agent marketplace, all needing quality coverage before release.

Approach

Led QA across all modules. Authored test plans and cases in TestRail covering functional, regression, smoke, UI/UX, and security. Validated multi-step authentication and the multi-chain payment flow end to end with Postman plus manual testing, and exercised the AI agent marketplace and enterprise dashboard.

Result

Ensured design fidelity across 50+ screens by cross-referencing Figma against live builds, logging UI defects in Jira with annotated screenshots. Shipped a complex multi-platform product with auth and payments validated end to end.

artifact — Auth-flow test cases (TestRail excerpt)
IDTitleStepsExpectedStatus
TC-014 Valid login Enter valid credentials, submit Redirect to dashboard Pass
TC-018 2FA / OTP step Submit valid OTP within window Session established, token issued Pass
TC-022 Session timeout Idle past expiry, perform action Re-auth prompt, no data loss Pass
TC-031 Multi-chain payment Pay across two chains, confirm Both txns reflected, balance correct Review

why it matters: Auth and payments are where trust is won or lost. Structured TestRail cases make that coverage auditable, not anecdotal.

CS-02

Gems Trade — Centralized Crypto Exchange

Web & Mobile · Full test strategy

100+ screens · web/mobile parity

Problem

A centralized crypto exchange on web and mobile where real-time market data accuracy and wallet security were non-negotiable, and any drift between platforms would erode user trust.

Approach

Designed and executed a comprehensive test strategy across all modules. Validated real-time market-data accuracy against source feeds, tested the multi-step wallet security flows, and verified feature parity and UI consistency between web and mobile.

Result

Confirmed feature parity and UI consistency across 100+ screens, web versus mobile, with market data and wallet flows validated for accuracy and security before release.

artifact — Bug report (Jira ticket)
GEMS-2218 Critical
Market price freezes on mobile after websocket reconnect
Steps to Reproduce
1. Open a trading pair on mobile. 2. Background the app for 30s, reopen. 3. Observe the live price ticker.
Expected
Ticker resubscribes and resumes streaming live prices.
Actual
Ticker shows the last cached price; trades execute against stale data.
Environment
staging · Android 14 · app v3.2.0 · ws-feed v2

why it matters: A reproducible ticket with clear expected-vs-actual is the difference between a one-sprint fix and a trader losing money on stale data.

CS-03

Gems Rocks — Memecoin Launchpad

Web3 · Token creation & bonding curves

Full suite · performance & load tested

Problem

A Web3 memecoin launchpad where token creation and bonding-curve mechanics had to behave correctly under load, with on-chain logic that fails loudly and expensively if wrong.

Approach

Built and executed a full test suite for token creation and bonding-curve mechanics, ran performance and load testing against the platform, and tracked defects through their lifecycle in Jira.

Result

Token-creation and bonding-curve flows validated for correctness and stability under load, with defects triaged and resolved before they reached users on-chain.

artifact — Postman API test (bonding-curve quote)
// Postman test script — validate bonding-curve quote
pm.test("Status is 200", () => {
  pm.response.to.have.status(200);
});

pm.test("Quote price increases with supply", () => {
  const body = pm.response.json();
  pm.expect(body).to.have.property("price");
  pm.expect(Number(body.price)).to.be.above(0);
  pm.expect(body.supply).to.be.a("number");
});

pm.test("Slippage within tolerance", () => {
  const { expected, quoted } = pm.response.json();
  const slip = Math.abs(quoted - expected) / expected;
  pm.expect(slip).to.be.below(0.01); // < 1%
});
smoke api load regression sign-off

why it matters: On a launchpad, a wrong quote is real money lost. API-level assertions catch curve and slippage errors before they hit a wallet.

CS-04

Flash Wallet — Lightweight Crypto Wallet

Mobile · Full QA lifecycle owner

All wallet APIs validated · security-first

Problem

A lightweight mobile crypto wallet where a single unhandled API edge case could mean lost funds, requiring security-first QA across the whole product.

Approach

Owned the full QA lifecycle. Authored the test plan and complete test suite, validated all wallet API endpoints via Postman covering request/response, authentication, and error handling, and took a security-first approach to every flow.

Result

Every wallet API endpoint validated for correct responses, auth, and error handling, with the full suite documented and repeatable for future releases.

artifact — Wallet API error-handling matrix
EndpointCaseExpectedStatus
POST /tx/sendInsufficient balance402, no broadcastPass
POST /tx/sendInvalid address checksum400, validation errorPass
GET /balanceExpired auth token401, re-auth requiredPass
POST /tx/sendNetwork timeout mid-sendSafe retry, no double-spendReview

why it matters: In a wallet, the error paths are the product. Validating every failure mode is what makes "lost funds" a non-event.

More products I've shipped QA on

  • Tasks Platform Web3 · PM + QA Lead

    Led project management and QA; validated platform APIs end to end via Postman.

  • Tomi Web3 Super App

    End-to-end functional, regression, and UI/UX testing, with API validation via Postman.

  • DOP — Data Ownership Protocol Oracles

    Tested oracle ingestion APIs in Postman, validating on-chain data ingestion flows.

  • Gems.vip Web3

    Regression and smoke testing executed and tracked in TestRail.

Resume

The one-page version.

A clean, current CV: summary, the full skills taxonomy, experience with project highlights, education, and certifications. It downloads on the first click. (A QA engineer would check.)

Contact

Let's talk about quality.

Looking for a QA engineer who treats your release like it's their reputation on the line? I'm open to full-time roles, contract work, and freelance QA projects.

Send a message