QA ENGINEERING (AUTOMATIONS)

GSP (Global Student Pathway) is a configuration-first student-recruitment platform: per-country document checklists, market-scoped pipelines, a 15-stage admissions lifecycle, agent commission rate cards and a three-level permission model. That flexibility is our strength and our biggest quality risk, because a configuration change can break a workflow as easily as a code change. Technically, GSP is a MEAN-stack single-page application: Angular front end, Node/Express APIs, MongoDB, so your automation will live in the JavaScript/TypeScript ecosystem. You will build the safety net that lets a small team change a large platform with confidence.

• Build an automated end-to-end test suite (Playwright, Cypress or similar) for the critical journeys: lead capture to enrolment, quick-apply, offer/CAS/visa stages, commission calculation, and agent onboarding.
• Make the permission model provably safe: automated checks that each role — staff, agent, admin — sees exactly what it should, and nothing more.
• Wire the suite into CI/CD with our DevOps engineer so no release ships without the core journeys passing.
• Design regression coverage for configuration changes: when an admin edits a checklist, pipeline or rate card, we know what still works.
• Do exploratory and edge-case testing on the paths automation can’t reach — exception flows like drop-out with CAS, refunds, invalid-contact sequences — and triage bugs with the engineers.
• Establish lightweight QA process: test plans for new features, a bug severity scheme, and release sign-off criteria sized for a small team.

• 3+ years testing web applications, with at least one substantial automated suite you built (not just maintained) in Playwright, Cypress, Selenium or similar.
• Strong JavaScript/TypeScript — our stack is MEAN, and your test frameworks, fixtures and CI integrations will live in that ecosystem.
• Experience testing complex, workflow-heavy systems — CRMs, case management, fintech or similar — where state and permissions matter more than pixels.
• A tester’s mindset: you enjoy breaking things, you think in edge cases, and you can reason about a 9-market × multi-course-level combination space without trying to test all of it.
• Clear written communication — your bug reports and test plans are documentation the whole team relies on.

API testing (Postman, REST clients); performance or load testing basics; experience with data-sensitive platforms and UK and Europe GDPR awareness; edtech or marketplace background.

Remote from India, employed through an employer-of-record or as a direct contractor (agreed at offer). Working hours: the full UK day, 10:30–19:00 UK time (15:00–23:30 IST during British Summer Time; 16:00–00:30 IST in winter). Company laptop provided.

Originally posted on Himalayas