Part 7 · 1 chapters · ~10 min
The Story Bank
Eight behavioural stories drawn from manager-written reviews and recent project documents, each told as situation, action, result and what changed, mapped to the questions the SAATHI and CEO rounds ask, with one story written out in full and the rule against inventing numbers.
10
Eight stories, one shape
Behavioural rounds reward specific, honest stories that are consistent from one answer to the next. The source used here is personal/about-me/team-impacts/reviews.md: what your managers wrote, quarter by quarter. Tell each story in the same shape, and close it with what changed in you.
| story | source | answers |
|---|---|---|
| liveness verification POC and Node services, volunteered | Q2 2024 review, 6.0 | ownership, learning, initiative |
| session-timeout redirect preserving context for field agents | Q1 2025 review | user empathy, finding problems |
| code reviews across five teams; GDPR across public platforms | Q1 2025 review | influence, raising the bar |
| over-engineering named as a growth area; simpler first versions since | Q3 2024 review | weakness, acting on feedback |
| Account Overdraft Loans MVP, fast iteration after demos | Q4 2023 review | shipping, product partnership |
| loan agreement flow with guarantor status; manual overdraft repayment | Q1 2025 review | money flows, reducing drop-off and support load |
| complex implementations passing QA without bugs | Q3 2024 review | quality, testing discipline |
| Letter of Non-Indebtedness: 249 manual issues a month, agentic spec pipeline | 2026 project docs | outcomes, AI-native delivery |
code
STORY: the session-timeout redirect (≈ 90 seconds)
situation Field agents verifying businesses kept losing their task when the session timed out:
they logged back in at the home screen and had to find the task again.
action I traced the logout flow, preserved the intended route through re-authentication,
and added direct task links from the front-office app so agents could jump straight in.
result The navigation complaints stopped; my manager called out reduced frustration
and better field efficiency in the Q1 2025 review.
changed I now treat "what happens when the session ends mid-task" as part of every flow's
design, the same way I treat a payment timeout: a designed state, not an error.fill the gaps honestly
Some reviews give qualitative results with no numbers. Never invent a number. Use the manager's words instead ("reduced drop-offs and support inquiries"), and say what you would measure now. Interviewers trust a plain, true answer over a polished, inflated one.
THE STORY BANK
eight stories from manager-written reviews, each told in the same shape, each mapped to what the behavioural round probes
swipe the figure sideways, or tap expand for full screen
1/6
the shape
The shape: situation (one sentence of context), your action (what you did, with "I" for your part), the result (observable, ideally measured), and what changed (what you do differently now). The last beat is what separates a staff answer from a mid-level one: it shows you learn from your own work.