QA Engineer Intern

About the role

You join a cohort of nine interns building Stage 2 of SiteDay, our field production software for sitework contractors. You write the test plan in week 2, before a single feature is built, then hold the QA gate: from week 3 you are failing other interns' work back with notes. In week 8 you run the regression and give the go or no-go. The eight weeks run in three phases: weeks 1 and 2 you learn the codebase and help write the specification, weeks 3 to 6 you build your slice in parallel with the other tracks, and weeks 7 and 8 are integration, release and a demo you run yourself.

What you will learn

• Writing a test plan from a written specification before the software exists
• Test design: boundaries, equivalence classes, state transitions, traceability
• Bug reports a developer can reproduce without a single follow-up question
• API testing with Supertest, browser flows with Playwright, mobile flows in Flutter
• Attacking a public endpoint: guessing, replay, flooding, and what the response reveals
• Release sign-off, and saying no with evidence to people you like

What we look for

• Attention to detail and curiosity about how things break
• Clear written English
• Basic HTML and HTTP knowledge, and willingness to write code

What you would build

The Stage 2 test plan and its automation, including the abuse cases for a public approval endpoint: guessed tokens, replayed decisions, simultaneous submissions, and proving the response leaks nothing about the company.

How the 8 weeks run

• Weeks 1 to 2: learn the codebase, read the specification, and ship one small change. The design intern produces the wireframes everyone else builds from
• Weeks 3 to 6: build your slice in parallel with the other eight tracks, reviewed weekly, with a mid-point review in week 4
• Weeks 7 to 8: integration, regression, and a release you demo to the company yourself
• Every week: a written daily standup, a Monday cohort sync, a 30-minute 1:1 with your mentor, and a Friday demo

Screening task