QA Engineer 路 Intern to senior
QA interviews look for someone who thinks about risk: what to test, at which level, and how to keep an automated suite fast and trustworthy as the product grows.
43 questions
Treat a flaky test as a bug: quarantine it so it stops blocking the pipeline, reproduce it by running it repeatedly, fix the root cause (usually timing, shared state or external dependencies), then bring it back.
Selenium is the long-established, language-agnostic standard built on WebDriver; Cypress runs inside the browser with an excellent developer experience for JavaScript apps; Playwright offers fast, auto-waiting cross-browser automation with multiple tabs, contexts and languages. For a new web project, Playwright is usually the strongest default.
Describe a real technical or process disagreement, show that you listened and argued with evidence rather than opinion, explain how a decision was reached, and how you supported it afterwards even if it was not your idea.
Describe a problem you noticed, why you decided to act, how you coordinated with others, and the impact of taking ownership.
Explain how you identified ambiguity, clarified the important decisions, made reasonable assumptions and kept delivery moving.
Explain how you assessed urgency, impact, dependencies and risk, then communicated the resulting priorities.
Show respectful disagreement, evidence-based reasoning, willingness to listen and commitment after the final decision.
Identify a recurring source of wasted time or risk, make a focused improvement, and demonstrate its impact.
Explain the manual problem, why automation was worthwhile, how you implemented it safely and what time or error reduction resulted.
Show how you adapted your explanation to the audience, focused on the outcome and avoided unnecessary technical jargon.
Show how you noticed a risk early, validated it, communicated it and added a safeguard.
Describe how you understood the stakeholder鈥檚 goals, handled disagreement professionally and reached a workable outcome.
Explain why you accepted, reduced or paid down technical debt and how you managed the associated risk.
Start with the problem, evaluate alternatives, validate the technology with a small experiment and explain how you managed adoption and risk.
Explain how you identified what the developer needed, coached rather than simply solved the problem, and measured their progress.
Show how you built trust, understood competing concerns, used evidence and helped the group reach a decision.
Explain the constraints, alternatives, trade-offs, decision criteria and why the chosen option was appropriate for the context.
Cover detection, communication, mitigation, investigation, recovery and the changes made afterwards to reduce recurrence.
Explain why the technology looked attractive, what problem it actually solved, and why its cost or complexity was not justified in your context.
Explain the deadline, the quality risks, what you protected, what you simplified and how you managed any remaining debt.