Companies / Atlassian

Atlassian practice pack

Product company. Quality in a continuous-delivery culture with shared ownership.

These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.

Skills this role is usually tested on

  • Whole-team quality
  • Test automation in code
  • Feature flags
  • Observability
  • Pairing

Business areas used for scenarios

  • developer tools
  • team collaboration
  • cloud software

6 questions

Answer out loud first, then open the guide. Most people read the guide too early.

  1. 1

    Developers own quality here. What is the role of a QA engineer then?

    mediumCulture

    A strong answer covers

    Coach on testing, build shared tooling, review test strategy, explore for what automation misses, and use production data to find risk.

  2. 2

    How do you test a feature behind a flag that rolls out gradually?

    mediumFeature flags

    A strong answer covers

    Both flag states, targeting rules, rollout percentage behaviour, kill-switch speed, data created while on then switched off, and cleanup of old flags.

  3. 3

    Which tests belong at unit, integration, and end-to-end level for a comment feature?

    mediumAutomation

    A strong answer covers

    Rules and formatting at unit, persistence and permissions at integration, a small number of user journeys end to end. Say what each level would NOT cover.

  4. 4

    What would you monitor after releasing a change to search?

    hardObservability

    A strong answer covers

    Latency percentiles, error rate, zero-result rate, click-through, and resource use, with alerts tied to a rollback decision.

  5. 5

    Write a test helper that retries an assertion until it passes or times out. What are the risks?

    mediumCoding

    A strong answer covers

    Poll with a deadline and interval, rethrow the last error. Risks: hiding real slowness, masking flaky behaviour, and long total runtime.

  6. 6

    Run a 30-minute exploratory session on a kanban board. What is your charter?

    easyExploration

    A strong answer covers

    Mission, areas (drag, limits, concurrency, permissions), notes, bugs, questions, and a debrief. Time-boxed and written down.

Now say it to an interviewer

Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.

Start a mock interview Build a plan from a job description