What to Ask a Content Writer Before Hiring

Last updated: October 13, 2026

Quick Answer: ask 6 questions before hiring a content writer; in most cases, they should be able to explain process, research, revision, and fit in 10–15 minutes. In short: ask the questions that reveal process, judgment, and fit — not just writing samples. The right writer can explain how they shape a brief, handle edits, protect accuracy, and adapt to your audience; the wrong one talks only in generalities and promises to “make it engaging.”

What do you need to hear before you trust a writer?

You need to hear how they think about what to ask a content writer before hiring them, because the first draft is only one part of the job. A good screening call should tell you whether the writer can handle your topic, your level of revision, and your tolerance for speed versus polish. If you hear vague answers to concrete questions, that is your answer.

I would start with the basics: ask what kinds of writing they do most often, how they approach research, and what they need from you to start. Then ask for one example of a piece that involved source work, a difficult subject, or a deadline problem. A writer who can explain the trade-offs in that assignment is usually safer than one who only says “I write blog posts, landing pages, and emails.”

The question that matters most is this: can the writer show judgment? That means they can tell the difference between a topic that needs authority and one that needs voice, between a technical page and a sales page, between a quick SEO article and a piece that must survive legal or editorial review. If they cannot explain those differences in plain language, they may still write clean sentences, but they may not solve your problem.

For a quick filter, I would ask these five questions first:

1. What type of writing do you do most often?
2. How do you research a topic you do not already know?
3. What do you need from me before you start?
4. How many revision rounds do you include?
5. What kind of projects are not a fit for you?

That last question saves time. A writer who says “anything” is often telling you they have not thought hard enough about scope.

What should I ask about process and research?

You should ask how they get from a brief to a finished draft, because that tells you whether the work will be usable or a mess you have to clean up. Process is where weak writers hide. Strong writers can describe it in stages.

Ask, “How do you research a topic, and what sources do you trust first?” You want a specific answer: industry docs, standards bodies, product manuals, primary sources, interviews, or client-provided material. If the writer answers with “I use Google,” that is too thin for anything that needs accuracy. If the topic touches health, money, or law, I would want to hear caution, source discipline, and a willingness to flag limits rather than overstate claims. For regulated subjects, ask whether they are comfortable writing under review by a subject-matter expert.

Ask, “What do you do when sources conflict?” That question is gold. A good writer will say they compare dates, publication types, and original documents, then choose the strongest evidence or note the disagreement. A weaker one will act as if all sources are equal. They are not.

Ask, “How do you build an outline before drafting?” That reveals whether the writer can structure an argument instead of stacking paragraphs. It also shows whether they can write for a page that has a goal: sign-up, rank, educate, or convert.

Ask, “What do you need in the brief to avoid rework?” This helps you see what kind of manager you are dealing with. A serious writer will mention audience, target action, brand rules, examples, forbidden claims, and deadline. If they do not ask for these things, expect more back-and-forth later.

For a practical screen, I would also ask for one named process artifact: an outline, a source list, or a sample brief. You do not need a full free sample article to judge professionalism. You do need proof they can organize work before they start typing.

What should I ask about experience and proof?

You should ask for proof that matches your job, not proof in the abstract. A shiny portfolio means little if the writer cannot show a relevant category, tone, or complexity level. I would ask for 2–3 samples closest to your assignment and one piece that was harder than it looked. The harder piece matters because it shows how they handle constraints.

Ask, “Which of these samples is closest to my project, and why?” That forces a writer to compare work instead of merely listing it. A good answer will mention audience, length, search intent, technical depth, or editorial constraints. A weak answer will point to a favorite piece without explaining the match.

Ask, “What changed from draft to final?” This is a very useful question. It tells you whether they can work with editors, absorb feedback, and improve a piece after critique. If they cannot describe revisions, they may be used to writing in isolation, which is a problem for most client work.

Ask, “Have you written for this industry before?” The useful part is not the yes or no; it is the follow-up. If they have not, ask how they would ramp up. If they have, ask what they already know and where they would still check facts. That distinguishes real domain familiarity from generic confidence.

I would also ask for one sentence on results, but only if the writer can state it honestly. Not every project has clean metrics. A case study, an editorial turnaround, or a message that survived legal review can be proof enough. What you want is evidence of impact, not inflated numbers.

This is also where I would be careful about portfolio volume. Ten samples are not automatically better than three if those three match your needs. Look for relevance, not quantity.

How do I judge fit for my brand and editor?

You judge fit by asking how the writer handles tone, constraints, and pushback. A writer can be skilled and still be wrong for your brand if they write in a voice that does not belong to you. That mismatch is expensive because it usually shows up after the draft is done.

Ask, “How do you adapt to a brand voice you have not written in before?” The right answer usually includes studying existing pages, style notes, and examples of words to use or avoid. If the writer says they “match any tone,” I would be skeptical. Tone adaptation is not magic; it is careful imitation with judgment.

Ask, “How do you handle feedback when an editor wants a major rewrite?” This question separates clients who want collaboration from writers who want applause. You are listening for calm, not defensiveness. A practical writer will talk about revision limits, clarifying comments, and when they think a brief needs to change instead of the copy.

Ask, “What kind of feedback helps you most?” Good writers know what makes their work better. Some want annotated edits; some want a call after the draft; some want one decision-maker instead of five. That answer matters because the wrong feedback process can slow everything down.

Ask, “What would make you push back on a request?” A strong writer will have a boundary here. They may push back on factual claims, unethical framing, keyword stuffing, or a tone that hurts the reader. That is not stubbornness. That is editorial judgment. I would rather hire a writer who can explain why a request is weak than one who agrees to everything and ships sloppy copy.

If you need consistency across a site, ask how they handle style guides, terminology lists, and recurring phrases. A writer who can keep “lead” and “lead” from drifting across pages is useful. A writer who cannot is a source of invisible disorder.

The honest side-by-side

A specialist writer wins when the topic is narrow, technical, or reputation-sensitive. A generalist writer wins when you need volume, variety, and decent execution across common formats. I would not confuse those two.

The table hides the real decision: if factual error would hurt trust, hire the specialist. If the work is formulaic and you need a lot of it, the generalist may be the smarter fit. I would not pay niche rates for a simple listicle. I also would not save money with a generalist on a page that could trigger corrections, legal review, or customer confusion.

The weakness of specialists is scope creep. They can be too expensive or too slow for broad content programs. The weakness of generalists is depth. They may write smoothly while missing the detail that makes the piece credible. That is why I ask different questions depending on the assignment.

What are the red flags I should not ignore?

You should walk away when the answers stay vague after one follow-up. Vague answers usually mean the writer is hiding in style, not substance. A few examples are enough to know.

If a writer says they do not need a brief, that is a problem. Even strong writers need direction. If they say they never revise much because their first draft is usually right, I would be cautious. Revision is part of the craft. If they cannot explain how they handle source checking, I would not hire them for anything beyond low-risk marketing copy.

Watch for overpromising. “I can rank anything” is not a serious answer. “I can write any voice” is usually not true either. So is “I work fast and cheap.” Those phrases often hide inexperience, not efficiency.

I also pay attention to what is missing. If a writer never asks about audience, conversion goal, publishing platform, or approval chain, they may be thinking only about the sentence level. Good writing lives above that level. It has to fit a page, a reader, and a business goal.

One more warning sign: a portfolio that looks polished but comes with no explanation of role. If the writer cannot tell you what they actually contributed, the sample is not very useful. Ghostwritten work is common, and that is fine, but the writer should still be able to discuss approach without claiming credit they cannot support.

When should I hire this writer — and when should I keep looking?

Choose the writer if they can answer your questions with specifics, show relevant samples, and explain their process without hiding behind buzzwords. Choose another writer if they are cheap but vague, polished but untested in your category, or confident but allergic to revision. Choose neither if your project needs legal, medical, financial, or technical accuracy and the writer cannot show source discipline or subject review.

Exception scenarios that flip the answer

The answer flips if the project is simple, repetitive, and low-risk. In that case, a generalist with solid workflow may be the right hire even if they lack deep niche credentials.

The answer also flips if the writer is bringing a strong editorial background but little direct industry experience. For a startup blog or a brand refresh, that can be enough if they can learn fast and take direction well.

The answer flips again if your internal team already has deep subject experts. Then the writer’s job is shaping and clarifying, not inventing the facts. A strong editor-writer can outperform a niche specialist in that setup.

It flips one more time when budget is the main constraint and the work is disposable. If the piece does not affect trust, conversion, or search performance much, paying for specialty may not buy enough value.

The questions I would use in a real hiring call

I would keep the call tight and ask these in order:

• What kinds of writing do you do most often?
• How do you research a topic you do not know well?
• What do you need from me before you start?
• Which sample is most like my project, and why?
• How do you handle revision?
• What would make you say no to a project like this?

Those six questions usually tell me enough. If the writer answers them clearly, I know they can probably handle the work. If they dodge them, I know that too.

FAQs

How many writing samples should I ask for?

Two to three relevant samples are enough in most cases. More than that often creates noise instead of clarity.

Should I ask for a paid test?

Only if the project is ongoing, high value, or hard to judge from samples alone. For a one-off low-stakes assignment, a detailed sample review is usually enough.

Is subject-matter experience required?

No, but it helps when the topic is technical, regulated, or reputation-sensitive. For simpler marketing pieces, strong editorial judgment may matter more.

What if the writer is great but outside my industry?

That can still work if they research well, ask smart questions, and accept review from a subject expert. I would not use that person for anything where a factual miss would be costly.

What is the single best question to ask?

Ask, “How would you approach this specific project?” A strong answer shows research thinking, audience awareness, and practical judgment in one shot.

Key takeaways

• I would screen for process, not just polished samples.
• The best answers sound specific, not impressive.
• Deep niche knowledge matters most when mistakes carry cost.
• Revision comfort is a better sign than raw confidence.
• A writer who knows when to push back is usually safer than one who agrees to everything.
• If the project is high-stakes and the writer cannot explain source handling, keep looking.

Source notes

I rely on standard editorial practice and widely used source-quality norms from organizations such as the Associated Press Stylebook, the Society for Editors and Proofreaders, and the Poynter Institute.

Drafted with AI; not yet reviewed by a person.