Preparação para entrevistas técnicas de QA em inglês

Entrevistas de QA em inglês costumam começar com perguntas conceituais:

"What is the difference between verification and validation?"

Resposta modelo: "Verification checks that we're building the product right — it focuses on the process and whether we're following the requirements. Validation checks that we're building the right product — it focuses on the outcome and whether the product meets the user's actual needs."

"Can you explain the difference between severity and priority?"

Resposta modelo: "Severity is the technical impact of a bug — how badly it breaks the system. Priority is the business urgency — how quickly it needs to be fixed. A spelling mistake on the homepage has low severity but could have high priority because it's the first thing customers see."

"What automation framework have you worked with?"

Resposta modelo: "I've primarily worked with Playwright for end-to-end testing. I appreciate how it handles modern web apps — async/await, multiple browsers, built-in trace and screenshot on failure. I've also worked with the Page Object Model pattern to keep tests maintainable."

"How do you decide what to automate?"

Resposta modelo: "I prioritize automating tests that are: frequently executed (like regression and smoke tests), stable (the feature is unlikely to change often), and have clear expected outcomes. I avoid automating exploratory tests or one-time scenarios — the ROI isn't there."

"How do you integrate QA in an Agile team?"

Resposta modelo: "I believe QA should be involved from the beginning — during story refinement, not just at the end. I collaborate with developers on acceptance criteria, write test cases before development starts (shift-left), and participate in code reviews when changes touch critical flows. Testing is a team responsibility, not a gate at the end."

"How do you handle tight deadlines when there's not enough time to test everything?"

Resposta modelo: "I use risk-based testing. I map out the features by business impact and probability of failure, and focus my testing time on the highest-risk areas. I communicate clearly with the team about what was tested and what wasn't, so everyone understands the release risk."

Entrevistas internacionais frequentemente usam o método STAR (Situation, Task, Action, Result):

"Tell me about a time you found a critical bug close to release."

Estrutura STAR em inglês:

• Situation: "We were 2 days from releasing a payment feature when..."
• Task: "My job was to run the final regression suite."
• Action: "I found that the total amount was being calculated incorrectly for orders with discounts. I immediately documented the bug with steps to reproduce and escalated to the lead developer."
• Result: "The team fixed it in 4 hours. We delayed the release by one day but avoided shipping a bug that would have affected every discounted order."

Em inglês, qual é a diferença entre 'verification' e 'validation'?