bout the role

We run a multi-role billing platform used by ASA's internal teams and partner centers. It covers enrollments, weekly reports, NSF tracking, adjustments, A/R, calendars and role-based dashboards, and we ship often through dev, UAT and prod.

The tester finds bugs before UAT does and protects the money-handling logic. We hire on demonstrated skill, not years of experience: freshers and early-career candidates are welcome.

Location: [Hybrid / Remote / On-site]

What you'll do

- Test features end to end across roles: center users (user, approver, viewer, center support), billing roles and the ASA team. Check each role sees and does only what it should.
- Verify the numbers. Weekly-report counts, NSF charges, waive-offs, adjustments and billing summaries must reconcile across screens, exports and uploads.
- Test the bulk upload flows (enrollments, weekly report, NSF import): large files, malformed rows, duplicates, re-uploads, rejected files, partial failures and the staged preview-and-confirm steps.
- Test background processing: queue-driven jobs and notifications that get stuck, fail or run twice.
- Test dates and time zones. Calendar dates such as attendance and week start/end must show the same day for every viewer.
- Test sorting, filtering and pagination: server-side sorting, URL-driven filters, and combined entity, state and center selections.
- Test users and access: user import/export, assigned centers versus SPOC centers, dual-role users, deleted or deactivated users and centers, and login edge cases.
- Check light and dark mode, and desktop and mobile layouts.
- Write clear bug reports with steps, expected versus actual result, environment, role and evidence (screenshots, network logs, console errors).
- Run regression passes on each UAT release candidate and confirm fixes on dev before sign-off.




- Write and maintain automated tests and test cases for the flows that break most often.

Must-have skills

- Test design: equivalence classes, boundary values, negative and state-based testing, and writing good test cases from vague requirements.
- Browser DevTools: reading network calls, status codes, payloads and console errors, and telling a UI bug from an API bug.
- API testing: Postman, Bruno or similar, covering auth tokens, role-based access and validation errors.
- SQL basics (PostgreSQL): joins, filters and aggregates to check that UI numbers match the database.
- Spreadsheets and CSV: comfortable building and breaking CSV and Excel files for upload testing.
- Bug reporting: exact, reproducible and prioritised reports.
- Attention to detail with numbers: you notice when a total is off by one record.

Strong plus Any one of these helps you stand out:

- Automation with Playwright or Cypress (TypeScript or JavaScript)
- Unit and component testing with Vitest or Jest and React Testing Library
- Understanding of REST, JWT auth and role-based access control
- Awareness of queues, retries, idempotency and soft-delete behaviour
- Basic Docker and Git, and the ability to read a pull request to see what changed
- Accessibility and responsive testing
- Experience with Jira, Linear or a similar tracker
- A personal project, open-source bug report or portfolio that shows how you test

Our stack and what success looks like You will work with a Next.js 16 / React 19 / Tailwind frontend, a Node/TypeScript backend with TypeORM and PostgreSQL, queue-based background jobs, Vitest for tests, and Docker-based dev, UAT and prod environments

How to apply

Send your resume or profile, plus one example of a bug report or test document you've written. Links to GitHub or a portfolio are welcome. Contact: [email protected] 0r (phone hidden)

Pay: ₹500,000.00 - ₹600,000.00 per year

Work Location: In person

📌 Jr. Software Tester (Mumbai)
🏢 Ashish Shah u0026 Associates
📍 Mumbai