You have until tomorrow to write a 500-word password-reset guide for new customers who rarely use web apps. How would you define its audience, task, and purpose before drafting?

I would define one reader, one successful task, and one observable result before I outline the guide. - The audience is a signed-out customer who can access their email but may not know terms such as authentication token. - The task starts at the sign-in page and ends when the customer signs in with a new password. - The purpose is to let the customer recover access without contacting support, so I would exclude account-security theory and administrator recovery.

Support asks for a one-page guide that helps 30 warehouse operators reconnect a handheld scanner after Wi-Fi drops. What would you clarify before writing?

I would confirm the operators' context and the exact recovery point before choosing instructions. - I would ask which scanner model and software version all 30 operators use, because button names may differ. - I would observe one operator reproduce the disconnect and note what they can see, including the error message and available network. - I would agree that success means one test scan reaches the inventory system, not merely that the Wi-Fi icon returns.

Three help pages call the same control workspace, project, and space, while the product UI says workspace. You must fix them before Friday. What would you do?

I would use workspace consistently because documentation should match the current product UI. - I would confirm with the product owner that the three words do not represent different objects. - I would replace project and space in the three pages, including headings, link text, screenshots, and alt text. - I would add workspace to the team glossary with the rejected variants so future writers can find the decision.

A 120-word status-page note for small-business owners says, 'Service functionality may experience intermittent degradation.' How would you rewrite and check it in 20 minutes?

I would replace the abstract phrase with a direct statement about what customers may notice. - I would write, 'Some customers may not be able to upload invoices,' if that is the confirmed impact. - I would add the affected time or region only when engineering has verified it. - I would read the full 120-word note aloud and remove words that do not help the owner decide whether to retry or wait.

A setup guide for 15 office administrators says, 'The configuration file should be copied to the server.' How would you revise this passive instruction?

I would name the person or system performing the action and give the exact destination. - If the administrator acts, I would write, 'Copy config.yaml to /etc/acme/config.yaml.' - If the installer acts automatically, I would say that instead so the administrator does not repeat the action. - I would verify the command and path on a clean test server before publishing the guide.

Five beta users failed a CLI installation guide because Python and an access key were missing. You have one hour to repair the prerequisites section. What would you add?

I would add a short prerequisites section that users can verify before step one. - I would name the supported Python version and provide a command such as python --version to check it. - I would state where to create the access key, which permission it needs, and that the secret must not be committed. - I would include the supported operating systems and link to installation instructions rather than duplicating them.

A database cleanup procedure for a support engineer deletes up to 500 test records, but its warning appears after the delete command. What would you change before today's review?

I would move the warning immediately before the first irreversible step and state the consequence plainly. - The warning would say that the command permanently deletes matching test records and cannot be undone. - I would require the engineer to run the provided count query and confirm the result is at most 500. - I would add a backup or approval step if the team's cleanup policy requires one.

A CSV import guide ends after 'Select Upload,' and 12 payroll users cannot tell whether 2,000 rows were accepted. What verification step would you add?

I would end the procedure with a result the payroll user can compare with the source file. - I would tell the user where the completion status and imported-row count appear. - I would state that the accepted count should equal 2,000 minus any rows listed in the error report. - I would add the next action for a mismatch, such as downloading the error CSV and correcting the named rows.

You must document user invitations for two audiences by Thursday: team owners invite one colleague in the UI, while administrators import 100 users by CSV. Would you use one page or two?

I would create two task pages and connect them from a short invitation overview. - The owner page would cover the single-user UI flow with the role choices visible to that audience. - The administrator page would cover the CSV template, the 100-user limit, validation errors, and import verification. - Separating them prevents owners from reading irrelevant bulk-import details while keeping both paths discoverable.

A product manager asks for 'complete billing documentation' by tomorrow, but you can deliver only one 800-word page for trial customers. How would you narrow the assignment?

I would turn the broad request into one agreed user task that fits the deadline. - I would ask which trial-customer question causes the most support cases, such as adding a payment method before trial expiry. - I would define the page boundary, required screenshots, reviewer, and a testable completion result. - I would record refunds, invoice administration, and tax details as separate follow-up pages instead of pretending one page is complete.

You need a 20-minute learning document that guides a new developer from an empty folder to a working weather app. Which Diátaxis type would you choose and how would you shape it?

I would write a tutorial because the reader is learning through a guided, successful experience. - I would provide a tested path with one supported language, prepared sample data, and minimal choices. - Each stage would produce a visible result, such as the first API response and then a rendered temperature. - I would link to reference pages for parameter details rather than interrupt the lesson with every option.

An experienced administrator must rotate a TLS certificate during Friday's maintenance window. They need a two-page document they can follow while working, not a lesson on certificates. How would you design it?

I would produce a practical how-to guide centered on completing and verifying that one production task. - Before the steps, I would list the required access, certificate files, backup, and approved maintenance window. - The ordered path would replace the certificate, reload the service, and verify both the served certificate and its expiry date. - I would test the path in staging and link optional public-key background separately so it cannot interrupt the work.

Eighteen SDK configuration keys are described in scattered paragraphs, and developers cannot quickly compare their types, defaults, or allowed values. What one-page artifact would you build by Monday?

I would build a reference page with a repeatable entry for each key and a predictable lookup order. - Every entry would contain the exact name, type, required status, default, allowed values, effect, and version availability. - I would sort or group the keys by the convention already used in the SDK and add anchors for direct links. - I would validate the values against the configuration schema and keep task steps in a linked how-to instead of the lookup page.

A five-minute dashboard delay is expected behavior, but developers interpret it as data loss. Support wants a 600-word article that helps them understand when fresh data becomes visible. What would you explain?

I would write a conceptual explanation that gives readers a causal mental model of the delay. - I would trace one event through ingestion, batching, and cache refresh, explaining why each stage exists. - A timeline would show how a change at 10:02 can appear by 10:07 without implying that the event was lost. - I would state the normal freshness boundary and link delays beyond five minutes to a separate troubleshooting procedure.

A draft called 'Learn backups' contains a beginner exercise, a production restore procedure, and a 25-field command table. You have one day to restructure it using Diátaxis. What would you do?

I would split the draft into separate tutorial, how-to, and reference documents with clear links between them. - The tutorial would restore a harmless sample database so a beginner can learn the workflow. - The how-to would guide an operator through restoring a real backup under production safeguards. - The reference would define all 25 command fields, defaults, and constraints in a consistent format.

You receive seven unordered steps for connecting a printer, including a restart and a test page, for a one-page office guide due today. How would you structure the procedure?

I would arrange the seven steps around prerequisites, action order, and a final proof that printing works. - I would put the printer model, network access, and driver requirement before the numbered steps. - Each step would contain one action, the exact UI label, and any immediate result needed before continuing. - I would finish with printing one test page and give a recovery link if the expected page does not appear.

Ten users report 'Sync failed' after installing desktop app version 4.2, and support needs a troubleshooting page in three hours. How would you organize it?

I would organize the page by observable symptom, likely cause, diagnostic check, and safe fix. - I would capture the exact error text, version 4.2, operating system, and whether the failure affects all files or one file. - I would order checks from low risk to high effort, starting with service status and account connectivity before reinstalling. - I would give an escalation condition and list the log file and timestamp support needs if the fixes fail.

Version 2.6 ships tomorrow with two new filters, one renamed button, and an internal database migration. What belongs in the customer release notes?

I would report the three changes only through their customer-visible effect and omit the internal migration if it changes nothing for users. - I would name both new filters and state what records each helps customers find. - I would mention the old and new button labels so returning users can recognize the change. - I would include any required action or known limitation, but keep implementation tickets and migration details in internal records.

Support collected 40 questions about exports, but 28 are variations of 'How do I download last month's invoices?' Should this become an FAQ entry or another document?

I would create or improve one canonical how-to guide and use the FAQ only as a short route to it. - The repeated question describes a task with steps, date filters, file format, and a completion result. - The FAQ entry can answer in one sentence and link to the full invoice-export procedure. - I would group the remaining 12 questions to see whether they expose missing reference details or genuine brief answers.

Version 3.0 changes the CLI configuration format. Existing users must run a converter once, and custom keys can trigger an 'Unsupported field' error. Would you put this in release notes, a migration guide, or troubleshooting documentation?

I would use all three artifacts for different decisions, with the migration guide as the canonical path. - The release note would state who is affected, the deadline or version boundary, and link to the required migration. - The migration guide would cover backup, conversion, verification, and the approved rollback path for existing configurations. - Troubleshooting would start from the exact 'Unsupported field' symptom, list verified causes and fixes, and define when to escalate.

Technical Writer interview questions

100 real questions with model answers and explanations for Junior Technical Writer candidates.

See a Technical Writer resume example →

Practice with flashcards

Spaced repetition · Hunter Pass

Questions

passwords

I would define one reader, one successful task, and one observable result before I outline the guide.

The audience is a signed-out customer who can access their email but may not know terms such as authentication token.
The task starts at the sign-in page and ends when the customer signs in with a new password.
The purpose is to let the customer recover access without contacting support, so I would exclude account-security theory and administrator recovery.

Why interviewers ask this: The interviewer checks whether you can turn a small assignment into a clear audience, task boundary, and user outcome.

warehouse

I would confirm the operators' context and the exact recovery point before choosing instructions.

I would ask which scanner model and software version all 30 operators use, because button names may differ.
I would observe one operator reproduce the disconnect and note what they can see, including the error message and available network.
I would agree that success means one test scan reaches the inventory system, not merely that the Wi-Fi icon returns.

Why interviewers ask this: A strong answer gathers only the facts needed to make a short task guide accurate and verifiable.

I would use workspace consistently because documentation should match the current product UI.

I would confirm with the product owner that the three words do not represent different objects.
I would replace project and space in the three pages, including headings, link text, screenshots, and alt text.
I would add workspace to the team glossary with the rejected variants so future writers can find the decision.

Why interviewers ask this: The interviewer evaluates whether you verify meaning, follow the interface, and preserve a terminology decision.

I would replace the abstract phrase with a direct statement about what customers may notice.

I would write, 'Some customers may not be able to upload invoices,' if that is the confirmed impact.
I would add the affected time or region only when engineering has verified it.
I would read the full 120-word note aloud and remove words that do not help the owner decide whether to retry or wait.

Why interviewers ask this: The interviewer checks whether you can make technical status language concrete without inventing facts.

config

I would name the person or system performing the action and give the exact destination.

If the administrator acts, I would write, 'Copy config.yaml to /etc/acme/config.yaml.'
If the installer acts automatically, I would say that instead so the administrator does not repeat the action.
I would verify the command and path on a clean test server before publishing the guide.

Why interviewers ask this: A strong answer uses active voice to remove ambiguity about who does what and where.

python

I would add a short prerequisites section that users can verify before step one.

I would name the supported Python version and provide a command such as python --version to check it.
I would state where to create the access key, which permission it needs, and that the secret must not be committed.
I would include the supported operating systems and link to installation instructions rather than duplicating them.

Why interviewers ask this: The interviewer checks whether prerequisites are specific, testable, and limited to what the procedure actually needs.

database

I would move the warning immediately before the first irreversible step and state the consequence plainly.

The warning would say that the command permanently deletes matching test records and cannot be undone.
I would require the engineer to run the provided count query and confirm the result is at most 500.
I would add a backup or approval step if the team's cleanup policy requires one.

Why interviewers ask this: The interviewer evaluates whether you place a warning where it can prevent harm and pair it with a concrete safeguard.

I would end the procedure with a result the payroll user can compare with the source file.

I would tell the user where the completion status and imported-row count appear.
I would state that the accepted count should equal 2,000 minus any rows listed in the error report.
I would add the next action for a mismatch, such as downloading the error CSV and correcting the named rows.

Why interviewers ask this: A strong answer treats verification and recovery as part of completing the user's task.

I would create two task pages and connect them from a short invitation overview.

The owner page would cover the single-user UI flow with the role choices visible to that audience.
The administrator page would cover the CSV template, the 100-user limit, validation errors, and import verification.
Separating them prevents owners from reading irrelevant bulk-import details while keeping both paths discoverable.

Why interviewers ask this: The interviewer checks whether you separate content when audiences, scale, and workflows materially differ.

documentation

I would turn the broad request into one agreed user task that fits the deadline.

I would ask which trial-customer question causes the most support cases, such as adding a payment method before trial expiry.
I would define the page boundary, required screenshots, reviewer, and a testable completion result.
I would record refunds, invoice administration, and tax details as separate follow-up pages instead of pretending one page is complete.

Why interviewers ask this: The interviewer evaluates whether you can negotiate a realistic scope without losing the user's immediate goal.

diataxis

I would write a tutorial because the reader is learning through a guided, successful experience.

I would provide a tested path with one supported language, prepared sample data, and minimal choices.
Each stage would produce a visible result, such as the first API response and then a rendered temperature.
I would link to reference pages for parameter details rather than interrupt the lesson with every option.

Why interviewers ask this: The interviewer checks whether you recognize a learning-oriented journey and protect it from reference overload.

tlsdesign

I would produce a practical how-to guide centered on completing and verifying that one production task.

Before the steps, I would list the required access, certificate files, backup, and approved maintenance window.
The ordered path would replace the certificate, reload the service, and verify both the served certificate and its expiry date.
I would test the path in staging and link optional public-key background separately so it cannot interrupt the work.

Why interviewers ask this: A strong answer turns an operator's real goal into a safe, testable how-to rather than another learning journey.

configartifacts

I would build a reference page with a repeatable entry for each key and a predictable lookup order.

Every entry would contain the exact name, type, required status, default, allowed values, effect, and version availability.
I would sort or group the keys by the convention already used in the SDK and add anchors for direct links.
I would validate the values against the configuration schema and keep task steps in a linked how-to instead of the lookup page.

Why interviewers ask this: The interviewer evaluates whether you can design and verify a consistent reference artifact, not merely name a Diátaxis category.

I would write a conceptual explanation that gives readers a causal mental model of the delay.

I would trace one event through ingestion, batching, and cache refresh, explaining why each stage exists.
A timeline would show how a change at 10:02 can appear by 10:07 without implying that the event was lost.
I would state the normal freshness boundary and link delays beyond five minutes to a separate troubleshooting procedure.

Why interviewers ask this: A strong answer uses explanation to change the reader's understanding and leaves diagnosis to an operational artifact.

diataxisbackups

I would split the draft into separate tutorial, how-to, and reference documents with clear links between them.

The tutorial would restore a harmless sample database so a beginner can learn the workflow.
The how-to would guide an operator through restoring a real backup under production safeguards.
The reference would define all 25 command fields, defaults, and constraints in a consistent format.

Why interviewers ask this: The interviewer checks whether you can separate different reader needs instead of forcing them into one mixed document.

I would arrange the seven steps around prerequisites, action order, and a final proof that printing works.

I would put the printer model, network access, and driver requirement before the numbered steps.
Each step would contain one action, the exact UI label, and any immediate result needed before continuing.
I would finish with printing one test page and give a recovery link if the expected page does not appear.

Why interviewers ask this: A strong answer makes a short procedure scannable, sequential, and verifiable.

troubleshooting

I would organize the page by observable symptom, likely cause, diagnostic check, and safe fix.

I would capture the exact error text, version 4.2, operating system, and whether the failure affects all files or one file.
I would order checks from low risk to high effort, starting with service status and account connectivity before reinstalling.
I would give an escalation condition and list the log file and timestamp support needs if the fixes fail.

Why interviewers ask this: The interviewer evaluates whether your troubleshooting path is evidence-based and avoids random destructive fixes.

databasemigrationsrelease-notes

I would report the three changes only through their customer-visible effect and omit the internal migration if it changes nothing for users.

I would name both new filters and state what records each helps customers find.
I would mention the old and new button labels so returning users can recognize the change.
I would include any required action or known limitation, but keep implementation tickets and migration details in internal records.

Why interviewers ask this: A strong answer keeps release notes useful to customers and separates internal engineering history.

I would create or improve one canonical how-to guide and use the FAQ only as a short route to it.

The repeated question describes a task with steps, date filters, file format, and a completion result.
The FAQ entry can answer in one sentence and link to the full invoice-export procedure.
I would group the remaining 12 questions to see whether they expose missing reference details or genuine brief answers.

Why interviewers ask this: The interviewer checks whether you avoid hiding substantial procedures inside an ever-growing FAQ.

documentationmigration-guidesrelease-notes

I would use all three artifacts for different decisions, with the migration guide as the canonical path.

The release note would state who is affected, the deadline or version boundary, and link to the required migration.
The migration guide would cover backup, conversion, verification, and the approved rollback path for existing configurations.
Troubleshooting would start from the exact 'Unsupported field' symptom, list verified causes and fixes, and define when to escalate.

Why interviewers ask this: A strong answer separates announcement, planned migration, and symptom-based recovery instead of forcing one document to serve all three needs.

Locked questions

21
A 900-word Markdown guide for contributors uses three level-one headings and jumps from level two to level four. What would you fix before the PR today?
markdown
22
A Docusaurus page for developers contains 12 links labeled 'click here,' and four internal links use the production domain. How would you revise them by Friday?
docusaurus
23
You need to compare four subscription plans across six limits on a mobile-friendly help page. Would you use a Markdown table, and what would you check?
markdown
24
A Python quickstart has three commands shown as plain paragraphs, and copy-paste failures are increasing. You have 30 minutes to fix the Markdown. What would you change?
quickstartspythonmarkdown
25
You must update two Markdown pages without disturbing another writer's work on main. Describe the basic Git branch workflow you would use today.
gitmarkdown
26
Your pull request changes one setup guide and one screenshot for Windows users, and the release is tomorrow. What information would you put in the PR?
code-reviewpull-requests
27
Git reports a conflict in one paragraph because you and another writer edited the same installation page this morning. How would you resolve it safely?
git
28
A Jira issue asks you to update a two-page internal onboarding guide in Confluence before Monday. How would you keep the task and document connected?
onboarding
29
A small Docusaurus site needs a new three-page 'Webhooks' section for developers by next week. Where would you place the files and navigation?
docusauruswebhooks
30
A Docusaurus section relies on file names and an autogenerated sidebar, but the team now wants explicit page titles, stable URLs, and an agreed manual order for ten pages. What would you configure before Friday?
configdocusaurus
31
An OpenAPI file defines GET /orders/{orderId} for partner developers, and you have 45 minutes to draft its endpoint summary. What would you extract first?
endpointsopenapi
32
A search endpoint has one required query parameter, query, and two optional parameters, limit and cursor. How would you document them for a one-page API reference?
endpointsapi-referencequeries
33
You need one complete request example for POST /tickets aimed at first-time API users by tomorrow. The body requires subject and priority. What would you include?
api
34
The 201 response example for creating a user contains fullName, but the OpenAPI schema and live API return displayName. The docs publish in two hours. What would you do?
openapischema
35
A quickstart needs one curl command that lists the first 20 projects for a new developer. What makes the example usable?
quickstartshttp-tools
36
A public API guide has six examples containing a real staging token copied by an engineer. You must sanitize them before review today. What would you replace it with?
tokensvalidationapi
37
A payment endpoint documents 200, 201, 400, 401, 404, and 500 in six paragraphs. How would you turn them into a useful status table for integrators?
endpoints
38
An API returns three error codes, INVALID_EMAIL, DUPLICATE_USER, and RATE_LIMITED, but the guide only says '400 error.' You have one hour to add an error table. What fields would it contain?
api
39
Before publishing a login endpoint guide tomorrow, you can test only two examples. Which cases would you choose and what would you record?
endpoints
40
Engineering renamed GET /customers/{id} to GET /accounts/{id} for next week's release. You own four examples and one reference page. How would you verify the update?
reference-docs
41
You need three Snagit screenshots for a two-page Windows setup guide due today. How would you capture and edit them?
42
A five-step mobile guide currently uses a full-screen screenshot after every sentence, but the app UI changes monthly. What would you keep before Friday's update?
43
A screenshot in an account guide shows the Security page with the Two-step verification toggle enabled. Write useful alt text for screen-reader users in one sentence.
alt-textscreen-readers
44
A one-page keyboard setup guide uses color alone to identify two buttons and has four links named 'here.' What accessibility fixes would you make today?
documentation-accessibilitykeyboard-accessibilitya11y
45
Support wants a simple diagram showing how a browser, API, and database handle one profile request. You have 30 minutes and a nontechnical audience. What would you draw?
databaseapi
46
Three PNG screenshots make a two-page setup guide 24 MB and slow to load on mobile, but their interface labels must remain readable. You have one hour. How would you reduce the weight safely?
types
47
A 150-word dialog guide will be translated into six locales next week. It uses jokes, 'simply,' and a sentence with three embedded conditions. How would you make it locale-ready?
48
You have a 25-minute interview with an engineer to document a new file-upload limit for customer administrators by tomorrow. How would you prepare and run it?
49
A reviewer leaves 18 comments on your two-page draft, including one unclear request and two suggestions that conflict. The page is due tomorrow. How would you respond?
50
For a junior technical-writer application due Friday, you can submit only two portfolio samples from a README rewrite, an unpublished essay, and a tested API quickstart. Which would you choose and why?
quickstartsapi
51
A 6-page password-reset procedure still shows the old Settings menu, and the product release is tomorrow at 3 p.m.; how would you fix it?
passwords
52
In docs/import-desktop.md, step 4 sends Windows and macOS users to C:\Exports, and two macOS testers cannot finish the 8-step import; how would you repair it?
53
An onboarding guide tells users to accept an invitation after it tells them to sign in, but accounts do not exist until the invitation is accepted; how would you repair the steps?
onboarding
54
A 4-page reporting guide says Select Export CSV, while the released button says Download report and produces an XLSX file; what would you do before Friday's release?
55
A cleanup article includes rm -rf ~/app-data as its first example, and the support lead wants it published today; how would you handle it?
56
Support has received 18 tickets this week from users who lost their MFA phone, but the 7-page sign-in guide covers only normal login; what update would you propose?
57
A deployment procedure says Configure logging appropriately before step 8, and two new operators interpreted it differently; how would you make the instruction usable?
deploymentloggingconfig
58
A quickstart requires Node.js 18, but the repository now enforces Node.js 22 and the tutorial release is due in 2 days; what would you update?
tutorialsquickstarts
59
A 12-step plugin upgrade procedure has no rollback section, and staging failed at step 10; what would you do before customers use it?
rollback
60
Nine support tickets say users cannot see a newly enabled dashboard feature until they refresh cached data; how would you close the documentation gap for Monday's patch?
documentationcaching
61
Docusaurus reports 14 broken links in a 30-page guide after a folder rename; how would you prepare a safe fix?
docusaurus
62
Your two-line edit to docs/install.md appears in Git as a 600-line replacement because your editor changed line endings; how would you prepare a clean review?
git
63
Markdownlint fails your 5-file pull request with MD025 and MD040 one hour before review; how would you fix it?
markdownpull-requestscode-review
64
An image renders locally in guide/setup.md but is missing from the deployed site because its path uses C:\Users\me\Desktop\setup.png; how would you correct it?
deployment
65
A new release-note page builds without a title in navigation because its front matter contains tite and an unquoted date; what would you change?
66
Support says a rate-limit note disappeared from docs/api/limits.md last week, but no ticket explains why; how would you investigate in Git before restoring it?
gitapi
67
Version 2.4.1 ships from a small release branch Friday, and you must update one workaround plus the release notes; how would you work without pulling unrelated main changes?
release-notes
68
The MDX build fails on docs/auth.mdx with Unexpected character < after you add a sample response; how would you investigate?
69
You need to rename faq.md to account-faq.md, but 11 pages link to it and the old URL appears in support macros; how would you proceed?
70
A reviewer requests changes on 3 of 8 pages in your pull request while the other 5 are approved; what would you do before merging?
code-reviewpull-requests
71
The quickstart sends JSON to POST /attachments, but openapi.yaml defines multipart/form-data and staging returns 415; how would you update the page?
openapiformsyaml
72
The orders endpoint moves from /v1/orders to /v2/orders in release 3.0, and 7 guides contain the old path; what would you change?
endpoints
73
The API now returns 422 with code invalid_address instead of a generic 400 for address validation; how would you document it by Thursday?
validationapigenerics
74
A curl example for POST /invoices returns 401 in staging even though the page says it creates a 201 response; how would you verify and repair it?
http-tools
75
Acme API.postman_collection.json creates a project, but its next Get project request uses a hard-coded ID and returns 404 for every new user; how would you fix the collection?
api
76
Authentication changes from an X-API-Key header to Bearer tokens for a beta endpoint in 5 days; how would you update its quickstart?
authtokensendpoints
77
GET /events changes from page and limit parameters to cursor pagination, with a maximum page size of 100; what documentation would you update?
documentationpagination
78
The Payment.status enum gains cancelled, but the generated reference and a 3-page tutorial list only pending, paid, and failed; how would you handle it?
tutorialsreference-docs
79
POST /charges now requires idempotency_key in the JSON body, and the release candidate rejects the old example; what would you do?
idempotency
80
DELETE /sessions now returns 204 with no body, but the API page shows a 200 JSON success object; how would you update and test it?
sessionsapi
81
A settings redesign changes 12 screenshots across an 18-page admin guide 3 days before release; how would you update them efficiently?
82
A PNG architecture diagram is outdated, but the repository contains a Mermaid source file for it; how would you make the small requested update?
architecture
83
Two screenshots in docs/team-invite.md show a real customer's email address and tenant ID, and review starts in one hour; how would you replace them safely?
84
A process diagram uses red and green arrows as the only way to distinguish failure from success; what would you change before publishing it?
concurrency
85
The Russian version of a 5-step onboarding page overflows its annotated screenshots because translated button labels are 40% longer; how would you fix the localized layout?
onboarding
86
A cropped screenshot in an upload guide hides the validation message that step 6 tells users to read; how would you repair the page?
validation
87
A 7-step screenshot tutorial uses arrows labeled 1, 3, 4 after image 2 was replaced; what would you check before correcting the annotations?
tutorials
88
An 8-second GIF in docs/key-rotation.md loops automatically, changes screens too quickly, and offers no pause control; how would you make the instruction accessible?
89
The SVG in docs/architecture-overview.md opens correctly on its own and is readable on desktop, but its two rightmost nodes are clipped at a 375-pixel viewport. How would you fix the published diagram?
cssarchitecture
90
A 4-minute setup video has no captions, and its companion page explains a mouse-only drag action; what accessibility updates would you make?
documentation-accessibilitya11y
91
Your SME has not reviewed a 6-page backup guide, and the release cutoff is tomorrow at noon; what would you do?
backups
92
Two hours after publishing, you discover that the engineer's requested change to step 7 was missed and the current command fails; what would you do?
93
You have 30 minutes to peer-review docs/first-login.md for another junior writer before their first handoff; how would you leave useful feedback?
feedback
94
Jira DOC-241 says Update login docs by Friday but has no affected version, audience, or acceptance criteria; how would you start the intake?
specs
95
You have 4 hours to audit 40 help-center pages before a minor release; how would you prioritize the findings?
prioritization
96
A 10-page account guide is approved for release 5.2 at 4 p.m.; what publishing and retest steps would you perform?
97
Your lead asks you to prepare a review checklist for a 3-page CLI tutorial due next week; what would you include?
tutorials
98
Support reports that users still fail after following your revised proxy article, and Jira is ready to close; how would you retest it?
proxy
99
A hiring exercise gives you 2 hours to improve a confusing 2-page API quickstart and present the result; how would you approach it?
quickstartsapi
100
You must hand off an 8-page import guide for Monday publication while one SME comment and two localization checks remain open; what would your handoff contain?
localization

Questions

1You have until tomorrow to write a 500-word password-reset guide for new customers who rarely use web apps. How would you define its audience, task, and purpose before drafting?

2Support asks for a one-page guide that helps 30 warehouse operators reconnect a handheld scanner after Wi-Fi drops. What would you clarify before writing?

3Three help pages call the same control workspace, project, and space, while the product UI says workspace. You must fix them before Friday. What would you do?

4A 120-word status-page note for small-business owners says, 'Service functionality may experience intermittent degradation.' How would you rewrite and check it in 20 minutes?

5A setup guide for 15 office administrators says, 'The configuration file should be copied to the server.' How would you revise this passive instruction?

6Five beta users failed a CLI installation guide because Python and an access key were missing. You have one hour to repair the prerequisites section. What would you add?

7A database cleanup procedure for a support engineer deletes up to 500 test records, but its warning appears after the delete command. What would you change before today's review?

8A CSV import guide ends after 'Select Upload,' and 12 payroll users cannot tell whether 2,000 rows were accepted. What verification step would you add?

9You must document user invitations for two audiences by Thursday: team owners invite one colleague in the UI, while administrators import 100 users by CSV. Would you use one page or two?

10A product manager asks for 'complete billing documentation' by tomorrow, but you can deliver only one 800-word page for trial customers. How would you narrow the assignment?

11You need a 20-minute learning document that guides a new developer from an empty folder to a working weather app. Which Diátaxis type would you choose and how would you shape it?

12An experienced administrator must rotate a TLS certificate during Friday's maintenance window. They need a two-page document they can follow while working, not a lesson on certificates. How would you design it?

13Eighteen SDK configuration keys are described in scattered paragraphs, and developers cannot quickly compare their types, defaults, or allowed values. What one-page artifact would you build by Monday?

14A five-minute dashboard delay is expected behavior, but developers interpret it as data loss. Support wants a 600-word article that helps them understand when fresh data becomes visible. What would you explain?

15A draft called 'Learn backups' contains a beginner exercise, a production restore procedure, and a 25-field command table. You have one day to restructure it using Diátaxis. What would you do?

16You receive seven unordered steps for connecting a printer, including a restart and a test page, for a one-page office guide due today. How would you structure the procedure?

17Ten users report 'Sync failed' after installing desktop app version 4.2, and support needs a troubleshooting page in three hours. How would you organize it?

18Version 2.6 ships tomorrow with two new filters, one renamed button, and an internal database migration. What belongs in the customer release notes?

19Support collected 40 questions about exports, but 28 are variations of 'How do I download last month's invoices?' Should this become an FAQ entry or another document?

20Version 3.0 changes the CLI configuration format. Existing users must run a converter once, and custom keys can trigger an 'Unsupported field' error. Would you put this in release notes, a migration guide, or troubleshooting documentation?

Locked questions