Structured interviews: STAR isn't enough if the pre-read pack is fuzzy

What the STAR method really is

STAR breaks a behavioural answer into four blocks:

• Situation: the factual context (project, client, constraint)
• Task: the candidate’s precise responsibility in that context
• Action: what they actually did themselves, not “the team” in general
• Result: measurable impact: number, deliverable, deadline met

The idea is simple: force the candidate out of generalities. No more “I worked on a complex team project.” Instead, a story grounded in verifiable facts.

Why everyone uses it (and why it isn’t enough)

STAR caught on because it gives the interviewer a thread. Instead of open questions and hoping for something interesting, it channels the exchange toward specifics.

The problem: STAR is an answer format, not a preparation method. It structures the conversation once you know what to dig into. But if no one has identified upfront which experience to probe and why, the interviewer is flying blind. They latch onto a keyword on the CV, the candidate runs with what flatters them most, and you get a smooth but non-discriminating exchange.

Two candidates can deliver two flawless STAR narratives about experiences that are totally off brief for the real need. The interview looks structured. The decision stays gut-feel.

---

The real issue: what happens before the interview

The competency pack drives everything

A STAR interview is only as good as the framing that precedes it. In an ESN, that framing rests on the competency pack sent to the client before the meeting.

If the pack is a generic PDF with a list of technologies and missions described in two lines, the client walks into the interview not knowing what to ask. They skim the CV, spot “Java” or “cloud migration”, and fire a broad question. The candidate answers on their comfort zone. No one validates real fit.

What the client needs to know before the first question

For a STAR interview to be useful, the client should arrive with three clear pieces of information:

• Which assignment in the track record is closest to their need: same sector, same stack, same type of deliverable or constraint
• Which specific aspect of that assignment to probe: technical scope, team leadership, schedule discipline, relationship with the business
• What orders of magnitude to expect: number of users, team size, release cadence, budget or criticality

Without those anchors, the interviewer does their own triage. And their triage is not necessarily the right one.

A concrete example

You pitch a Java lead for a core banking system overhaul. Their pack lists eight assignments over six years. The client latches onto the most recent one, a mobile e-commerce app, because it’s the first thing they see. They spend twenty minutes in STAR on React Native and Stripe. Relevant for another role. Totally off brief for their Java/Spring overhaul on a fifteen-year legacy.

If the pack had highlighted assignment #3 (migration of a banking monolith to microservices, team of twelve, production rollout over six months) the client would have started on the right ground. Same candidate, same STAR method, radically different interview outcome.

---

Building a pack that feeds STAR

The rule of three assignments

A pack that lists everything at the same level of detail forces the interviewer to prioritise themselves. In practice, they don’t: they start with whatever catches their eye.

Three well-chosen assignments beat an exhaustive three-page timeline. For each highlighted assignment:

The last row is the most neglected. Making the explicit link between past experience and the client’s current need is the salesperson’s or delivery manager’s job, not the interviewer’s who discovers the pack thirty minutes before.

Prioritise, don’t just summarise

Prioritising doesn’t mean cutting. The other assignments stay in the pack, but in short form, one line of context, stack, duration. The interviewer knows they exist. They can go back if they want. But they also know where to start.

That’s the difference between a pack that says “here’s everything, figure it out” and one that says “here’s what matters for your need, and here’s why”.

---

Classic pitfalls of an underprepared STAR

Pitfall #1: the candidate drives the interview

Without framing, the candidate naturally picks the experience that shows them in the best light. That’s human. But it isn’t necessarily the one that proves they’re the right profile for this specific assignment.

A senior developer can brilliantly recount how they rescued a drifting project, and omit that they’ve never worked on the kind of architecture the client uses. The story is good. Proof of fit is missing.

Pitfall #2: comparing incomparable stories

You present three candidates for the same role. The first does STAR on a cloud migration. The second on CI. The third on production crisis management.

Three interesting stories. No common basis for comparison. The client picks whoever tells the story best, not whoever fits best. To compare, all three need to be questioned on the same type of experience, with the same evaluation criteria.

Pitfall #3: confusing eloquence with competence

STAR favours candidates who can tell a story. That’s a strength. It isn’t the only one. A developer who handled a critical production incident at 3 a.m. but tells it in a flat way will score lower on “STAR” than a consultant who perfectly structures a narrative about a standard assignment.

The competency pack rebalances the scales: if the facts are laid out in black and white before the interview, the interviewer is no longer dependent on the candidate’s storytelling to assess how relevant their track record is.

Pitfall #4: STAR on repeat

Some interviewers apply STAR mechanically. Every question follows the same pattern. The candidate adapts and produces formulaic answers. The interview becomes predictable for both sides. You lose the ability to surprise, dig into an unexpected angle, or test reaction to the unexpected.

A solid pack upfront lets the interviewer move beyond pure STAR when it makes sense. They already know the facts. They can ask judgment questions, trade-offs, scenarios, without risking staying on the surface.

---

STAR in the ESN context

What’s specific about the model

In an ESN, interviews have a twist: the candidate is often introduced by someone else. The salesperson or delivery manager has set the stage. The client has read a pack. The candidate walks into a frame that’s already partly defined.

That changes things compared with classic hiring where the candidate applies directly. The pack isn’t a nice-to-have, it’s the first impression. And that first impression steers the whole interview.

Calibrating STAR questions to the client’s need

Instead of generic STAR questions (“Tell me about a difficult situation”), questions should be tuned to the client’s context:

The second column is only possible if the interviewer has a pack with facts. Otherwise they stay in the first column. And in the first column, every candidate sounds the same.

---

Structuring the scorecard

Why a scorecard is essential

Without a scorecard, post-interview evaluation rests on memory and impression. The client remembers that “the first candidate was good” and “the third seemed motivated”. That doesn’t hold up when you need to justify a choice to a project lead or a CTO.

A simple scorecard that works

You don’t need a twenty-column spreadsheet. Five criteria cover most ESN roles:

Each criterion is scored on a simple scale. A four-point scale forces a choice: no middle score to hide behind “average”.

The competency pack partially pre-fills the first two criteria. The STAR interview confirms or challenges what the pack states, and covers the last three.

---

Impact on the sales team

The junior problem

A senior salesperson instinctively knows which assignments to highlight and how to brief the client before the interview. A junior doesn’t. They send a complete but unprioritised pack. The client gets a dense document, doesn’t know where to start, and the interview drifts randomly.

Standardising the structure of the pack, not the content, narrows that gap. The junior follows the same frame as the senior: three highlighted assignments, explicit link to the need, orders of magnitude spelled out. Content varies by candidate. Preparation quality stays consistent.

The corridor summary

After the interview, the client doesn’t remember your methodology. They remember whether they can pitch the profile to their manager in two sentences. “We saw a lead who did exactly the same migration as us at [client], same stack, comparable scope. They hit the deadlines over six months with twelve people.”

That summary doesn’t come from nowhere. It comes from a pack that already laid out those points clearly, and an interview that confirmed them in STAR. If the pack doesn’t set that frame, the corridor summary becomes “they seemed fine, they know Java”. That doesn’t drive a decision.

Training through structure

The best training on structured interviews isn’t a PowerPoint on STAR. It’s a pack template that forces the right questions:

• Which assignment is most relevant for this client?
• Why that one and not another?
• Which specific aspect should the client probe in the interview?
• Which numbers or deliverables can the candidate cite?

When the salesperson fills that template, they do the prep work. And when the client receives the result, they know what to ask. Betterfolio bakes this logic into pack generation: dated assignments, stacks listed cleanly, named deliverables, so the factual base exists before the interview starts.

---

Checklist: preparing a STAR interview that actually helps

Before sending the pack

• Identify the 2–3 assignments closest to the client’s need
• For each: context, scope, actual role, quantified result
• Make the explicit link between each assignment and the current need
• Move the other assignments to short form (one line each)
• Reread the pack asking: “If I were the client, would I know what to ask in the interview?”

Before the interview

• Brief the client on which assignments to probe and why
• Prepare 3–4 STAR questions calibrated to the highlighted assignments
• Define evaluation criteria (simple scorecard, 4–5 criteria)
• Brief the candidate on what the client will likely dig into

After the interview

• Fill in the scorecard while it’s fresh (not the next day)
• Check that the summary passes the “two-sentence corridor test”
• Compare candidates on the same criteria, not on overall vibe
• Archive the scorecard so you can justify the choice if asked three weeks later

---

What to remember

STAR is a good tool. It isn’t sufficient on its own. The quality of a structured interview is decided before the interview, in how the competency pack is prepared.

A pack that prioritises assignments, ties them to the client’s need, and states verifiable facts turns STAR from a storytelling exercise into a validation tool. The candidate isn’t spinning a good yarn: they’re confirming facts the client already has in front of them.

For the sales team, that’s a direct lever: less time lost on off-brief interviews, reliable comparisons between candidates, and decisions that stand up when you have to justify them. All without changing the method, just preparing what comes before it better.