The role

You are the gate before a release ships.

Every time we prepare a build, you work through it methodically and answer two questions, in this order:

- Does everything still work? Features behave as specified, the new work does what it claims, and nothing that worked last release is broken now.
- Does it still feel right? The fix didn't make a screen confusing, the new button didn't push something significant off-screen, the error message still makes sense to a non-technical person.

The first question is the job. The second is what separates a good tester from a checklist. We're hiring for both, weighted that way.

You'll test our consumer mobile app on real iOS and Android devices, and our admin platform in a browser. We provide the test plans, the device matrix, and the specifications each feature is built to. You execute them thoroughly and report what you find clearly enough that a developer can act without asking you a single follow-up question.

Why the rigour matters: roughly 90–95% of our users only view content, and many are older adults opening an app for the first time to hear a relative's voice. Creating content requires explicit permission from the governing organization or community. People trust us with recordings of things they've never said aloud. A regression that loses a recording isn't a cosmetic problem — it's the product failing at the only thing it promises.

What a release pass looks like

- Read what changed — release notes, fixed tickets, new features
- Test the new work against its specification, including the paths where it should fail gracefully
- Run the regression suite — the standing checklist, end to end, on both platforms, across the device matrix
- Run the focused regression — the areas adjacent to what changed, where breakage is most likely
- Run the experience check — walk the core journeys as a real person would, confirming nothing became harder, slower, or more confusing than last release
- Report — what passed, what failed, what's blocked, severity of each,



and a clear recommendation on whether it's ready to ship
- Re-test fixes and confirm they're resolved without breaking something adjacent

What you'll be testing

You don't need to know these systems on day one — we'll train you.

Mobile app (iOS + Android, built in React Native)

- Sign-up, verification, sign-in, password reset, logout, session expiry
- The ways a user joins an organization or community: invite code, invite link, QR scan, request to join, email invitation, company domain, single sign-on
- Correct branding resolving at the correct moment once a community is identified
- Viewer versus Creator permissions, and the upgrade-by-code and request-approval flows
- Browsing and finding content: Home, channel directory, feeds, topics, collections, search, sort and filter, back-navigation
- Audio recording and playback: quality, long recordings, pause and resume, phone-call interruptions, backgrounding, screen lock, headphones and Bluetooth, poor network, low storage
- Device permission prompts — microphone, notifications, photos — including denied and revoked states
- Empty states, error states, loading states, and offline behaviour

Admin platform (browser)

- Organization or community setup: branding, languages, roles, policies
- User management, access code generation, expiry, revocation, redemption
- Content management: topics, channels, collections, featured items, scripts
- Publishing: links, QR codes, embeds, landing pages
- Content sharing between organizations or communities, including approval queues
- Isolation checks — confirming content belonging to one organization or community never appears to another.



These cases are scripted for you and carry the highest priority of anything you run.

Release verification

- Builds in test tracks (TestFlight and Google Play closed testing) before release
- Clean installs, updates over a previous version, and first-run behaviour on a fresh device

What we're looking for

Required

- Some hands-on software testing experience — 1–2 years, an internship, a bootcamp, or demonstrable self-taught work all count
- Comfortable using both iPhone and Android devices, and a desktop browser
- Genuinely methodical: you run the full checklist every time, and don't skip step 40 because steps 1 through 39 passed
- Clear written English — most of your output is written defect reports, and they need to stand on their own
- Organized enough to track what's been covered, what hasn't, and what's blocked
- Willing to repeat the same tests across devices, accounts, and configurations without cutting corners
- Enough empathy for non-technical users to notice when something is confusing rather than assuming you're the problem

Nice to have — not required

- Asana, or comfort picking up a collaborative work-tracking tool — it's where our work and your findings live
- Experience keeping structured test cases or coverage records
- Basic familiarity with APIs or a tool like Postman
- Any test automation exposure (Maestro, Appium, Detox) — a growth path, not an entry requirement
- Previous experience testing across both iOS and Android
- Interest in oral history, heritage work, archives, or community organizations

You'll do well here if you

- Find satisfaction in being thorough rather than fast
- Ask when something is ambiguous instead of guessing
- Report the small odd thing you noticed, even when it isn't on the list
- Understand that our product carries people's memories, and hold it to that standard

Pay: ₹400,000.00 - ₹700,000.00 per year

Benefits:

- Flexible schedule
- Paid sick time
- Paid time off
- Work from home

Work Location: Hybrid remote in Mohali, Punjab

📌 QA Release Tester — Mobile App and Admin Platform (Sahibzada Ajit Singh Nagar)
🏢 Wonder Engineering & Research
📍 Sahibzada Ajit Singh Nagar