- 2–4 years in a software development team, including testing native iOS and Android applications.
- Identify edge cases and risks beyond acceptance criteria, and design tests based on risk and customer impact.
- Write, maintain and debug automated tests for mobile and API environments.
Role Type
Description
Quality Engineer
Organisation: Team RH
Location: Gateshead
Reporting to: Head of Quality
Contract: Full-time
Salary: Competitive
About the Role
The Quality Engineer takes ownership of quality within a mobile squad, building native iOS and Android apps that help people track their nutrition, fitness and health. Our members use these apps every day as part of routines they care about, so a crash during a food log or corrupted weight data lands hard. The role sits within the growing Quality Engineering team, in the Software Development department.
You’ll work closely with Developers, Product Owners and other Quality Engineers throughout the development lifecycle, from understanding a story and identifying risks through to testing, automation and release. This is a hands-on role: you’ll combine exploratory, manual and automated testing to build confidence in what we ship, design your own test approaches and focus testing where it matters most.
We are actively growing our mobile and API automation, so you’ll also help improve our automated coverage and the way we test our products, sharing knowledge with the wider QE team as you go.
Key Responsibilities
1. Scope & Ownership
- Take ownership of the quality approach for features and changes within the mobile squad.
- Plan and carry out testing independently for the majority of your work.
- Assess the risks associated with a change and decide where testing should be focused.
- Work with Developers and Product Owners to understand requirements, challenge assumptions and identify issues early.
- Provide clear quality input into release decisions rather than simply reporting test results.
2. Test Design & Exploratory Testing
- Design appropriate test approaches for new features before development starts.
- Use risk, customer impact and technical complexity to decide what and how to test.
- Carry out structured exploratory testing across native iOS and Android applications.
- Go beyond acceptance criteria to identify edge cases, unexpected behaviour and areas of risk.
- Perform regression testing to make sure changes haven’t introduced issues elsewhere.
- Investigate problems thoroughly and write clear, reproducible defect reports that help Developers fix them quickly.
3. Test Automation
- Contribute to our mobile automation strategy and expand automated coverage alongside the features you test.
- Write, maintain and debug automated tests.
- Contribute to our XCUITest and Jetpack Compose automation and improve the reliability and maintainability of the existing test suite.
- Decide what is worth automating and where exploratory or manual testing provides greater value.
- Identify opportunities to improve our automation and testing tools.
4. API & Technical Testing
- Test APIs as part of your end-to-end approach to validating features.
- Use tools such as Postman to validate requests, responses, error handling, authentication and data.
- Contribute to API automation as our framework develops.
- Develop a good understanding of how the mobile application interacts with APIs and supporting services.
- Investigate issues across the mobile application and backend where appropriate.
5. Working with the Squad
- Work with Product and Development during refinement and 3 Amigos discussions to agree acceptance criteria, risks and edge cases before development begins.
- Take an active part in sprint planning, stand-ups, retrospectives and other team activities.
- Work alongside Developers throughout implementation rather than waiting until a feature is ready to test.
- Challenge requirements, technical decisions or assumptions that could affect quality.
- Share knowledge with, and support, other members of the QE team.
- Contribute to improving how the squad builds and delivers software.
TEAM RH
Quality Engineer — Person Specification
Essential Experience
- Experience working as a Quality Engineer, QA Engineer or equivalent within a software development team.
- Around 2–4 years of relevant QA/QE experience, including testing native mobile applications.
- Strong exploratory testing skills, with the ability to find edge cases without relying on predefined test cases.
- Experience designing your own test approaches based on risk and customer impact.
- Hands-on experience with test automation and writing and maintaining reliable automated tests.
- Experience testing REST APIs using tools such as Postman or similar.
- Working knowledge of Git and of working with code within a development team.
- Understanding of Agile development and how Quality Engineering fits throughout the development lifecycle.
- Strong problem-solving skills, with the ability to investigate issues and own your area of work without day-to-day direction.
- Clear communication and the confidence to give quality opinions and challenge when necessary.
Desirable Experience
- Experience with mobile test automation, ideally XCUITest and Swift.
- Experience with Kotlin or other mobile automation technologies.
- Experience with API automation.
- Experience contributing to or maintaining test automation frameworks.
- Experience working with CI/CD pipelines and automated test execution.
- Experience testing applications backed by APIs and supporting services, including non-functional testing such as performance, accessibility or security.
Core Competencies
- Independent.
- Analytical.
- Curious.
- Risk-aware.
- Collaborative.
- Clear communicator.
- Thorough.
- Pragmatic.
Our Values
We Treat People Right
Everyone gets the same level of respect. Your role doesn’t change how you speak to people, or how you’re spoken to.
We Set High Standards
We are a high-performing team (Team RH) pursuing excellence for our members, and we measure ourselves against the best in the world, not just the industry.
We Don’t Have Egos
Ego stays at the door. Curiosity comes in. The best idea wins, whoever it came from — and admitting you were wrong is part of the job, not a mark against you.
We Trust Our Gut
If something feels wrong, it usually is. Raise it on instinct, then back it with data.
We Answer to the Member
Is this right for the member? That’s the question behind every decision, and it outranks every other interest in the room.
Australia
New Zealand
United Kingdom
Canada
Singapore
Malaysia