Pine Labs
Website:
pinelabs.com
Job details:
Senior QA Engineer / SDET III
5+ years of experience
We at Pine Labs are looking for those who share our core belief - “Every Day is Game day”. We bring our best selves to work each day to realize our mission of enriching the world through the power of digital commerce and financial services.
Why this exists
What if the app that handles your home’s money never broke when it mattered?
Fave is a UPI app built around homes, not individuals. Flat mates splitting rent and groceries. Dual-income couples managing a household together. Families paying th ecook, the maid, the driver. The everyday money that moves between the people you live with — finally in one place.
The Role:
UPI made payments invisible. That’s the magic — until something fails. The moment money doesn’t move, trust doesn’t come back. In payments a bug isn’t a cosmetic glitch; it’s someone’s rent that didn’t reach their flat mate, a settlement that silently dropped. You’re the person who finds that failure before a user ever does.
No one’s built a payments app around how homes work. Not flat mates, not couples, not families. If we get this right, we’re the operating layer for how people manage money together. UPI does 14 billion transactions a month, and that number’s only going up. The cost of a quality miss scales right along with it.
You’ll be on a very small team. No QA department to hide behind, no wall to throw bugs over. You won’t be “the QA person who runs test cases.” You’ll be the quality back bone of the product — someone who thinks like a PM, breaks things like a hacker, and automates like an engineer.
Day to day, you’ll read the PRD before the code exists, stress-test transaction paths nobody thought to spec, and automate the boring parts so your judgment goes where it actually matters.
What you’ll spend time on:
- Owning product quality end-to-end — reading PRDs, challenging assumptions, mapping user journeys, finding the gaps before code is written
- Hunting edge cases in UPI flows — stress-testing every transaction path across devices, UPI apps, and network conditions, finding the failures nobody thought to spec
- Building and maintaining automated regression suites — golden-path transaction flows must never break; you own the framework (Flutter integration tests, E2E tools like Patrol/Maestro), wire it into CI/CD, and keep it healthy as the product evolves
- Testing at the API layer — simulating timeout and failure scenarios, validating reconciliation logic, catching state-machine bugs before they hit production
- Using AI aggressively — LLMs to generate test cases from PRDs, write automation scripts, analyse logs, build internal QA tooling; you’re faster because of it, not just comfortable with it
- Collaborating directly with product and engineering — filing bugs that change product decisions, pushing back on ambiguous requirements, maintaining a living edge-case library the whole team references
Who we’re looking for
We want judgment. Not a test-case spreadsheet.
In the post-AI world, anyone can generate a thousand test cases. What’s rare is knowing which ten matter — the instinct to look at a flow and feel where it’ll break before you can prove it, and the discipline to automate it so it never breaks again.
Use Postman, Charles, flutter_test — whatever gets you to the failure faster. We only care about what you catch.
- 5+ years in QA/SDET roles, with at least 2 years on mobile apps
- Payments or fintech domain experience — you’ve tested UPI, wallets, lending, or card payment flows; you understand async transaction lifecycles, callback handling, idempotency, and reconciliation edge cases
- Flutter experience preferred — familiarity with flutter_test, widget testing,integration testing, and the Flutter/Dart ecosystem; if not Flutter, strong native mobile testing experience and the willingness to ramp up fast
- API testing expertise — Postman, REST clients, mocking API responses, validating webhook payloads is second nature
- Automation mindset — you’ve built and maintained regression suites, not just one-offscripts; CI/CD integration experience (GitHub Actions, Bitrise, Codemagic, or similar)
- Already using AI in your daily workflow, or aggressively learning to — Claude,ChatGPT, Copilot, Cursor for test generation, code, log analysis, internal tooling
- Product thinking — given a feature brief, you independently enumerate user journeys,failure modes, and edge cases; you’ve filed bugs that changed product direction
Bonus: You’ve worked at a UPI app or payments company. You’re comfortable with Charles Proxy / mitmproxy for inspecting API traffic, reading Dart/Flutter code, devicefarms (BrowserStack, Firebase Test Lab) for Android fragmentation, or performance and load testing. You’ve worked on a team small enough that there was no one else to blame.
Why you shouldn’t join
We want it fast and we want it bulletproof. We won’t pick one.
That’s the hardest thing about this role. We ship fast — there’s no two-week QA cycle to park a release behind. But this is money. A bug here isn’t a cosmetic regression; it’s someone’s rent that didn’t arrive. If you need a long stabilization phase to feel safe, you’ll feel rushed. If you’re fast but let real failures through, it shows immediately — in someone’s bank balance. The people who thrive here are the ones who’ve figured out how to be both.
How to apply
Show us a bug you’re proud of.
Email : asif@fave.money / george@fave.money
with a short write-up of one real bug you caught — ideally one others had missed. Walk us through how you found it, how you reproduced it, what it would have cost in production, and what you changed so it couldn’t happen again.
It doesn’t have to come from a payments product, and it doesn’t have to be dramatic.
We’re reading for how you think, not how big the bug was.
No cover letter. No test-plan template. Just the bug, the hunt, and what you learned.
Click on Apply to know more.