Loading...
Loading...
Browse 7 real-world technical and behavioral interview questions about Decision rights. Review scenarios, edge cases, and architectural best practices.
Collect written evidence before anyone speaks, then work out whether the two disagree about what the candidate did or about where the bar sits, because only the second is yours to settle. Decide on the evidence against the competency, name the decision as yours, and fix whichever part of the loop produced the split.
Stay current on failure modes, cost and architecture rather than on syntax, and keep off the critical path. When you disagree with a design, declare whether you are giving input, asking a question, or making a decision — because unlabelled opinions from a manager are heard as instructions.
Make the team convert the ask into a measured cost the current service imposes and a payback period, then test whether an incremental route reaches the same place. Say no on the arithmetic rather than on authority, and if you say yes, agree in advance what would make you stop.
Work out the shortfall in engineer-weeks so the gap is arguable, then rank the three on value at risk and on what other people committed on the strength of your date, take the trade-off to whoever owns it rather than deciding quietly, and stop the dropped item cleanly.
Stop negotiating between opinions and get the disagreement written down as two named decisions with their consequences, then push it to whoever owns the budget; as an outsider your leverage is that you can make the conflict visible without being a party to it.
Name the delivery impact concretely, then look for the structural cause — most such conflicts are an unadjudicated design or ownership dispute wearing a personality mask. Hear both separately, decide what they cannot, set observable expectations with a review date, and separate them only as a last step.
Establish who owns the decision before arguing about the decision, then make it cheap for that person to decide by putting the trade-off in writing with options, consequences, a recommendation and a decide-by date. You are not the arbiter; you are the reason the arbiter can choose quickly.