Interview Copilot

Using the Knowledge Base

Giving Copilot the material your resume leaves out.

Your resume is compressed by design: a decade of work in two pages. The Knowledge Base is where you put the detail that does not fit, so Copilot has something to draw on when an interviewer asks a question a resume bullet cannot answer.

What to put in it

• Detailed project write-ups: what the problem was, what you did, what the result was, what you would change.
• Portfolio pieces, case studies, or published work.
• A longer-form career history covering roles compressed to a single line on the resume.
• Notes on the specific employer: their product, the team, why you want this job.
• Your own numbers for a salary conversation.

How many documents you get

• Starter: 3 documents.
• Pro: 5 documents.
• Premier: 10 documents.

Working within the limit

These limits are lower than they sound, because a document can be long. One well-organised document covering six projects is more useful than six thin ones, and it leaves slots free for employer-specific notes. Treat a slot as a topic, not as a file.

Writing documents Copilot can use

The Knowledge Base is searched live, mid-conversation, while you are waiting to speak. Structure matters more than polish.

• Use clear headings. They are how the right passage gets found quickly.
• Lead each section with the point. Copilot surfaces the opening, so context-then-conclusion buries what you need.
• Include the concrete details: numbers, technologies, timelines. Those are what you will be asked for.
• Write in your own voice, so anything surfaced already sounds like you.