Testability and Testing Practices Questions

Emphasizes designing code for testability and applying disciplined testing practices to ensure correctness and reduce regressions. Topics include writing modular code with clear seams for injection and mocking, unit tests and integration tests, test driven development, use of test doubles and mocking frameworks, distinguishing meaningful test coverage from superficial metrics, test independence and isolation, organizing and naming tests, test data management, reducing flakiness and enabling reliable parallel execution, scaling test frameworks and reporting, and integrating tests into continuous integration pipelines. Interviewers will probe how candidates make code testable, design meaningful test cases for edge conditions, and automate testing in the delivery flow.

MediumTechnical

0 practiced

Explain a consumer-driven contract testing workflow between service A and service B using tools like Pact. Describe how contracts are published, how providers verify contracts in their CI, and how SREs can integrate contract verification to reduce regressions and enable safer rollouts.

EasyTechnical

0 practiced

What are the most common causes of flaky tests in CI for SRE-managed services (for example timing, concurrency, or external dependency variability)? Provide a prioritized triage checklist you would follow when you first encounter flaky tests in critical pipelines.

HardSystem Design

0 practiced

How would you provide production-like integration environments for running pre-deploy tests that require realistic network topologies, multi-zone failover, and external dependencies while minimizing cost and preventing exposure of production data? Describe provisioning, data strategies, telemetry collection, and governance controls.

HardTechnical

0 practiced

Propose a system where scheduled chaos experiments are used to validate SLO robustness. Include automation to schedule and scope experiments, safety controls, how to measure SLO impact, what rollback or mitigation to run automatically if experiments cause excessive degradation, and how experiment results feed into reliability improvements.

HardSystem Design

0 practiced

Design a contract testing platform to ensure backward compatibility across hundreds of interdependent services. Include contract publishing, versioning, provider verification in provider CI, a compatibility policy engine, and automation that can prevent incompatible merges. Discuss operational overhead and patterns to reduce friction.

Unlock Full Question Bank

Get access to hundreds of Testability and Testing Practices interview questions and detailed answers.

Join thousands of developers preparing for their dream job.