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 351–400 of 1216 on this page.
C · Value judgment and direction setting42
- 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?
- One section of a community has stayed quiet for a long time. How do you judge whether it deserves continued investment or should be shrunk or merged?
- For the whole, is the part you own a lever, a fulcrum, or just one link? How do you judge that, and how do you show it is not merely important-looking?
- The team wants to keep optimizing the performance of a core API. What basis do you use to decide how far is far enough, and when to stop investing more?
- 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?
- As the industry enters a stock era, the company demands a complete shift from thinking in transaction volume to thinking in net profit. How do you raise net profit by adjusting the take rate and optimizing supply-chain operating costs without triggering large-scale exits or protests from merchants or creators?
- How would you calculate a product direction’s return on investment? How would you account for labor, cost, and revenue, use annual recurring revenue (ARR), and identify where the calculation might overstate value?
- Three business teams have raised similar needs, and someone suggests building a shared platform. How do you judge whether it is worth building, or whether each domain should first get a local solution?
- 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?
- What were the short-term and long-term benefits of this project? When the two conflicted, how did you trade them off?
- You discover that a new direction you pushed is wrong. How do you cut your losses, how do you judge whether to continue, adjust, or stop, how do you treat sunk cost, and how do you explain it to those involved?
- 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?
- A competitor launches a lower-priced substitute. Customers start negotiating harder, but usage has not changed much. How would you choose a response?
- A free feature attracts many active users, but inference and support costs rise too. How would you evaluate the business role of the free tier?
- The algorithm team expects an upgraded recommendation model to lift conversion by 3%, but operations would lose the ability to adjust key placements manually. How would you design an experiment and decision rules while accounting for value the experiment cannot measure?
- After the bot upgrade, sessions with no handoff to a human are counted as resolved, and the rate went from 72% to 91%. In the same week the handoff button moved into a submenu and the denominator changed. How do you respond today to the proposal to cancel weekend human coverage?
- What business result did your project bring? How do you confirm it came from this project and not from something else?
- Retention rose during a marketing campaign, and the team credits the channel, but a new product flow also launched and participants may already have been more active. How would you establish a credible comparison, estimate the campaign’s net lift, and state the limits of the conclusion?
- Who you compare against changes the conclusion directly. Why did you choose these comparisons, and how would your conclusion change with a different one?
- When you benchmark against a competitor's data, how do you decide what is comparable and what is not? What decision did you finally use it for?
- The completion rate of a key task fell this week. Before explaining why, in what order do you confirm that the change is real, where it is concentrated, and what cost users bear?
- How is your core metric defined? What are the numerator, denominator, time window, de-duplication, and exclusion rules, and why is it the core metric?
- How was your funnel built? Why are the steps divided the way they are, where does most of the drop-off happen, and how do you confirm the steps neither overlap nor leave gaps?
- How do changes at each funnel stage ultimately act on the business metric? Improving which stage by a little moves the business metric the most, and what is that judgment based on?
- Once your metric is converted to the industry's common definition, where does it stand? What assumptions did the conversion make, and what information did it lose?
- A dashboard holds dozens of metrics and the team's attention keeps getting pulled to the most visible numbers. Pick one user task and explain how you would tier the metrics and decide which enter the core list.
- An improvement you made has no reliable numbers. What other evidence would you offer that it really improved something?
- A target was set for a metric you own. How do you break it down into specific levers and actions, and judge along the way whether it can be met?
- The metric was met, but you felt the business did not really get better. Has that happened to you? How did you notice, and what did you do?
- After a feature launches, how do you judge whether it met its original goal? When do you review it, and what would you decide differently afterwards?
- The boss raises a business pain, such as high acquisition cost and poor retention. How do you translate it into goals the technical team can tackle, and show how technical means act on those business metrics?
- For the last new feature you launched, what were the specific before-and-after changes in the core metric, such as conversion, click-through, or retention? If the numbers fall short of expectation, along which dimensions do you usually investigate the cause?
- A feature encourages invitations, so inviters and friends may land in different experiment groups. Results are significant, but spillover cannot be fully isolated. How would you assess the conclusion?
- User mix or external conditions change during a project, making the original baseline incomparable. How would you continue judging the outcome?
- The target metric improved, but refunds, complaints, or manual handling also worsened. How would you decide whether the outcome is acceptable?
- The initial effect of a feature is strong but fades over several months. How would you distinguish novelty from lasting behavior change?
- The final business outcome will take months to appear, but the team must decide whether to continue investing now. How would you use leading indicators?
- Several teams changed the product, pricing, and operations at once, and the overall outcome improved. How would you assess each contribution?
- An experiment shows no expected lift, but also does not prove the idea ineffective. How would you decide whether to continue, change, or stop?
- Two projects each meet some goals, but one delivers more user benefit per unit of investment. How would you reallocate resources?
- A pilot meets its target, but results vary when expanded to more regions or segments. How would you judge whether the result is replicable?
- A redesign improves paid conversion but leaves more users unable to complete a core task. How would you judge whether the growth is worth it?
No questions in this section match your target. ·
H · Professional responsibility and work style8
- A critical data migration has no owner, and each team says it is outside its scope. How would you make sure the migration is completed safely while naming the final owner and ongoing responsibilities?
- A project falls short of its commitment, partly because of external dependencies and untested assumptions. How would you distinguish your responsibility, external factors, and corrective actions? If a dependency team refuses to address a gap, how would you assign ownership and escalate?
- You realize your status report omitted a risk that could change the decision, and executives have already relied on it. How would you correct it?
- A leader asks you to show only favorable segments and describe an insignificant result as a trend. How would you respond and preserve factual accuracy?
- You notice another team’s operation may expose user data; they have not invited you, and release is imminent. How would you decide whether and how to intervene?
- The technical decision authority and growth scope discussed during hiring differ substantially from the actual role. How would you establish facts, negotiate, and decide whether to stay?
- The team routinely relies on night-time responses for long-running emergencies, conflicting with your sustainability boundary. How would you raise the issue and seek a workable arrangement?
- You are asked to commit to a delivery date before dependencies and risks are confirmed, with unclear authority. How would you communicate without making a false commitment?
No questions in this section match your target. ·