ROLE
Backend
Compare expectations across career stages →
These are the same questions found in the library, grouped here by the capability each one mainly examines.
1216 questions
Extended questions 401–450 of 1216 on this page.
C · Value judgment and direction setting31
- The company's funding lasts about 12 months, the key capability you need takes roughly 18 months to grow, and the market window has only 6 months left. How does your plan handle these unsynchronized time scales?
- When planning the next six months, do you work forward from your resources and current state, or backward from the goal? Do the two give the same conclusion?
- Your quarterly plan leaves out several important items. How do you record them so that when someone wants to revisit one later, the discussion rests on the judgment rather than re-arguing how important it is?
- How do you confirm that your team's goals are consistent with the company's strategic goals? When they are not, do you adjust the team's goals or try to influence the goals above?
- If you had to plan a technical direction over three to five years, how would you do it? How do you keep it from becoming a vision list that cannot be tested?
- The company’s growth is slowing, and your manager asks you to explore an unfamiliar, highly competitive market with a limited budget. What would you learn and test in the first 30 days, and what evidence would determine whether to continue or stop?
- A market window is short and a full solution takes two months. A reversible one-week pilot is possible, but cannot validate every long-term risk. How would you choose the sequence?
- Looking back at work you have already finished, which three things do you now think were not worth doing? Why did you do them then, and what changed in your judgment?
- The team lacks capacity for all three: a short-term revenue project, strategic exploration, and technical refactoring. What criteria would you use to compare and rank them? How would you explain strategic value or maintenance risk that cannot be measured directly?
- A new product exploration has consumed two quarters. Pilot completion stays below target, while the team argues one more feature will fix it. How would you judge evidence for further investment and stopping?
- In a review, three candidate projects are each marked P0 by their owners, all for the reason 'very important.' How would you turn the review from arguing about order into a trade-off people can check?
- Looking back over the past six months, what were the three most worthwhile things you did? Why those, what benefit did they bring, and how did you confirm that benefit?
- Choose a project you are working on. Given its goal and ranking criteria, what are the three most important things to do and the two easiest to pause or stop?
- The release window moves up by two weeks, and the team can finish only three of six planned items. Business, reliability, and compliance leads each say their work cannot slip. How would you verify which commitments are truly non-negotiable, surface any infeasible combination, and decide what to deliver or escalate?
- How did you apply the industry's practices to your current business? Which applied directly, which needed adapting, and which did you judge not to apply, and why?
- A high-traffic flow was changed into sequential steps, raising overall completion. Support reports, however, show users struggle to find exit, undo, or change options. How would you determine whether this is a real experience improvement, a segment difference, or a metric artifact?
- Describe a prediction you made about a market or technology change. What evidence and mechanism supported it at the time, what happened afterward, and what evidence would have shown the prediction was wrong?
- You say this solution is the most advanced in the industry. What is that based on, and what did you compare against, along which dimensions, and as of when?
- A legacy feature has few users but supports month-end reconciliation, and maintenance cost keeps rising. How would you compare migration, paid maintenance, and retirement?
- Describe a product decision where a short-term metric worsened, but the team expected a longer-term benefit. What evidence informed the decision, how did you monitor it, and what later evidence linked the outcome to that choice rather than outside factors?
- A new process doubles weekly feature releases, but task completion is unchanged and support tickets rise slightly. How would you decide whether to continue, adjust, or stop?
- 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?
No questions in this section match your target. ·
D · Delivery and ongoing operations19
- 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?
No questions in this section match your target. ·