Atlassian Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Online Assessment (HackerRank)60 minMedium

   1-2 medium DSA problems with clean code expectations; India campus and early-career funnels start here.

2. 2Coding Round60 minMedium

   Live DSA problem solved to working code with tests; interviewers probe complexity and edge cases conversationally.

3. 3Code Design Round60 minHard

   Atlassian's distinctive craft round: design classes and APIs for an evolving problem (rate limiter, file system, game) - extensibility and SOLID over algorithms.

4. 4System Design Round60 minHard

   Design a collaboration-scale system (Jira issue search, Confluence page tree, tagging service) with multi-tenant and consistency tradeoffs.

5. 5Values Interview45 minMedium

   Dedicated behavioral round mapping STAR stories to the five named Atlassian values; a weak values signal can sink an otherwise strong loop.

6. 6Management Round45 minMedium

   Senior candidates discuss leadership, conflict, project trade-offs and growth with a senior engineering manager.

1. Q1

   How would you test a REST API endpoint for Atlassian's notification preference center with authentication, pagination, and error responses?

   MediumAPI/UI automationAPI testingAtlassian-specific

   Context:

   Atlassian notification preference center

   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.

2. Q2

   How would you use Postman/Newman in CI for Atlassian's checkout journey without making the suite hard to maintain?

   MediumAPI/UI automationPostman/NewmanAtlassian-specific

   Context:

   Atlassian checkout journey

   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.

3. Q3

   Design REST API tests for create, update, and delete operations in Atlassian's order tracking workflow

   MediumAPI/UI automationREST testingAtlassian-specific

   Context:

   Atlassian order tracking workflow

   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.

4. Q4

   What integration tests would give confidence that Atlassian's login and account recovery flow works across frontend, backend, and third-party services?

   MediumAPI/UI automationintegration testingAtlassian-specific

   Context:

   Atlassian login and account recovery flow

   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.

5. Q5

   Which logs, screenshots, traces, and videos would you collect when automation for Atlassian's seller onboarding flow fails?

   MediumDebugging and test strategylogs/debuggingAtlassian-specific

   Context:

   Atlassian seller onboarding flow

   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.

6. Q6

   How would you decide the regression suite for Atlassian's order tracking workflow after a major refactor?

   MediumTesting fundamentalsregression testingAtlassian-specific

   Context:

   Atlassian order tracking workflow

   How to answer:

   Separate smoke, sanity, targeted regression, and full regression. 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 Atlassian's order tracking workflow into CI/CD without slowing every pull request?

   MediumDebugging and test strategyCI/CD test executionAtlassian-specific

   Context:

   Atlassian order tracking workflow

   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 Atlassian's subscription billing workflow, and what tradeoffs would you call out?

   MediumAutomation codingCypressAtlassian-specific

   Context:

   Atlassian subscription billing workflow

   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 Atlassian's seller onboarding flow. When does it help, and when does it become a bad abstraction?

   MediumAutomation codingPage Object ModelAtlassian-specific

   Context:

   Atlassian seller onboarding flow

   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 Atlassian's login and account recovery flow?

    MediumAutomation codingPlaywrightAtlassian-specific

    Context:

    Atlassian login and account recovery flow

    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

    Which SQL checks would you write to validate data created by Atlassian's subscription billing workflow?

    MediumAPI/UI automationSQL for testingAtlassian-specific

    Context:

    Atlassian subscription billing workflow

    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.

12. Q12

    How would you handle dynamic elements in Selenium or Playwright for Atlassian's search and filtering experience?

    MediumAutomation codingSeleniumAtlassian-specific

    Context:

    Atlassian search and filtering experience

    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.

13. Q13

    What accessibility checks would you include for Atlassian's notification preference center?

    MediumDebugging and test strategyaccessibility testing basicsAtlassian-specific

    Context:

    Atlassian notification preference center

    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.

14. Q14

    Write the structure of a high-quality bug report for a failure in Atlassian's login and account recovery flow

    MediumDebugging and test strategybug reportingAtlassian-specific

    Context:

    Atlassian login and account recovery flow

    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.

15. Q15

    How would you work with developers when automation exposes recurring defects in Atlassian's login and account recovery flow?

    EasyBehavioral/project discussioncross-functional communicationAtlassian-specific

    Context:

    Atlassian login and account recovery flow

    How to answer:

    Focus on shared ownership, actionable reports, root cause, and prevention. 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 Atlassian Qa Automation Engineer Sdet mock

Solid coding & design; prepare a strong values/behavioral round; show craftsmanship

Qa Automation Engineer Sdet interviews at other companies