Data Analyst Job Description Template 2026

Last updated: June 19, 2026 | By Robert Ardell

A strong data analyst job description names the type of analytics work, the seniority level, the core tools, and a salary band, because the title spans three different roles that pay anywhere from the high $50,000s to north of $130,000. The template below is pulled from postings that actually filled, not the wishlist JDs that draw 300 applicants and produce zero hires.

Ask five hiring managers what a data analyst does and you will get five different jobs. One means the person who builds the Tableau dashboards. One means the analyst who runs the A/B tests on the product. One means the spreadsheet specialist in marketing who owns the attribution model. One is quietly describing a data scientist and hoping to pay analyst money for it. The fifth just wants someone to make the numbers stop disagreeing.

Same title. Five different jobs. All five write “Data Analyst” at the top of the req, then wonder why the resumes are a mess.

I’m Robert Ardell. I co-founded KORE1 back in 2005, and I have watched this one title stretch from “runs the weekly reports” into a half-dozen specialties over those twenty years. Our data analyst staffing desk fills these roles inside our broader IT staffing services work, so yes, I have a bias, and I will state it plainly. We get paid when you hire through us. The template and the salary data below work whether you hand us the search or run it yourself with the job board open at 11 p.m.

Scope it tightly and the right people raise their hands. Leave it vague and you sort through 300 who do not fit. The posting decides.

Which Data Analyst Are You Actually Hiring?

Data analyst hiring splits into three profiles in 2026: the BI or reporting analyst who turns the warehouse into dashboards, the product analyst who runs experiments and reads funnels, and the marketing or growth analyst who owns attribution and channel ROI. Each one pays differently. Each one needs its own posting.

That distinction is not academic. It is a $40,000 spread, and the title at the top of your JD does more filtering than any bullet underneath it, because most candidates decide whether a role is for them on that one line before they read another word.

BI / reporting analyst. The default hire. It is who most people picture when they say “data analyst.” This person lives in SQL and a dashboard tool, usually Tableau or Power BI, sometimes Looker. They turn warehouse tables into reports leadership actually opens, they own the weekly numbers, and they are the one who gets the Slack message when the revenue chart looks off. Entry sits around $60,000 to $72,000. Mid-level lands $78,000 to $98,000. If your problem is “we have the data but nobody can see it,” this is your seat.

Then there is the analyst who works a step closer to the engineers.

Product analyst. Designs and reads experiments, sizes funnels, and figures out why activation dropped three points last Tuesday. SQL plus Python or a real notebook habit, and enough statistics to know when an A/B test is lying to everybody. They sit with product managers, not in a reporting silo. The work pays more, especially at software companies where the product metrics are the business. That premium is real. Mid-level runs $95,000 to $125,000, and seniors clear $150,000 where experimentation drives the roadmap.

Marketing / growth analyst. Owns attribution, channel ROI, the LTV and CAC math the CMO carries into the board meeting. SQL, a BI tool, and a hard-won tolerance for marketing data that arrives from six platforms that never agree with each other. Mid-level runs $80,000 to $102,000. No role here draws the wrong title more often. And for a lot of companies, this is the first analyst they actually needed, usually hired about two years late.

Decide which of the three you are hiring before you write a single bullet. Nail that down. If a short conversation with the hiring manager does not make it obvious, the posting will try to describe all three, and it will screen out every strong candidate for each.

Blended bands from ZipRecruiter (June 2026) and Glassdoor (2026). Major metros and tech employers push the top end higher. Equity changes the senior picture. Our salary benchmark tool calibrates a range for your exact market and level.

The Data Analyst Job Description Template

What follows is the skeleton. Edit the bracketed fields, cut the profiles that do not apply, and the rest holds. I assembled it from three analyst searches our desk closed this spring, one BI role and two product roles, then removed the parts unique to those teams so you can slot in your own. The notes in parentheses explain why each piece earns its place.

Job Title

[Data Analyst / Senior Data Analyst / Product Analyst / Marketing Analyst / BI Analyst]

(Pick the title that matches the work most of the time. “Data Analyst” is the broadest search term and the safest default for a generalist BI role. Use “Product Analyst” or “Marketing Analyst” when the work really lives in one of those orgs, because a different and better-matched candidate searches those exact phrases. Add “Senior” only if you truly need five-plus years. Tacking it on to justify a lower band just shrinks your pool.)

About the Role

(Two or three sentences. What does this person own, whose decisions do they inform, and who do they report to? Skip the company-mission paragraph. Analysts scroll past it.)

[Company] is hiring a [title] to own [the executive reporting layer / product experimentation / marketing analytics] that drives [what it informs: the weekly business review, the product roadmap, the paid-channel budget]. You will [build dashboards in Tableau / run A/B tests and read funnels / model attribution across channels] and turn questions from [leadership / product / marketing] into answers people trust. This role reports to [the Head of Analytics / Director of Product / VP of Marketing] and is [remote / hybrid in {city} / onsite in {city}].

What You’ll Own

(Six concrete responsibilities. Name the real tools and the real data. “Analyze data to drive insights” tells a candidate nothing about Tuesday. “Own the dashboard the CFO reads every Monday” tells them exactly what the job is.)

• Write and tune the SQL behind [the executive dashboards / product funnels / campaign reporting], against [Snowflake, BigQuery, or Redshift]
• Build and maintain dashboards in [Tableau / Power BI / Looker] that people actually open, and retire the ten that nobody does
• Turn vague questions like “why did signups drop” into a clear answer with the caveats stated, not a chart with no point of view
• Partner with [product / finance / marketing] to define metrics once, so the same number means the same thing in every meeting
• [Design and analyze A/B tests, including the part where you tell a VP the result was noise] (product analyst)
• [Own the attribution model and explain, calmly, why the six platforms will never tie out to the penny] (marketing analyst)

What You Bring

(Be ruthless about the line between must-have and nice-to-have. Every requirement you add quietly narrows the pool, and most postings pad the required column with things that are really preferences nobody would reject a strong analyst over.)

• [2-4] years in an analytics role, with strong SQL as the non-negotiable core
• Fluency in at least one BI tool you actually use day to day, whether that is Tableau, Power BI, or Looker
• The ability to explain a finding to a non-technical stakeholder without losing either the nuance or the room
• A track record of owning a recurring report or metric end to end, including the awkward week the number was wrong and you caught it first

Nice to have, not required: Python or R, experience with dbt, exposure to [your industry’s data], or a stats background. Keep these here. The moment they creep into the required list, you have quietly cut your applicant count in half for skills the role can teach.

Compensation and Logistics

(Post the band. I will defend that below. State location, work model, and sponsorship too, so the first phone screen is about the work and not about deal-breakers you could have disclosed in the posting.)

Salary range: [$X to $Y, based on the bands above and your metro]. Location: [remote / city]. Work model: [remote / hybrid, N days]. Sponsorship: [available / not available].

Tools Worth Naming on a Data Analyst Posting

Name the stack the person will actually touch. Not every tool that has ever been adjacent to analytics. A good analyst reads a tool list the way you read a resume, and a posting that lists nine “required” technologies tells them the team has not decided what the job is.

Start with SQL, because it is the floor. In the 2025 Stack Overflow Developer Survey, SQL was used by 58.6 percent of all respondents, more than any other database technology and ahead of most programming languages. For a data analyst it is not a nice-to-have. It is the job. Say “strong SQL required” and mean it.

Then name your one BI tool. Just one. Tableau, Power BI, and Looker do the same job three ways, and an analyst fluent in one picks up another inside a few weeks because the hard skill is knowing what to put on the chart, not which menu hides the filter. Requiring all three screens out good people to no purpose. Pick the one your company runs, and treat the others as transferable.

Now the part most postings get backward. Python and R are wonderful, and for a BI or reporting analyst they are usually a preference dressed up as a requirement. Plenty of excellent analysts do their whole job in SQL and a dashboard tool and never open a notebook. If the role genuinely needs Python, that is a clue you may actually be hiring a product analyst or a junior data scientist, which is a different posting and a different band. Be honest about which one you want.

Data Analyst Salary Benchmarks for 2026

Most U.S. data analysts make between $62,000 and $122,000 in 2026, and the averages cluster around $82,000 to $93,000 depending on specialty, metro, and seniority. Senior analysts at tech companies routinely clear $130,000.

The aggregators agree on the middle of the market and argue about the top. The argument is where the useful information hides.

Look at the senior line. Glassdoor’s self-reported seniors average $131,627. ZipRecruiter’s senior sample sits near $99,231, weighed down by advertised bands that underpay experienced people. Same title, $32,000 apart. The split is methodological. One figure is scraped from job ads; the other is what working analysts report actually hitting their accounts. That gap is the lesson. For a senior band, trust the self-reported paychecks. For entry, the posted ads run closer to the truth.

A note on the government figure. The Bureau of Labor Statistics has no “data analyst” code at all. The closest tracked roles are Operations Research Analysts, at a $91,290 median with 21 percent projected growth through 2034, and the higher-skill Data Scientists category, up 34 percent over the same decade. Real demand for the title lives somewhere in that blend, which is why title-specific aggregator numbers beat any single government code when you are setting a budget.

Here is the part only a recruiter sees. KORE1 closes data and analytics roles in 17 days on average across more than 30 U.S. metros, and 92 percent of those placements are still in the seat a year later. A contract analyst usually costs a 10 to 15 percent premium over the salaried equivalent, worth pricing in when you weigh contract or contract-to-hire against a direct hire. If the title still feels slippery, our data analyst interview questions guide works as a scoping checklist for what you are really testing.

Where Data Analyst Job Descriptions Go Wrong

Five patterns turn a fillable role into a six-week slog. I see most of them every week. Here they are.

One posting, three jobs. The BI work, the product experimentation, and the marketing attribution get stapled into a single req because all three say “analyst.” No one person is great at all three, and the generalists who apply are rarely strong at the one you needed most. Pick the profile. Write that posting.

The tool wishlist. SQL, Python, R, Tableau, Power BI, Looker, dbt, and “machine learning a plus,” all under Required. It does not read as a high bar. It reads as a team that has not scoped the role, and the analysts with options close the tab. Name three or four tools. Stop.

Requiring a specific degree. Some of the sharpest analysts our recruiters have placed came from finance, operations, journalism, or a bootcamp and two hard years of real reporting work. A strict degree filter would have cut every one of them. Make it preferred, or drop it, and let a SQL screen do the actual sorting.

No salary band. In this market an unposted range is a self-inflicted wound. It costs you applicants who will not gamble a week of interviews on a mystery number, and it wastes the screens you do get when the band finally comes up and it was never going to work. List the number.

Asking for a data scientist at analyst pay. If the bullets want statistical modeling, machine learning, and production Python, you wrote a data scientist req and put an analyst title on it to protect the budget. The few people who can do that work know exactly what it pays, and they keep scrolling. Either fund the role you described or scope it down to the analyst you can afford. Pick one.

What Hiring Managers Ask Us About Data Analyst JDs

How long should a data analyst job description be?

Shorter than most people make it. Three hundred to five hundred words of real content is plenty to scope the role, name the tools, and post a band. The reqs that run past a thousand words are almost always padding the requirements list, which is the one section that actively repels strong applicants. Put the role and the stack up top, keep the responsibilities concrete, and push the legal boilerplate to the bottom.

Do data analysts need to know Python, or is SQL enough?

For most BI and reporting roles, strong SQL plus a dashboard tool is the whole job, and Python is a preference. The analysts who genuinely need Python tend to be product or experimentation analysts, which is a more senior and better-paid profile. So decide which one you are hiring first. If you list Python as required for a basic reporting role, you will pay more and wait longer than the work demands.

What separates a data analyst from a data scientist on a JD?

Two things, really. The verbs and the math. A data analyst describes, reports, and explains what happened using SQL and dashboards; a data scientist predicts and models what will happen using statistics and machine learning. If your bullets are dashboards, metrics, and stakeholder reporting, you are writing an analyst posting. If they lean on modeling and experimentation depth, that is a data scientist, with the comp to match.

Should I require a specific BI tool like Tableau or Power BI?

Name the one you run, and treat the rest as transferable. An analyst fluent in Power BI will be productive in Tableau or Looker within a couple of weeks, because the real skill is knowing what belongs on the chart, not memorizing one vendor’s menus. Requiring expertise in all three screens out excellent people for a logo. State your tool, welcome comparable experience, and let the interview test how they think with data.

Is it worth posting the salary range?

Post the band, every time. A posted range is now expected across much of the country and quietly assumed everywhere else, and leaving it off reads as either disorganized or evasive. The range filters out mismatches before they cost anyone a phone screen, and it pulls in the candidates who would not otherwise risk the time. The only thing an unposted band protects is your option to underpay, and the good analysts already priced that in.

Contract or direct hire for a data analyst?

It tracks how settled the work is. A reporting backlog, a one-off migration, a launch you need covered for a quarter, all point to contract staffing, which usually carries a 10 to 15 percent rate premium over salary. If the metrics are something the business will lean on indefinitely, hire direct. Still deciding? Contract-to-hire buys you a few months of watching the work before you commit. We place analysts under all three models.

Next Steps

So pick the one profile you are hiring, fill the brackets with your real stack and your real band, and strike every requirement that is secretly a preference. The posting that comes out the other side will read like your team wrote it, because it did. Put it up.

Prefer a second set of eyes on it? A recruiter on our desk will stress-test the JD, set the band for your metro, and hand you a short list of analysts who actually fit instead of 300 who do not. Start that conversation with our team. We work data and analytics searches through contract, contract-to-hire, and direct hire. When you are ready to move from the posting to the hire, our guide to hiring a data analyst picks up where this one leaves off.