Question 1
What is worth an automated test for this product, and what is a waste of a brittle end-to-end script?
Approach. Pick the risk that costs users, and say the check you would keep manual on purpose.
QA engineer interview questions from a job description
Map a QA or test-engineer job description to the automation, risk, and release questions it is likely to ask.
Matched in your browser from the requirements in the posting and Luna’s interview-question hub. These are practice prompts, not a claim that this wording will be asked.
Requirements in the posting
QA Engineer
Own product quality with automation and judgment.
You will:
- Build test automation in JavaScript with Playwright and Cypress where the UI risk is real
- Push tests into CI/CD so a failure stops the release
- Test APIs at the contract, not only through the browser
- Decide what is a waste of a brittle end-to-end suite
- Partner with engineers on bugs that escaped and the layer that should own the next check
We will ask what you would still test by hand, and why.
Own product quality with automation and judgment.
You will:
- Build test automation in JavaScript with Playwright and Cypress where the UI risk is real
- Push tests into CI/CD so a failure stops the release
- Test APIs at the contract, not only through the browser
- Decide what is a waste of a brittle end-to-end suite
- Partner with engineers on bugs that escaped and the layer that should own the next check
We will ask what you would still test by hand, and why.
Likely questions
Coding
Testing and quality
Build test automation in JavaScript with Playwright and Cypress where the UI risk is real
Question 2
A release is blocked and the failure is unclear. How do you narrow it?
Approach. Say the first reproduction, what you would stop rerunning, and how you would tell the team.
Coding
JavaScript
Build test automation in JavaScript with Playwright and Cypress where the UI risk is real
Question 3
Walk through a JavaScript function you would write for this role and the bug you would check before calling it done.
Approach. Restate the input, give the naive version, then name one edge — empty, duplicate, or async — and how you would prove it.
Question 4
When would you reach for a plain object, a Map, or an array, and what does that choice cost?
Approach. Tie the structure to the access pattern in the posting, and say the time cost of the common operation.
System design
CI/CD and infrastructure
Push tests into CI/CD so a failure stops the release
Question 5
Walk through how a change for this team should get to production. Where can it stop?
Approach. Name the checks before deploy and the rollback that does not need a hero.
Question 6
How would you manage infrastructure so a new environment is not a one-off?
Approach. Say what is code, what is still manual, and why that manual step remains.
Behavioral
Collaboration
Partner with engineers on bugs that escaped and the layer that should own the next check
Question 7
Tell me about a disagreement with someone who did not report to you. What did you do with their objection?
Approach. Name the objection, what you changed, and what you did not. Do not flatten it into “we aligned.”
Question 8
How do you bring a partner along when this posting’s work depends on their team?
Approach. Say the ask, the artifact you left them, and what you refused to take over.
Behavioral
Ownership
Decide what is a waste of a brittle end-to-end suite
Question 9
Tell me about something you owned after it shipped, when the interesting part was over.
Approach. Spend the time on the follow-through: the metric, the bug, or the user you went back to.
Question 10
What would you do in the first month if you owned the area this posting describes?
Approach. Name what you would learn, what you would not pretend to know, and the first small outcome.
What to prepare
- List the three risks you would automate and the one you would keep as a short manual check.
- Rehearse one array transformation out loud, including the empty case and the cost.
- Draw the path from merge to production and mark the step that can fail safely.
- Have one story where someone disagreed and you kept the working relationship.
- Pick one project you owned after the launch, not only until the launch.
- Mark the three requirements you cannot yet support with a story.
- Say each answer out loud once, in under two minutes.
QA postings are a risk interview. Automation tools matter less than which risk you would put in a unit test, which in a contract test, and which you would keep as a short manual pass. CI bullets mean they will ask how a red build should block a release. API bullets mean they will ask how you test a contract without the whole product.
“Quality ownership” is a story about a bug that escaped and the layer that should have caught it. Do not answer with a tool tour.
Prepare three risks for the product you are interviewing with, even if you have to infer them from the posting. The sample is a product QA role that writes code.
Sample job description
The posting below is already in the tool. The questions are the ones its requirements point to. Replace it with a posting you are actually interviewing for.
Related: Microsoft coding questions · Edge-case checklist · Google coding questions