TOPIC
Engineering systems
These are the same questions found in the library, grouped here by the capability each one mainly examines.
97 questions
Questions 51–97 of 97 on this page.
A · Professional problem solving and implementation19
- 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?
- 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?
- 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?
- 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?
- 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?
- 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?
- Several teams copy de-identified data into development, staging, and performance environments with different refresh schedules. How would you design access, lifecycle, and reproducibility?
- 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?
- The same release behaves differently across clusters, and configuration changes are not fully audited. How would you establish configuration sources, drift detection, and rollback?
- Different teams own creation, editing, and review, and their form feedback is becoming inconsistent. How would you decide which patterns to standardize and which to keep distinct? How would you check loading, empty, error, and recovery states?
- Teams are copying shared components and adding local variants, making similar features inconsistent. How would you decide which differences belong in the shared design system and which should remain team-specific? How would teams help maintain those rules?
- A shared library releases a backward-compatible version, but application repositories cannot upgrade promptly because of pinned dependencies, generated code, or different release windows; a security fix remains blocked. How would you design compatibility policy and the dependency-upgrade process?
- 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?
- 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?
- Teams can release micro-frontend modules independently, but loading, navigation, error messages, and accessibility behavior are becoming inconsistent. How would you decide which capabilities belong to the platform and which stay with product teams?
- A backend API generates TypeScript, Java, and Swift SDKs, but nullable types, enums, and error models are drifting across languages. How would you design the contract source, generation process, and cross-language compatibility tests?
- 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?
- 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?
- Several product teams override shared component styles with CSS, causing frequent regressions after upgrades. How would you choose between adding configuration, splitting the component, or keeping exceptions?
No questions in this section match your target. ·
B · Business understanding and domain modeling8
- A database field has been replaced, but reports, exports, and external integrations still read it; deleting it directly could cause silent errors. How would you plan compatibility migration, consumer confirmation, and final removal?
- Business reporting needs the duration of every state transition, while an operations page needs only the object's current state; a wide table overwrote history during updates. How would you separate event facts, snapshots, and current-state models?
- Business categories may be added, merged, or renamed. Reports must reproduce the definition used at the time and compare results under the current definition. How would you preserve source categories, mapping versions, and report definitions?
- The system changes its user key from email to an immutable ID, but mobile caches, partner callbacks, and historical exports still reference email. How would you design mappings, a dual-read period, privacy cleanup, and retirement of old references?
- Several teams define user-status events differently, and the platform plans to unify them; some consumers rely on special meanings in old fields and cannot migrate at once. How would you build compatibility adapters, parallel validation, and deprecation governance?
- A new model requires additional features and changes the meaning of existing ones, while online serving must still support rollback to the old model. How would you version feature contracts, deployment order, dual-read cost, and retirement criteria?
- Orders, inventory, and loyalty points are owned by separate services; messages may be duplicated, reordered, or delayed. How would you define event identity, idempotency boundaries, and compensation records?
- A product line splits into two business units. Old orders belong to the previous organization, while future orders use the new structure. How would you represent organization versions and historical views?
No questions in this section match your target. ·
C · Value judgment and direction setting8
- In the past year, how much team capacity did you secure to address technical debt (accumulated maintenance and rework) or improve engineering infrastructure such as builds and releases? When these problems slow product work, how do you explain their impact and risk to business leaders and secure time to refactor?
- A new platform could reduce future development cost, but the legacy system needs two more years of support and this quarter funds only one major investment. How would you compare build, migration, and status-quo options?
- The boss or the business side squeezes the schedule and says "ship first, messy code is fine". As the owner, how do you respond? Which quality can give way and which cannot, and how do you make the concession open and time-limited rather than quietly becoming permanent debt?
- The business wants new features while the team has built up technical debt. How do you decide how much to invest in each this quarter?
- Describe a technology-platform project you worked on that few teams used and that produced little visible business value after launch. What evidence or assumptions justified the investment at the time? Which assumptions did later evidence disprove, and what validation did you add?
- Several teams spend hours each month resolving deployment configuration problems; a platform change could remove repeated work but adds no immediate revenue, while product features have explicit revenue targets. How would you estimate attributable platform value and investment limits?
- 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?
- The team can build an internal identity service or purchase a vendor product; building better fits unusual workflows, while buying is faster but involves migration, compliance, and long-term licensing. How would you compare lifecycle cost and reversibility?
No questions in this section match your target. ·
D · Delivery and ongoing operations4
- A system keeps having problems again and again, and each fix is followed by another failure. How do you find the root cause, how do you move the team from firefighting to real repair, and how do you show it no longer recurs?
- How do you keep the same kind of personal mistake from happening again? Did you improve the process and tooling, or just remind yourself to be careful? How do you know the improvement works?
- How do you measure engineering effectiveness? Which metrics do you choose, how do you keep the numbers from being gamed, and how do you turn the measurement into real improvement?
- Several teams use one deployment pipeline and fixed maintenance windows, but their changes differ in size and rollback readiness; one team's delay steals validation time from others. How would you plan release capacity and resolve conflicts?
No questions in this section match your target. ·
E · Collaboration, communication, and influence2
- Describe a time engineering found a technical constraint, undefined edge state, or unexpected cost while implementing your design. How did you clarify the real constraint, negotiate behavior and scope, and confirm that the final implementation still supported the core user task?
- Several teams maintain similar interfaces with inconsistent cost and user experience. You must promote a shared approach without management authority. How would you build adoption?
No questions in this section match your target. ·
F · People and organization building5
- A platform team owns shared capabilities, while business teams want rapid customization and the backlog grows. How would you design service boundaries and collaboration?
- One expert knows core system release and recovery procedures; others handle only simple tasks. How would you reduce the dependency?
- A strong-willed, technically good developer on your team dislikes writing unit tests and reviews carelessly. Talking to them directly may annoy them. What rules or mechanisms would you use to change the behavior, and how do you make them open and fair to everyone?
- After growing from six to fourteen people, the team still uses its old division of work. Members disagree on architecture decisions, operations support, and quality ownership. How would you reset the team agreement?
- Technology moves fast. As the team's technical lead, how do you keep the team from losing external market competitiveness by long maintaining the company's aging in-house systems? How do you balance business stability against each person's market value as an engineer?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth1
No questions in this section match your target. ·