Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse fresh openings from leading companies and apply with a resume tailored to the role.
14200 openings
5713-5720 of 14200Affidea BV
Free to start · No card · 5 credits the moment you sign up
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.
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.
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.
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.
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.
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.
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.
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.
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
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.