45 Content Writer interview questions to ask job applicants

Most content writer interviews fail in the first ten minutes, and not because the questions are bad. They fail because the questions ask a writer to describe their craft instead of showing it. Anyone can describe a process. Far fewer can walk you through the brief they were handed, the draft they threw away, and the one line an editor changed that made the piece work.

The market gives you room to be picky, and also a reason to move. The Bureau of Labor Statistics counted 135,400 writer and author jobs in 2024, with a median wage of $72,270 and about 13,400 openings a year through 2034. That is a steady, mid-sized market, not a scramble. A slow, sloppy interview loop will still lose you the three candidates worth hiring.

So here are 45 content writer interview questions, grouped by what each group actually measures, with what to listen for under every one. Use them to build a structured interview: same questions, same order, same scoring notes for every candidate. That structure is not a formality. In the largest recent meta-analysis of selection methods, structured interviews came out with a mean validity of 0.42, the highest of any standalone predictor Sackett and colleagues examined in 2023. Unstructured ones, the kind that drift into a chat about favorite authors, sit well below that.

TL;DR

• Ask about shipped work, not process theory. A candidate who can reconstruct a brief, an edit, and a result is telling you something a portfolio cannot.
• Score every candidate on the same questions in the same order. Structured interviews are the strongest standalone predictor in the current selection research, at a mean validity of 0.42.
• Split your 45 questions across three jobs: what they know, how they work, and how they handle being edited.
• Test the craft separately from the conversation. A 45-minute writing exercise against a real brief beats another hour of talking.
• Ask how they use AI, and expect a specific answer. Vagueness here is the single most common tell in 2026.
• Watch for the writer who blames every weak piece on the client. That pattern rarely improves after hire.

Which content writer interview questions actually work?

The questions that work make a candidate show their thinking on real work, not describe it in the abstract. Ask about a piece they shipped, the brief behind it, the edit that changed it, and how they knew it worked. Vague questions get rehearsed answers. Specific ones get evidence.

That is the whole idea behind the Testlify Competency-to-Evidence Matrix: start with the role, map it to the competencies that actually matter, then connect each competency to evidence you can collect and compare. For a content writer, five competencies carry most of the weight, and each one has a natural place to look.

The point of the matrix is that no single question covers a competency. A portfolio shows finished work chosen by the candidate, with unlimited time and a topic they picked. None of those conditions exist on the job. The interview is where you find out what happens without them.

Is dissatisfaction a necessary trait in a writer interview?

Not a required trait, no. But a useful probe. "Discontent is a necessary requirement for a writer" is a line writers argue about, and asking a candidate whether they agree tells you how they treat their own drafts. Strong writers describe dissatisfaction as a working habit. Weak ones treat it as a personality badge.

Why discontent is a necessary requirement for a writer in interviews

The claim shows up often enough that plenty of candidates have seen it before, which is exactly why it is worth asking. It is not a trick question and there is no correct answer. What you are listening for is whether the candidate connects the idea to something they actually do.

A good answer sounds mechanical rather than romantic. The candidate describes reading a published piece back and finding the paragraph that does not earn its place. They talk about a headline they rewrote eleven times, or a section they cut after it had already been approved. Dissatisfaction, in their telling, is a step in the process with an off switch, because a writer who is never satisfied never ships.

A weak answer stays abstract. It treats discontent as a quality writers have rather than something they do, usually with a nod to suffering and the creative temperament. Push once: "What is the last thing you changed after you were happy with it?" The pause tells you plenty.

There is also a version of this that should worry you. Some candidates use discontent to explain why nothing they produce is ever finished, why deadlines slip, why the last three editors did not understand the work. Perfectionism that never ships is a delivery risk, not a craft signal. Ask how they decide a piece is done, and who gets to make that call.

What general questions should you ask a content writer?

These 15 open the interview and cover research, audience, and search. Keep them in this order for every candidate so the answers stay comparable.

1. Walk us through a piece you are proud of. What was the brief, and what did you change from the first draft?
2. How do you research a topic you know nothing about? Name the last one.
3. What makes a source good enough to cite, and what makes you drop one?
4. Tell us about a time you found a claim that turned out to be wrong. What did you do?
5. How do you handle a stat you cannot verify but the brief asks for?
6. How do you work out who you are writing for when the brief does not say?
7. Describe a piece you wrote for an audience very different from you.
8. How does your writing change between a landing page, a long guide, and an email?
9. What is the first thing you cut when a draft runs long?
10. How do you decide the structure of a piece before you write it?
11. How do you approach keyword research, and where does it sit in your process?
12. What does search intent mean in practice? Give an example where you got it wrong.
13. How do you write for search without the piece reading like it was written for search?
14. How do you know whether something you published worked?
15. Tell us about a piece that underperformed. What did you learn?

What to listen for: specifics over frameworks. Question 2 separates writers who have a research routine from writers who open a search engine and start typing. Question 12 is the one most candidates fumble, because admitting you misread intent means admitting a page failed. Question 15 is the highest-signal question in this block, and a candidate who has no answer has probably never checked.

Strong answers to question 1 sound like this in shape: the candidate names the brief and its constraint (a launch date, a word count, a nervous legal reviewer), describes what the first draft got wrong, and explains what changed and why. Weak answers describe the finished piece and how well it did, which is a summary, not a process.

Which behavioral questions reveal how a writer works?

Writing is mostly rewriting, and rewriting is mostly other people's opinions. These 15 look at deadlines, feedback, and what happens when the work goes sideways.

1. Describe a time you received hard feedback on a piece. What did you change?
2. Tell us about an edit you disagreed with. How did you handle it?
3. When was the last time you cut something you loved? Why?
4. Walk us through your revision process on a piece that needed three rounds.
5. How do you respond when a reviewer rewrites your work in their own voice?
6. Describe a deadline you missed. What caused it?
7. How do you plan a week with four pieces due and one client who keeps changing the brief?
8. Tell us about a time you had to write on a topic you found dull.
9. What do you do when you are stuck on an opening?
10. Describe a piece that needed sensitivity. How did you handle the wording?
11. How do you work with a designer or an SEO lead who wants different things?
12. Tell us about a time you pushed back on a brief. What happened?
13. How do you keep a consistent voice across a team of writers?
14. Describe a mistake that made it to publication. What did you do next?
15. What does a good handover look like when you leave a project mid-way?

What to listen for: ownership and specificity. Question 21 is the honesty test, and "I have never missed a deadline" is the wrong answer in a job where briefs change weekly. Question 29 matters more than most teams realize, because a writer who hides a published error costs you more than one who catches it late. In question 20, listen for whether the candidate can separate a voice preference from a correctness issue. Both come back as edits, and they need different responses.

A strong answer to question 17 does not end in surrender or a fight. The candidate makes the case once, in terms of the reader rather than their own taste, then accepts the call and moves on. Writers who cannot do that generate a lot of friction per published word.

Which personality questions predict craft and grit?

The last 15 get at motivation, standards, and how a candidate thinks about the tools now sitting in the middle of the job.

1. What kind of writing do you do when nobody is paying you?
2. Which writer or publication do you read for craft, and what do you take from them?
3. What is a rule of writing you have deliberately broken, and why?
4. Do you agree that discontent is a necessary requirement for a writer?
5. How do you know when a piece is finished?
6. What is the last thing you learned that changed how you write?
7. What part of the job do you like least, and how do you get through it?
8. What would make you leave a writing job?
9. How do you want your work to be reviewed?
10. What does a good week of writing look like for you?
11. How do you use AI in your writing, concretely? Walk us through the last time.
12. Where has AI produced something you had to throw away?
13. What in your process would you never hand to a model, and why?
14. How do you fact-check something a model gave you?
15. If your role added 30% more editing and 30% less drafting, would you still want it?

What to listen for: questions 41 to 44 are the ones worth slowing down on. The honest labor-market picture is that this part of the job is moving. Indeed Hiring Lab's AI at Work Report put 26% of jobs in the "highly transformed" bucket for generative AI and found that 46% of skills in a typical US job posting are set for hybrid transformation. Writing sits squarely in that mix. A candidate who says they never touch AI and a candidate who cannot name a single thing it got wrong are both telling you they have not thought about it.

The wider skills picture points the same way. The World Economic Forum's Future of Jobs Report estimates that 39% of a worker's existing skills will be transformed or outdated between 2025 and 2030, and names analytical thinking as the core skill employers want most, cited by 7 in 10 companies. For a writer, that is an argument for hiring on judgment rather than on output speed. Speed is the part that is changing fastest.

Question 45 is a filter, not a trap. Plenty of writing jobs are quietly becoming editing jobs, and a candidate who lights up at drafting but dreads revision will be unhappy within two quarters. Better to hear it now.

Question 34 is the discontent question from earlier, placed here deliberately. By this point in the interview the candidate is warmed up and less likely to give you the polished version.

How should you test a content writer's skills?

Test the craft separately from the conversation, and keep the test short enough that a good candidate will actually do it. A 45-minute exercise against a real brief tells you more than a second interview. Pay for it if it runs longer than an hour, and never ask for work you intend to publish.

Four things are worth measuring, and they do not all need the same format:

• Writing against a brief. Give a real brief, a word count, an audience, and one awkward constraint. What comes back shows structure, tone control, and whether they read the brief at all.
• Editing. Hand them 400 words of weak copy and ask for a rewrite with a note explaining the three biggest changes. This is the fastest read on craft you will get, and it is the skill most portfolios hide.
• Grammar and mechanics. A short grammar and editing test is a floor check, not a ranking. Use it to screen, not to choose.
• Search and structure. Ask them to outline a page for a given query and justify the sections. You learn whether they think about intent or about keyword placement.

A structured content writer assessment is useful here mainly because it makes candidates comparable. Scoring a hundred writing samples by feel is where good processes quietly fall apart, and the tenth sample never gets the attention the first one did. If you are hiring adjacent roles at the same time, the same approach works for technical writer interview questions and for the copy editor interview set.

Pro Tip: send the writing exercise before the interview, then build 15 minutes of the interview around it. Ask what they would change now, what they cut, and what the brief did not tell them that they wished it had. You get a live edit-and-defend session out of work they have already done, and it costs the candidate nothing extra.

On portfolios: read them for range, not for polish. Every piece in a portfolio was chosen by the writer, written to a topic they liked, with time they controlled. That is the opposite of the job. The useful question is not "is this good" but "what would this have looked like with two days and a brief they disagreed with".

What red flags should you watch for?

Six patterns come up again and again, and most of them are audible in the first twenty minutes.

• Every weak piece was someone else's fault. Clients, editors, and briefs take all the blame. This rarely improves after hire.
• No numbers, ever. A writer who has published for three years and cannot say whether anything worked has not been paying attention to the point of the work.
• Portfolio pieces they cannot explain. Ask about the brief behind any sample. Hesitation here sometimes means the work was not theirs.
• Vagueness about AI. Not the use of it. The vagueness. "I use it a bit for ideas" after three follow-ups is a non-answer.
• Craft talk with no shipping. Strong opinions about prose, thin evidence of finished work at volume.
• Defensiveness in the rewrite exercise. Watch how they take a note on their own paragraph. You are hiring for the next two years of edits, not for this draft.

One caveat worth saying plainly. Writers coming from agencies, journalism, or freelance work often have gaps in analytics access rather than gaps in judgment. If a candidate cannot cite performance numbers, ask whether they ever had access to them. The answer changes what the silence means.

Hire content writers on evidence, not guesswork

Testlify gives hiring teams role-based assessments, writing and editing exercises, cognitive and personality tests, and structured reviewer scoring, so the shortlist is built on comparable evidence before the first call rather than on a stack of self-selected samples. Reviewers score against the same criteria, and the results sit in one place instead of a spreadsheet nobody trusts.

Want to see what a content writer assessment looks like against your own brief? Book a 30-minute demo and bring a live role.

Key Takeaways

• Structure beats rapport. Structured interviews carry a mean validity of 0.42, the highest of any single predictor in the current selection research, while unstructured conversations track interviewer preference more than candidate ability. Practically: fix the questions and the order before the first call, and write scoring notes as you go rather than after.
• Ask about shipped work, not process. Process answers are rehearsable and every candidate has one. A reconstructed brief, a discarded draft, and a named edit cannot be faked at speed. Practically: open with question 1 and stay on it for five minutes before moving on.
• Test editing, not just writing. Most content roles are more revision than drafting, and revision is the skill portfolios are built to hide. Practically: send 400 words of weak copy and ask for a rewrite plus three reasons.
• Treat AI questions as judgment questions. With 26% of jobs in the highly-transformed bracket for generative AI, how a writer decides what to hand a model matters more than whether they use one. Practically: ask for the last concrete instance and one thing it got wrong.
• The discontent question is a working-habit probe. It reveals whether a candidate revises deliberately or performs the artist. Practically: follow it with "what is the last thing you changed after you were happy with it".
• Watch for blame patterns early. A candidate who attributes every weak piece to a client or an editor will bring that to your team. Practically: ask about a published mistake and listen for what they did next, not who caused it.
• Keep exercises short and paid past an hour. Long unpaid tests lose the candidates with options, which is the group you are trying to hire. Practically: cap at 45 minutes and never publish submitted work.

FAQs