TEST MODULE LEAD - Mobile functional testing

Senior QA Engineer

Bangalore ? Full - time

01

Why this exists

Wha t if the app tha t handles your home ? s money never broke when i t ma tt ered ?

Fave is a UPI app buil t around homes , no t individuals . Flatma t es spli t ting ren t and

groceries . Dual - income couples managing a household t ogether . Families paying the

cook , the maid , the driver . The everyday money tha t moves between the people you live

with ? finally in one place .

02

The role

UPI made paymen t s invisible . That ? s the magic ? until something fails . The momen t

money doesn ? t move , trus t doesn ? t come back . In paymen t s a bug isn ? t a cosmetic

gli t ch ; it ? s someone ? s ren t tha t didn ? t reach their flatma t e , a se t tlemen t tha t silently

dropped . You ? re the person who finds tha t failure before a user ever does .

No one ? s buil t a paymen t s app around how homes work . No t flatma t es , no t couples , no t

families . If we ge t this right , we ? re the operating layer for how people manage money

t ogether . UPI does 14 billion transactions a month , and tha t number ? s only going up . The

cos t of a quali t y miss scales righ t along with it .

You ? ll be on a very small t eam . No QA departmen t t o hide behind , no wall t o throw bugs

over . You won ? t be ? the QA person who runs t es t cases .? You ? ll be the quali t y backbone

of the produc t ? someone who thinks like a PM , breaks things like a hacker , and

au t oma t es like an engineer .

Day t o day , you ? ll read the PRD before the code exis t s , stress - t es t transaction paths

nobody though t t o spec , and au t oma t e the boring par t s so your judgmen t goes where i t

Wha t you ? ll spend time on :

? Owning produc t quali t y end - t o - end ? reading PRDs , challenging assumptions ,

mapping user journeys , finding the gaps before code is wri tt en

? Hunting edge cases in UPI flows ? stress - t esting every transaction path across

devices , UPI apps , and network conditions , finding the failures nobody though t t o

spec

? Building and main t aining au t oma t ed regression sui t es ? golden - path transaction

flows mus t never break ; you own the framework ( Flu tt er in t egration t es t s , E 2 E t ools

like Patrol / Maestro ), wire i t in t o CI / CD , and keep i t healthy as the produc t evolves

? Testing a t the API layer ? simulating timeou t and failure scenarios , validating

reconciliation logic , ca t ching s t a t e - machine bugs before they hi t production

? Using AI aggressively ? LLMs t o genera t e t es t cases from PRDs , wri t e au t omation

scrip t s , analyse logs , build in t ernal QA t ooling ; you ? re fas t er because of it , no t jus t

comfor t able with it

? Collaborating directly with produc t and engineering ? filing bugs tha t change produc t

decisions , pushing back on ambiguous requiremen t s , main t aining a living edge - case

library the whole t eam references

03

Who we ? re looking for

We wan t judgment . No t a t es t - case spreadsheet .

In the pos t - AI world , anyone can genera t e a thousand t es t cases . What ? s rare is

knowing which t en ma tt er ? the instinc t t o look a t a flow and feel where it ? ll break

before you can prove it , and the discipline t o au t oma t e i t so i t never breaks again .

Use Postman , Charles , flutter_test ? wha t ever ge t s you t o the failure fas t er . We only

care abou t wha t you ca t ch .

? 5+ years in QA / SDET roles , with a t leas t 2 years on mobile apps

? Paymen t s or fin t ech domain experience ? you ? ve t es t ed UPI , walle t s , lending , or card

paymen t flows ; you unders t and async transaction lifecycles , callback handling ,

idempo t ency , and reconciliation edge cases

? Flu tt er experience preferred ? familiari t y with flutter_test , widge t t esting ,

in t egration t esting , and the Flu tt er / Dar t ecosys t em ; if no t Flu tt er , strong native

? API t esting expertise ? Postman , REST clien t s , mocking API responses , validating

webhook payloads is second na t ure

? Au t omation mindse t ? you ? ve buil t and main t ained regression sui t es , no t jus t one - off

scrip t s ; CI / CD in t egration experience ( GitHub Actions , Bitrise , Codemagic , or similar )

? Already using AI in your daily workflow , or aggressively learning t o ? Claude ,

ChatGPT , Copilot , Cursor for t es t generation , code , log analysis , in t ernal t ooling

? Produc t thinking ? given a fea t ure brief , you independently enumera t e user journeys ,

failure modes , and edge cases ; you ? ve filed bugs tha t changed produc t direction

Bonus : You ? ve worked a t a UPI app or paymen t s company . You ? re comfor t able with

Charles Proxy / mitmproxy for inspecting API traffic , reading Dart / Flu tt er code , device

farms ( BrowserS t ack , Firebase Tes t Lab ) for Android fragmen t ation , or performance and

load t esting . You ? ve worked on a t eam small enough tha t there was no one else t o

blame .

04

Why you shouldn ? t join

We wan t i t fas t and we wan t i t bulletproof . We won ? t pick one .

That ? s the hardes t thing abou t this role . We ship fas t ? there ? s no two - week QA cycle t o

park a release behind . Bu t this is money . A bug here isn ? t a cosmetic regression ; it ? s

someone ? s ren t tha t didn ? t arrive . If you need a long s t abilisation phase t o feel safe ,

you ? ll feel rushed . If you ? re fas t bu t le t real failures through , i t shows immedia t ely ? in

someone ? s bank balance . The people who thrive here are the ones who ? ve figured ou t

how t o be both .

05

How to apply

Show us a bug you ? re proud of .

Email asif @ fave . money with a shor t wri t e - up of one real bug you caugh t ? ideally one

others had missed . Walk us through how you found it , how you reproduced it , wha t i t

would have cos t in production , and wha t you changed so i t couldn ? t happen again .

I t doesn ? t have t o come from a paymen t s product , and i t doesn ? t have t o be dramatic .

We ? re reading for how you think , no t how big the bug was .