Behavioural Interviews Module 7 – Expectations by level and role
Behavioural answers early in your career
Find behavioural stories in projects, internships, clubs and part-time work, state your own part in group work, and answer HR-round questions with evidence.
What you will learn
- Find strong stories in projects, internships, clubs, volunteering and part-time work
- Scale a story honestly, so that small scope still shows a clear behaviour
- State your own part in a group project, with the size of the team
- Answer common campus HR-round questions with evidence and without promises you cannot keep
Before you start
What you’ll learn · Before you start
What you will learn
- Find strong stories in projects, internships, clubs, volunteering and part-time work
- Scale a story honestly, so that small scope still shows a clear behaviour
- State your own part in a group project, with the size of the team
- Answer common campus HR-round questions with evidence and without promises you cannot keep
Before you start
On this page
Atlassian tells intern and graduate candidates to expect 3 to 4 interviews, and its leadership and values rounds both use behavioural and situational questions. A final-year student with no full-time job still needs a true story for each of those questions, and most have more material than they think.
Early in a career nobody expects large scope. Interviewers listen for behaviours at your level: noticing a problem and acting on it, learning quickly, handling a disagreement, owning a mistake. Below, Meera, an invented final-year student, builds six such stories from five places, tells each at its real size, makes her part in group work clear and prepares for an HR round: An interview round run by a recruiter or someone from HR rather than an engineer, about your motivation, how you communicate and whether the job's conditions, such as its location and shifts, suit you..
Not affiliated
Based on public information about Atlassian, Amazon, Google, Microsoft and Dropbox. MySmartCoPilot is not affiliated with Atlassian, Amazon, Google, Microsoft and Dropbox, and Atlassian, Amazon, Google, Microsoft and Dropbox’s real hiring practices may differ from what this lesson describes.
Stories from study, clubs and part-time work count
Employers that publish their hiring advice say so directly. The UK Civil Service’s guide for candidates lists volunteering and hobbies beside work experience as places an example can come from. Amazon’s guide to its interview loop, explaining the situation of a story, asks where you were “working (or studying or volunteering)”. Google’s résumé tips ask recent graduates to “include school-related projects or coursework that demonstrate relevant skills and knowledge”.
What counts is one real occasion with you acting in it. Step through Meera’s notes:
The drawing shows the whole scene; its 7 steps are listed below.
Every step as text
- Five places, no job. Meera, a final-year computer science student, has never held a full-time job. Her notes list five places where she acted: her final-year project, a summer internship, a volunteering camp, a tutoring job and a hackathon.
- The project, twice. The final-year project gives two stories. In a team of four she built the module that syncs the phone app's attendance marks to the college sheet, and she argued, against the plan, for testing with a real class list.
- The internship. In an eight-week internship she learned enough SQL to trace a report that failed twice a week to a time-zone bug, and fixed it with her mentor's review: a story about learning, with a result she can check.
- The camp. At a health camp of her college's NSS unit, the registration queue took about 40 minutes. On the second morning she split it into two desks, one for each village, and the wait fell to about 15: initiative.
- The tutoring job. She marked 23 practice papers with an answer key she had not checked. It had two wrong answers. She told the centre head the same day and re-marked every paper: a mistake owned, and its repair.
- The hackathon. Her coding club's hackathon: a team of three, first prize out of 28 teams, and her own part, the offline cache that kept their bus-timing app working without a signal. The prize was the team's; the cache was hers.
- The bank, covered. Six stories from five places cover the five behaviours she wants to show: initiative, learning, a disagreement, a mistake owned and teamwork. Not one of them needed a job title.
Five places gave her six stories, and they cover the five behaviours she wants to show. A habit (“I always help my friends”) is not a story, and neither is a group’s achievement without her part in it.
An NSS camp is a real occasion
The National Service Scheme is the Ministry of Youth Affairs and Sports’ community-service scheme for students in India. A camp you helped run is as fair a source as a job: say what you organised or changed there.
Checkpoint
Check: Where early-career stories come from
A small story can still show a clear behaviour
Entry-level scope is small by design. Dropbox’s public career framework describes its first engineering level as executing on defined tasks and delivering code “with direction from the team”, while asking questions to clarify expectations and owning decisions and mistakes. An interviewer hiring at that level listens for those behaviours, not for a large result.
So keep each story at its real size and make the behaviour exact: what you noticed, what you did, what changed. Here are three of Meera’s occasions beside the inflated tellings she was tempted to give:
| Behaviour | What really happened | The inflated telling |
|---|---|---|
| Initiative | Split one camp registration queue into two desks; the wait fell from about 40 minutes to 15 | “Transformed the camp’s operations” |
| Learning | Learned enough SQL in an internship to fix a report that failed twice a week | “Became the team’s database expert” |
| A mistake owned | Told the centre head about her unchecked answer key the same day and re-marked 23 papers | “Ensured quality at a tutoring centre” |
The true versions are smaller and stronger: each names an action an interviewer can probe, and each survives the next question. An inflated telling invites a probe the story cannot answer.
Key idea
Tell a small story at its real size: the behaviour, told exactly, is the evidence, and a scope you cannot defend under a probe is a risk.
Checkpoint
Check: A small story at its real size
Say how many of you there were and which part was yours
Most student work is group work, and an interviewer cannot score “we”. Amazon’s guide asks candidates to “focus on your individual contributions—even if you were working on a team”. One sentence settles it: the team size, then your part. Meera’s version: “Four of us built an attendance app; I built the module that syncs the phone’s marks to the college sheet and ran the user test with two classes.”
The program checks a mini story bank: Your written set of prepared interview stories, usually eight to twelve, each kept as a card of notes and marked with the competencies it shows, so that every competency you target has a story ready. More in “Building and maintaining a story bank” against three MySmartCoPilot rules: at least three
sources, a team size and your own part for every group story, and a result for every story. It runs on Meera’s draft,
then on her revision. Press Edit, put your own stories in REVISED, and run it again:
// A six-story mini bank for an early-career candidate, checked twice: Meera's first draft, then her revision.
// Meera, her stories and every number are invented. Put your own stories in REVISED and run it again.
// The behaviours Meera wants her bank to show (a MySmartCoPilot list for entry-level roles).
const BEHAVIOURS = ['initiative', 'learning', 'disagreement', 'mistake', 'teamwork'];
// Each story: a title, where it happened, whether it was group work and the size of the group, your own part,
// the result, and the behaviours it shows.
const DRAFT = [
{
title: 'Attendance sync', source: 'final-year project', group: true, team: 4,
part: "I built the module that syncs the phone app's marks to the college sheet and ran the user test with two classes.",
result: 'Two classes used it for three weeks; taking attendance fell from about 6 minutes a lecture to under 2.',
shows: ['teamwork'],
},
{
title: 'Real test data', source: 'final-year project', group: true, team: 4,
part: 'I argued that we should test with a real class list instead of made-up names, and ran that test myself.',
result: 'The test found 11 duplicate roll numbers a week before the demo.',
shows: ['disagreement'],
},
{
title: 'Failing report fixed', source: 'internship', group: false, team: null,
part: "I learned enough SQL to trace a report that failed twice a week to a time-zone bug, and fixed it with my mentor's review.",
result: 'The report did not fail again in the last four weeks of my internship.',
shows: ['learning'],
},
{
title: 'Two registration desks', source: 'NSS camp', group: true, team: 12,
part: 'I split the single registration queue into two desks, one for each village, on the second morning.',
result: '',
shows: ['initiative'],
},
{
title: 'Unchecked answer key', source: 'tutoring job', group: false, team: null,
part: 'I marked 23 practice papers with an answer key I had not checked, then told the centre head the same day and re-marked them.',
result: 'All 23 students had corrected marks before their results went home.',
shows: ['mistake'],
},
{
title: 'Hackathon cache', source: 'coding club', group: true, team: null,
part: '',
result: 'We won the college hackathon.',
shows: ['teamwork', 'learning'],
},
];
// The revision changes only the two stories the draft check flags, with facts Meera already had.
const REVISED = DRAFT.map((s) => {
if (s.title === 'Two registration desks') {
return { ...s, result: 'The wait at registration fell from about 40 minutes on the first day to about 15 on the second.' };
}
if (s.title === 'Hackathon cache') {
return {
...s, team: 3,
part: 'I wrote the offline cache that kept our bus-timing app working without a signal, and gave the demo.',
result: 'Our team of three won first prize out of 28 teams.',
};
}
return s;
});
// MySmartCoPilot recommendations: at least three different sources; a team size and your own part, in the first
// person, for every group story; a result for every story, with a number or a change someone could see.
const MIN_SOURCES = 3;
const NUMBER = /\d|\b(?:one|two|three|four|five|six|seven|eight|nine|ten|half|twice|first|second)\b/i;
const VISIBLE = /\b(?:stopped|started|adopted|replaced|fixed|no longer|switched to|won)\b/i;
function check(name, stories) {
console.log(name);
const width = Math.max(...stories.map((s) => s.title.length)) + 2;
let toFix = 0;
stories.forEach((s, i) => {
const notes = [];
if (s.group && !s.team) notes.push('group story without a team size');
if (!s.part) notes.push(s.group ? 'group story without your part' : 'no part of your own');
else if (!/\bI\b/.test(s.part)) notes.push('your part is not in the first person');
if (!s.result) notes.push('no result');
else if (!NUMBER.test(s.result) && !VISIBLE.test(s.result)) notes.push('result has no number or visible change');
if (notes.length) toFix++;
console.log(`${String(i + 1).padStart(3)} ${s.title.padEnd(width)}${notes.length ? notes.join('; ') : 'ok'}`);
});
const sources = [...new Set(stories.map((s) => s.source))];
const shown = BEHAVIOURS.filter((b) => stories.some((s) => s.shows.includes(b)));
const missing = BEHAVIOURS.filter((b) => !shown.includes(b));
console.log(` sources: ${sources.length} (${sources.join(', ')}): ${sources.length >= MIN_SOURCES ? 'ok' : `not yet, at least ${MIN_SOURCES}`}`);
console.log(` behaviours shown: ${shown.length} of ${BEHAVIOURS.length}${missing.length ? ` (missing: ${missing.join(', ')})` : ''}`);
console.log(` ${toFix ? `${toFix} ${toFix === 1 ? 'story' : 'stories'} to fix` : 'every story ready'}`);
console.log('');
}
check('Draft', DRAFT);
check('Revised', REVISED);Output
Draft 1 Attendance sync ok 2 Real test data ok 3 Failing report fixed ok 4 Two registration desks no result 5 Unchecked answer key ok 6 Hackathon cache group story without a team size; group story without your part sources: 5 (final-year project, internship, NSS camp, tutoring job, coding club): ok behaviours shown: 5 of 5 2 stories to fix Revised 1 Attendance sync ok 2 Real test data ok 3 Failing report fixed ok 4 Two registration desks ok 5 Unchecked answer key ok 6 Hackathon cache ok sources: 5 (final-year project, internship, NSS camp, tutoring job, coding club): ok behaviours shown: 5 of 5 every story ready
Recorded with Node.js 24.21.0 on macOS 26 arm64. To run it yourself: mise exec node@24.21.0 -- node mini_bank.mjs
Runs on this device, in your browser. The first run downloads JavaScript (about 0.6 MB), which is kept for the next runs.
Your run, in this browser
The draft fails twice: the hackathon story says “We won” with no team size and no part of hers, and the camp story has no result. The revision fixes both with facts she already had.
Checkpoint
Check: Your part in group work
A campus HR round, answered with evidence Pro: opens with a Pro, Premium or Ultimate pass
An HR round asks a short list of questions about you, your plans and the job’s conditions, and each one can be answered with evidence instead of a slogan. Here is an original mock round of six questions, a weak and a strong answer to each scored on one rubric, and the answers to give about moving, shifts and further study.
In this part:
- What a campus HR round asks, and what each question is for
- Six answers, weak and strong, scored on one rubric
- Moving, shifts and further study: answers you can keep
1 runnable example (JavaScript) · about 5 minutes
Opening this part with your pass…
This part opens with any MySmartCoPilot pass.
- Pro pass · 1 week₹79$2.99
- 30 days₹179$5.99
- 1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so this part can’t be opened at the moment. The free part above stands on its own. If you have a pass, enter your licence key.
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
Growing a small story without stretching it Pro: opens with a Pro, Premium or Ultimate pass
Early-career answers often lose marks by borrowing scope: the team’s prize told as yours, a strength recited from a website, coordinating called leading. This part rewrites four such answers, runs a check that catches the patterns, and shows how a small story gains depth without gaining size.
In this part:
- Four stretched answers, rewritten with the facts
- A check that flags borrowed scope, run on the four answers
- Adding depth to a small story without adding size
1 runnable example (JavaScript) · about 4 minutes
Opening this part with your pass…Pro part. It opens with the same pass as the part above.
Practise: build your mini bank
Write six stories from at least three sources, give every group story its team size and your part, and run the program on them until no story is left to fix. Then answer the questions below:
Online Notepad Keep your mini bank as a note in this browser: the place, your part and the result of each story.Practice that adapts to you
Practise this lesson
7 questions about 5 ideas of this lesson. Each answer is explained at once, and what you get right is kept in this browser.
Interview questions
The warm-up is answered here. Answer the other three aloud, with your own stories, before you read their first steps.
-
Fresher · Warm-up
What does an interviewer look for in a behavioural answer from someone at the start of their career?
Behaviours rather than scope: noticing a problem and acting on it, learning quickly, handling a disagreement, owning a mistake and working in a team. The stories can come from study, internships, clubs, volunteering or part-time work, as long as each is one real occasion with you acting in it. Tell each at its real size. Dropbox's public career framework describes its first engineering level as delivering code with direction from the team, so nobody expects you to have led a large project. In group work, give the size of the team and then your own part in the first person, and end with a result, even a small one, such as a queue that fell from about 40 minutes to 15. A small story told exactly, which survives the next question, beats a large one told vaguely.
-
Fresher
You have not worked full time yet. Tell me about a time you did more than you were asked to.
-
Fresher
This role may mean moving to another city and working rotating shifts in your first year. How do you feel about that?
-
Fresher
Most people we hire have a few years of experience. What evidence can you give that you will do well here without it?
Key takeaways
- Employers accept stories from study, internships, clubs, volunteering and part-time work, provided each is one real occasion with you acting in it.
- Entry-level scope is small by design, so tell each story at its real size and make the behaviour exact.
- One sentence makes your part in group work clear: the size of the team, then what you did yourself.
- A mini bank of six stories from at least three sources, each with a result, covers the behaviours an entry-level interviewer listens for.
Terms in this lesson
- HR round
- An interview round run by a recruiter or someone from HR rather than an engineer, about your motivation, how you communicate and whether the job's conditions, such as its location and shifts, suit you.
References
- Early careers interview guide (Atlassian)
- Success Profiles: candidate overview (UK Cabinet Office (GOV.UK))
- The interview loop (Amazon.jobs)
- How we hire: build your resume (Google Careers)
- Student interviewing tips (Microsoft Careers)
- IC1 Software Engineer (Dropbox Engineering Career Framework, Apache-2.0) (Dropbox)
- National Service Scheme (Ministry of Youth Affairs and Sports, Government of India)
Related tools
Report a problem with this lesson
Kept only in this browser. Your Learn progress