Your Experience Inventory and Story Bank, Without an Internship

The interviewer says, "Tell me about a time you disagreed with a teammate." You have never had a teammate in a job. Your mind goes blank, and you produce something generic: "We had some differences, but we discussed and resolved them." The interviewer writes "no clear example" and moves on.

You did have teammates, of course: in your final-year project, a hackathon, a college fest, a cricket team, a group assignment where one person did nothing. Behavioral questions are about behaviour, and you have been behaving in groups, under pressure and with responsibility for years. The material exists. What is missing is a habit of collecting it before the interview.

• What behavioral questions actually test.
• Where a fresher's raw material comes from.
• How to build an experience inventory and sort it with AI.
• The ten story types that cover most questions, and how one story can answer several.

Interviewers ask about the past because it is the best available evidence of how you will act in the future. A behavioral question tests one or more competencies:

None of these require a job. They require a situation where the competency showed.

Go through each source and write down everything, even if it seems small. Small, specific stories often work better than grand, vague ones.

Write one line per experience, without filtering. Aim for 20 to 40 lines. For example:

- Final-year project: teammate stopped responding in week 6; I took over his module.- Hackathon: we changed our idea 10 hours in after mentors said it already existed.- College fest: managed 15 volunteers for registrations; the payment link failed on day one.- Taught my younger cousin Class 10 maths online for six months.- My expense-tracker project: rewrote the backend after realising I'd stored money as floats.- Open-source PR: maintainer asked for changes three times; merged on the fourth.- Failed the first DSA assessment I took; made a 6-week plan; cleared the next two.- Worked weekends at my uncle's shop during COVID; set up a simple stock spreadsheet.

An assistant is good at seeing which competencies an experience could show and which ones have the most story potential. Give it your raw list and tell it not to add details.

Below is my raw list of experiences from college and life. I'm a fresher with nointernship, preparing for behavioral interviews.For each line:1. Which competencies could it demonstrate? Choose from: ownership, problem-solving,   collaboration, conflict, failure and learning, ambiguity, pressure and   prioritisation, leadership without authority, communication, learning quickly,   user focus, receiving feedback.2. Story potential: strong, possible (needs more detail), or weak. Say why.3. One question I should answer to make it stronger.Then list my top 10 story candidates, making sure they cover as many competenciesas possible, and name any competency none of my experiences covers.Do not add any details to my experiences; ask questions instead.[paste inventory]

An illustrative extract:

Example response (illustrative)"Teammate stopped responding in week 6; I took over his module"- Competencies: ownership, collaboration, conflict, pressure.- Potential: strong, if you can describe what you did before taking over  (did you talk to him? tell the guide?) and the result.- Question: What exactly did you do in the first 48 hours after you noticed?Gap: no clear example of "user focus".

How to check: confirm the assistant did not invent anything ("you led a team of five" when you wrote "managed volunteers" is an invention). For any gap it names, go back to your sources; you may have forgotten an experience. If you truly have none, that is fine; one strong story can often stretch to cover it.

Aim for one story of each type. Some of your experiences will fill two.

1. The project that went wrong, and what you did to rescue it.
2. Initiative: something you did without being asked.
3. The difficult teammate: someone not contributing, or hard to work with.
4. The technical challenge: a hard bug or design problem, and how you reasoned through it.
5. The failure: something that did not work, owned honestly, and what changed afterwards.
6. Learning fast: a new technology or skill under time pressure.
7. Explaining: making something technical clear to someone who was not.
8. The deadline: delivering under pressure by making a trade-off.
9. Feedback: hard criticism you received and acted on.
10. The judgement call: a decision with incomplete information that you owned.

A strong story can answer different questions depending on what you emphasise. Take the final-year project where a teammate stopped responding:

So ten stories, each with three or four angles, give you answers for most behavioral questions. Note the angles next to each story in your notes.

Prefer stories that:

• are specific: you can name the week, the problem, the number of people, the error message;
• show your actions, not only the team's ("I", not just "we");
• have a result, even a modest or mixed one, and something you learned;
• are recent, from the last two or three years where possible;
• are true in every detail, because the follow-up questions (article 36) will test them.

Avoid stories that make someone else look foolish, involve very personal matters you would not want discussed, or that you cannot remember clearly.

Nandini, a 2026 B.Sc. graduate, believes she has "nothing to talk about". Her inventory has 26 lines after an evening of looking through photos and chats. The AI sorting marks 9 as strong and 8 as possible, and finds no "user focus" story.

Going back to her sources, she remembers changing the colour scheme and font size of an attendance app she built for her department after two older faculty members said they could not read it on their phones. That becomes her user-focus story.

Her final bank: ten stories from her group project, a coding club she ran, a failed scholarship application, tutoring, an open-source fix and a summer at her family's medical store. Not one is from a job, and each can answer three or four questions.

• Waiting for the question to think of a story. Build the bank before interviews.
• Dismissing college experiences as "not real". Interviewers of freshers expect them.
• Choosing grand but vague stories over small, specific ones.
• Letting AI add details to make a story sound bigger.
• Only "we" and never "I". Interviewers need to know what you did.
• Very personal stories you are not comfortable being questioned about.

• Next: STAR Stories With AI as Interrogator, Not Author shapes each story into an answer you can defend.
• For common HR questions, see Common HR Interview Questions and How to Answer Them (With Examples).
• For interview practice with AI, see Interview Preparation and Mock Interviews with AI.