What automation stack is used by QA teams at Datadog?

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 Datadog rated for culture, growth and work-life?

2 approved anonymous reviews from testers give Datadog 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

Datadog

Q: What does the QA interview loop at Datadog 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

Datadog

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-life3.5
Growth4.0
Management3.5

QA interview loop at Datadog

Difficulty 8/10

1
Recruiter screen
20–30 min
Compensation, notice period, why QA, why this company.
2
Live coding / pairing
60 min
Automate a small flow end-to-end; explain trade-offs while typing.
3
Automation deep-dive
60 min
Selenium/Playwright architecture, waits, POM vs screenplay, flaky test triage.
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: ~27 days. Prep with our QA interview question bank.

Green flags to look for

Test data seeded via API, not hand-crafted UI clicks.
Bug reports get triaged inside 24h with a named owner.
Automation runs on every PR — not a nightly wishful cron.
SDETs and manual testers get the same career ladder.

Red flags to grill in your loop

"We'll add tests later" — later never arrives.
No blameless post-mortems after a prod incident.
PMs push scope changes on the day of release.
Automation is measured by count of scripts, not defects caught.

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~27 days

Questions testers reported being asked

Case design
Given a spec, write 6 test cases for the login endpoint — happy, negative, boundary, security.
Architecture
Explain the trade-offs between Page Object Model and Screenplay pattern.
Debugging
How would you catch a race condition in a checkout that only reproduces in prod?
Automation
Walk me through how you'd stabilise a Playwright suite that fails 1 in 10 runs.
Strategy
Design a test strategy for a payment refund flow across web, mobile and BE.
SQL
Write SQL to find users who placed 3 or more orders in the last 30 days.

Role-specific prep kit for Datadog

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

Hiring at Datadog? 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
Jun 29, 2026
Pros
Perf and observability tooling is world-class - you learn a lot by osmosis.
Cons
Compensation stretched thin outside US/EU hubs.
4/5·Anonymous QA · Senior · 2026· Recommends
Jun 16, 2026
Pros
Security team collaborates well with QA. Real DAST in CI, not just theatre.
Cons
On-call is not for the faint of heart.