Indus | Investing in India from Anywhere
About Indus
Indus is a mobile-first fintech platform used by thousands of global Indians to invest seamlessly in Indian markets. By disposition of being a mobile-first fintech platform where reliability and trust are non-negotiable.
Our users rely on us for high-stakes financial actions, which means quality must be intentional, consistent, and owned.
We’re looking for a QA Engineer with
at least 2 years of hands-on experience
, strong
Flutter app testing experience
, and a background in
fintech, payments, or other high-trust products
, who can combine
manual testing with automation
across mobile, web, and admin surfaces.
What you’ll own
Quality across:
This is an
end-to-end, user-facing QA role
(no API-only testing).
What you’ll do
Manually test new features, enhancements, and bug fixes
Own
regression testing
before every release
automated test coverage
(mobile + web)
Flutter-based mobile apps
across Android and iOS devices
Validate web functionality across browsers and screen sizes
Test admin workflows, permissions, and edge cases
Identify edge cases in critical financial flows (onboarding, KYC, payments, SIPs, withdrawals)
Create clear, actionable bug reports with repro steps, evidence, and context
Work closely with developers during sprint cycles and release planning
Continuously improve QA processes, checklists, and release confidence
Tech stack
Flutter (Android & iOS)
Next.js
Mobile-first, with web as a core surface
Manual + Automation
Tested indirectly via UI flows
What we’re looking for (Must-haves)
Minimum 2 years of professional QA experience
Proven experience
testing Flutter applications
Android and iOS apps
web applications
fintech, payments, or other high-trust products
manual testing
fundamentals
test automation
regression testing
end-to-end user journeys
High-quality bug reporting and communication skills
Comfortable working in a
fully remote
environment
What success looks like
High confidence releases with minimal production issues
Stable critical flows with few regressions
Automation improves reliability rather than adding noise
Developers trust QA feedback and release sign-off
How we work
Fully remote
High ownership, low bureaucracy
QA has a strong voice in release quality
We optimise for trust, stability, and long-term reliability