Junior QA Tester

Junior QA Tester · Scape ScapeWorld Entertainment · Hired in Ireland About us We are Scape, a Swedish game studio of about 30 people, fully remote by choice. We are launching Gravity on Steam Early Access later this year: a precision climbing game where 100 players share one server, one tower, and one long way down. Gravity is the first game inside Scape, a growing platform of multiplayer games where a player's identity carries across all of them; Scape itself follows. Our senior team has shipped and run live games at studios including Arrowhead (Helldivers 2), Avalanche Studios, and Ubisoft. Every bug a player never meets started as a report someone wrote well, and we are looking for the person who writes them. The role You join the QA team and report to the Lead QA. Your job is to test Gravity the way players run it: packaged builds installed through the Steam client from a branch, never the editor. You run the test plans the Lead QA sets, hunt for what breaks, write bug reports a developer can act on without having been there, and confirm fixes once they land. It is not a playtest seat and it is not a lead seat: you do not decide what ships or how bugs are prioritised, and you do not need to. Some of what you chase only shows up with other players in the instance, so you will test with the team as often as alone. What you will own - Running smoke tests, quick tests, log in tests and the Steam pass on every candidate build you are given - Your bug reports in Jira, from first sighting to a report that reproduces from its own text - Reproduction work on defects a developer could not reproduce, and returning them with corrected steps - Fix validation on the defects you verify, including regression on the features around them - The test record for every run you make: plan, build, branch, configuration, result - Loading every candidate build against our archive of saves from earlier versions You - You understand the software testing lifecycle: test cases, test plans, regression testing, smoke testing - You write clear, reproducible bug reports: numbered steps to reproduce, expected against actual result, severity and likelihood set with care - You have used a bug tracker such as Jira, Bugzilla, Azure DevOps or TestRail - You notice things: edge cases, exploits, inconsistencies, the thing that is slightly off - You communicate well with developers and designers, in writing above all, because that is how a remote team works - You read and write English well enough to work in it all day; it is the language of every ticket and every conversation - You love games, and climbing, falling and trying again sounds like a good time Helpful, not required - A basic understanding of how games are built: client and server, builds, patches - You run your own day without needing to be asked twice What we offer A real game heading to Steam, a lead who teaches, and bugs that matter from your first week. We are a self-motivated team, remote by choice and flexible in how we work, and we run on people helping each other rather than watching each other. No timesheets, no theatre: everyone here is trusted to own their part, and supported when they need a hand. And we are early. Gravity is heading to Steam with everything still ahead of it. Joining now means building something with a real chance of becoming big, and being one of the people it belongs to when it does. Practical - Hybrid. We are a distributed team, and your working day overlaps CET. - Full time, hired in Ireland. - Recruitment is ongoing. How to apply Apply through the link; a few short questions are part of the application form. If we shortlist you, the next step is interviews and a short unpaid take-home, a bug hunt on a build with your written reports, about two hours. We reply to everyone at every step. Disclosure This application will be evaluated with the help of an AI tool that checks your CV and application against the criteria for this role. A human recruiter always makes the final decision. The AI does not reject or accept anyone on its own. If your application isn't taken forward, you can ask us for an explanation of how the AI was used in that decision. See our Candidate Privacy Policy below for full details, or contact us at privacy@br.ink with any questions.