Uber Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Recruiter Screen30 minEasy

   Role targeting, level calibration and process expectations.

2. 2Technical Phone Screen60 minMedium

   One or two medium DSA problems (CodeSignal or live) with emphasis on correct, runnable code and edge cases.

3. 3Onsite Coding I60 minHard

   Practical problem such as building a rate limiter or an in-memory index, judged on working code and API cleanliness.

4. 4Onsite Coding II60 minHard

   Algorithmic problem often with a geospatial or streaming flavor, pushed to optimal complexity.

5. 5System Design60 minHard

   Design a real-time marketplace system (dispatch, ETA, surge) with hard follow-ups on scale, geo-sharding and failure modes.

6. 6Behavioral / Hiring Manager Round45 minMedium

   STAR stories mapped to Uber's cultural norms: ownership, bold bets, customer obsession and conflict handling.

1. Q1

   How would you use Postman/Newman in CI for Uber's login and account recovery flow without making the suite hard to maintain?

   MediumAPI/UI automationPostman/NewmanUber-specific

   Context:

   Uber login and account recovery flow

   How to answer:

   Use environments, data files, assertions, secret handling, and useful reports. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

2. Q2

   What integration tests would give confidence that Uber's search and filtering experience works across frontend, backend, and third-party services?

   MediumAPI/UI automationintegration testingUber-specific

   Context:

   Uber search and filtering experience

   How to answer:

   Define contracts, mocks, test environments, and rollback-safe checks. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

3. Q3

   Which logs, screenshots, traces, and videos would you collect when automation for Uber's admin approval workflow fails?

   MediumDebugging and test strategylogs/debuggingUber-specific

   Context:

   Uber admin approval workflow

   How to answer:

   Explain artifacts that help engineers reproduce issues quickly. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

4. Q4

   How would you design a maintainable test automation framework for Uber's admin approval workflow?

   MediumTesting fundamentalstest automation frameworksUber-specific

   Context:

   Uber admin approval workflow

   How to answer:

   Explain layers, fixtures, reporting, ownership, and when manual checks still matter. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

5. Q5

   Design test cases for Uber's notification preference center. Which equivalence classes, boundary cases, and negative paths matter most?

   MediumTesting fundamentalstest case designUber-specific

   Context:

   Uber notification preference center

   How to answer:

   Cover risk-based coverage, traceability, and clear expected results. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

6. Q6

   How would you test a REST API endpoint for Uber's order tracking workflow with authentication, pagination, and error responses?

   MediumAPI/UI automationAPI testingUber-specific

   Context:

   Uber order tracking workflow

   How to answer:

   Cover contract checks, status codes, auth failures, paging boundaries, and schema validation. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

7. Q7

   How would you integrate automated tests for Uber's checkout journey into CI/CD without slowing every pull request?

   MediumDebugging and test strategyCI/CD test executionUber-specific

   Context:

   Uber checkout journey

   How to answer:

   Use suite tiers, parallelism, ownership, quarantines, and release-blocking criteria. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

8. Q8

   When would you choose Cypress over Playwright or Selenium for Uber's seller onboarding flow, and what tradeoffs would you call out?

   MediumAutomation codingCypressUber-specific

   Context:

   Uber seller onboarding flow

   How to answer:

   Compare browser coverage, debugging, network control, speed, and CI behavior. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

9. Q9

   Explain Page Object Model for Uber's admin approval workflow. When does it help, and when does it become a bad abstraction?

   MediumAutomation codingPage Object ModelUber-specific

   Context:

   Uber admin approval workflow

   How to answer:

   Keep page APIs user-intent oriented and avoid hiding assertions or business rules. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

10. Q10

    How would you debug a flaky Playwright test in Uber's search and filtering experience?

    MediumAutomation codingPlaywrightUber-specific

    Context:

    Uber search and filtering experience

    How to answer:

    Discuss locators, waits, traces, retries, isolation, network timing, and deterministic assertions. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

11. Q11

    Design REST API tests for create, update, and delete operations in Uber's checkout journey

    MediumAPI/UI automationREST testingUber-specific

    Context:

    Uber checkout journey

    How to answer:

    Check idempotency, validation, permissions, response shape, and audit events. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

12. Q12

    Which SQL checks would you write to validate data created by Uber's seller onboarding flow?

    MediumAPI/UI automationSQL for testingUber-specific

    Context:

    Uber seller onboarding flow

    How to answer:

    Check records, joins, statuses, timestamps, aggregates, and reconciliation with UI/API results. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

13. Q13

    How would you handle dynamic elements in Selenium or Playwright for Uber's subscription billing workflow?

    MediumAutomation codingSeleniumUber-specific

    Context:

    Uber subscription billing workflow

    How to answer:

    Prefer stable locators, explicit waits, app test IDs, and avoiding brittle sleeps. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

14. Q14

    What accessibility checks would you include for Uber's order tracking workflow?

    MediumDebugging and test strategyaccessibility testing basicsUber-specific

    Context:

    Uber order tracking workflow

    How to answer:

    Cover keyboard navigation, labels, focus order, contrast, screen-reader basics, and automated plus manual checks. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

15. Q15

    Write the structure of a high-quality bug report for a failure in Uber's search and filtering experience

    MediumDebugging and test strategybug reportingUber-specific

    Context:

    Uber search and filtering experience

    How to answer:

    Include environment, steps, expected versus actual, evidence, severity, and business impact. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

Practice these with instant AI feedback in a live mock interview → Start a Uber Qa Automation Engineer Sdet mock

Strong DSA and scalable system design; prepare analytical/behavioral stories

Other roles at Uber

Qa Automation Engineer Sdet interviews at other companies