How to Hire a Data Analyst: A Step-by-Step Guide for Small Hiring Teams
Companies hire their first data analyst when someone senior gets tired of building spreadsheets, and the hire often fails because the role was never defined beyond 'do the numbers'. This guide is the process for hiring an analyst who will change decisions rather than decorate them.
- Name the decisions the analyst will inform: Pricing, marketing spend, product priorities, hiring plans: write down the three decisions that are currently made on instinct and would be better made on evidence. The role description is the first screening step, and it decides who applies.
- Fix the data access before the hire, not after. An analyst who spends the first two months getting read access to the warehouse and arguing about metric definitions will quit or drift.
- Source where data analysts already are: analysts at companies with a mature data culture who want more ownership, and finance, operations or marketing people who have visibly done the analytical work in their roles.
- Screen every CV against a written rubric of the four things the job cannot be done without, then interview for evidence: what the candidate built, decided or fixed, scored against notes written before the interview.
- Decide within a week of the final interview and make the offer with reasons. The common mistakes below, starting with hiring for a tool list instead of for decisions influenced, are how good candidates are lost.
The process
- 1
Name the decisions the analyst will inform
Pricing, marketing spend, product priorities, hiring plans: write down the three decisions that are currently made on instinct and would be better made on evidence. That is the role. It also tells you who the analyst's stakeholders are.
- 2
Fix the data access before the hire, not after
An analyst who spends the first two months getting read access to the warehouse and arguing about metric definitions will quit or drift. Decide where the data lives, who owns it and what the core metrics mean before the first interview.
- 3
Source from adjacent roles too
Analysts come from finance, operations, marketing and science as well as from analyst titles. Someone who has answered real questions with data in another job often outperforms a career dashboard-builder.
- 4
Screen against a rubric, not a feeling
Write down the four things the job cannot be done without and score every CV against them before reading any further. Three minutes per CV with a rubric beats fifteen without one, and the decisions can be explained afterwards.
- 5
Interview for evidence
Every interview question should ask for something that happened: a system, a deal, a decision, a failure. Score answers against what a strong one contains, written down before the interview, so two interviewers agree.
- 6
Decide fast and tell everyone
Candidates judge a company by its process. Decide within a week of the final interview, tell the ones you passed on, and make the offer with the reasons you chose them. The best candidates have other offers.
Where to find candidates
- Analysts at companies with a mature data culture who want more ownership
- Finance, operations or marketing people who have visibly done the analytical work in their roles
- Graduates with a quantitative project that reached a conclusion they can defend
- Referrals from your engineers and your finance lead, who meet analysts professionally
- A job posting that lists the decisions the analyst will inform
Mistakes that lose good candidates
- Hiring for a tool list instead of for decisions influenced
- Reporting the analyst to someone who wants confirmation, not information
- No data access, no definitions, no warehouse: the analyst becomes a spreadsheet person
- Setting a take-home exercise on synthetic data that tests nothing but tool fluency
- Expecting a data engineer and a data scientist in the same hire
Running it well
Interview with your own data. Give the candidate a real, anonymised extract and a real question the company has, and talk through what they did with it. You will learn how they think, and you will find out whether they ask what the number is for before computing it, which is the single best predictor for the role.
Be honest in the posting about the state of the data. 'Our warehouse is new and our definitions are contested' attracts analysts who like building order out of mess, and it warns off the ones who need a finished stack. Both outcomes are good.
Decide who the analyst reports to with care. Reporting into the function that most wants the numbers to look a certain way is how analysts become report generators. Reporting to someone who wants to be told when they are wrong is how they become valuable.
Frequently asked questions
Should our first data hire be an analyst or a data engineer?
If the data is not accessible or reliable, an engineer first, or an analyst comfortable with pipeline work. If the data is fine and nobody is answering questions with it, an analyst.
How much should we pay?
What the market for the role in your location and stage pays, found by looking at postings and asking candidates. Underpaying this role is common and the good ones leave within a year.
Remote or in the office?
Analysts work well remotely if the stakeholders make time for them. The risk is isolation, not productivity; schedule the stakeholder conversations deliberately.
Related guides
- How to Hire a Product Manager: A Step-by-Step Guide for Small Hiring Teams
- How to Hire a Marketing Manager: A Step-by-Step Guide for Small Hiring Teams
- How to Hire a Backend Engineer: A Step-by-Step Guide for Small Hiring Teams
- How to Hire a Customer Success Manager: A Step-by-Step Guide for Small Hiring Teams
- How to Hire a DevOps Engineer: A Step-by-Step Guide for Small Hiring Teams
Screening data analyst CVs this week?
Paste the job description into WadeCV, check the rubric it drafts, and upload the CVs. Each one is read against the rubric and scored with an explanation. Ten screenings are free; there is no subscription.
Screen your first CVs free