Copywriter interview questions

I start from one core proposition and reshape it to each channel's context and attention span instead of pasting the same line everywhere.

• On out-of-home I get maybe six words and one idea, so I keep only the single strongest line.
• In paid social I lead with a scroll-stopping hook and one tight CTA.
• In email I have room to build context and proof before the ask.
• The promise and voice stay constant while length, structure, and specificity flex per channel.

I first pin down the single most ownable thing about the product and who it is for, then generate widely before I judge.

• I write dozens of options across angles: benefit-led, provocative, playful, and plain.
• I read them aloud and cut anything a competitor could also say.
• I pressure-test the shortlist against the brand voice and how each holds up next to the logo.
• A strong tagline is short, true, and hard to claim about anyone else.

I turn abstract adjectives into concrete writing rules before I draft.

• Confident means I make direct claims and cut hedging like just, maybe, and we think.
• Warm means I use second person, contractions, and everyday words instead of corporate jargon.
• I keep a short do and don't table with real example sentences so my copy and any reviewer check against the same bar.

I let the complexity of the sale and the reader's awareness level set the length, not a personal preference.

• A high-consideration or expensive product earns long-form so I can handle objections and stack proof.
• A skeptical cold audience also needs room to build trust before the ask.
• A familiar brand, a retargeting ad, or a simple impulse buy wants short and punchy.

AIDA is Attention, Interest, Desire, Action, and I treat it as a checklist for whether a piece moves someone from a glance to a click.

• I open with a hook tied to the reader's problem, then build interest with a relevant benefit.
• I create desire with proof or a vivid outcome, then close with one clear action.
• I do not force all four into every asset, so a display ad lives on Attention and Action while a landing page runs the full arc.

PAS is Problem, Agitate, Solution: name the pain, make it feel real and costly, then present the product as the relief.

• I reach for it when the audience already feels the problem but has been tolerating it.
• Agitation raises the urgency to act now rather than later.
• I keep the agitate step honest and specific, since overdone fear reads as manipulative and hurts brand trust.

The headline has to make the single most important promise clear in the time it takes to skim.

• I lead with the specific outcome the reader wants, not the product category.
• I pair a benefit-led main headline with a subhead that adds the how or the proof.
• I match the message to the ad or link that brought them there so there is no scent break.
• Then I write five to ten versions and test rather than trusting the first one I like.

I make the CTA specific about what happens next and frame it around the reader's benefit rather than the effort.

• Start free trial or Get my quote beats Submit because it answers what do I get.
• Benefit-led wording lowers the perceived risk of clicking.
• I mind the surrounding microcopy, like a no card required note under a signup button, since those words often remove the last hesitation.

I map it to the subscriber's first days, not to what we want to sell.

• Email one delivers the promised value and sets expectations.
• The next couple build trust with a useful story or the founder's why.
• Only after some credibility exists do I make a clear offer.
• Each email has one job and one CTA, and I write the subject lines with as much care as the body.

Curiosity plus a clear hint of value, kept specific and honest to the content inside.

• I favor concrete over vague, so Your invoice is ready beats Big news.
• I keep it short enough to survive mobile truncation and skip spammy caps and exclamation stacks.
• The test is whether the body pays off the promise, because a great open with a letdown inside kills future opens.

I start with a hypothesis, not a random variant, for example that leading with price beats leading with the benefit for a bargain audience.

• I change one meaningful element at a time so I can attribute the result.
• I keep everything else identical and define the success metric and run length before we peek.
• Testing benefit versus price versus social proof teaches me something reusable, while testing a comma placement wastes traffic.

First I check the result is real before I react to it.

• I confirm it reached enough conversions and ran long enough rather than being noise from a tiny sample.
• If it is real, I try to learn why the losing angle failed instead of just reverting.
• A benefit that flopped tells me something about what the audience actually cares about, which I feed into the next hypothesis.

I tell the user plainly what went wrong and, more importantly, how to fix it, in calm human language.

• Instead of Invalid input I write Enter an email like name@example.com, so the message doubles as instruction.
• I drop blame and error codes that mean nothing to the user.
• I match the brand voice but dial down jokes, because a frustrated person wants out, not entertainment.

I treat the empty state as an onboarding moment rather than a dead end.

• I explain what will appear here so the blank screen is not confusing.
• I nudge the one action that fills it, with the button right there.
• For an empty projects screen I might say No projects yet, create your first to get started, so the copy encourages rather than just describing emptiness.

I go past demographics to the actual language and pains people use.

• I mine customer reviews, support tickets, sales call notes, and community threads.
• I look for the exact phrases customers use to describe the problem and the outcome they want.
• I fold those words back into the copy so it sounds like their own head talking, which usually beats anything I could invent from a persona doc.

I audit competitors to find the gaps and the sameness, not to borrow lines.

• When everyone claims fast and easy, that is a signal to stake a different, more specific angle.
• Reading their copy shows me which objections they leave unanswered.
• I use it as a map of the conversation already in the customer's head so I can enter it from a fresh direction.

I list the real reasons someone would hesitate and answer each where it naturally arises in the read.

• The usual doubts are too expensive, will it work for me, and is it hard to switch.
• Objection handling can be a guarantee near the price, a FAQ block, a comparison, or a testimonial from someone just like the reader.
• The goal is to reach the CTA with the top three doubts already resolved so nothing stalls the decision.

I run each feature through a so what filter until it lands on something the reader feels or gains.

• A feature like 256-bit encryption becomes your data stays private even if your laptop is stolen.
• The feature earns trust but the benefit is what moves people.
• I usually keep both, leading with the benefit and using the feature as the proof underneath it.

I write to the space instead of fighting it.

• I count characters for headlines and buttons so nothing gets truncated or wraps awkwardly.
• If the constraint genuinely breaks the message, I show the designer a real example and propose different copy or a small layout tweak.
• I frame it around the user rather than my preference and collaborate early instead of dumping text over the wall.

I separate the note from the fix, since the stakeholder is usually pointing at a real problem even if their wording is worse.

• I ask what they are worried about and restate it back to them.
• I offer a version that solves that concern while protecting the clarity or voice.
• If it still comes down to taste, I back my choice with the objective or a test, then disagree and commit if it is their call.