Rishihood University is a non-profit university founded by technocrats, philanthropists, policymakers, social and spiritual leaders, entrepreneurs, and educators. It nurtures leadership and promises a triple impact to its learners - professional success, personal satisfaction, and public service.
About Rishiverse
Rishiverse is the in-house ERP and LMS platform that runs admissions and onboarding, student profiles, programs and curriculum, attendance, timetables, complaints, faculty workflows and administrative reporting. Every student, faculty member and administrator on campus uses it, which means a defect in production is not an abstraction. it is a student who cannot see their attendance, or a semester's marks that do not add up.
What you will do
Own functional testing across modules: Write and maintain test cases for new features and regression suites, execute them against staging before every release, and be the last checkpoint before code reaches students and faculty/staff.
Test the APIs, not just the screens: Validate REST endpoints in Postman — request/response contracts, status codes, payload validation, auth and role-based access, error handling and edge-case behaviour. A large share of our bugs live below the UI.
Verify data end to end: Confirm that what the UI shows matches what the database actually holds. Run SQL queries against our PostgreSQL database to check that records were created, updated and related correctly — especially for bulk imports, backfills and multi-step workflows.
Turn requirements into test coverage: Read user stories and acceptance criteria, ask the questions that expose gaps before development starts, and build test scenarios that cover happy paths, negative cases, boundaries and role permutations (student, faculty, admin).
Report defects that developers can act on: Clear reproduction steps, expected vs. actual, environment, severity, evidence (screenshots, network logs, API responses). Track them to closure and verify the fix.
Test across roles, devices and browsers: Our users are on desktop and mobile; validate responsive behaviour and cross-browser consistency for the flows that matter most.
Support releases and post-release checks: Run smoke tests on production after deployment, and help triage issues reported by students, faculty and the support desk.
Grow the automation layer: Start by scripting the regression cases that cost us the most time to run by hand, and build from there. You do not need to arrive with this skill — you need to want it.
Requirements
Must have
1–3 years of hands-on experience in manual/functional testing of web applications.
Solid grasp of QA fundamentals: test case design, test scenarios, functional, regression, smoke, sanity, UAT support, and the software testing life cycle.
Practical API testing experience with Postman — comfortable reading an API contract and testing against it independently.
Working knowledge of SQL: able to write SELECT queries with JOINs to verify data across related tables.
Experience with a bug tracking / project management tool (Jira, Notion, Linear, Azure DevOps or similar).
Browser developer tools — able to read the network tab and console to tell a frontend bug from a backend one.
Written communication that is precise. A QA engineer's main output is a clearly written defect.
A tester's instinct: curiosity about how things break, and the persistence to reproduce an intermittent issue instead of closing it as “not reproducible”.
Good to have
Exposure to any automation framework — Playwright, Cypress or Selenium — even at a learning-project level.
Familiarity with Git and how code moves from a branch to staging to production.
Experience testing role-based systems where the same screen behaves differently for different user types.
Exposure to ERP, LMS, EdTech or any complex internal business platform.
Basic scripting in JavaScript or Python.
Familiarity with a BI or analytics tool (Metabase, Power BI) for verifying reported numbers.
ISTQB Foundation certification.