CodeCV IAM Career Prep · Phase 2
Support Training · Phase 2

The competency (STAR) interview — build your stories

In Ireland, the behavioural / competency round is where most technically-strong candidates lose. This phase is not about memorising answers — there are no answers here on purpose. It's about you building your own real stories, with guidance on how to shape each one. You draft; then we refine them together in our weekly session so you can deliver them naturally.

How to use this. For each question, read the "How to approach this" box, then draft your own answer in STAR shape in the box below it. Use real situations — mostly from your IT-support and identity work. When you've drafted a few, click Send drafts to your coach at the bottom. Don't aim for perfect — aim for real. We polish together.

The STAR method — a quick recap

Every behavioural answer follows four beats. Keep each tight — the whole answer is about 90 seconds.

SSituation — set the scene TTask — your responsibility AAction — what YOU did RResult — the outcome
The two rules that win this round: (1) In Action, say "I", not "we" — they score your contribution. (2) Always finish with a Result, ideally measurable ("cut reset tickets by ~30%", "zero access errors after the change").

Core competency questions

These come up in almost every Irish interview, in any role. Draft one story each.

1 Tell me about a time you worked in a team to achieve a goal.

How to approach thisThey test collaboration and your specific role — not the team's. Pick a real example (an IT-support project, your HDip group work). In the Action, use "I": state exactly what you personally did. Finish with a measurable result. Avoid a story where you were a lone hero, or where you can't point to your own contribution.

2 Describe a time you handled a difficult situation under pressure.

How to approach thisThey test composure and decision-making. An outage or an urgent access issue works well. Emphasise how you prioritised and stayed calm — show a process, not panic. Result: what you restored or protected. Avoid over-dramatising or blaming others.

3 Give an example of when your attention to detail made a difference.

How to approach thisIn identity, one wrong permission can be a breach — so this competency matters more for you than for most roles. Use a real case where you caught or prevented an error (an account, a permission, a config). Show the specific check you ran. Make this one strong.

4 Tell me about a time you explained something technical to a non-technical person.

How to approach thisIAM analysts talk to end users and managers constantly. Pick explaining MFA, a password policy, or why access was denied. Show empathy and a simple analogy. Result: they understood or complied. Don't use jargon while telling the story — that undercuts the point.

5 Describe a time you took ownership of a problem no one else did.

How to approach thisTests initiative. A recurring ticket you fixed at the root, or a small process you improved. Show you went beyond your remit. Quantify the impact (fewer tickets, time saved).

6 Tell me about a time you disagreed with a colleague or manager.

How to approach thisThey test professionalism and communication — not that you "won". Show you listened, used facts, stayed respectful, and reached a resolution. In IAM this is often pushing back on an over-broad access request. Avoid making the other person look bad, or "I just did what I was told".

7 Give an example of learning a new skill or technology quickly.

How to approach thisThis is your question — the HDip, self-study, labs and certifications are the story. Show your method for learning and the concrete result (a cert, a working lab). This reframes your career change as a strength, not a gap.

8 Tell me about a mistake you made and what you learned.

How to approach thisTests self-awareness and accountability. Pick a real, low-stakes mistake, own it with no excuses, and spend most of the answer on the fix and the lesson (ideally a process change). Avoid a fake "I work too hard" answer, or blaming others.

IAM-specific behavioural questions

These blend behaviour with the security mindset interviewers want in identity roles.

9 Tell me about a time you handled sensitive or confidential information.

How to approach thisDirectly tests security mindset. Use AD account or user-data handling from IT support. Show you followed least privilege and process, and name the principle (confidentiality, need-to-know).

10 Describe a time you had to follow a strict process or procedure.

How to approach thisIAM runs on process discipline (joiner-mover-leaver, access approvals). Show you value the why behind the process — audit, compliance, security — not that you follow rules blindly.

11 Tell me about a time you spotted a security or access risk.

How to approach thisShows proactivity and a defender's eye. An over-privileged account, a stale/orphaned account, a shared password. Show you spotted it and what you did or recommended.

Motivation questions (not STAR, but always asked)

12 Why are you moving into cybersecurity / IAM, and why Ireland?

How to approach thisBe concise and genuine: your IT/identity background → the HDip → the Irish IAM market. Mention your Stamp 1G as readiness ("I can start immediately"). Avoid "for the money" or a vague "I like security" — connect it to what you've actually done.

Build your story bank

You don't need a different story for every question. Aim for 6–8 strong stories that you can flex to answer many questions. Map them like this:

One strong story about……can answer
Fixing a recurring issue at the rootOwnership, initiative, attention to detail
An urgent outage / access incidentPressure, decision-making, teamwork
Onboarding/offboarding a user correctlyProcess discipline, sensitive info, detail
Learning for the HDip / a cert / a labFast learning, motivation, resilience
Explaining MFA / a policy to a userCommunication, empathy, stakeholder handling
Pushing back on a bad access requestDisagreement, security mindset, judgement
Your goal this week: draft at least 5 of the questions above. They don't need to be polished — we sharpen the wording, the "I", and the results together in the weekly review.

Your work saves automatically

Everything you type here is saved to your training space as you go — there's no submit button. Your coach reviews your drafts before the weekly session, and you can return any time to continue where you left off. Make sure your name is correct in the bar at the top.

CodeCV · IAM Career Prep · Phase 2 — The Competency (STAR) Interview · Market: Ireland