Ahmedabad, India

Open to work · remote or hybrid

Malay Adalja, QA Automation Engineer (SDET)I find whatbreaks paymentsbefore customers do.

Seven years on crypto payments. BTC, ETH, USDT, XAUT, Lightning, ERC-20 contracts, payouts. Manual and automated. API and database. Web and mobile. When the tooling ran out, I built my own.

Experience
7 yrs 4 mo
QA only, from Jun 2019
Now
Openxcell
Software Engineer — QA
Domains
Crypto payments
BTC · ETH · USDT · XAUT · LN
Based in
Ahmedabad, IN
open to remote

↓ Six chapters, about two minutes. By the end you will know whether to email me.

Ch.01What I look for

The bug nobody wrote a test for.

The failure classes that survive a happy-path suite. These are the ones worth hunting.

  1. 01

    Idempotency · payments

    Refund issued twice on a retried webhook

    caught by
    Status flips to paid exactly once, however many times the webhook fires

  2. 02

    Timing · crypto

    Invoice expires mid-checkout with no retry path

    caught by
    An expired invoice issues a fresh one instead of failing silently

  3. 03

    Validation · security

    Payout accepted for an unverified wallet address

    caught by
    Unverified destination is refused. No override path exists

  4. 04

    Boundary · logic

    Cashback tier miscounted across a month boundary

    caught by
    Tier maths asserted on the last and first second of the period

  5. 05

    Config drift · compliance

    Country dropdown offers more than the allowlist permits

    caught by
    The rendered list is diffed against the allowlist, not eyeballed

  6. 06

    Fallback · pricing

    Rate drifts past tolerance on the fallback path

    caught by
    The fallback quote is held to the same tolerance as the primary

  7. 07

    Reconciliation · data

    DB row and API response disagree after a transfer

    caught by
    Every money-moving flow reconciles the ledger against the response

  8. 08

    State · realtime

    Session desyncs after a host reconnect

    caught by
    Reconnect is asserted from both sides, not just the host

15+
projects delivered
7 yrs
4 months in QA
2,300+
test cases authored
—Proof, not claims

This page tests itself.

Everything above this line is a claim. This is not. The suite below is real, it runs in your browser against this document, and it has no idea this section exists.

Six real defects, injected into this live page. Watch the suite go red, then fix them one at a time and watch it come back.

Now break it on purpose
A coverage grid: eight payment surfaces down the side, five test layers across the top, filled cells where that surface has been taken through that layer, and blanks where it has not.
Thirty-three of fifty cells. The blanks are the point — a coverage grid with none in it is a lie.

That is the method. Here is where it ran.

Three projects, opened in full. The problem, what I actually did, and what changed because of it.

Ch.05Selected work

Three that show the range.

Each one opens as its own page — the problem, what I actually did, and what changed.

Also shipped

TM2 (Teach Me To Online)

E-learning platform. Course upload, purchase flow, secure payment, student dashboards and access control.

NLC (Natural Living Care)

E-commerce with a multi-level bonus system. Cart, checkout, bonus tier calculation and user activity tracking.

OZ Road Code

Ride assessment platform on web and mobile. Video recording, map tracking and real-time speed logs.

Dekabes Domino

Multiplayer game. Real-time stability, AI difficulty and fairness, private tables and invites.

Moana Pasifika

Community app. Purchases, gifting, secure transactions and a shared feed across mobile and web.

E-commerce builds

Multiple storefronts. End-to-end UI/UX validation, cart, checkout, payment success and email notifications.

Ch.08Contact

Got something that needs breaking?

Open to work · remote or hybrid. Open to QA engineering and test-automation roles — especially anything with payments in it.