Airbnb QA engineer interviews test automation frameworks, test strategy, CI integration, performance testing, and debugging complex multi-service systems.
All Roles
Software Engineer
Backend Engineer
Frontend Engineer
Full Stack Engineer
Mobile Engineer
Data Engineer
Data Scientist
ML Engineer
DevOps Engineer
DevOps Engineer
Product Manager
SRE
Security Engineer
Engineering Manager
Data Analyst
UX/UI Designer
QA Engineer
No verified questions yet for Airbnb.
system design
Senior
testing
#1
1. [OA] Design a Flaky Test Detector for Airbnb's CI system
Airbnb's continuous integration (CI) system must accurately report flaky tests that can lead to unreliable build statuses. You need to design a system to track test results over multiple runs to identify flaky behavior.-
-
Input:
Input:
Input:
Output:
Explanation: The test passed and failed, indicating flakiness. Example 2:
Input:
Input:
Output:
Explanation: The test has only passed once and is not flaky.Constraints:
- At most
- The system maintains results for up to
def report_result(self, test_name: str, result: bool) -> None: Records the result of a test run.-
def is_flaky(self, test_name: str) -> bool: Returns True if the test has shown flaky results, False otherwise.Example 1: Input:
report_result('login_test', True) Input:
report_result('login_test', False) Input:
is_flaky('login_test') Output:
True Explanation: The test passed and failed, indicating flakiness. Example 2:
Input:
report_result('search_test', True) Input:
is_flaky('search_test') Output:
False Explanation: The test has only passed once and is not flaky.Constraints:
- At most
1000 different test names.- The system maintains results for up to
50 runs per test.Related Airbnb QA Engineer interview prep
Start practicing Airbnb questions
Sign up for free to access walkthroughs, AI-generated questions, and more.
Get Started Free