The NDIS Interview Question That Reveals Real Judgment

Welcome to the show -- Winter, if a candidate gives you a spotless CV, perfect references on paper, and then fumbles one question about a participant choosing something risky, I'm telling you now: that one answer matters more. The "risky choice" question? Exactly. "Tell me about a time a participant wanted to do something risky. What did you do, and what happened?" Because disability support is not just tasks and punctuality. It's rights, judgment, communication, and what someone does when autonomy and safety are tugging in different directions. And a polished CV won't tell you that. A CV can say "three years' experience, medication support, manual handling." It does NOT tell you whether that person can respect choice when they're under pressure... or whether they'll panic and take over. Yes. And in 2026, that gap matters even more because expectations around NDIS recruitment are sharper now. Auditors under the NDIS Practice Standards don't just want to know that you interviewed someone. They expect evidence your process was structured, values-based, and applied consistently. Wait -- "structured, values-based, and consistently applied" is the bit I think services underestimate. A lot of places still run interviews like a friendly coffee chat. "Tell us about yourself, why do you wanna work here, you seem lovely." Lovely is not a capability. No, it's not. And that friendly-chat style creates two problems at once. First, it gives you unreliable information. Second, it creates legal and compliance exposure because different candidates are being tested on different things -- or not tested at all. I'll push you a little, though. I don't think interviews are some magic crystal ball. I've seen people interview brilliantly and then, on shift, they're rigid, overwhelmed, or just... off. So can interviews really predict support worker success? On their own? No -- and that's the important correction. An interview alone is not a strong predictor of success. But a structured interview is still powerful because it tests judgment and values in a consistent way. Then you strengthen it with multiple assessment methods -- screening, behavioural assessment, maybe a practical demonstration, sometimes even a panel that includes a participant or family member where appropriate. Right, so the answer isn't "ditch interviews." It's "stop treating them like vibes." Use the interview as one piece of a proper selection process. That is EXACTLY it. And the risky-choice scenario is such a good example because it forces the candidate to reveal how they think. Do they talk only about stopping the participant? That's a red flag. Do they ignore the risk entirely and call it empowerment? Also a red flag. What you want is someone who can weigh autonomy and safety together -- person-centred support in real life, not in a slogan. Let me try to play that back. A strong answer would sound something like: "I listened first, understood why the participant wanted to do it, checked the actual risks, considered safeguards, explained options, documented concerns, and involved the right people without stripping the person's choice." Is that roughly the shape? Pretty close. And then I'd listen for what they actually DID. That's where STAR-style behavioural questions help -- Situation, Task, Action, Result. Not just, "I value choice." Tell me the situation. Tell me your role. Tell me the action you took. Tell me the result. Because support work is full of people saying the right values words. The interview has to get underneath the words. And STAR does one more thing, I reckon. It shows you how they communicate. If someone can't explain a real situation clearly -- calmly, logically, respectfully -- that's information. Support workers are constantly explaining, reassuring, checking in, documenting, handing over. Yes, and I wouldn't be shy about guiding candidates into that format either. Make them comfortable. Tell them what you're looking for where appropriate. You're not trying to trap them. You want the best chance of seeing their actual capability. Because the person who pays for a sloppy interview process is usually not the organisation. It's the participant who ends up supported by the wrong worker. And that's the standard to hold in your head the whole time. Not, "Did I enjoy the chat?" More like: "Would I trust this person to support someone I care about when something goes sideways?" So if we're building this properly, where do you start? Not with random questions. You start with the NDIS Workforce Capability Framework and pick, what, three to five capabilities that really matter for the role? Yep. Three to five is a good working number before you write a single question. And for support worker roles, the Framework's five broad objective areas are the backbone: upholding rights, engaging and motivating, delivering supports, managing safety, and checking in. I'm glad you said all five, because "managing safety" gets a lot of airtime, but "checking in" is one people forget. Monitoring outcomes, communicating with families, updating the team -- those little loops of communication are where quality often lives or dies. Good catch. And "upholding rights" isn't soft or optional either. That's participant autonomy, dignity, choice. If the role is supervisory -- team leader, coordinator -- then you'd add the extra supervisory capabilities as well. But for most frontline interviews, those five areas give you the map. Then you mix question types, yeah? Not just one style the whole way through. Exactly. Three types work especially well. Behavioural questions about actual past experience. Situational questions -- hypothetical but role-relevant. And organisational fit questions about values and working style in your context. Let's put some flesh on that. Behavioural is your "Tell me about a time..." stuff. So: "Tell me about a time you suspected abuse or neglect. What did you do?" And if the answer never gets to mandatory reporting obligations, the NDIS Code of Conduct, or reporting protocol... that's not a small gap. No, it's a significant one. Mandatory reporting is essential. An exceptional answer should show the candidate understands both the ethical duty and the process -- not gossiping, not hesitating, not trying to privately solve something that requires formal action. And privacy is another big one. Ask, "How do you handle confidential participant information?" If they blur the line between what's appropriate to share and what must remain private, you've just learned something very important before they ever touch a roster. Right -- privacy and confidentiality questions reveal awareness of the Privacy Act and the Code of Conduct, but also trustworthiness. You are testing whether they can protect participants, families, and your organisation from avoidable breaches. Then situational questions help newer candidates, which I really like. Someone coming from aged care, hospitality, youth work -- maybe they don't have years of direct disability experience, but they can still show transferable judgment. Give them a scenario and ask what they'd do. Yes, and that's one reason multiple assessment methods matter. Structured interviews shouldn't just reward the person who's had the exact same title before. The Framework lets you assess attitudes, skills, and knowledge -- empathy, communication, personal accountability -- not just qualifications. And organisational fit isn't fluff either. "What does meaningful support work look like to you?" or "What kind of team environment do you work best in?" Those answers can tell you whether they'll thrive with your participant cohort, your pace, your expectations. Absolutely. Someone might be capable in a broad sense and still be wrong for your setting. That's not failure, that's alignment. Same reason you should ask about stress and resilience. Support work can be emotionally and physically demanding. How do they self-regulate? How do they maintain boundaries? What do they do under pressure without burning out or disengaging? "Stress and resilience" is one of those phrases that can go vague really quickly. I'd want specifics. Not "I'm resilient." Tell me about a high-pressure shift. What were the warning signs for you? What supports did you use? What did you learn? That's a strong follow-up. And once you've asked the questions, here's where a lot of services still slip: scoring. Before the interview starts, prepare what a basic, competent, and exemplary answer looks like for each question. Then score each candidate immediately after the interview -- not three days later when memory has blurred and confidence has replaced evidence. That "basic, competent, exemplary" scale is gold because it stops the post-interview debrief from becoming, "I just had a good feeling about him." A good feeling is not defendable. A scored answer against a capability is. And document it. Brief notes, scores, rationale. That documentation is part of your audit evidence trail under the Human Resources Management requirements in the NDIS Practice Standards. It also protects you if a hiring decision is challenged under the Fair Work Act. Plus it makes your actual decision better. You can compare candidates on the same core questions, the same criteria, the same standard. Less unconscious bias, quicker decision-making, cleaner reasoning. And where appropriate, consider bringing participants into the process -- maybe a panel format, maybe part of a two-stage interview, maybe a practical demonstration. Because the most direct evidence of future support isn't always in the answer itself. Sometimes it's in how the candidate listens, adapts, and speaks to the person in front of them. Yeah... if someone can't make a participant feel heard in the interview room, it's hard to imagine that improving at 7:15 on a rushed Tuesday shift. Which is why the question after every interview probably isn't, "Did they impress us?" It's, "Did we actually see enough evidence to trust them?"