QA and UAT Tester
Free to start · No card · 5 credits the moment you sign up
Job description
The QA and UAT Tester is responsible for ensuring that software releases meet functional, quality, and business acceptance requirements before reaching production, through rigorous manual and UAT testing. This is a defined growth role: the successful candidate is expected to progressively build test automation skills and contribute an increasing share of automated coverage over time, supported by structured training and mentorship, with a clear path toward a Test Automation Engineer profile as capability develops.
Test Planning & Case Design
Writes clear, traceable test cases and scripts from requirements, user stories, and acceptance criteria.
Maintains an organised, up-to-date test case repository aligned to current functionality.
Ensures test coverage maps back to requirements and identifies gaps before test execution begins.
Participates in requirement/acceptance-criteria reviews to raise testability concerns early.
Manual & UAT Test Execution
Executes functional, regression, and end-to-end test cycles according to the test plan.
Plans and coordinates UAT cycles with business stakeholders, including scheduling, scripts, and sign-off.
Documents test results, evidence, and outcomes clearly for audit and traceability.
Flags scope, environment, or data issues that put a test cycle at risk.
Defect Management & Reporting
Logs defects with clear reproduction steps, evidence, severity, and priority.
Tracks defects through to resolution and retests fixes before closure.
Maintains accurate defect status and communicates blockers or high-risk defects promptly.
Analyses defect trends to identify recurring problem areas.
Quality Gate & Release Readiness
Contributes to and upholds the team's Definition of Done and quality gate criteria.
Provides a clear go/no-go quality recommendation ahead of each release.
Escalates quality risks early rather than allowing them to surface at release time.
Maintains release-level test summary documentation for audit and stakeholder visibility.
Test Automation Skill-Building & Contribution
Actively develops automation skills through training, mentorship, and hands-on practice as part of an agreed development plan.
Contributes to and maintains automated test scripts for repetitive regression scenarios, with support from senior team members.
Progressively takes on greater ownership of automation as competence grows, moving from assisted to independent contribution.
Shares learnings and automation progress with the wider QA and development team.
Collaboration with Development & Product
Works closely with developers, Business Analysts, and the Product Owner to clarify requirements and acceptance criteria.
Participates in sprint planning, refinement, and review to provide a quality perspective early ("shift-left" testing).
Pairs with developers to understand root causes of defects and prevent recurrence.
Provides constructive, timely feedback on testability and edge cases during design and development.
Continuous Improvement & Documentation
Identifies and proposes improvements to test processes, templates, and tooling.
Maintains clear, current test documentation and a shared testing knowledge base.
Actively participates in retrospectives and follows through on agreed improvement actions.
Stays current with testing best practice and emerging automation tools/techniques.
Requirements
Bachelor's degree or diploma in Computer Science, Information Technology, or a related field (or equivalent practical experience).
ISTQB Foundation Certification (or equivalent testing certification) is advantageous.
1-3 years' experience in manual and/or User Acceptance Testing (UAT) within a software development environment.
Experience writing clear, traceable test cases and test scripts from requirements and acceptance criteria.
Experience executing functional, regression, and UAT test cycles and documenting results.
Experience logging, tracking, and retesting defects using a defect-tracking tool (e.g. Jira, Azure DevOps, Zephyr, Xray).
Working understanding of the Software Development Lifecycle (SDLC) and Agile/Scrum ways of working.
Basic SQL skills for data validation and test-data setup.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Affidea BV. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.