Hire QA Tester for Schools
Senior, direct, no layers

In schools, a parent misses a closure notice, a pupil's record follows them incomplete between year groups, and a trip payment is chased by three different letters. The question a tester asks first is not whether the software works on a good day, but what happens on the bad paths: the failed payment, the double submit, the record that arrives half-formed.

Testing here means exercising parent messaging, attendance recording, grade entry, and trip-payment flows the way customers do, then the way customers do when something goes wrong: bad input, slow networks, expired sessions, and conflicting updates.

Start with a single surface, usually admissions and enrolment, and one release: the plan, the run, and a defects list ordered by customer impact, not by how easy each fix looks. Discuss that first workflow directly; wider scope follows only if the first piece earns it.

The systems in play are school information systems, parent apps, grade books, and payment tools. That stack is the starting point, not something to replace.

Tests are written against the staging copy of that stack, with test data that mirrors real records rather than tidy samples, so a case that passes in staging means something in production.

Testing does not make a bad workflow good, and it does not replace fixing the underlying process. If a step only works when one person remembers to do it, the test plan will say so plainly.

What changes is the release conversation: instead of arguing about whether something was tested, the team looks at the run record for admissions and enrolment and sees exactly what passed, what failed, and what was left open deliberately.

That is the standard this engagement is measured against: not a launch announcement, but a workflow the business still uses months later, maintained by its own team with documentation handed over at the end. Browse all hire engagements or discuss your workflow directly.