Loading...
Loading...
Browse 8 real-world technical and behavioral interview questions about Estimation. Review scenarios, edge cases, and architectural best practices.
Reject the choice between a fabricated date and no answer. Ask what decision the date serves, separate known work from assumed and unknown work, give a range with its confidence and assumptions attached, buy the missing information with a timeboxed spike, and offer to fix scope or date but not both.
Find out what the date is being used for, then commit to something you can actually control — a timeboxed discovery end, a date for the date, or a narrow first slice — and never issue a single-point estimate for scope that is still undefined.
Estimate bottom-up against comparable work, carry an explicit three-point range with contingency as a visible line, then choose a commercial shape that matches the uncertainty. When asked to cut, change scope, phase or team mix — never re-estimate the same work downwards.
A product market sizing case should define the revenue pool, work top-down from households to willingness to pay, sanity-check penetration, then turn the estimate into a build-or-don't-build recommendation. It also connects estimation to the point an interviewer is testing.
Show the arithmetic once, then convert the gap into a decision the customer can take: what the stated budget genuinely buys as a coherent first phase, what the full scope costs, and which specific outcome is deferred. Never deliver the full scope at the reduced number.
Convert effort to duration through explicit productive capacity, then check it against the critical path and the customer's dependencies, because dates are often bound by sequence rather than effort. Against a promised date, commit a smaller scope rather than a compressed plan.
An estimate nobody in delivery has accepted is a number your company will be held to and nobody will defend. Get the person who will run the work to own it before submission, and when they refuse, escalate the disagreement in writing rather than averaging it away.
Points are relative sizes that trade false precision for a fast conversation whose real output is surfaced disagreement. Estimates that are always wrong are a system symptom, so diagnose unclear criteria, oversized stories, invisible work and interruptions, then forecast with throughput and cycle time.