Writing & communication interview questions
9 questions across 4 sections, in the order you would learn them. Every answer here is one that works — but an answer you have read is not an answer you can give, so use Test yourself and say it out loud first.
Work nobody can follow has not landed
Read the section that teaches thisIf this comes up in an interview
How do you structure a technical write-up?
Problem and why it matters, what is missing from existing approaches, what you did, what happened with numbers, and what it means and does not mean. Written so the abstract and figures carry the contribution on their own.
Why state limitations explicitly?
An unacknowledged limitation found by a reviewer reads as a flaw. The same limitation stated by the author reads as scope and rigour. It also stops readers drawing conclusions the evidence does not support.
Then they push further
What separates a real limitation from a decorative one?
Whether writing it costs you something. A real limitation narrows a claim you made, says which direction it would move the result, and is checkable — all four collections are English technical documentation, and we expect the gain to shrink on prose without headings because the method keys on section boundaries. A decorative one could be pasted into any paper in the field: results may not generalise to all settings. Reviewers read hundreds of the second kind and discount them instantly.
Your experiment was one benchmark on one model. How do you state the result?
At the highest rung the evidence reaches, which is the specific one: accuracy improved by 3.2 points on GSM8K with Llama-3-8B, averaged over five seeds with a standard deviation of 0.6. Not our method improves reasoning, which would need several benchmarks, families and scales. And not merely our method scored higher on our run, which declines to generalise at all and leaves a reader with nothing they can use. The worst option is the one most papers take: the broad claim in the abstract and the narrow one in the results, so the paper visibly contradicts itself and the reviewer has to guess which version you believe.
What gets marked up. Strong answers name the claim and the evidence it requires in the same breath, and treat precision as a way of making the claim stronger rather than as a retreat.
Revising, reviewing and responding
Read the section that teaches thisIf this comes up in an interview
How do you get useful feedback on a draft?
Ask a specific question, and ask the reader to state the main contribution in one sentence. If they cannot, the draft is not communicating it, whatever the quality of the prose.
How do you handle a reviewer who misunderstood your work?
Treat it as evidence the draft allowed the misunderstanding and revise the text so the next reader does not repeat it. Arguing the reviewer was wrong rarely helps.
A reviewer asks for an experiment you think is the wrong experiment. What do you write?
Accept the observation behind the request before addressing the request, because the observation is usually correct even when the proposed fix is not. Then narrow whatever claim prompted it, decline the specific experiment with a technical reason — what your existing runs varied, and why more of them would not answer the question being raised — and name the experiment that would settle it, adding it to the limitations. Conceding the claim while declining the method is a stronger position than either capitulating or arguing, and it rests on knowing exactly what your own experiment varied.
Then they push further
What are the ways a response loses a reviewer?
Agreeing warmly and changing nothing, which is visible immediately and reads as bad faith. Answering an adjacent question, which reads as evasion. And arguing about whether they should have been confused, which is the most tempting and never worth it: their confusion is data about the text and it is the only data of that kind you get before publication.
What gets marked up. Marked up for separating the observation from the requested remedy, and for naming what would settle it. Candidates who either fold on every point or defend every point both score badly.
Show me how you would tighten a paragraph.
Work in one pass over mechanical things before touching anything else: delete the throat-clearing openers, replace quantity words with quantities, cut stacked hedges down to one statement plus an explicit condition, and move the result to the first sentence. A useful crude check is how many digits the paragraph contains — an abstract with none is usually an abstract with no evidence in it. Protect three things from the cut: the sentence saying what the result does not show, the sentence dispatching the obvious alternative, and any definition of a term you are using non-standardly.
Writing a paper section by section
Read the section that teaches thisIf this comes up in an interview
How do you structure the experiments section of a paper?
Around the claims in the introduction. Each claim gets the experiment that supports it, with fair baselines and variance reported, followed by ablations that attribute the gain and an honest account of where the method fails.
Writing about your work in public
Read the section that teaches thisIf this comes up in an interview
Tell me about something you have written or shared publicly about your work.
Describe the post, the one idea it made, the evidence behind it, what readers asked or pushed back on, and what you changed as a result. Having a link ready is better than any description.
Then they push further
What did the post say it could not establish?
Answer this specifically, because it is the real question. Name the conditions — one dataset, one model, one grader, unblinded — and the consequence you drew from them, such as that the number is an upper bound rather than a measurement. An interviewer is checking whether you know the difference between what you observed and what it supports, and that is the same judgement they need on the job.
What gets marked up. Marked up for a link, a number, and a limitation the candidate volunteers rather than concedes. A polished description of a project with no result in it scores below a small measured finding honestly bounded.
These are the questions for one topic. The whole question bank covers every topic on the site.