Why pre-screen senior SEO managers before the interview
Every candidate has a chart going up and to the right, and most of those charts have several causes. What separates senior candidates is attribution: which change produced which movement, what did nothing, and what happened in the month a core update landed badly. A short screen asks what they did that caused the growth, and how a drop was diagnosed, which most decks never cover.
What actually matters when screening Senior SEO Manager candidates
- 01
Campaigns that performed
Ask for specific sites they grew: organic sessions before and after, revenue or lead impact, timeframe, and whether gains survived a core algorithm update.
- 02
Audience and segmentation
Probe how they build keyword and intent maps: tools like Ahrefs, Semrush or Search Console, cannibalisation checks, and clustering by funnel stage.
- 03
Measurement and testing
Test measurement rigour: GA4 and Looker Studio reporting, log file analysis, Core Web Vitals, crawl budget diagnostics, and how they isolate SEO from other channels.
- 04
Working with the business
Check how they move work through others while remote: briefing writers, getting engineering tickets prioritised, and defending SEO requirements during site migrations or replatforms.
Pre-screening questions to ask Senior SEO Manager candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Growth they caused
3 questions01Can you share examples where your work produced a large increase in organic traffic?
Listen forGrowth attributed to specific changes with timing, and revenue or conversion movement alongside sessions.
Total traffic growth with no isolated cause, or session growth reported without any conversion data.
02Can you explain how you used keyword research to grow traffic in a previous role?
Listen forSelection based on intent and realistic competitiveness, with the resulting pages and rankings named.
Keywords chosen by volume alone, or research that never turned into published pages.
03How do you measure SEO performance?
Listen forSegmented reporting by template and intent, with branded traffic separated from the rest.
Reporting on total organic sessions only, or branded search counted as SEO performance.
Depth past dashboards
4 questions04How proficient are you with HTML and CSS?
Listen forEnough to read a template, spot a rendering problem and write a fix an engineer can implement.
Technical work handed entirely to engineering, or markup issues identified only by a tool.
05How have you handled mobile search performance in past projects?
Listen forMobile-first indexing understood, with parity between mobile and desktop content actually verified.
Mobile treated as a page speed score, or content differences between versions never checked.
06How would you describe your approach to on-page versus off-page work?
Listen forEffort allocated by what limits the site, with a diagnosis behind the split rather than a fixed ratio.
A fixed split applied to every site, or one side neglected regardless of the diagnosis.
07How important do you think link building is, and how do you approach it?
Listen forLinks earned through content or relationships, with paid link schemes explicitly avoided and why.
Bought links or private networks described as normal practice, or link volume treated as the goal.
Recovered from a drop
3 questions08How have you handled a ranking penalty or a bad core update?
Listen forDiagnosis before action, with the affected pages isolated and the recovery timeline described honestly.
Recovery described as waiting, or wholesale changes made before the cause was identified.
09How do you ensure the changes you make stay within search engine guidelines?
Listen forA clear line they will not cross, with a tactic they refused despite pressure to use it.
Guidelines treated as advisory, or tactics described as fine because everyone uses them.
10What is your experience with testing changes before rolling them out?
Listen forTemplate changes tested on a page subset, with results measured before a site-wide rollout.
Changes rolled out site-wide at once, or no way to tell whether a change helped.
Team ships without them
2 questions11What is your experience managing remote SEO teams?
Listen forTeam size and structure described, with work that shipped while they were not in the room.
Management described as reviewing reports, or every decision routed through them.
12How do you manage a team spread across different time zones?
Listen forWritten handovers and clear ownership, so work continues without waiting for an overlap window.
Reliance on synchronous meetings, or team members waiting hours for routine decisions.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Campaigns that performed
30%5Names properties, cites organic traffic and revenue deltas with dates, and explains which levers (technical fixes, content, links) drove them.
Audience and segmentation
25%5Describes intent-based clusters and topical hubs tied to buyer stage, plus how they retired or merged competing URLs.
Measurement and testing
30%5Uses annotated dashboards, controlled rollouts or holdout pages, and distinguishes algorithm volatility from genuine performance change.
Working with the business
15%5Cites a migration or redesign where they secured dev resource, ran redirect mapping, and prevented traffic loss with documented sign-off.
Every candidate has a chart going up. A one-way video screen asks which change actually caused it.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish attributed growth, test technical depth, and hear how they handled a traffic drop.
What extra should I check for a remote role?
How work gets shipped without them present. SEO changes usually depend on engineering and content teams, and a manager who cannot move those remotely will produce recommendations nobody implements.
Evaluating answers
What is the strongest signal when screening this role?
Attribution. Senior managers say which change moved which pages and how they know. Anyone presenting total traffic growth with no isolated cause was present during growth, not responsible for it.
How do I judge their technical depth?
Ask what they diagnosed that a tool did not flag. Real answers involve rendering, crawl behaviour or template logic. Anyone whose work stops at an audit score is running software.
























