Interview Under Time Pressure: Justifying a Rejected Option
A candidate's Paper describes selecting a gravity retaining wall over a reinforced-soil alternative. In the interview, a panel member says: 'Your Paper says reinforced soil was cheaper and faster. You rejected it in one sentence. Defend that.' The Paper's actual reasoning was that the site had constrained access, the reinforced-soil supplier's lead time was 14 weeks against a 10-week programme, and the candidate had no prior experience with reinforced soil. The candidate now realizes the third reason is weak and the second was based on a verbal quote that was never confirmed in writing. The panel gives no indication of which point it is probing.
1. Construct the candidate's response, distinguishing strong reasons from weak ones and handling the unverified quote.
Read the worked answer
Lead with the strongest reason: programme. A 14-week lead time against a 10-week programme is a decisive constraint, because a cheaper wall delivered late fails the client's need. Then address access: constrained access affects construction method and may erode the reinforced-soil cost advantage, which is a legitimate secondary point. Then handle the weak reason honestly: inexperience is not a valid basis for rejecting a technically sound option, and the candidate should say so. On the unverified quote, the candidate should concede it was verbal and that the decision would be stronger with written confirmation, while noting the programme risk was large enough that a written quote was unlikely to close a 4-week gap. This sequence shows the candidate can rank reasons by weight, distinguish technical from personal grounds, and acknowledge evidential weakness without abandoning a defensible decision.
2. The panel asks: 'If inexperience isn't a valid reason, why did you include it, and what does that tell us about your judgement?' Give a model answer.
Read the worked answer
Answer directly: it was included because it was true, but it should not have been presented as a design justification, and on reflection it belongs in a risk note rather than a rejection rationale. What it shows is a gap between recording a genuine concern and presenting it as an engineering reason. The candidate can add that inexperience is managed by supervision, training, or specialist input, not by avoiding the option, and that if reinforced soil had been otherwise preferable the correct response would have been to seek specialist support. This answer works because it accepts the criticism without over-apologizing, shows the candidate understands the difference between a personal limitation and a project constraint, and demonstrates learning. The panel is testing self-awareness and the ability to separate the engineer's comfort from the client's interest.
3. How should the candidate close the answer so the panel is left with a clear view of the decision's soundness?
Read the worked answer
Close by restating the decision in one sentence with its governing constraint: 'The wall was selected because the reinforced-soil option could not meet the 10-week programme, and the access constraints made its cost advantage uncertain.' Then state what would have changed the decision: a confirmed lead time within programme, or a programme extension. That shows the decision was conditional on facts rather than preference. Finally, note the improvement for next time: obtain written lead times before the options appraisal closes. A concise close prevents the answer from dissolving into qualifications and leaves the panel with the reasoning structure: constraint, comparison, condition, lesson. The candidate should stop there rather than inviting further probing with unnecessary detail.