ROLE
AI engineering
Compare this role’s stage expectations →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1175 questions
Questions 51–100 of 1175 on this page.
A · Professional problem solving and implementation50
- Cloud costs keep rising and finance asks for cuts while teams are improving reliability. How would you find savings without shifting risk elsewhere?
- 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?
- How do you identify and record technical debt and pay it down without stopping business delivery? Which debts are worth paying and which can be left for good, and how do you judge?
- Your solution depends on a lower-level service or library. If it changes substantially, how would you migrate, fall back to a version that preserves core features, or replace it?
- 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?
- In the technical area you work in, how is the industry developing? Is your solution adapting to that trend or going against it?
- 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?
- 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?
- 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?
- 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?
- What technical gains did this project bring? How do you measure them, and what complexity and maintenance cost did you pay for them?
- You take over a module that is about to ship and has very low test coverage, and time is short. How do you decide which tests to add first, and how do you explain that order to the team?
- Two services write directly to the same business table, and an immediate shutdown is impossible. How would you gradually establish a single data owner?
- An order is updated successfully, but a cross-service report reflects it minutes later. The product asks for “real-time status.” How would you define and implement consistency expectations?
- A cross-service flow includes payment, inventory reservation, and shipment. How would you define compensations and irreversible boundaries when later steps fail?
- Incidents recur at service boundaries. Each team can show its service is healthy, but nobody owns end-to-end recovery. How would you repair accountability?
- Several services have separate owning teams, yet a small change often requires three or four teams to release together. How would you assess whether the service boundaries have failed?
- A user edits offline and queues several changes. When connectivity returns, the token has expired and some requests may already have reached the server. How would you design reauthentication, idempotency, and conflict handling?
- 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?
- 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?
- 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?
- A team decides to split a large repository, but history, CI, package releases, and ownership are connected. How would you sequence the migration?
- 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?
- Packages have very different release cadences, but shared version numbers force unrelated teams to release together. How would you design versioning and release policy?
- 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?
- After an async task starts, the caller immediately mutates an input object, and results sometimes change. How would you determine whether this is shared mutable state, copy semantics, or an ownership issue?
- Two usernames that look identical are treated as different, or distinct spellings are treated as the same. How would you analyze Unicode normalization and identity comparison?
- A critical user journey across several pages and services regresses often. How would you define the scope and priority of automated tests?
- A user requests deletion of personal data, but some records have reached backups, analytics warehouses, and downstream systems. How would you design a verifiable deletion process?
- A widely used dependency is disclosed as critically vulnerable, but upgrading may introduce compatibility issues. How would you sequence the response?
- 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?
- Backups report success, but the team has never verified restored data integrity or recovery time. How would you establish demonstrable recovery capability?
- A new external service will access user data and trigger internal actions. How would you perform a lightweight but effective threat model?
- The system uses pre-signed URLs for private downloads, but links can be forwarded or retained for a long time. How would you design authorization and expiry boundaries?
- How should the permission system of a large operations back office be designed? How do you organize roles, data scope, approvals, and audit, and how do you keep it from getting out of control as permissions multiply?
- How would you design an article editing and publishing system? How should state and data be organized for drafts, review, scheduled publishing, multi-channel distribution, and edits after publication?
- Issuing a coupon after payment used to run synchronously, and it is being changed to an async queue with retries. Review this change: which failure sequences worry you most, and what would you rehearse before release?
- How would you design an online audio or video editor? How should the timeline, assets, non-destructive editing, preview, and final export each be designed?
- How would you design a platform where operations staff build campaigns and game mechanics themselves? How do you abstract campaigns, mechanics, rules, and features into configurable parts, and how do you keep a configuration correct once it goes live?
- Before drawing any architecture diagram, which few numbers would you use to decide whether a service should be split or cached? Use a service you know to explain.
- How would you design a document system for real-time multi-user editing? When several people edit the same passage at once, how do you guarantee eventual consistency, and how do you merge after offline edits?
- From an engineering view, how do you estimate the overall cost of a system? How are storage and compute costs each calculated, and which grow linearly with scale and which do not?
- When the business operates across several countries and regions and user data must flow across borders, how do you solve data compliance in systems and processes, and how do you judge and decide in gray areas where the rules are unclear?
- The local database has updated, but syncing the cache or sending a downstream message fails. How would you make the systems converge and handle retries, compensation, or manual recovery?
- A major promotion or international launch may increase traffic fivefold next year. Starting from the current architecture, how would you check for bottlenecks in the gateway, critical request flows, storage, and machine resources? How would you phase the work, staff it, and validate your assumptions?
- How would you design a product where a person and an AI write together? How are the AI's edits shown, accepted, or rejected, and how are conflicts handled when both edit at once?
- Design a collaboration product that supports large-file uploads with resumability, where files must be validated and scanned before other members can access them. What constraints would you clarify, and how would you design upload, temporary storage, scanning, publication, permissions, and cleanup boundaries?
- How would you design a large-model chat system? How do you handle streamed output, multi-turn context, history, interruption, and retries, and how do you control cost and latency?
- How do the costs of a recommender system add up, including retrieval, ranking, feature serving, storage, and experimentation? How would you trade effect against cost?
- How would you design an invitation-based viral marketing campaign? How do you design invitation relationships, reward payout, abuse prevention, and effect evaluation?
No questions in this section match your target. ·