A mind map for job interview prep

What the interviewer is actually testing

An interview is a prediction problem, and the person across the table is making one about you. Most preparation is a list of skills you have. The useful map holds what the role needs on one side and the evidence from your own history on the other, so you can see which claim about yourself is still unsupported.

Put the role title in the root node, then add one branch for each of the four or five things the person would be hired to do. The posting is a list of nouns and the branches should be verbs. If a requirement in the ad has no branch, that is the part of the interview that gets probed.

A second side of the same map holds your material: three stories, each a child of a branch such as "evidence I can offer". Tab adds a child and Shift+Tab takes you back to the parent, while Enter or F2 renames the node you are standing on. The keyboard shortcut cheat sheet lists the rest.

• One branch per job the person would do
• A requirement with no branch is a rehearsal gap
• Every claim needs a piece of your history
• Keep the root short enough to read

Research the role and the company

Research exists to make the branches specific. The job title is generic, and the actual job is one team, one product and one problem this quarter. Add branches for what the team is shipping, what broke last month, who the first hire sits next to, and how many interview rounds there are. Each one turns a rehearsed answer into a specific one.

Keep the research in the rich notes of the node rather than in the label. A rich note is a small editor that opens in a modal, with bold, italic, underline, bulleted and numbered lists and a button to add a link. Type the facts, paste a line from the posting, or use Dictate, which turns what you say into text inside the note while the call is fresh.

• One branch per research area, with the raw material in the note
• Record what the interviewer said, in their words
• Dictate is fastest straight after the recruiter call
• Keep labels to ideas so the map stays scannable

Note: Dictate uses the browser's own speech recognition, so it needs a working microphone and a browser that supports it. If nothing appears when you dictate, type the note instead.

Mine your history for three stories

Three stories is the right number: enough that each requirement has one, few enough that you can rehearse them. Write each story as a child of a branch called "evidence I can offer", and inside it put the three beats every good answer needs, which are the situation, the specific thing you did, and the result. A story without a result is an anecdote, and an interviewer cannot score an anecdote.

A story also has to be sayable in two minutes, which means the detail has to be chosen. "I led the migration" is a title. "I ran the migration of forty accounts across three teams and cut the failure rate from six percent to under one" is a claim with a shape. Put the long version in the note and let the label carry the sentence you would say. If you also rehearse for pitches, the client presentation map uses the same shape.

• Three stories, each with situation, action and result
• Every story must be sayable in under two minutes
• One story should be about a problem you did not cause
• A story with no result is an anecdote

Note: None of the thirteen starter templates is an interview map, and that is not a gap worth fixing. A blank map with the role title in the root keeps the structure yours, because your history is too specific for a template.

Turn one story into a two-minute answer

Put the beats on the map as children of the story node. Presentation mode shows a first-level branch with its immediate children, so the beats belong one level down rather than buried three levels in. Name each beat as a verb phrase such as "set the cutover date" or "argued for a staged rollout". Verbs tell you what to say next.

Now draw the cross-link that makes the map a rehearsal rig instead of a biography. Link each story node to the requirement branch it proves. The link appears as a tube between the two nodes, and there is no label editor for it, so record the pairing in the note of the story, for example "proves requirement two, delivery under pressure".

A map gives you up to 2,000 nodes and 4,000 cross-links, far more room than three stories need. The real constraint is attention: a story with nine sub-branches is harder to deliver than a story with three beats, because you have to choose at the moment you are speaking.

1. Draft the beats as child nodes. Under each story, add one child per beat in order, labeled as a verb phrase you would say aloud.
2. Write the evidence in the note. Put the details, the numbers and the names you do not want to forget into a bulleted list on the story node.
3. Link the story to the requirement. Draw a cross-link from the story to the branch it proves, and note in one line why the pair belongs together.
4. Time the spoken version. Say the answer against a timer and trim the note until it lands under two minutes without losing the result.

Note: Cross-links show as tubes between nodes and cannot be labeled in the app, so the note on the node is where the pairing is actually written down.

Rehearse branch by branch in presentation mode

Press P and the map becomes a deck. Slide one shows the root label, and every slide after that shows one first-level branch together with its immediate children. If the branches are your three stories, you get a root slide and three story slides, and each story slide lists the beats in the order you will say them. ArrowRight and Space move forward, ArrowLeft goes back, and Esc leaves.

Rehearse out loud, one branch at a time, and do not read. The branch slides hold your structure while you speak, the way paper notes would if you had them. When a branch feels shaky, collapse it with the chevron on the node and try to say the answer with that branch hidden, because a story that only works while the beats are visible is not learned yet.

• One slide per story, with the beats as its children
• Say the answer aloud; the slides are the scaffold
• Hide a branch you do not trust and rebuild it
• Use Esc to leave and the arrow keys to move

Note: Presentation mode shows the root and one level of children, so anything deeper than a beat belongs in the rich note rather than on a slide.

Questions to ask that come off the map

Good interview questions are not memorized, they are read off the map. Look for branches that are still thin: a requirement you have no story for, a team whose current problem you could not find, a part of the role that sounds broad and undefined. Each thin branch is a legitimate question, and asking it shows you were listening rather than reading a list.

Add a branch called "questions to ask" and give each question a child node. In the rich note, write the question and one line about why you want to know it. If a second pair of eyes would help, the map has to leave your machine, because Canvasola has no share links: export it as a PNG or an SVG for a picture, or as Markdown for an outline, and attach the file.

• A question for every thin branch, not a stock list
• Three questions is usually enough
• Write the reason you want to know it in the note
• Export to PNG or Markdown for a mentor

Note: Cloud sync is opt-in and an account holds up to five projects of 2 MB each, so keep a .canv file or an export as your own backup.

A checklist you can reuse

• The root node holds the exact role title from the posting
• Every requirement in the ad has a branch on the map
• Each requirement branch has a story attached with a cross-link
• Every story carries situation, action and result as its children
• Each story can be said out loud in under two minutes
• The evidence behind every answer sits in a rich note
• You have rehearsed every branch in presentation mode

Common mistakes to avoid

• Listing skills instead of evidence. A map of tools and adjectives gives the interviewer nothing to probe. Write the claim you want them to believe, then attach the history that supports it.
• More than three stories. Every extra story is another answer you will rehearse badly. Three well-shaped stories beat eight fragments you half remember.
• Putting the detail in the label. A long label is unreadable on a slide and slow to speak. Move the numbers, the names and the dates into the rich note.
• No link from story to requirement. Without the cross-link you have to remember which story answers which requirement under pressure. Draw the link and note the pairing.
• Reading the slides instead of speaking. Presentation mode exists to hold your structure, not to be read out. Rehearse aloud with the slides as a scaffold and nothing more.

Frequently asked questions

How many stories should I prepare for a job interview?

Three is the useful number. It covers most postings without turning the map into a biography, and it is a number you can rehearse. If a posting lists six requirements, map each one to a story and note the two that share one, rather than writing answers you will never use.

Can I send my interview mind map to a mentor?

There is no share link in Canvasola, so you export instead. Export the map as a PNG or an SVG for a picture, or as Markdown for an outline you can paste into a document, and attach that file. If your mentor has Canvasola, send the .canv project file, which keeps the notes and links intact.

Why does presentation mode not show the whole story?

Presentation mode shows the root label first, then one slide per first-level branch with that branch's immediate children. Anything deeper than one level never reaches a slide. That is why the beats of your answer belong as children of the story branch, and the evidence in the note.

Should the map be in tree or radial layout?

Use the tree layout for rehearsal. It puts the root on the left and the branches to the right in reading order, which is the order you will speak in. Press L to switch to the radial layout, which looks better on a poster and is harder to scan quickly.

This guide is part of the mind map use cases collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.