Interview red flags at OASC, AOSB, and AIB: blaming others in scenario answers

Scenario and competency questions come up in almost every OASC, AOSB, and AIB interview, usually some version of "tell me about a time something went wrong." How a candidate answers that question tells the board a lot more than the story itself does. One of the clearest red flags an assessor watches for is a candidate who, even subtly, shifts responsibility onto someone else rather than owning their own part in what happened.

Why this matters so much to assessors

Officer selection is ultimately trying to work out whether someone can be trusted to lead under pressure, and leadership means being accountable for outcomes even when other people or circumstances contributed to them. A candidate whose failure story is really about a teammate who let the side down, or a resource that wasn't available, or timing that was out of their hands, is showing the board the opposite of that. It doesn't matter whether the blame is factually accurate. What the board is listening for is whether the candidate can locate their own agency in a difficult situation, and that's much harder to demonstrate if the story is framed around someone else's failure.

How the blame creeps in without candidates noticing

Very few candidates walk into an OASC, AOSB, or AIB interview intending to blame anyone. It usually creeps in through the framing rather than a direct accusation. Phrases like "the rest of the team weren't pulling their weight" or "I wasn't given enough information to work with" can be entirely true and still land badly, because they put the explanation for the outcome outside the candidate rather than inside their own decisions and actions. The fix isn't to lie about what happened, it's to change where the weight of the story sits.

Reframing without losing honesty

The strongest answers acknowledge the circumstances briefly, then move quickly to what the candidate did about it. Instead of "the team member missed the deadline, which put us behind," a stronger version is "I noticed early we were behind pace and should have checked in with the team sooner rather than assuming it would sort itself out." Same underlying situation, but the second version puts the candidate's judgement at the centre of the story rather than someone else's shortfall.

This applies just as much to the Result section of a STAR-style answer as it does to the Action. Candidates sometimes handle the Action well, then undo it in the Result by explaining why the outcome wasn't fully their fault. If the result wasn't good, own that too, and say what you'd do differently next time. Boards consistently rate honest self-assessment of a poor outcome more highly than a defensive explanation of a good one.

MAP's coaching sessions spend real time on exactly this kind of reframing, going through a candidate's own stories and rebuilding the ones that unintentionally shift blame before they ever reach a real board.

The same principle across all three boards

The specific scenarios differ across OASC, AOSB, and AIB, aircrew leadership situations, army command tasks, naval team scenarios, but the underlying test is identical. Every board is listening for ownership, not a flawless story. A candidate who can calmly say "that was on me" about a genuine mistake, and explain what they learned from it, will consistently outperform one who tells a technically impressive story that quietly avoids taking responsibility for anything that went wrong.