DevOps

• On-call engineers receive many alerts each day, yet user complaints and service objective violations still go unnoticed. How would you redesign alerting?Engineering systems
• A repository accepts external contributions, and CI runs build scripts, reuses caches, reads test credentials, and produces release artifacts. How would you separate untrusted execution, credential permissions, and cache boundaries so code cannot read secrets or poison trusted artifacts?Engineering systems
• Cloud costs keep rising and finance asks for cuts while teams are improving reliability. How would you find savings without shifting risk elsewhere?Engineering systems
• A long-lived credential is shared by several services. Security requires prompt rotation, but all dependents cannot be stopped at once. How would you proceed?Quality, security, and safety
• The root cause of an incident is still unknown, but business stakeholders ask when service will recover. How would you update them, communicate uncertainty, and avoid misleading commitments?Engineering systems
• Some production resources differ from their declared configuration, including undocumented emergency fixes. How would you distinguish intentional changes from unexplained differences, assess the risk of overwriting state, restore trust, and prevent recurrence?Engineering systems
• A release must reach thousands of runtime nodes with varying versions and network conditions. How would you design rollout batches, health checks, and pause criteria?Engineering systems
• After a release goes wrong, the team says “we can roll back.” How would you check that this is true and not just a line in the plan?Engineering systems
• The application can be rolled back, but a database migration removed an old field and the previous version can no longer start. How would you redesign release order and rollback?Engineering systems
• After code changes, the build system sometimes misses affected apps and sometimes rebuilds the entire repository. How would you validate the dependency graph and cache invalidation rules?Engineering systems
• One repository contains multiple teams and production deployment config, but code-owner rules do not cover temporary admins and automation accounts. How would you review permission and approval boundaries?Engineering systems
• Two product packages form a dependency cycle, and splitting them creates a need to share domain types. How would you change the boundaries without hiding the cycle in a new shared package?Engineering systems
• A team decides to split a large repository, but history, CI, package releases, and ownership are connected. How would you sequence the migration?Engineering systems
• In a monorepo, shared packages are casually changed by one team, while consumers discover behavior changes only after upgrading. How would you establish ownership and compatibility contracts?Engineering systems
• Packages have very different release cadences, but shared version numbers force unrelated teams to release together. How would you design versioning and release policy?Engineering systems
• The repository has hundreds of packages and full CI is slow. The team wants to test only “affected” areas. How would you prove selective testing does not miss critical dependencies?Engineering systems
• A widely used dependency is disclosed as critically vulnerable, but upgrading may introduce compatibility issues. How would you sequence the response?Quality, security, and safety
• Service failures have exceeded the target range, but the business has firm feature commitments. How would you adjust the release pace and investment in reliability?Quality, security, and safety
• Backups report success, but the team has never verified restored data integrity or recovery time. How would you establish demonstrable recovery capability?Quality, security, and safety
• A build registry must clean up years of images, but production services may still roll back to old versions. How would you define retention and artifact recoverability?Engineering systems
• An organization must move several repositories from an old CI system to a new platform without pausing delivery across teams. How would you sequence migration and decide which repositories enter each wave?Engineering systems
• Message backlog often falls after scaling out, then returns a few hours later. What producer, consumer, and message characteristics would you inspect to locate the actual bottleneck?Debugging
• Hundreds of repositories pin different third-party versions, and security teams struggle to identify exposure when a severe vulnerability appears. How would you establish dependency updates and risk handling?Engineering systems
• A defect appears only in production and cannot be reproduced in development or staging. How would you determine whether the cause is environment, traffic shape, or data characteristics, and improve environment design?Engineering systems
• Several services read feature flags and audience rules on request paths. How would you design the control plane and local evaluation so behavior remains predictable when the control service fails?System design
• A critical end-to-end test fails intermittently: it passes alone but fails in a parallel suite, and the team has started rerunning it until it passes. How would you determine whether it exposes product risk, isolate shared state, resource contention, clock or ordering dependencies, and improve the test workflow?Quality, security, and safety
• After an update, some users occasionally load new HTML with old JavaScript and the page fails. How would you design asset naming, cache policies, and release order to reduce inconsistency?Engineering systems
• A new model improves offline evaluation, but answer quality may fall for a small set of high-value users. How would you stage a canary, observe it, and decide when to expand traffic?AI engineering
• A product depends on an external model API, and the provider may restrict request frequency or change available models. How would you design switch rules and temporary shutdowns for noncritical features so quality changes after switching are visible?AI engineering
• Teams share a repository but release at different cadences; shared package changes often block unrelated teams. How would you design boundaries, impact analysis, and release agreements?Engineering systems
• The same release behaves differently across clusters, and configuration changes are not fully audited. How would you establish configuration sources, drift detection, and rollback?Engineering systems
• The same commit passes reliably on a developer's machine but occasionally fails in CI because of time zones, random ordering, shared caches, or parallel races. How would you classify, reproduce, and reduce this nondeterminism?Engineering systems
• A feature is fully launched, but switches created years ago still control several code paths; the team does not know which flags can be removed and relies on memory during rollback. How would you establish flag lifecycles and cleanup ownership?Engineering systems
• A production dependency has a different artifact hash from the build associated with its repository tag, and the team cannot confirm it passed the expected CI. How would you establish build traceability, artifact verification, and release authorization?Engineering systems
• New clients use a replacement API, but users upgrade slowly and older versions still account for meaningful traffic; continued support also constrains server evolution. How would you set a support window, capability detection, migration notices, and retirement criteria?Engineering systems

No questions in this section match your target. Change target · View all questions

• The team releases monthly, and the business wants weekly releases, but automated testing, rollback, and monitoring are immature. How would you plan release capability without using deployment frequency as the only success measure?Planning

No questions in this section match your target. Change target · View all questions

• An incident is resolved, and the review lists more than ten actions for monitoring, capacity checks, and documentation; earlier actions were never verified. How would you assign owners and dates and confirm whether improvements worked?Reliability and incidents
• After a mobile release, network failures rise while server metrics remain normal; affected users cluster on older OS versions and weak connections. How would you scope the incident, reduce impact, and decide whether to pause or roll back?Reliability and incidents
• A critical dependency vulnerability needs prompt remediation, but the patch may conflict with the current release candidate; delay prolongs exposure, while immediate rollout could disrupt service. How would you plan validation, temporary mitigation, and release authorization?Reliability and incidents

No questions in this section match your target. Change target · View all questions