QA & test engineer

What does a QA & test engineer do?

A QA and test engineer checks that software does what users and the business expect before it goes live.

You plan tests, run them by hand and with code, and report defects so developers can fix them.

In a Singapore organisation, the role sits in an engineering or IT team. You find it in banks, government agencies, start-ups and software vendors. Some firms keep a separate QA team. Others place QA engineers inside product teams.

The Singapore SkillsFuture QA engineer profile is wider than software. It also covers quality audits, non-conformance and quality systems in sectors such as manufacturing. The focus here is software testing.

What the work involves

• Read user stories and requirements, then write test cases that cover normal use, edge cases and errors.
• Run manual tests on new features and log defects in Jira with clear steps to reproduce them.
• Write and maintain automated tests in tools such as Playwright, Cypress or Selenium.
• Check API responses, status codes and error handling before the front end is ready.
• Watch test runs in the CI/CD pipeline and find out why a build fails.
• Prepare test data and walk business users through scenarios during user acceptance testing (UAT).

Pay in Singapore

Back to top

Skills a QA & test engineer needs

Back to top

QA & test engineer job description

We are looking for a QA and test engineer to check web, mobile and API releases before they reach users.

You will join an agile team, write test plans and automated tests, and report defects clearly. You will work with developers, product owners and business users through each release and UAT cycle.

Responsibilities

• Review requirements and user stories, and raise gaps or unclear points early.
• Design test plans, test cases and test data for new features and changes.
• Run manual functional, regression and exploratory tests across browsers and devices.
• Build and maintain automated UI and API tests in Python, JavaScript or TypeScript.
• Run automated tests in the CI/CD pipeline and fix or report failures.
• Log defects in Jira with severity, evidence and steps to reproduce, and retest fixes.
• Support UAT by preparing scripts, test data and defect logs, and helping business users.
• Analyse the root cause of repeated defects and suggest ways to prevent them.
• Join sprint planning, stand-ups and retrospectives, and give test status to the team.
• Write release test reports that show what was tested and what risks remain.

Requirements

• Diploma or degree in computer science, information technology, engineering or a related field. Career switchers with course or bootcamp training are also hired.
• Typically 0 to 3 years of testing experience for entry roles, and 4 or more years for senior roles.
• Hands-on use of an automation tool such as Selenium, Cypress or Playwright.
• Working skill in Python, JavaScript or TypeScript, and the ability to read application code.
• Experience with APIs, Git, Jira and a CI/CD tool, and a working knowledge of Agile and Scrum.
• Clear written English for defect reports and test documents.

Back to top

QA & test engineer career path

SkillsFuture lists two steps for this job: QA engineer, then senior QA engineer.

Singapore firms commonly use titles above and below those two as well.

1. Test analyst or junior QA

   Entry

   You run test cases, log defects and learn the product, the team's tools and the release process.

2. QA engineer

   Mid · SkillsFuture title

   You design test plans, write automated tests, and take responsibility for the quality of a feature or service.

3. Senior QA engineer

   Senior · SkillsFuture title

   You set the test approach for a product, guide others, run root cause reviews and improve how the team works.

4. QA lead or test lead

   Lead

   You lead a group of testers, plan testing across projects and agree release criteria with product and engineering.

5. QA manager

   Head

   You own the quality strategy, hiring, tooling and budget for testing across several teams.

Steps marked "SkillsFuture title" follow the career pathway in the SkillsFuture Skills Framework. The others are titles commonly used in Singapore.

Related jobs and their pay

Back to top

QA & test engineer interview questions

We wrote these questions from the skills this job needs. They are not an official question bank.

1. What is the test pyramid, and how do you decide what to automate?

   What a good answer covers

   • Explains many unit tests, fewer API tests and fewer UI tests, with reasons.
   • Automates stable, repeated, high-risk checks such as regression and smoke tests.
   • Leaves exploratory and one-off checks to manual testing.
   • Weighs the cost of maintaining a test against the time it saves.

2. A Playwright test passes on your laptop but fails now and then in the pipeline. How do you find the cause?

   What a good answer covers

   • Checks for timing problems and replaces fixed waits with waits on conditions.
   • Looks at test data, shared state and the order tests run in.
   • Uses traces, screenshots and videos from the failed run.
   • Compares the pipeline environment with local, such as browser version and data.
   • Quarantines the test and tracks it until it is fixed.

3. You must test an API endpoint that creates an order. What do you check?

   What a good answer covers

   • Valid requests, with correct status codes and response body.
   • Missing fields, wrong data types and values outside allowed limits.
   • Authentication and permissions, including a user who should be refused.
   • Repeat requests and what happens to the data after the call.
   • Response time and how errors are reported.

4. How would you use Python to check that two JSON responses match when some fields, such as timestamps, change every time?

   What a good answer covers

   • Loads both responses into dictionaries.
   • Removes or masks the fields known to change before comparing.
   • Compares nested data and reports which field differs.
   • Puts the check in a test function so it runs in the pipeline.

5. Why might a team write its automated UI tests in TypeScript instead of plain JavaScript?

   What a good answer covers

   • Types catch wrong names and wrong data shapes before the test runs.
   • Editors give better autocomplete and safer refactoring.
   • Shared types can match the application code.
   • Mentions the cost, such as a build step and a learning curve.

6. Where in a CI/CD pipeline do different kinds of tests run, and why?

   What a good answer covers

   • Unit tests and linting run first because they are fast.
   • API and integration tests run after the build is deployed to a test environment.
   • A small UI smoke suite runs on each change, and the full regression suite runs less often.
   • Failing tests block the release step, with clear reports for the team.

7. What goes into a good defect report in Jira? How do severity and priority differ?

   What a good answer covers

   • Gives a clear title, environment, steps to reproduce, expected and actual results.
   • Attaches screenshots, logs or a short recording.
   • Severity is the impact on the system, and priority is how soon the business wants it fixed.
   • Gives an example where the two differ, such as a typo on the home page.

8. What is the difference between system testing and UAT, and what does a QA engineer do in each?

   What a good answer covers

   • System testing checks the whole system against requirements, usually by the QA team.
   • UAT is done by business users to confirm the system fits real work.
   • In UAT, the QA engineer prepares scripts and data and tracks defects.
   • Sets entry and exit criteria, such as no open critical defects.

1. It is the day before release and you find a serious defect in a feature the product owner wants shipped. What do you do?

   What a good answer covers

   • Confirms the defect, finds its scope and gathers evidence.
   • Tells the product owner and developers straight away, with the user impact.
   • Presents options: fix and retest, release without the feature, or delay.
   • Leaves the release decision to the people who own the risk, and records it.

2. During UAT, business users reject the build because it does not match how they work. Requirements were signed off earlier. How do you respond?

   What a good answer covers

   • Listens and records each point as a defect, change request or training gap.
   • Checks the signed-off requirements to separate real defects from new requests.
   • Brings the product owner and users together to agree what changes.
   • Updates test cases and plans retesting.
   • Finds out how to catch the gap earlier next time.

3. A teammate uses Claude Code to draft automated tests for a new feature. How do you review them before they go into the repository?

   What a good answer covers

   • Runs the tests and checks they fail when the feature is broken.
   • Checks that assertions test real behaviour and go beyond confirming the code runs.
   • Looks for made-up selectors, endpoints or data, and for hard-coded secrets.
   • Confirms the tests match the team's style and cover edge cases.
   • Treats the draft as a starting point, and owns the final tests.

1. Tell us about a time a developer disagreed that something you reported was a defect. What happened?

   What a good answer covers

   • Describes the situation and the evidence you brought.
   • Stays factual and refers to requirements or user impact, not opinion.
   • Involves the product owner if the two could not agree.
   • Shows the working relationship stayed good.

2. Describe a bug that reached production after your testing. What did you do afterwards?

   What a good answer covers

   • Takes ownership and does not blame others.
   • Explains the root cause analysis and what was missed.
   • Describes the fix, such as a new test case or a changed process.
   • Says how the change reduced similar defects.

1. Your test environment needs realistic customer data. How do you handle personal data under the Personal Data Protection Act (PDPA)?

   What a good answer covers

   • Avoids copying real production data into test environments where possible.
   • Uses synthetic data, or masks and anonymises real data when it is needed.
   • Limits who can access test data and removes it when it is no longer needed.
   • Knows to ask the organisation's data protection officer when unsure.

2. You are testing a mobile banking feature for a Singapore financial institution. How does regulation shape your testing?

   What a good answer covers

   • Knows that financial institutions follow technology risk expectations from the Monetary Authority of Singapore (MAS).
   • Keeps test evidence, approvals and defect records that auditors can review.
   • Follows change control and keeps test and production access separate.
   • Includes security, access control and failure handling in test scope.
   • Asks the compliance or risk team when a requirement is unclear.

Common questions about a QA & test engineer job

Sources