Interview questions for documentation skills: 14 questions about writing things down so others can use them
On this page
- Documentation skills, defined as something you can observe
- Ten behavioral questions, with red flags and probes
- Four situational questions
- A ten-minute follow-the-doc test
- Documentation, written communication and attention to detail compared
- What strong and weak answers sound like
- A 1–4 anchored rating scale for documentation skills
- Common interviewer mistakes with documentation skills
- Questions people ask
Interview questions for documentation skills are easy to skip because documentation looks like a side task. It is not a side task for the person who covers the role during leave, the new hire who inherits the process, or the auditor who asks why something was done. Good documenters decide what is worth recording, write it so someone without their context can act on it, and keep it current when things change. Poor documenters either write nothing or write everything and update none of it. Below are fourteen questions, ten behavioral and four situational, each with what a strong answer contains, red flags and a follow-up probe, plus a short follow-the-doc test, a comparison with neighboring competencies, illustrative sample answers, a 1–4 anchored scale and common mistakes.
Documentation overlaps with two competencies that have their own pages. Interview questions for written communication cover clear, persuasive writing for a reader who is reading it now. Interview questions for attention to detail cover accuracy and catching errors. This page covers creating and maintaining records that other people rely on later, when the author is not there to explain.
Documentation skills, defined as something you can observe
Definition: documentation skill is producing and maintaining written records, such as procedures, handovers, case notes, decision logs and reference guides, that let another person understand what was done, why, and how to do it again, without needing the author. Listen for four behaviors:
- Choosing what to record. Documents what someone else will need: decisions and their reasons, steps that are easy to get wrong, exceptions. Leaves out what is obvious or recorded elsewhere.
- Writing for the next person. Assumes the reader lacks context, uses steps in order, names where things live and defines terms.
- Keeping it current. Updates documents when the process changes and removes or marks what is out of date.
- Making it findable. Puts documents where people will look, with names they would search for.
Ten behavioral questions, with red flags and probes
| Question | A strong answer contains | Red flags | Follow-up probe |
|---|---|---|---|
| 1. Tell me about a document you wrote that someone else used to do the work without you. | Who used it, what it covered, how the candidate knew it worked and what they changed after feedback. | No evidence anyone used it. | "What did they still have to ask you?" |
| 2. Describe a time you inherited poor documentation or none at all. What did you do? | Rebuilt what was needed while doing the work, checked it with others and left it better. | Complained and worked around it, leaving the same gap for the next person. | "What did you leave behind?" |
| 3. How do you decide what is worth documenting? | A clear rule of thumb, such as anything done rarely, anything with a costly mistake, or any decision someone will later question. | "Everything," or "only when asked." | "What is something you chose not to document?" |
| 4. Tell me about a time documentation was out of date and caused a problem. | What went wrong, how they fixed the document and what they changed so it stayed current. | Fixed the immediate issue but not the document. | "Who owns keeping it current now?" |
| 5. Describe the handover you prepared before your last leave or role change. | Open work, status, contacts, where things live, decisions pending and what to do if something breaks. | A verbal walkthrough only. | "What happened while you were away?" |
| 6. Tell me about a decision you recorded and why. | What was decided, the options considered, the reason, and how the record helped later. | Decisions live in memory or chat history. | "When did someone look it up?" |
| 7. How have you written instructions for someone much less experienced than you? | Tested it on a newcomer, added the steps experts skip, defined terms. | Assumes readers know what they know. | "What did the newcomer get stuck on?" |
| 8. Describe a time you had to document something under time pressure, such as an incident or a busy shift. | Captured the essentials at the time, filled in the rest promptly, and was accurate about what was known versus assumed. | Wrote it up days later from memory. | "What did you write first?" |
| 9. Tell me about a time you got people to actually use a shared knowledge base or procedure. | Made it findable, linked it from where work happens, pointed people to it instead of answering from memory. | Built it and assumed people would come. | "How did you know people used it?" |
| 10. Describe documentation you are proud of and one you would rewrite. | Specific features of the good one, and an honest diagnosis of the weak one. | Cannot name a weakness in their own documents. | "What would you change first?" |
Questions 1 and 4 matter most. Question 1 checks whether the candidate's documents work for other people. Question 4 checks whether they keep them working.
Four situational questions
-
"You join a team where the only person who knows how month-end runs is leaving in three weeks. What do you do?"
Probes: What would you capture first? How would you check it is complete? -
"Your team's procedure says one thing, and everyone actually does something else. What do you do?"
Probes: Which do you change, the document or the practice? Who decides? -
"A colleague says documentation slows the team down and nobody reads it. How do you respond?"
Probes: Where might they be right? What would you keep, and what would you cut? -
"Something went wrong overnight, and you are the first person in. What do you write down, and for whom?"
Probes: What do you record as fact and what as assumption? Where does it go?
Situation 12 is especially useful: weak candidates assume the document is always right, and strong candidates find out why practice drifted before deciding which to fix.
A ten-minute follow-the-doc test
Talking about documentation is weaker evidence than seeing it. For roles where documentation is central, add a short exercise that every candidate does the same way.
- Choose a simple, job-related task the candidate can describe without confidential information, such as resetting a user's access, closing out a shift or processing a returned item. Use the same task for everyone.
- Give the candidate ten minutes to write instructions that a new starter could follow alone on their first day.
- After the interview, have a second person follow the instructions literally, or read them as if they were a newcomer, and mark every point where they would have to stop and ask.
- Score against a short rubric agreed in advance: steps in order, decision points covered, terms defined, where to find things, what to do if something goes wrong.
Do not score spelling, formatting style or length unless they get in the way of following the instructions. Any scored exercise used to decide who moves forward is a selection procedure, so keep it tied to the real job and apply it consistently. The four-fifths rule explainer shows how to check pass rates, and the written communication page explains the legal caution on scored writing exercises in more detail.
Documentation, written communication and attention to detail compared
| Documentation skills | Written communication | Attention to detail | |
|---|---|---|---|
| Main question | Can someone else use this later without me? | Will this reader understand and act on this now? | Is this accurate and consistent? |
| Reader | A future colleague, auditor or newcomer | A current audience | Anyone relying on the work |
| Typical output | Procedures, handovers, logs, case notes | Emails, proposals, updates | Error-free work, caught mistakes |
| Typical failure | Missing, stale or unfindable records | Unclear or unpersuasive message | Errors that reach others |
If the candidate's strength is redesigning the process itself rather than recording it, score that under process improvement.
What strong and weak answers sound like
Illustrative answers to question 1, written to show the difference in structure.
Weak: "I'm big on documentation. I wrote loads of guides at my last job and put them all on the shared drive. People always said they were really thorough."
There is no specific document, no evidence that anyone used one to do the work, and "thorough" may mean too long to follow.
Strong: "I ran supplier onboarding, which only happened a few times a quarter, so people forgot the steps. I wrote a one-page checklist with the order of steps, which system each step happens in, and the two places it usually goes wrong, with what to do. I asked a colleague who had never done it to onboard the next supplier using only the checklist while I watched without helping. She got stuck once, on a tax form, so I added that. When I went on leave she ran two onboardings without calling me. I review the checklist whenever a system changes, and I put my name and the last review date at the top."
The strong answer chooses a task worth documenting, tests the document on a real newcomer, fixes the gap, proves it worked in the author's absence and builds in a way to keep it current.
A 1–4 anchored rating scale for documentation skills
| Score | Anchor |
|---|---|
| 1 — No evidence | Documents only when required, or not at all. Knowledge lives in their head. Handovers are verbal. |
| 2 — Limited | Writes documents when asked. They are accurate but assume the reader's context, and are rarely updated. |
| 3 — Solid | Chooses what to record, writes for a reader without context, keeps documents current and puts them where people look. Has evidence others used them. |
| 4 — Strong | Everything at 3, plus tests documents on newcomers, sets up ownership and review so documentation stays current, and gets a team to rely on shared records. |
For distributed teams, written handoffs are a core part of how work moves. Interview questions for remote collaboration cover that day-to-day side.
Common interviewer mistakes with documentation skills
- Rewarding volume. More pages is not better documentation. Ask what someone could do with the document.
- Confusing polish with usability. A beautifully formatted guide that skips the hard step is worse than a plain checklist that covers it.
- Asking for confidential samples. Asking candidates to bring internal documents from another employer puts them in a difficult position. Ask them to describe the documents, or use an exercise.
- Ignoring maintenance. Writing a document once is the easy part. Ask how the candidate kept it current.
- Writing "good documenter" in the notes. Record the behavior: "wrote supplier onboarding checklist; tested on a newcomer; colleague ran two onboardings during leave without help."
Questions people ask
What is the difference between documentation skills and written communication?
Written communication is about getting a message across to a reader now: an email, a proposal, a status update. Documentation is about creating a record that someone else can rely on later, often when the author is not around to explain it: a procedure, a runbook, a handover note, case notes or a decision log. A persuasive writer can still produce documentation nobody can follow, and a plain writer can produce excellent documentation.
How is documentation different from attention to detail?
Attention to detail is about accuracy: catching errors and inconsistencies in your own or others' work. Documentation depends on accuracy, but it also requires judgment about what to record, structure that a newcomer can follow and the discipline to keep records current as things change. A careful person can be accurate in their own work and still leave nothing behind for the next person.
Which roles need documentation skills questions?
Any role where other people depend on records the candidate creates: operations and IT, engineering, quality and compliance, healthcare and social care, finance and accounting, legal support, customer support and anyone who runs a process that someone else will cover during leave or after they move on.
Is it fair to ask candidates for samples of documentation from a previous job?
Be careful. Most workplace documentation is confidential, and asking for it invites candidates to share material they should not. Ask them to describe documents they created instead, or use a short exercise with the same job-related prompt for everyone.