Last month, Joseph from the Recruitment Room got invited to interview at Football Radar. Jake is in the process at Chelsea and Brentford. Robin has made it through the first stages at a German club.

All three messaged me the night before their first call with the same question.

What are they actually going to ask me?

I've been on both sides of this. Sat in interviews as a candidate and been rejected. Sat on hiring panels, reviewed data tasks, and helped decide who makes the shortlist. The questions you get in a football analyst interview aren't the ones on Glassdoor, and they aren't generic sports analyst questions. They're specific, football-led, and designed to expose whether you actually understand the game or just know how to write SQL.

This article lays out the real questions, how to approach them, and what the data task looks like.

What the interview process actually looks like

Most clubs run a similar shape.

Stage one is a 30-minute screening call with recruitment or a talent partner. Low stakes, but people still fail it by being vague about what they want.

Stage two is a technical or data task, usually 48 to 72 hours. A shortlist, player report, or opposition analysis. The biggest filter. More below.

Stage three is a panel with head of recruitment, lead analyst, and sometimes a tactical coach. They pressure test your task and see how you think on the spot.

Stage four is often a final with the sporting director. Shorter, more about fit and trust.

End to end, expect two to four weeks, though some clubs drag it out for months.

Emphasis differs by role. A performance analyst interview leans on video and tactical understanding, can you sit next to a coach and break down a half. A recruitment analyst interview leans on data and player profiling, can you back a signing in a recruitment meeting. A scout interview leans on live games and report writing, can you go to a 3pm kick off in League Two and come back with a clear view. Overlap is big, but know which one you're in for.

The technical questions clubs ask

These expose whether you actually understand football. You cannot bluff them. If you've spent six months on courses without watching games with a scout's eye, it will show inside two minutes.

Here are the ones I've been asked, and the ones RR members are being asked right now.

1. Walk me through how you'd scout a right-back for our system.

The most common opener in a recruitment analyst interview. It sounds simple. It's not. They're testing whether you understand their context, can structure a process, and can finish with a recommendation.

2. What metrics do you trust and which ones do you ignore?

They want an opinion, not a lecture on every stat under the sun. The people who nail this name specific metrics, explain when they're useful and when they're noise, and admit what they don't trust.

3. Tell me about a player you rated that nobody else did. What happened?

They're checking you actually watch players and form views. If you can't answer this, you've been reading about football rather than watching it. The best answers include a player you got wrong too.

4. How do you combine video and data?

Pure data people lose football. Pure video people miss patterns. Clubs want both. Your answer should explain your actual workflow, not a theoretical one.

5. What's wrong with xG?

A classic trap. They're not looking for "nothing, it's brilliant." They're also not looking for "it's rubbish." They want a mature, balanced view that shows you've thought about the limits of the models you use.

6. Talk me through our last transfer window. What profile are we signing?

This is the one that catches people out. If you haven't looked at their recent business, you've told them you don't care enough.

7. Who's a player in our squad you'd sell, and why?

Have an opinion. Back it up. Be willing to be wrong.

8. How would you structure a shortlist brief from a head coach?

They're checking whether you can turn a vague request into a clear process.

A full worked answer: "Walk me through how you'd scout a right-back for our system"

Here's how I'd structure a response. This is the shape, not the script.

"The first thing I'd do is make sure I actually understand the brief. Before I go near any data, I want to know what we're looking for. Is this a starter or a squad player? What's the budget bracket? Are we replacing a specific player or adding a profile we don't currently have? I'd clarify that with the head of recruitment in five minutes rather than waste two weeks going the wrong direction.

Assuming you want a starter to fit your current system, which from watching you looks like a back four with an attacking right-back who inverts into midfield in possession, I'd start by defining the profile. I'd put numbers around it. Age range, say 22 to 26. Contract situation, entering the final 18 months. Physical benchmarks for your league. Then the in-possession traits, progressive carries, switches of play, receptions in the half-space. And the out of possession, duels won, recovery runs, defensive line height.

From there I'd build the shortlist in three layers. A wide data filter first, probably 60 to 80 players from the leagues we can realistically sign from. Then a video cut, watching 20 to 30 minutes per player to remove anyone who doesn't pass the eye test on the key traits. Then a deep dive on the final eight to ten, full matches, contract data, injury history, personality checks through the network.

The output would be a one-page summary per player with a clear recommendation. I'd rank them, and I'd be willing to defend the ranking in a meeting. If I'm not willing to argue for a player, I shouldn't be putting him forward.

The last thing I'd flag is context. A right-back who looks brilliant at a possession-dominant team in the Eredivisie is not automatically a fit for a transition-heavy Premier League side. I'd make that risk explicit in the report so the decision-maker can weigh it properly."

That's the structure. Brief, profile, shortlist process, output, risk. Six to eight minutes when you talk it through. You don't need to memorise it, you need to be able to think in that shape under pressure.

The behavioural questions that matter more than people think

Most candidates over-prepare the technical and under-prepare these. Behavioural answers are where panels decide if they actually want to work with you.

1. Why do you want to work for this club?

The most failed question in football interviews. Most people say something generic about passion, history, or the badge. Means nothing.

A bad answer to "why Brighton": "I've always admired Brighton and I love the way they play football. I think it would be a great opportunity to develop."

A good answer: "Brighton's recruitment model is the one I've studied most closely. The way you've turned recruitment into a revenue engine through Caicedo, Mac Allister and Mitoma is the model I'd want to contribute to. The way the data team is embedded with scouts rather than siloed fits how I think recruitment should work. Your last four windows show a clear U23, high volume on the ball, progressive leagues profile. That's the work I've been doing in my own projects."

Same energy works for any club. Specifics. Recent business. A view on their model. Why you in particular.

2. Tell me about a time you disagreed with a senior colleague.

They're checking you have a spine but can handle authority. The worst answers: "I've never disagreed" or "I was right and they were wrong." The best show you held a view, presented it respectfully, and accepted the decision.

3. How do you present data to a coach who doesn't trust numbers?

Asked at almost every club. If your answer is dashboards and visualisations without mentioning how you'd frame the conversation, you're failing it.

4. Where do you want to be in three years?

Ambition is fine. Arrogance isn't. "Your job" is bad. "Leading a recruitment analysis team at this level" is fine if you mean it.

The data task, what to expect and how to approach it

The data task is the biggest filter in the process. I'd bet 60 to 70 percent of candidates lose the job here, not in the interview.

Common formats:

What they're really testing:

The biggest mistake I see is over-engineering. People try to prove how clever they are. They load every metric into a radar chart, build a bespoke model, and forget to write a summary. The hiring manager spends ninety seconds on your work. If they can't get the answer in ninety seconds, you've lost.

Here's how to structure a response.

One page written summary up front. Context, approach, recommendation, risk. That's it. Everything else is supporting material the reader can dig into if they want to.

A clear shortlist or ranking if the brief asks for one, with a short justification per player. Two or three sentences is plenty.

The underlying data and methodology somewhere accessible, but not front and centre. Appendix, notebook, linked sheet.

A recommendation at the end, stated clearly. "I would sign player X at a maximum fee of Y. The main risk is Z." That sentence alone puts you ahead of most candidates.

Do not dump every stat. Do not build a radar chart for every player. Do not forget to write actual words. Do not ignore the context the club operates in. If you're scouting for Derby, don't send them a Premier League benchmark. If you're scouting for Brentford, don't ignore set piece detail.

Spend roughly half the time thinking and half the time producing. Most people invert that and it shows.

Questions you should be asking them

This is half the interview. Candidates who don't ask good ones look like they don't care.

Recruitment process. Who signs off on a signing? How does info flow from scout to sporting director?

Tooling. Data stack, video setup, and workflow between the two?

Team structure. Who would I report to? How big is the group? How often do you meet first team staff?

The role in twelve months. What does success look like?

Don't ask about salary or holiday in a first interview. Save that for when they've decided they want you.

Common mistakes that kill interviews

Not knowing recent signings or the current squad. Unforgivable. If you can't name the last five signings and why, you haven't prepared.

Overselling tools. "I'm expert in Python" followed by a basic task failure is worse than "I use Python for specific things and I'm still learning others."

Generic "why this club". Passion, badge, history. Means nothing.

Talking without a point. If you can't make your point in 90 seconds, you don't have one.

No opinion on players. "I'd need to research" is fine once. Twice and they're wondering what you actually think.

Treating it as a quiz, not a conversation. If you're rigid and scripted, the chemistry dies.

How to prepare the week before

You don't need three months. One focused week.

Watch two or three recent matches with a scout's eye. Take notes on system, strengths, weaknesses, roles.

Pull the last four transfer windows. Age, league of origin, fee bracket, in-possession traits. Write down the strategy.

Prep one story per competency. Technical disagreement. Time you were wrong. Time you changed someone's mind.

Practise the data task. Find an old job spec, give yourself 48 hours. Read it next morning like you're the hiring manager. Fix what makes you cringe.

Sleep the night before. Seriously.

Walk in sounding like you already do the job

Candidates who get hired don't walk in hoping to prove themselves. They sound like they already do the job. Specific opinions, grounded context, structured thinking, quiet confidence.

You can't fake that. You build it by watching football, forming views, and doing the work in public before anyone asks you to.

If you want the weekly breakdowns on what's actually working in football hiring, the newsletter is where I share the specifics I don't post anywhere else. Sign up here.

And if you'd rather prep alongside other people going through the same process, Joseph, Jake, Robin and everyone else in live recruitment stages, that's what The Recruitment Room is for.

FAQ

What questions do clubs ask in football analyst interviews?

Clubs ask a mix of technical, behavioural and club-specific questions. Technical ones include scouting a profile for their system, metrics you trust, what's wrong with xG, and a player you'd sell from their squad. Behavioural ones include why this club, how you handle disagreement, and how you present data to a coach who doesn't trust numbers. Almost every process also includes a data task. What they're not asking is generic sports analyst questions. Everything is football-led and tied back to their context.

How long does the football analyst interview process take?

End to end, expect two to four weeks for most clubs. Stage one is a 30-minute screening call. Stage two is a data task, usually 48 to 72 hours to complete. Stage three is a panel interview with the head of recruitment, lead analyst, and sometimes a tactical coach. Stage four is often a shorter final with the sporting director. Some clubs run the full process in ten days. Others drag it out for months, especially if the role is brand new or they're waiting on budget sign-off.

What is a football analyst data task?

A data task is a take-home exercise you're given between the screening call and the panel interview. Common formats are a shortlist for a specific position and brief, a sign or don't sign analysis on a named player, an opposition analysis for an upcoming fixture, or a full scouting report from live or video footage. You usually get 48 to 72 hours. It's the biggest filter in the process. Most candidates lose the job here by over-engineering, burying the recommendation, or ignoring the club's actual context.

How do you answer "why do you want to work for this club"?

Be specific. Reference their recent transfer business, their playing model, and how their recruitment structure matches how you think. Avoid passion, history and badge talk. A strong answer names recent signings, identifies the profile pattern, and ties it back to work you've done yourself. If you can't name the last five signings and explain what profile they fit, you haven't prepared. The question is a filter for whether you actually care about this club or just need a job in football.

What mistakes do candidates make in football analyst interviews?

The most common are not knowing the current squad or recent signings, overselling tools you can't back up, giving a generic "why this club" answer, talking without a clear point, refusing to have an opinion on players, and treating the interview as a quiz rather than a conversation. On the data task, the big ones are no written summary, dumping every stat into radar charts, no clear recommendation at the end, and ignoring the club's budget and league context. Over-engineering kills more candidates than under-preparing.

How do you prepare for a football scout interview in a week?

Watch two or three of the club's recent matches with a scout's eye and take notes on system, strengths and weaknesses. Pull their last four transfer windows and write down the profile they're signing. Prep one story for each competency area, including a technical disagreement, a time you were wrong, and a time you changed someone's mind. Run a practice data task using an old job spec and a 48-hour deadline. Read what you produced the next morning like a hiring manager. Fix what makes you cringe. Sleep the night before.

Do you need a degree to work as a football analyst?

No. Clubs care about what you can do, not what you studied. A degree helps for work visas in some countries and can open doors with bigger clubs, but the candidates who actually get hired tend to share a pattern: visible work, specific opinions, a body of analysis they've shared publicly, and a network of people in the game. A masters can compress the learning curve, but it doesn't replace doing the work. The Recruitment Room members who land roles are the ones who produce output, not the ones with the most qualifications.