What automation stack is used by QA teams at Atlassian?

Tech stack signals are extracted from peer reviews on this page. Common defaults include Playwright or Selenium, Postman/RestAssured for API, Jenkins/GitHub Actions for CI, and SQL for data validation.

How are QA and SDET roles at Atlassian rated for culture, growth and work-life?

2 approved anonymous reviews from testers give Atlassian an average culture score of 4.0/5, with 100% saying they would recommend the company to another QA engineer.

SoftwareTestPilot home

QA Hangar

Company Pulse

Atlassian

Q: What does the QA interview loop at Atlassian look like?

Peer-reported rounds typically include a recruiter screen, QA fundamentals, an automation deep-dive (Selenium/Playwright), an API + SQL round, and a hiring-manager conversation. See the round-by-round breakdown on this page.

Approved anonymous reviews from software testers. Anonymous by default.

All companies

Atlassian

4.0 / 52 reviews· 100% would recommend

Website

Rating distribution

5★
0
4★
2
3★
0
2★
0
1★
0

Culture axes

QA culture4.0
Work-life4.0
Growth3.5
Management3.5

QA interview loop at Atlassian

Difficulty 6/10

1
QA fundamentals
45 min
Test design, boundary/equivalence, defect life-cycle, severity vs priority.
2
Automation deep-dive
60 min
Selenium/Playwright architecture, waits, POM vs screenplay, flaky test triage.
3
API + SQL round
45–60 min
REST verbs, contract testing, JSON assertions, joins, window functions.
4
System / test-strategy design
60 min
Design a test strategy for a payments/checkout system, quality gates in CI/CD.

Median time-to-offer from peer reports: ~17 days. Prep with our QA interview question bank.

Green flags to look for

There's a shared observability dashboard testers can read.
Bug reports get triaged inside 24h with a named owner.
Automation runs on every PR — not a nightly wishful cron.
Test environments look like prod — not last quarter's snapshot.

Red flags to grill in your loop

Flaky tests get muted, not fixed.
Only QA is on the release call at 11pm.
Automation is measured by count of scripts, not defects caught.
One shared UAT environment that everyone fights over.

QA tech stack signals

PlaywrightSeleniumPostman / APIJenkinsSQLGit

Common industry defaults — replace with peer-reported stack as reviews arrive.

Live culture signals

Fresh reviews (90 days)2
Would-recommend rate100%
Culture vs site average+12%
Est. time-to-offer~17 days

Questions testers reported being asked

Automation
Walk me through how you'd stabilise a Playwright suite that fails 1 in 10 runs.
Architecture
Explain the trade-offs between Page Object Model and Screenplay pattern.
Case design
Given a spec, write 6 test cases for the login endpoint — happy, negative, boundary, security.
Debugging
How would you catch a race condition in a checkout that only reproduces in prod?
Strategy
Design a test strategy for a payment refund flow across web, mobile and BE.
Release
You have 15 minutes before a release and one flaky E2E — quarantine or block? Defend it.

Role-specific prep kit for Atlassian

Playwright interview questions Selenium interview questions API testing questions SQL for QA Full QA interview hubATS-check your resume before applying

Hiring at Atlassian? Check Jobs Radar for the latest openings.

Insider FAQ — before you accept

＋What does the QA interview loop actually look like here?

Based on peer reports, expect a recruiter screen, a QA fundamentals round, an automation deep-dive (Selenium/Playwright), an API + SQL round, and a hiring-manager conversation. Ask the recruiter upfront whether there is a live coding round — that single question changes how you prep.

＋Do QA engineers here own test strategy or just execute it?

Look for it in the reviews below. A healthy signal: testers are in grooming, own the test plan, and can veto a release. A weaker signal: QA gets a finished spec and a deadline. Ask in your loop: 'Show me the last release where QA said no.'

＋What automation stack should I brush up on before the interview?

Whatever the pros/cons below mention most. If nothing is listed yet, assume the industry default: Selenium or Playwright + a Java/JS/Python runner, Postman or RestAssured for API, Jenkins/GitHub Actions for CI. Warm up on flakiness, waits and parallelisation — that's where 70% of tough questions live.

＋Is manual testing respected or treated as a stepping-stone?

This is culture, not process. Skim the 'Cons' below for phrases like 'only automation gets promoted' or 'manual testers left out of design reviews'. If it's absent, treat that as neutral and ask directly in the loop.

＋How is on-call and release ownership handled for QA?

Ask specifically: who joins the release bridge, who signs off, and what happens at 11pm on a Friday if a critical bug surfaces. Reviews mentioning weekend releases or lone-QA sign-off are the loudest red flag on this page.

＋What salary band should a mid-level SDET target here?

Cross-check the QA salary guides linked in the prep kit above — bands vary by city and years of experience, but the recruiter almost always negotiates within a ±15% window of their internal grid. Anchor with data, not a wish.

Approved reviews

4/5·Anonymous QA · Senior · 2026· Recommends
Jul 8, 2026
Pros
Mature test frameworks. Good separation of unit/integration/e2e. Strong QA community.
Cons
Some legacy Selenium suites nobody wants to touch.
4/5·Anonymous QA · Mid · 2026· Recommends
Jun 21, 2026
Pros
Playwright migration going well. Leadership actually reads QA reports.
Cons
Bureaucracy when adding new tools. Approval loops for new SaaS.