ROLE
Mobile
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1143 questions
Extended questions 351–400 of 1143 on this page.
C · Value judgment and direction setting11
- 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?
- The request is 'add an Export to Excel button to the order list page.' Show how you move from the surface request to the user's behavioral obstacle, and then to the value outcome.
- A colleague proposes adding a settings switch to a feature. Before discussing how to build it, which questions would you ask to judge whether the switch is worth building?
- Overall onboarding conversion falls. The funnel shows the most exits at address verification, but support records point to identity checks. How would you choose research and fix priorities?
- How does technology truly drive the business, rather than merely support it? Tell me about a time technology opened a possibility the business did not have before, and how you judged it was not just technology amusing itself.
- When you did your research, what were the industry level, the best practice in this direction, and the level already reached inside your company? Where does your solution fall, and why?
- Choose one technology shift you have followed. Based on available material and direct observation, which types of companies may be most affected over the next two years? Explain your evidence and inference, what it could mean for your company, and what you have done to test or respond.
- The team wants to “use our own product more,” but the last product-use session produced only scattered impressions. How would you design a feedback loop from a real task to a verified fix?
- A platform has migration, reliability, and productivity workstreams, but annual capacity supports only two. How would you sequence and trade off the quarters?
- A team plans to end support for an old technology, but critical systems still depend on it and replacement is expensive. How would you create a retirement roadmap?
- Brand asks for low-contrast text, but users with low vision struggle to read it; increasing contrast changes the brand presentation. How would you make and validate the design decision?
No questions in this section match your target. ·
D · Delivery and ongoing operations39
- Faced with a large problem that is still unclear, how do you plan how many people and resources are needed? How do you estimate under uncertainty, invest in stages, and ask upward for resources?
- A team has held delivery for months only by working overtime. How do you tell whether it is a people problem or a capacity gap, and what do you do?
- Incidents and recovery work interrupt every iteration, and roadmap commitments keep slipping. Leadership wants the dates preserved without adding staff. How would you propose capacity and goal changes?
- For several quarters, production support, customer escalations, and cross-team requests have displaced roadmap work. Someone proposes a universal 20% reserve, though interruption rates vary. How would you set the reserve?
- How do you work out what your team can really commit to next cycle, rather than headcount times working days?
- When you made this decision, what resources did you have and how wide was your scope of collaboration? How did those limits shape your choices?
- A business partner brings you a problem that is not clearly defined. What sources would you check, whom would you consult, and how would you separate confirmed facts from assumptions? How would you turn the findings into an actionable plan?
- Different teams provide conflicting data and explanations for the same business problem, while the project is already planned for this quarter. How would you decide what to investigate first and what to defer?
- Tell me about the most complex feature you owned. How do you break a vague business request down, step by step, into a requirements document without logical gaps, and how do you design fault tolerance and interaction for edge cases such as a lost connection or an abnormal account?
- Halfway through a project, available capacity suddenly drops by half while the deadline stays fixed. How would you resequence work and reset expectations?
- A customer asks for “a real-time dashboard,” but their examples suggest they only discover inventory errors later in the day. How would you guide the discussion?
- You receive a request in an area you have never worked in. How do you break it down and give an estimate that can be checked later?
- A campaign goes live overnight, but heavy traffic stalls the system. Users cannot claim coupons and start complaining. As an engineer involved in the campaign, how would you coordinate with operations and support on temporary business measures while restoring the system?
- 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?
- A production service suddenly fails widely. In what order do you act during the first hour?
- A major incident produces 18 actions across architecture, monitoring, training, and process, but teams already have quarterly commitments. How would you select actions that reduce recurrence risk?
- 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?
- Describe a re-engagement or referral campaign you contributed to as an engineer. Which systems, data, or delivery work did you own, how did you clarify budget and key user behavior with operations, and how did you verify incremental impact and your actual contribution?
- The promotion strategy is set and you are responsible for execution. What goals, rules, resources, risks, and acceptance criteria would you confirm before launch?
- Sales, support, and engineering can all label customer issues top priority, so the queue cannot distinguish business outages from general dissatisfaction. How would you design severity and escalation?
- You are about to run a growth experiment in production. What checkpoints and stop conditions do you prepare first?
- During an outage, engineering wants to disable a feature, business wants to keep accepting orders, and support has promised a recovery time. Responders receive conflicting directions. How would you organize the response?
- How would you move from one-off campaigns and acquisition toward automated, data-informed lifecycle operations? Describe a case where data tracking and algorithms turned manual work into repeatable rules.
- A strategic change requires you to shut down at once a business that brings many users but has lost money for years. How do you, in the shortest time, reassure thousands of affected partners, complete the wind-down compliantly and smoothly, and prevent a group public-relations crisis?
- A critical operations playbook is still used by multiple regions, but its author has left and recent system and policy changes were never incorporated. How would you identify which steps remain safe, establish temporary controls and ownership, and verify that frontline teams can use the new version correctly?
- Five projects flag the same platform dependency as a possible delay, yet each remains green. What evidence would tell you to change the portfolio instead of following up project by project?
- Two weeks before launch a stakeholder asks for one more feature. How do you decide to accept, defer, or decline, and what do you record?
- What was the biggest challenge in this project? Why was it hard, how did you push it forward at the time, and how did it end?
- A business lead says change approval slows market opportunities and asks teams to insert requests outside review. Past urgent work has caused rework. How would you design an exception path?
- A release date has been promised externally, but teams keep requesting features and fixes. How would you decide when to freeze scope, which exceptions to allow, and who owns replanning consequences?
- Engineering tells you that, because of the underlying architecture, the feature you specified will slip two weeks, while the business side wants it tomorrow. How do you cut half the features in a short time and keep a minimum viable version that can ship, and what do you rely on to decide what stays and what goes?
- Three projects list the same platform team as a critical dependency, and all buffer time is allocated. A new regulatory requirement must ship before quarter-end. How would you reallocate capacity and commitments?
- 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?
- One owner is responsible for four high-priority projects. Status reports look normal, but risk handling, cross-team decisions, and retrospectives are all delayed. How would you decide whether to add support, reassign ownership, or reduce the portfolio?
- You are leading a project across engineering, design, and operations. How would you clarify the shared goal and responsibilities when each group defines success differently?
- A key vendor has delayed an interface twice, but the project plan still uses the original date. Internal teams are building a temporary adapter in parallel. How would you reset the baseline, account for added work, and show leadership which commitments remain credible?
- Two projects' schedules collide and both need the same people. What do you do, how do you turn the conflict into options that can be discussed, and how do you get both sides to accept the result?
- Three weeks into a project you find two risks nobody owns. How do you make them manageable?
- An automated approval service stops working, so the operations team temporarily switches to a spreadsheet and limits user impact. Two weeks later, the service is still down, and the spreadsheet has inconsistent permissions and records. How would you manage the temporary process, restore automated approvals, and decide when to shut it down?
No questions in this section match your target. ·