Junior QA Engineer

Responsibilities

• Competitive Salary Packages Professional Development Opportunities Hybrid Work Setup Equipment Provided Day 1 HMO Life Insurance POSITION OVERVIEW The Junior QA Engineer tests Payreto’s software applications to help the team identify defects before release and reduce disruption for internal and external users.
• The role focuses on manual testing of web applications, business workflows, and integrations, with guidance from the Technology Leader and experienced team members.
• The engineer is accountable for accurate test results, clear defect reports, and timely escalation of testing gaps.
• The role provides evidence for release decisions and builds independence through feedback and practice.

WHAT WILL YOU DO?

• Test preparation and coverage Review requirements and acceptance criteria with the team to clarify expected behavior before testing begins.
• Prepare test cases and test data that cover key user workflows, error conditions, and boundary cases; agree testing priorities with the lead.
• Manual testing and regression Execute functional, exploratory, smoke, and regression tests to check new features and confirm existing workflows still work.
• Record results and evidence against the tested build, including relevant browser and device checks, so the team can understand what passed, failed, or remains untested.
• API and data validation Check application programming interface (API) responses and integrations against expected behavior, including invalid inputs and error handling, with guidance where needed.
• Use approved tools and basic database queries to check data accuracy in test environments; protect confidential information and use only authorized test data.
• Defect reporting and follow-up Report defects with reproduction steps, expected and observed results, test environment details, and supporting evidence so developers can investigate.
• Discuss defect impact and priority with the team, retest fixes, and check affected workflows before closing issues.
• Team collaboration and acceptance testing Contribute testing estimates, dependencies, and progress updates during planning and team discussions; raise blockers early.
• Support user acceptance testing (UAT) by preparing scenarios, helping business users reproduce issues, and recording their feedback.
• Test documentation and release support Keep test cases, results, and known issues current so the team can reuse them and understand testing coverage.
• Summarize completed tests, unresolved defects, and remaining risks for release review; escalate concerns to the Technology Leader for decisions.
• QA improvement and learning Use review feedback and defects found after release to improve test coverage and reduce repeat testing gaps.
• Learn the team’s QA tools and assist with simple automated tests under guidance as skills develop.
• Perform other related QA duties assigned by the supervisor.
• WHAT SHOULD YOU HAVE?
• Organize assigned work, keep the team informed of progress, and escalate risks or delays promptly.

Requirements

• Bachelor’s degree in Information Technology, Computer Science, Software Engineering, or a related field; equivalent practical experience may also be considered.
• 0–2 years in software testing or a related role.
• Fresh graduates with testing experience from internships, coursework, or personal projects are welcome to apply.
• Understand test cases, acceptance criteria, the defect lifecycle, and the purpose of functional and regression testing.
• Write clear test steps and defect reports, compare results against requirements, and identify missing or ambiguous behavior.
• Understand basic web application behavior, API request-response concepts, and database queries used for data validation.
• Use issue tracking and test documentation tools, and handle test data according to access and confidentiality requirements.

Preferred

• Exposure to API testing tools, Git, or basic test automation.
• Prior automation experience is helpful but not required.
• Examine details carefully and ask questions when requirements or results are unclear.
• Take feedback on board, follow agreed procedures, and show a willingness to learn.

Preferred

Explain issues clearly to technical and non-technical colleagues, and discuss findings constructively.