Product & QA Intern (3-Month Internship)

We're looking for interns to work across two connected disciplines for 3 months : Quality Assurance (manual testing of the platform before features ship) and Product (researching what schools actually need, and helping keep the team's sprints organized and on track). You'll sit close to the engineering team, see features go from idea to shipped, and have real input into what we build next. This is a hands-on role where you'll be testing real releases and tracking real sprints from week one. **Key Responsibilities :** **Quality Assurance (Manual Testing) :** * Write and execute manual test cases across the platform's core modules (curriculum \& syllabus, scheduling, attendance, assignments \& grading, admissions, finance, report cards) * Test across every user role (network admin, school admin, principal, teacher, student, parent) to catch role-specific bugs before they reach real schools * Log clear, reproducible bug reports, steps to reproduce, expected vs. actual behavior, severity * Do regression testing before releases to make sure new features don't break existing ones * Verify fixes and close the loop with engineering **Product Research \& Sprint Management :** * Research how schools and teachers actually use (or struggle with) similar tools,interviews, competitive research, feature requests from real users * Turn research findings into clear, written feature requests and user stories the engineering team can build from * Keep tabs on the sprint board, track what's in progress, what's blocked, and what's slipping, and flag it early * Help run sprint planning and retro meetings (agenda, notes, follow-ups) * Act as a point of contact between "what users need" and "what the team is building" **Qualifications \& Skills :** * Currently pursuing or recently completed a degree (Computer Science, Information Systems, Business, or related but we care more about aptitude than major) * Detail-oriented, you notice when something's off, and you don't just shrug it off * Clear written communication, bug reports and user stories are only useful if someone else can act on them without asking follow-up questions * Comfortable using spreadsheets and basic project-tracking tools (Notion, Jira, Trello, or similar) * Genuinely curious about how software gets built, not just how to use it * Proficient in English language * Having a *Responsible to Life* attitude **Nice to have (not required) :** * Any prior exposure to manual QA, test case writing, or bug tracking * Interest in EdTech or the education sector * Basic SQL or familiarity with reading through an admin dashboard/database (helps when investigating bugs) * QA Automation with Playwright and Selenium experience