How to Prepare for an SEO Interview

Most candidates prepare the wrong thing entirely.

They build a list. Forty questions, forty answers, memorized on the train in. Core Web Vitals. Canonical tags. The difference between a 301 and a 302 redirect. All correct. None of it useful for telling one candidate apart from the next.

Everyone on that shortlist has the same list. Same sources. Often the same wording.

So preparing for an SEO interview means preparing something nobody else can copy off a blog post. One project. Described in enough detail that somebody could try to catch you out on it.

The Interviewer Cannot Actually Test You

Think about what the room can measure.

Forty minutes. No login, no crawl, no six months of waiting to see whether your plan worked. Nobody hands a candidate a live site for the afternoon. Everything the hiring manager wants to know sits behind a delay they do not have.

So they substitute something else. They listen for one thing only. Whether you sound like a person who has watched rankings move. Or a person who has only read about it happening.

The tell is granularity. Nothing more sophisticated than that.

None of this is unfair, either. It is just the shape of the situation. Hiring into a discipline with a six-month feedback loop means guessing. Always. Your interview only decides how well-informed that guess turns out to be.

Pick One Project and Go Deep on It

Not five projects at surface level. One.

Choose whichever you touched most directly. Then reconstruct it properly. What the site looked like the week you arrived. Everything you changed. Which week each change shipped. The week anything first moved.

Write it on a single page. Dates down the left side.

This takes an evening. Most candidates skip it, since it feels like homework rather than preparation. Which is exactly why doing it separates you.

Say What Else Was Running at the Time

Here is the part almost nobody rehearses.

Organic traffic went up. Fine. Yet what else happened that quarter? Maybe the company ran paid search for the first time ever. Perhaps a competitor let their site fall over for three weeks. Or it was simply March, and March always beats February for that business.

A candidate who volunteers that unprompted sounds different straight away. Not weaker. More credible.

Try it from the other side of the table. Two people report a similar lift. One gives the number and stops there. The other gives the number, then names the paid campaign that was running alongside it. Only one of them has looked at their own results with any suspicion.

The alternative reads badly. A big round percentage claim invites exactly one thought in the listener’s head. Did you, though.

Own the ambiguity before somebody points at it.

Somebody Will Say Nobody Asks the Follow-Up

Often true. Plenty of interviews stay shallow. Behavioural questions, a technical checklist, thanks for coming in, we will be in touch.

That is the argument rather than an objection to it.

The shortlist does not get decided in the room. It gets decided ten minutes after you leave, when two people compare notes and one of them asks whether they believed you. Nobody has to interrogate you for that question to arrive. It arrives anyway.

Specifics survive that conversation. Round numbers do not.

Prepare the Result You Did Not Get

One real failure. Not a disguised strength.

Pick something recent enough that you still remember the detail. An old failure retold too smoothly sounds rehearsed, which defeats the whole point of telling it.

Something you tried that did nothing at all. A rewrite that lost ground. Rankings that climbed while enquiries stayed flat, which happens far more often than published case studies admit.

Then prepare what you did next.

Interviewers hear polished wins all day long. A candidate who can describe a flat quarter without flinching reads like somebody who has sat through one.

No Client Work Yet? The Preparation Is Identical

Juniors get the same rule. Only the project changes.

Your own site counts. A friend’s business counts. So does a volunteer job for a hockey club. What matters is whether you can name the query. Then the change. And the week it shipped.

Ship something small. Then watch it for a month. That month of watching beats another evening with flashcards.

Look at the Employer’s Site Before You Go In

Ten minutes, the night before. Skip the About page.

Open their service pages instead. See what each one is built to rank for. Check whether their phone number sits above the fold on mobile. Notice whether the blog stopped updating four years ago.

Then bring one question. Not a pitch, and not a free SEO audit. “Your service pages all target roughly the same phrase. Was that deliberate?” That question tells them more about you than any definition you could recite back.

Agencies publish an SEO portfolio for the same underlying reason. Specific work, named, checkable. A candidate needs the personal version of it.

What Not to Prepare For

Memorizing ranking factors. No verified list exists, and anybody quizzing you on one is testing recall instead of judgment.

Skip the tool trivia as well. Which button sits in which menu changes every few months. Knowing why you would open the tool matters. Where its export button hides does not.

Same goes for acronym drilling. Nobody has ever been hired for defining a canonical tag faster than the next applicant.

Spend the reclaimed hours on your timeline instead.

Questions You Ask Back Are Also Evidence

Most candidates save one polite question for the end. That slot gets wasted almost every time.

Ask things only a practitioner would think to ask. Who signs off on published content? How long does a page sit in review before it goes live? Does anybody own the redirect map? Those land differently, since each one describes a real bottleneck rather than curiosity about the culture.

Then ask the awkward one. What happened to the last person in this role.

The answer tells you whether the job is winnable at all. Some SEO roles fail on the work itself. Plenty more fail on an approval process nobody warned the new hire about. A site where every change waits six weeks for legal review will not produce what the job description promised.

You are being watched while you ask, too. Somebody probing for constraints sounds like a person planning to do the work.

The Calgary Version of the Same Problem

Smaller market. Different weight on identical answers.

An SEO job here usually means wearing several hats at once. One person handles keyword research and writes the content. Technical fixes as well. Often the Google Ads management too, whatever the job title says.

So prepare for range. Expect a paid search question inside a purely organic role.

SEO Company To-The-TOP! has run SEO in Calgary as a solo practice since 2007. That is the same range problem, made permanent. Nobody to hand the technical work off to. Candidates walking into a small Alberta business should assume something similar.

Common Questions About Preparing for an SEO Interview

How long should I spend preparing for an SEO interview?

One evening, spent well. Building the project timeline takes most of it. Reviewing the employer’s site takes another ten minutes. Anything beyond that usually goes into memorizing definitions, which is the low-value part.

What should I bring to an SEO interview?

Your one-page project timeline. Print it. Hand it over when the results question arrives, rather than describing numbers from memory. Interviewers remember the candidate who brought a document nobody asked for.

Do I need certifications to get hired in SEO?

Google offers no official SEO certification, so treat any claim of one carefully. One real exception sits on the paid side. A Google Ads certification carries a date. It expires after a year. Still, a documented project outranks a certificate in almost every hiring conversation.

What if I cannot share client data?

Talk in direction and ratio instead of raw figures. Traffic roughly doubled over five months. Rankings moved from page three onto page one for a named query type. That respects the NDA while keeping the detail that makes you believable.

How do I answer the first ninety days question?

Refuse to promise rankings. Describe what you would look at, in order. Then say plainly that meaningful movement takes months. Most hiring managers have been oversold before. Restraint reads as experience.