Behavioural¶
Senior roles weigh this heavily: ownership, judgement, influence, mentoring.
STAR, done well¶
| Part | Share | Tip |
|---|---|---|
| Situation | 10% | One or two sentences of context. No company history |
| Task | 10% | What you had to achieve, and the constraint (deadline, risk) |
| Action | 60% | What I did, step by step, and why. Say "I", not "we" |
| Result | 20% | A number or concrete outcome, plus what you learned |
Keep each story to about 2 minutes. Expect follow-ups: "What would you do differently?", "What did your manager think?", "What was the hardest part?"
The common questions, mapped to stories¶
| Question | Story from the bank |
|---|---|
| Tell me about a challenging project | Schema redesign, or blue/green migration |
| A time you failed / made a mistake | Prayog rule change rewrote history; or a work incident Fill in |
| Production incident you handled | Work incident Fill in; Prayog GC tail |
| Disagreement with a colleague or manager | Fill in (e.g. a design choice in code review) |
| Pushing back on a product owner | Scope vs. deadline Fill in |
| Tight deadline | ALT/SMA or white-labeling on a tight timeline |
| Leading without authority | AWS AI League, DeepRacer 2024 |
| Mentoring | Juniors at Portfolio Insights; reusable AI skills |
| Learning something new fast | Prayog's exchange internals; Galois maths; Index Research domain on joining |
| Improving a process | Java modernisation; BDD PoC; automating operations BAU tasks |
| Going beyond your role | DeepRacer reward visualiser; AI League |
| Ambiguous requirements | Fund suitability: turning "is this fund suitable?" into correlation |
Prepare 5 stories well; each can answer several questions.