Job Description

Good QA doesn’t stop at “it matches the ticket.” 

It asks whether the ticket missed something, whether the whole journey works, and what happens when a real customer takes a different path. 

At Vyking, we’re building the platform behind the next generation of iGaming. We’re looking for a Senior Manual QA Engineer who combines strong testing experience with a clear understanding of customer and business impact. Someone who spots risks early, asks the questions others haven’t, and takes ownership of quality from the first requirement to what happens after release. 

You won’t build alone. Our team brings ideas to the table, challenges approaches, and jumps in when things get difficult. Ownership here means taking responsibility from start to finish, with strong colleagues to spar with, challenge your thinking, and deliver work that stands the test of time. 

If that sounds like your kind of quality engineering, keep reading. 

What you’ll do 

  • You’ll own the QA process for work delivered by your customer-facing delivery team, working closely with the Project Manager, Developers, Customer Success Manager, and QA colleagues. 

  • This is not a back-office testing role where you wait for development to finish and work through assigned test cases. You’ll be involved in planning, refinement, and delivery discussions, making sure requirements are clear, risks are understood, and testing reflects how clients and their customers actually use the product. 

  • You don’t test a feature in isolation and move on. You follow the complete workflow, challenge assumptions, and consider what a defect means for the people relying on it. A working screen isn’t enough if the permissions are wrong, the reporting is misleading, or the next step in the journey breaks. 

  • You’ll give the team clear evidence for release decisions: what’s been tested, what remains uncertain, and which risks need attention. Deployment is a milestone, not the finish line. 

Your day-to-day 

  • Get involved before testing starts. Review client requirements, acceptance criteria, tickets, designs, and user flows. Challenge unclear expectations and find missing edge cases before they become delivery problems. 

  • Turn requirements and risks into practical test scenarios, test cases, checklists, regression packs, and release validation plans. Keep them useful as the product and client needs evolve. 

  • Perform functional, regression, smoke, exploratory, integration, and end-to-end testing. Go beyond the happy path into negative scenarios, unusual data states, and customer-specific workflows. 

  • Test the complete experience: frontend behaviour, backend-driven functionality, APIs, integrations, admin flows, reporting, user roles, and permissions. Check that the parts work together, not just separately. 

  • Report defects with evidence people can act on: clear reproduction steps, expected and actual results, screenshots or videos, relevant logs, severity, and customer impact. Work directly with Developers to investigate issues, validate fixes, and follow them through to resolution. 

  • Make release readiness clear. Communicate test results, blockers, outstanding risks, and quality concerns to the delivery team and, where needed, customer-facing stakeholders. Support UAT and post-release validation where required. 

  • Help the team deliver work that is stable, usable, professionally presented, and fit for purpose. Consider agreed client expectations alongside technical correctness. 

  • Prevent repeat problems. Improve coverage, documentation, and QA processes, and work with the Automation QA team to identify manual scenarios worth automating. 

What you bring 

  • Senior-level manual QA experience with web platforms, SaaS products, customer-facing systems, or other complex digital products. You’ve owned testing outcomes, not just completed assigned test runs. 

  • Experience working in cross-functional delivery teams alongside Project Managers, Developers, Customer Success Managers, and other stakeholders. You understand how quality decisions affect delivery commitments and client trust. 

  • Strong requirements analysis. You can spot an ambiguous acceptance criterion, a missing dependency, or an overlooked user journey and turn it into a useful discussion before work reaches release. 

  • Solid experience across functional, regression, smoke, exploratory, integration, end-to-end, and release testing, including UAT support. You choose coverage based on the work and its risks, not habit. 

  • A good understanding of modern web applications: frontend behaviour, backend logic, APIs, databases, integrations, permissions, roles, and data states. You can investigate beyond what appears on screen. 

  • Clear, actionable bug reporting and QA documentation. Your findings explain what happened, how to reproduce it, and why it matters to the business or customer. 

  • Experience with issue-tracking and test management tools such as ClickUp, Jira, TestRail, Zephyr, or similar, alongside documentation and collaboration tools. 

  • The judgement to prioritise under release deadlines. You can balance delivery speed with appropriate testing, make trade-offs visible, and raise concerns early rather than leave surprises for the last minute. 

  • Ownership without ego. You work independently, follow through, and ask for another perspective when it helps. You can challenge a requirement, explain a risk without creating friction, and change your mind when someone makes a stronger case. 

What you get 

  • Real ownership. Be the quality representative within your delivery team, with meaningful involvement from requirements through release and post-release validation. 

  • Strong sparring partners. Work through difficult questions with colleagues who care about getting the solution right, not winning the argument. 

  • Team spirit you can see in the work. People who share knowledge, challenge constructively, and jump in when a problem needs solving. 

  • Work with visible customer impact. Help shape deliverables that clients and their customers rely on, rather than testing without understanding who the work is for. 

  • A fully remote, full-time role in an international team. 

Sound like you? 

Tell us about a requirement you challenged before it became a defect. What did others miss, how did you raise it, and what changed? 

Walk us through a release you helped get right. How did you decide what to test, explain the remaining risks, and check that the result met customer expectations? 

We want people who take responsibility, make each other better, and stand behind the quality of what ships. Not just a CV with the right keywords. 

Long read? High expectations? Yes, on purpose. 

We’re Vykings. Warriors in our mindset, experts in our craft, and a team that stands behind what it builds. We bring ambition, take responsibility, and challenge each other to deliver work that lasts. 

We’re not here to spin the wheel and hope. We’re here to build the edge and win the game. Together. 

Vyking. Strong minds. Shared ambition. Built together