How to Know When You're Ready to Hire a Data Person (And What Role You Actually Need)

The Hiring Decision (Before You Post the Job)

Before you hire a data person: 1) Are you actually ready? 2) What role do you actually need? 3) How much should you pay? Getting these wrong costs a lot of money.

Are You Ready to Hire?

Signal 1: You're asking questions you can't answer ("How many customers? Which segment is growing? What's our churn?"). Signal 2: You have more data than you can analyze. Signal 3: You have clean, organized data (not perfect, but organized). If data is a mess, hire a data engineer first or spend 3 months cleaning. Don't hire an analyst to work with bad data. Signal 4: You have a defined problem. Signal 5: You have budget ($80-150k depending on role, plus tools and support).

You're NOT Ready If

Your data is fragmented and messy (fix first). You don't know what questions you want answered ("We need a data person for analytics" is too vague). You don't have time to onboard (CEO too busy to explain the business). You don't have leadership alignment (CEO wants one thing, CFO another). You haven't automated your data (someone still manually pulls reports — analyst will spend time on manual tasks).

What Role Do You Actually Need?

Role 1: Analytics-focused analyst — 70% analyzing, 20% reports, 10% tools. Good for understanding business, "why" questions. $80-120k. Hire when you have organized data and need someone to answer business questions. Role 2: BI-focused analyst — 50% dashboards, 30% analysis, 20% BI tools. Good for making data visible, self-service. $80-120k. Role 3: Data engineer — 60% infrastructure, 30% pipelines, 10% analysis. Good for scale, large datasets. $120-160k. Role 4: Data scientist — 60% models, 20% analysis, 20% infrastructure. Good for prediction, ML. $150-220k. Hire when you have clean data and want ML. Most companies starting out need Role 1.

How to Know Which Role

"Which customers will churn?" / "What will revenue be?" → Start with Analyst, maybe Scientist later. "How are we trending?" / "Which segment is growing?" → Analytics-focused Analyst. "Can everyone see key metrics?" / "Self-serve reports?" → BI-focused Analyst. "How do we handle 100M records?" / "Automate reporting?" → Data Engineer.

The Hiring Sequence

Phase 1: Hire for analytics (Role 1). Now if ready. $80-120k. Benefit: Understand business through data. Phase 2: Hire for BI or Engineer. 6-12 months after first. $80-160k. Phase 3: Hire data scientist. 12-24 months after first. $150-220k. Don't skip steps. Foundation (analytics) first.

How Much to Pay (US)

Analyst (analytics): $80-120k. Analyst (BI): $80-120k. Engineer: $120-160k. Scientist: $150-220k. Add 20-30% expensive city; add 50% for 10+ years; subtract 20-30% startup in inexpensive city.

Decision Tree

Do you have organized data? No → Fix data first. Yes → Do you have questions you want answered? No → Define questions first. Yes → Which role? Business questions → Analytics analyst. Dashboards/self-serve → BI analyst. Scale/infrastructure → Engineer. Prediction/ML → Scientist (later, after analyst).

Before You Post the Job

Answer: What specific problems will this person solve? What role are you hiring for? Do you have budget? Time to onboard? Is data organized? Does leadership agree on what they'll work on? If you can't answer all, don't hire yet.

The Downloadable Resource

We've created a Data Hire Readiness & Role Definition Guide that includes: Readiness assessment; role definitions; salary guidance by role and location; decision tree; hiring timeline; onboarding plan; 90-day success metrics template.

Download it here: aiforbusiness.net/resources/data-hire-readiness-guide

What's Next

Once you've hired the right person (or decided to do it yourself), you need to connect your fragmented systems. The next article, "How to Connect Your Disconnected Tools (Before You Panic About Integration)," covers integration without building custom code.