Copywriter Interview Questions (2026) and How to Answer

Behavioural questions (1–10)

How you've handled real situations. Answer each with one true story, in STAR order.

1. 1.Tell me about a piece of copy you're proudest of.

   What they're really asking: Can you explain craft decisions, not just show a nice result?

   Answer outline (STAR)

   • SituationA page or campaign with a real business goal attached.
   • TaskWrite something that moved the number the brief cared about.
   • ActionResearch the audience's actual words, draft several headline options, test the strongest against the goal.
   • ResultThe result it produced, and the line you'd still tighten today.

   Full sample answer (fictional example)

   A subscription box brand wanted to lower cancellations with a win-back email. I pulled twenty cancellation survey responses and noticed most people left because they felt the box was too generic, not too expensive. I wrote a subject line, 'Let's actually personalize this,' and a short email offering a quiz instead of a discount. It outperformed the previous discount-led email, recovering 11 percent of cancelling subscribers versus 4 percent before. I'm proud of it because it came from reading real complaints instead of assuming price was the problem. The line I'd still tighten is the second sentence, which repeats the subject line's idea.

2. 2.Tell me about a time a client or stakeholder rejected your copy.

   What they're really asking: Can you take a rejection and still land somewhere good?

   Answer outline (STAR)

   • SituationA headline or draft a stakeholder sent back with no clear reason.
   • TaskFind the real objection and fix it without just guessing.
   • ActionAsked what felt wrong, found it was tone not content, rewrote with examples at two tone levels.
   • ResultThe version they chose, and what you learned about reading vague feedback.

   Full sample answer (fictional example)

   I wrote a homepage headline for a fintech client that tested well internally, but the founder rejected it with just 'not quite right.' Instead of guessing again, I asked him to describe what 'right' sounded like, even loosely. He said it felt too playful for a product people trust with money. I wrote two versions at different formality levels and showed both side by side with his original concern written above them. He picked the more formal one immediately. I learned that vague feedback often hides a specific, nameable discomfort, and it's faster to ask for it directly than to guess three more times.

3. 3.Describe a time you had to write in a voice very different from your own.

   What they're really asking: Can you set your own style aside for the brand's?

   Answer outline (STAR)

   • SituationA brand with a tone of voice guide unlike anything you'd written before.
   • TaskSound convincingly like them, not like you.
   • ActionRead a stack of their existing copy, built a swipe file of their phrases and rhythms, drafted and checked it against the guide line by line.
   • ResultFeedback from the brand team, and copy they kept using after you left the project.

   Full sample answer (fictional example)

   I took on freelance work for a legal services brand whose voice guide called for 'warm but precise,' which was far from my usual punchy style. I read through a year of their blog posts and client emails and built a short list of phrases and sentence patterns they reused, like leading with reassurance before explaining a process. I drafted a service page using that pattern and checked it line by line against their guide before submitting. Their in-house editor made almost no changes, which rarely happens on a first draft, and asked me back for three more pages the following month.

4. 4.Tell me about writing under a tight deadline.

   What they're really asking: Do you protect quality when time is short, or just produce faster?

   Answer outline (STAR)

   • SituationA launch email or landing page needed same day.
   • TaskShip something on-brand and accurate, fast.
   • ActionConfirmed the one must-have message, wrote a single strong draft instead of several weak ones, got a quick second pair of eyes before sending.
   • ResultWhat shipped on time, and the follow-up polish you added after.

   Full sample answer (fictional example)

   Our biggest customer found a critical bug on a Friday afternoon, and marketing needed an apology and fix-update email out same day. I called the product lead to get the one fact that mattered most, which was the expected fix time, and wrote a single draft instead of circulating options, since there wasn't time to debate tone. I sent it to my manager for a two-minute read before it went out. It shipped within ninety minutes of the request. I followed up the next week with a longer post-mortem email once we had more detail to share.

5. 5.Tell me about a time you disagreed with an edit to your copy.

   What they're really asking: Can you push back on a bad edit professionally, and know when to let it go?

   Answer outline (STAR)

   • SituationAn editor or manager cut a line you thought was doing real work.
   • TaskGet the line back, or understand why it should go.
   • ActionAsked the reasoning, explained what the line was doing for the reader, offered a shorter version as a compromise.
   • ResultThe outcome, and whether you'd fight that battle again.

6. 6.Tell me about writing copy for a product you didn't personally like or use.

   What they're really asking: Can you write convincingly without pretending something you don't believe?

   Answer outline (STAR)

   • SituationA product or service outside your own interests or experience.
   • TaskWrite copy that was honest and still persuasive.
   • ActionTalked to actual users to find the real benefit, anchored the copy in their words rather than your opinion.
   • ResultCopy that tested well, and what it taught you about writing from research, not instinct.

7. 7.Tell me about a campaign that didn't work.

   What they're really asking: Can you own a miss and explain what you'd test differently?

   Answer outline (STAR)

   • SituationA piece of copy or campaign angle that underperformed.
   • TaskFigure out why, and avoid repeating it.
   • ActionChecked the data, compared against other variants, pulled in audience feedback where available.
   • ResultThe specific cause you identified, and the change you made on the next attempt.

8. 8.Tell me about collaborating with a designer on a piece of copy.

   What they're really asking: Can you write with layout in mind, not in isolation?

   Answer outline (STAR)

   • SituationA page where word count and visual space were both tight.
   • TaskMake the words and the design work together.
   • ActionShared drafts early, wrote flexible length options, adjusted copy once the layout was in front of you.
   • ResultThe finished piece, and what you'd brief differently next time.

9. 9.Tell me about a time you had to write about something technical you didn't fully understand at first.

   What they're really asking: Can you get up to speed fast enough to write accurately?

   Answer outline (STAR)

   • SituationA product with technical specs or mechanics new to you.
   • TaskWrite copy that was accurate and still clear to a general reader.
   • ActionInterviewed the product or engineering team, asked them to check your draft, simplified without dropping accuracy.
   • ResultThe copy that shipped, and the subject-matter expert's reaction to it.

10. 10.Tell me about managing several writing projects with competing deadlines.

    What they're really asking: Can you keep quality consistent across projects instead of just the loudest one?

    Answer outline (STAR)

    • SituationOverlapping deadlines for different stakeholders in the same week.
    • TaskDeliver all of them on time without any getting rushed.
    • ActionMapped out effort versus deadline for each, communicated realistic timing early, batched similar writing tasks together.
    • ResultWhat shipped on time, and what you'd renegotiate earlier next time.

Technical and role-skill questions (11–22)

Can you do the work itself? Think out loud and name the trade-offs.

1. 11.Walk me through how you write a headline.

   What they're really asking: Do you have a repeatable process, or just wait for inspiration?

   Answer outline

   • Start from the single benefit or tension the reader cares about most.
   • Write ten to twenty variations fast before judging any of them.
   • Pick finalists for clarity first, then punch, and read them aloud.

   Full sample answer (fictional example)

   I start by identifying the single benefit or tension the reader cares about most, usually from research rather than my own assumption. Then I write ten to twenty variations quickly without judging them, mixing direct benefit statements with curiosity angles and specific numbers where I have them. Only after that do I start cutting: first for clarity, since a headline nobody understands can't convert, then for punch. I read the finalists aloud, because anything awkward to say out loud is usually awkward to read too. For anything high-stakes, I'll suggest testing two finalists rather than picking by instinct alone.

2. 12.How do you adapt tone of voice across channels for the same brand?

   What they're really asking: Can you flex within a brand's rules instead of writing the same way everywhere?

   Answer outline

   • Start from the brand's core voice attributes, then adjust formality and length to the channel.
   • A tweet, an email subject line and a landing page headline shouldn't read interchangeably.
   • Check against the brand's style guide or past approved copy before sending.

   Full sample answer (fictional example)

   I start from the brand's core voice attributes, like 'confident but not arrogant,' and treat those as fixed. What changes by channel is formality and length. A push notification might use four words and an exclamation point if the brand allows it, while a landing page headline carries more weight and gets a fuller sentence. An email subject line sits somewhere between the two. Before sending anything, I check it against the style guide or recent approved examples, because tone drifts easily when you're writing fast across several channels in one day.

3. 13.How do you edit your own first draft?

   What they're really asking: Can you cut your own weak lines, or do you need someone else to do it?

   Answer outline

   • Leave the draft overnight if possible, then read it as the audience would.
   • Cut the opening until it starts at the actual point.
   • Read every line and ask if it's doing a job; if not, cut it.

4. 14.What makes a call to action work?

   What they're really asking: Tests whether you understand what makes a call to action convert.

   Answer outline

   • Specific and concrete beats vague: 'Start your free trial' over 'Learn more'.
   • Match the CTA's commitment level to how warm the reader already is.
   • Test wording changes one at a time so you know what moved the number.

   Full sample answer (fictional example)

   Specificity usually beats a safe, vague phrase. 'Start your free 14-day trial' tells the reader exactly what happens next and removes hesitation that 'Learn more' doesn't address. I also match the CTA's commitment level to how warm the reader already is; someone on a cold ad shouldn't see 'Buy now' as the only option. Button copy, surrounding microcopy and the visual design all affect conversion together, so I try not to over-credit the words alone. When I can, I suggest testing one wording change at a time so we actually learn what moved the number.

5. 15.How do you write for SEO without sounding stiff?

   What they're really asking: Can you satisfy search intent and still write something a human enjoys reading?

   Answer outline

   • Put the target phrase in the title and first paragraph naturally, not forced.
   • Write for the question the searcher actually has, then layer in related terms.
   • Read it aloud; if a phrase sounds like it was typed into a search box, rewrite it.

6. 16.How do you keep a long piece of copy on-brief?

   What they're really asking: Do you drift from the point under word count pressure?

   Answer outline

   • Keep the brief's single objective visible while drafting.
   • Cut any paragraph that doesn't serve that objective, even if it's well written.
   • Re-read the brief once more before calling it done.

7. 17.What's your process for proofreading before copy goes live?

   What they're really asking: Attention to detail, which is non-negotiable in this work.

   Answer outline

   • Check facts, names, numbers and links separately from style.
   • Read backward from the end, or aloud, to catch what skimming misses.
   • Have a second person check anything client-facing or paid.

8. 18.How do you write a subject line that gets an email opened?

   What they're really asking: A narrow, high-stakes piece of copy worth a dedicated question.

   Answer outline

   • Lead with specific value or curiosity, not a vague teaser.
   • Keep it short enough to survive mobile preview truncation.
   • Test two or three options rather than relying on gut feel alone.

9. 19.How do you write effectively for a character or word limit, like a push notification or meta description?

   What they're really asking: Constraint-writing skill, common in digital copy.

   Answer outline

   • Decide the one idea that must survive the cut, then build only around it.
   • Cut modifiers and connector words before cutting content words.
   • Count characters as you go rather than writing long and trimming at the end.

10. 20.What's your approach to writing copy that needs to work across multiple markets or languages?

    What they're really asking: Can you write copy that survives translation and localization?

    Answer outline

    • Avoid idioms and wordplay that won't translate cleanly.
    • Keep sentence structure simple enough for a translator to preserve meaning.
    • Flag anything culturally specific before it goes to localization.

11. 21.How do you use customer reviews or support tickets as research for copy?

    What they're really asking: Can you find real language instead of guessing at the audience's words?

    Answer outline

    • Pull recurring phrases customers use to describe the problem or benefit.
    • Use their actual words over your own paraphrase where it's stronger.
    • Watch for complaints that reveal a benefit nobody's writing about yet.

12. 22.How do you know when a piece of copy is actually done?

    What they're really asking: Can you stop polishing and ship, without shipping something sloppy?

    Answer outline

    • Check it against the brief's objective, not your own taste.
    • Confirm facts, links and formatting are correct.
    • Read it once more as a stranger would, then stop.

Take-home or live exercise: tips

Copywriter interviews often include a timed writing test, a live rewrite of weak existing copy, or a request to produce three headline options for a given brief on the spot.

• Ask clarifying questions about audience and goal before writing a single word, even under time pressure.
• Write more options than you think you need, then narrow down out loud so your thinking is visible.
• In a rewrite exercise, name what's wrong with the original before fixing it, so the interviewer sees your diagnosis.
• Keep one version simple and safe alongside a bolder option, so you show range, not just one instinct.

Situational questions (23–30)

Scenarios that test judgement: say what you'd do first, and why.

1. 23.A client gives you a brief with no clear goal or audience. What do you do?

   What they're really asking: Can you get what you need without annoying the client?

   Answer outline

   • Ask two or three specific questions rather than sending the brief back wholesale.
   • Propose a goal and audience based on what you know, for them to confirm or correct.
   • Note the gap so future briefs come in more complete.

   Full sample answer (fictional example)

   I don't send the brief back wholesale, since that usually just delays things and can read as unhelpful. Instead I ask two or three specific questions, like who typically reads this page and what they should do after reading it. If I already have context from past work with the client, I'll propose a goal and audience myself and ask them to confirm or correct it rather than leaving it fully open. That's usually faster than a back-and-forth. I also note the gap afterward so the next brief I receive from that client comes in more complete.

2. 24.Legal or compliance wants to water down a strong line. How do you respond?

   What they're really asking: Can you protect the work while respecting a real constraint?

   Answer outline

   • Understand exactly what the concern is before arguing.
   • Offer an alternative that keeps the energy but removes the risky claim.
   • Accept the final call; it's not your name on the regulatory risk.

   Full sample answer (fictional example)

   I ask what specifically concerns them before arguing for the original line, since sometimes it's one word, not the whole sentence. Once I understand the actual risk, I try to offer an alternative that keeps most of the energy while removing the exposure, rather than accepting the first flattened version they suggest. For one campaign, 'proven results for everyone' became 'results most customers see within 30 days,' which kept specificity and sounded more credible anyway. If they still want the softer version after that, I accept it. It's not my name on the regulatory risk, and a weaker line beats a legal problem.

3. 25.You're given six pieces due this week and the brief for one is unclear. How do you prioritise?

   What they're really asking: Can you keep output moving without quietly shipping something wrong?

   Answer outline

   • Flag the unclear brief immediately rather than guessing and writing anyway.
   • Work the clear briefs first while waiting for the answer.
   • Timebox how long you'll wait before escalating.

4. 26.A stakeholder keeps rewriting your copy into something weaker. What do you do?

   What they're really asking: Can you address a pattern, not just one bad edit?

   Answer outline

   • Look for the pattern: is it a voice mismatch, risk aversion or personal preference?
   • Raise it directly and ask what they're trying to protect.
   • Propose a lighter review step, like approving the angle before the full draft.

   Full sample answer (fictional example)

   I look for the pattern before reacting to any one edit, because a single weak edit might just be a bad day, but a repeated one usually points to something specific, like risk aversion or a voice mismatch I haven't picked up on. In one case, I realized a stakeholder kept softening urgency in CTAs because a past campaign had gotten complaints about being pushy. Once I understood that, I raised it directly and asked what she was trying to protect. We agreed on a lighter review step, approving the angle before I wrote the full draft, which cut the rewriting almost entirely.

5. 27.A/B test results say your weaker-feeling draft actually converts better. What do you do?

   What they're really asking: Will you trust data over your own taste?

   Answer outline

   • Trust the result over personal preference, once the test is sound.
   • Check the test size and setup before fully accepting the result.
   • Try to understand why it won, so you can apply the lesson elsewhere.

6. 28.You're asked to write copy for a claim that sounds exaggerated. What do you do?

   What they're really asking: Will you flag a credibility or compliance risk?

   Answer outline

   • Ask for the evidence behind the claim before writing it.
   • Suggest a version that's accurate but still compelling.
   • Escalate if asked to publish something you believe is false.

7. 29.A stakeholder wants to cram five messages into one landing page headline. How do you handle it?

   What they're really asking: Can you push back on scope creep in a single piece of copy?

   Answer outline

   • Explain that one strong message beats five diluted ones.
   • Offer to carry the other messages in subheads or supporting copy instead.
   • Show a mocked-up comparison if words alone don't land the point.

8. 30.You inherit a style guide that contradicts what actually performs well. What do you do?

   What they're really asking: Can you challenge an established rule with evidence?

   Answer outline

   • Bring data or examples rather than just opinion.
   • Propose updating the guide rather than quietly ignoring it.
   • Respect it until it's formally changed, even if you disagree.

Red flags to avoid in your answers

Each one is quick to fix before the day.

1. Showing portfolio pieces without explaining the thinking or the result.

   Pick work you can discuss in depth: the brief, the choice you made, and what happened after.

2. Getting defensive about edits to your own copy.

   Treat edits as information about the reader or brand, not a judgment on your skill.

3. Writing clever copy that drifts from the brief's actual goal.

   Re-read the brief before calling any draft finished, and cut lines that don't serve it.

4. Having no process, just 'waiting for the right words.'

   Describe a repeatable method: research, volume of drafts, then ruthless cutting.

How to prepare for a copywriter interview in 7 days

An hour or two a day is enough; the order matters more than the length.

1. 1

   Day 1: Samples walkthrough

   Pick three to five pieces and write out the brief, your key decision and the result for each, so you can talk through them without notes.

2. 2

   Day 2: Voice-matching drill

   Take a brand you don't normally write for and produce 100 words in their voice, checking it against their real published copy.

3. 3

   Day 3: Headline volume

   Pick one product and write twenty headline variations in thirty minutes, then narrow to your top three and say why.

4. 4

   Day 4: Rewrite practice

   Find a weak piece of marketing copy online and rewrite it, timing yourself at under ten minutes.

5. 5

   Day 5: Brief-reading practice

   Take a vague brief and write down the three clarifying questions you'd ask before writing anything.

6. 6

   Day 6: Narrative drafts

   Write out four STAR stories: proud work, a rejected draft, a tight deadline and a disagreement over an edit.

7. 7

   Day 7: Practice run

   Do a mock interview with a timed writing test and a portfolio walkthrough, then rest.

Questions to ask the interviewer

Pick two or three; the answers tell you whether you want the job.

1. Is there a documented brand voice or style guide I'd be writing to?
2. Who signs off on copy, and how many rounds of review are typical?
3. What does a brief usually include when it reaches the writer?
4. How is copy performance measured here, if at all?
5. What's an example of copy that performed better than expected recently?

Preparation tips

• Bring three to five portfolio pieces you can explain in detail, including one that didn't work and what you'd change.
• Practise rewriting a weak paragraph live, out loud, in under five minutes.
• Research the company's existing copy and tone before the interview, not during it.
• Prepare one honest story about taking tough feedback well.

Prepare the general questions too: tell me about yourself, why do you want to work here? and why are you leaving? Afterwards, send a thank-you email; when the offer comes, negotiate the salary.