Product company
Coding-first testing: clean code, edge cases, and testing at very large scale.
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.
What they tend to probe
- Coding
- Test design from first principles
- Large-scale and flaky-test thinking
- Debugging
- Clear communication
Question 1 · Test design · Medium
How would you test a search box with autocomplete?
Answer guide
Input classes (empty, long, unicode, emoji), latency budget, ordering and ranking stability, caching, privacy of suggestions, accessibility, behaviour under slow networks, and how you would measure quality, not just correctness.
Question 2 · Coding · Medium
Write a function that merges overlapping intervals and list the tests you would add.
Answer guide
Sort by start, sweep and merge. Tests: empty, single, touching intervals, nested, unsorted, duplicates, negative values, very large input.
Question 3 · Flakiness · Hard
A test fails about 1 in 200 runs across thousands of tests. How do you find the cause at scale?
Answer guide
Collect per-test pass history, correlate with machine, time, order and shared resources, rerun in isolation many times, quarantine with an owner and deadline, and fix the common causes in shared helpers.
Question 4 · Debugging · Medium
Users report a feature is slow, but your tests show it is fast. What next?
Answer guide
Your environment differs: data volume, region, device, network. Reproduce with realistic data, use field metrics and traces, and compare percentiles, not the mean.
Question 5 · Design · Hard
Design a test strategy for a feature that changes how results are ranked.
Answer guide
Offline evaluation sets, regression on known queries, A/B experiment with guardrail metrics, human review samples, rollback plan, and monitoring for slow quality drift.
Question 6 · Communication · Easy
You disagree with a developer about whether an issue blocks launch. How do you decide?
Answer guide
Frame it by user impact and risk, bring evidence, propose options (fix, mitigate, launch with a flag), and agree who makes the call and when.