Loading...
Loading...
Browse 5 real-world technical and behavioral interview questions about Judgement. Review scenarios, edge cases, and architectural best practices.
Separate what the design costs users from what you personally dislike, then reconstruct the constraint that produced it: a business model, an organisational boundary, a regulatory rule or a migration nobody can finish. Any change you propose has to survive that constraint or it is not a proposal.
Name the clock and what it was costing, say which facts you had and which you chose not to wait for, classify the call as reversible or not, act at the level you were authorised to and say so, and record the reasoning at the time so it can be judged on what you knew.
Separate a disagreement about the mechanism from a disagreement about the goal, then test your objection cheaply rather than argue it: a week spent proving the request will not move the number is usually worth more than either refusing or complying in silence.
Re-plan the remaining time against risk rather than against the test-case order, then report coverage as an explicit list of what was tested, what failed and what was never opened. The recommendation is yours; the decision to ship belongs to whoever carries the business consequence.
Choose work whose value you can state in the terms the business used, explain why you are proud of it in a way that reveals your standards, and be ready to be precise about which parts were yours. The choice itself is the signal the interviewer is reading.