Scenario-based interview questions

// 22 QUESTIONS · UPDATED MAY 2026

Scenario-based interview questions for QA engineers. Covers real-world web features (login, search, file upload, payment), API and system scenarios (REST endpoints, rate limiting, webhooks, third-party integrations), and the classic lateral-thinking questions (vending machine, elevator, coffee machine). Every answer follows the clarify-first, test-dimensions, automate-vs-manual structure.

Level

Showing 22 of 22 questions

  1. How would you test a login page?Junior

    Clarify the auth mechanisms and policies first, then cover functional happy paths, negative cases (wrong credentials, lockout), edge inpu…

  2. How would you test a registration / sign-up form?Junior

    Clarify required fields, email verification flow, and duplicate-account handling, then cover functional happy path, field validations, se…

  3. How would you test a search box / search functionality?Junior

    Clarify whether results are full-text or indexed, whether there is autocomplete, and what data sources are searched, then cover result re…

  4. How would you test a file upload feature?Mid

    Clarify supported file types, size limits, virus scanning, and storage destination, then cover functional upload, boundary inputs, securi…

  5. How would you test a payment / checkout flow?Mid

    Clarify payment providers, sandbox availability, guest vs authenticated flow, and retry policy first. Then cover the full transaction lif…

  6. How would you test a shopping cart?Mid

    Clarify persistence model and inventory reservation behavior, then cover item operations, price and quantity math, coupon codes, security…

  7. How would you test a password reset flow?Junior

    Clarify token expiry time, one-time use policy, and session invalidation on reset. Then cover the full happy path, token security, accoun…

  8. How would you test a date picker?Junior

    Clarify the valid date range and locale format, then cover navigation, boundary dates (leap years, DST, timezone), keyboard accessibility…

  9. How would you test a multi-step form / wizard?Mid

    Clarify whether progress is saved between steps, whether back-navigation retains data, and what triggers validation. Then cover step tran…

  10. How would you test a notification system (email, push, in-app)?Mid

    Clarify which channels are used, what events trigger notifications, and whether users can configure preferences. Then cover delivery corr…

  11. How would you test pagination on a results list?Mid

    Clarify whether pagination is server-side or client-side, cursor-based or offset, and whether URLs are shareable. Then cover boundary pag…

  12. How would you test a comment / review submission feature?Mid

    Clarify authentication requirements, moderation flow, and length limits. Then cover submission correctness, XSS/injection in content, IDO…

  13. How would you test a REST API endpoint?Mid

    Clarify the HTTP verb, authentication, request and response schema, and rate limiting. Then cover contract validation, all error status c…

  14. How would you test a rate-limited API?Mid

    Clarify the limit type (per user, IP, key), window strategy (sliding vs tumbling), and response format. Then assert the limit boundary, 4…

  15. How would you test a webhook integration?Mid

    Clarify triggering events, retry policy, HMAC signing, and expected latency. Then cover delivery correctness, retry behavior on failure,…

  16. How would you test for performance on a high-traffic page?Senior

    Clarify SLAs, expected concurrent users, caching strategy, and whether auto-scaling is in scope. Then run load, stress, spike, and soak t…

  17. How would you test the security of a web form?Senior

    Clarify the form's data type and rendering context, then systematically cover injection vectors (XSS, SQLi), transport security, authenti…

  18. How would you approach testing a feature with no requirements or documentation?Senior

    Clarify who the users are and what problem the feature solves, then use structured exploratory testing with charters, risk analysis, and…

  19. How would you test a feature that integrates a third-party service that's often down?Senior

    Clarify the expected behavior on third-party unavailability, whether a sandbox or mock exists, and what observability is in place. Then t…

  20. How would you test a vending machine?Junior

    Clarify payment methods, change-dispensing logic, and inventory tracking before listing cases. Then cover functional item selection, paym…

  21. How would you test an elevator?Junior

    Clarify whether it's a single or multi-elevator system and what safety protocols apply. Then cover functional floor navigation, door beha…

  22. How would you test a coffee machine?Junior

    Clarify drink types, water supply, pod or bean system, and whether payment is required. Then cover drink selection, resource states (no w…

// Continue exploring

AI for testing

Using AI as a force multiplier — test generation, self-healing, agentic testing, and knowing where it falls short.

Testing AI systems

How do you test something that never behaves the same way twice? Evaluating LLM and agent features.

Mobile QA

Appium architecture, real devices vs emulators, locator strategies, gestures, CI for mobile.