Sales Analyst Job Description Template - 2026 Guide

Post "Sales Analyst" and you'll get applicants for two different jobs answering the same listing. One builds the weekly pipeline deck and chases down why the CRM export doesn't match finance's number. The other owns the forecast model the VP of Sales stakes their number on, and tells leadership coverage won't carry the quarter. Both get hired off the same posting, and the pay gap between them runs close to $30,000.

The title also sits one step from four other analyst roles: sales operations analyst, revenue operations analyst, business intelligence analyst, and marketing analyst (see the boundary table below). A generic "someone who works with sales numbers" posting cannibalizes all four searches at once. For fundamentals that apply to any posting, start with our job description best practices guide.

Last updated: September 2026

Key Highlights

• No federal wage series for this title: the closest BLS occupations are Market Research Analysts at a $78,760 median and Financial Analysts at a $103,570 median (both May 2025), and which one applies depends on whether the job reports on the past or models the future.
• The gap is seniority, not scope: "Sales Analyst" covers a reporting-only tier and a decision-support tier that owns a forecast someone acts on, a spread of roughly $30,000 in our bands below.
• Sales-productivity data moved the right direction, and most articles still have it backward: Salesforce's 2026 State of Sales statistics put non-selling time at 60 percent of a rep's week, up from the widely repeated (and two editions stale) under-30-percent-selling figure from Salesforce's December 2022 report.
• The federal task list already describes half this job: O*NET's Market Research Analysts profile names "forecast and track marketing and sales trends, analyzing collected data" as a core task.
• Five titles crowd this one posting: sales analyst sits a step from sales operations, revenue operations, business intelligence, and marketing analyst. See the boundary table below.
• No certification gate exists for this title: unlike an auditor or a project manager, there's nothing to require. Screen for SQL, spreadsheet modeling, and CRM data fluency instead.

Why This Role Matters

Five Titles, One Job Family

"Sales analyst" doesn't fail alone. It sits inside a cluster of titles that get typed into the same job-board search, and each answers a genuinely different question.

The distinction isn't academic. A sales analyst dropped into a sales operations analyst's job produces a beautiful answer to a question nobody asked while the CRM stays broken underneath. Sending the wrong candidate away fast is a feature of a precise ad, not a failure of it.

Reporting Analyst or Decision-Support Analyst

Inside the sales analyst title sits a second fork that matters more than scope: two nearly identical postings can describe two different jobs, and the difference is seniority.

The reporting-tier analyst builds the recurring deck and answers "what happened" when asked. The decision-support-tier analyst owns a model someone else acts on: a forecast the VP defends to the board, a territory redesign that changes what fifteen reps get paid, a coverage number that decides whether the quarter gets rescued early or written off. Same functional title. Very different job.

Three questions separate them:

1. Does the analyst present findings to sales leadership directly, or does someone else present the work for them?
2. Do they own a model that a leader acts on (a forecast, a territory plan, a comp scenario), or hand off a number for someone senior to interpret?
3. Can they say no to a request ("that number isn't ready, here's why") without it going up the chain first?

A yes on two of three usually means decision-support, and the posting and salary band should say so. A no on all three means reporting-tier, and pricing it like decision-support wastes budget and patience once the mismatch surfaces.

The Data Nobody Checks

Here's what separates a correct number from a plausible one: whether the analyst understands what the CRM data actually means before building on it. A "created date" on an opportunity can mean the day a rep first spoke to the prospect, or the day someone finally logged it three weeks later. A deal sitting in "Negotiation" might genuinely be there, or might be a rep protecting their number from a manager who hasn't asked hard questions lately. O*NET's profile for Market Research Analysts lists "forecast and track marketing and sales trends, analyzing collected data" as core work, but that assumes the data underneath is trustworthy to begin with.

This is where the title splits from its closest neighbor. A sales operations analyst owns fixing that data: stage definitions, close-date audits, chasing reps who don't log activity. A sales analyst just needs to trust or distrust it. Hire someone who can only query clean data, and the first messy export hands them a confident, wrong answer.

The same skepticism applies to statistics candidates cite in interviews. Sales-productivity numbers are among the most recycled figures in B2B hiring, and the most-quoted ones are years stale. Salesforce's own 2026 State of Sales statistics page reports reps spending 60 percent of their time on non-selling tasks, an improvement over the widely repeated "under 30 percent selling" figure from Salesforce's December 2022 report. Quoting the old number as current is a tell for how a candidate handles a stale number in your own CRM.

Primary Job Description Template

Worth a quick read first: our job description best practices guide covers the fundamentals that apply to any posting, not only this one.

About the Role

We're hiring a Sales Analyst to turn our pipeline, win-rate, and quota data into answers our sales leadership acts on. You'll own [define here: the weekly pipeline deck / the forecast model / territory analysis], investigate why a metric moved, and present findings clearly enough that a VP of Sales can decide from your answer alone.

This role reports to [Sales Operations Manager / Sales Director], and works closely with account executives whose deals you'll analyze and finance on quota and comp questions. Decide before you post whether this is a reporting or decision-support role (see the test above), and write the requirements and band to match.

The ideal candidate can query messy CRM data without getting fooled by it, build a spreadsheet model that survives scrutiny, and explain a bad quarter to a sales leader who doesn't want to hear it, without softening the finding or picking a fight.

Key Responsibilities

• Pipeline and Performance Analysis: Analyze win rate, deal size, cycle length, and quota attainment by rep, territory, and segment to find what's driving or dragging performance.
• Forecast Support: Build and maintain the forecasting model, track accuracy against actuals, and flag when coverage won't carry the number before the quarter closes.
• Variance Investigation: When a metric moves, find out why: a real trend, a data-quality problem, or one deal skewing the average.
• Territory and Segment Analysis: Evaluate territory productivity to support planning, without owning the assignment process itself.
• Dashboard and Reporting: Maintain the recurring reports leadership relies on, and know which numbers need a caveat.
• CRM Data Partnership: Flag data-quality issues (stage definitions, close-date hygiene) to sales operations without owning the fix.
• Ad Hoc Analysis: Answer time-sensitive questions fast enough that the answer still matters.
• Presentation to Leadership: Present findings directly to sales leaders in a format built for a decision, not a data dump.
• Cross-Functional Input: Support finance on comp and quota questions, and revenue operations or marketing at the funnel handoff.

Requirements

Must-Have Qualifications:

• Bachelor's degree in business, economics, finance, or a related analytical field
• 2 to 5 years in sales analysis, business analysis, financial analysis, or a comparable role
• Strong SQL skills, enough to write and troubleshoot queries against a warehouse or CRM export unassisted
• Advanced spreadsheet modeling: pivot tables, lookups, scenario models another analyst can follow
• Working knowledge of CRM data structure: what a stage and a "created" timestamp mean, and where they get gamed
• Ability to explain a bad number to a sales leader clearly, under pressure, without hedging it into meaninglessness

Nice-to-Have Qualifications:

• Experience with a BI tool (Tableau, Power BI, Looker) for self-service dashboards
• Exposure to forecasting methodology beyond a trend line: weighted pipeline, historical conversion rates by stage
• Prior experience in sales operations, FP&A, or financial analysis
• Python or R for analysis past what SQL and a spreadsheet handle cleanly

Tools and Technical Skills

There's no certification worth requiring for this title, unlike a project manager or an auditor. No professional body issues a credential to check, and requiring one would shrink your pool for no real signal. Screen for tool fluency instead.

A candidate strong in one row and weak in the rest is common and often fine, depending on the tier. Fluent talk about tools with no specific analysis to point to is the real warning sign.

What We Offer

• Competitive Compensation: Base salary aligned with the tier (reporting or decision-support) and level detailed below
• Real Influence: Your analysis feeds decisions leadership actually acts on, not a report in a shared drive
• Comprehensive Benefits: Medical, dental, and vision coverage, retirement plan with employer match, and paid time off
• Modern Tooling: A current CRM and data stack, not a legacy system nobody wants to query
• Professional Development: Budget for BI tool training, SQL courses, or a modeling certificate program
• Growth Path: A defined track toward Senior Sales Analyst, Sales Operations Manager, or a lateral move into revenue operations or finance

Context Variations

Enterprise Sales Organization

At a larger company, a sales analyst usually owns one slice of the funnel (a region, a product line, a segment) inside a standing forecast cadence that runs regardless of who's analyzing it. The role sits inside a broader sales or revenue operations org, applying set methodology rather than inventing it. Deal sizes are larger and cycles longer, so a single misread deal can skew a whole territory's numbers.

High-Velocity or SMB Sales

High-velocity sales analysis trades depth for speed. Deal volume is high and deal size small, so a single deal barely moves the aggregate. This variant often reports more directly to a sales manager rather than a formal ops function, and leans reporting-tier, since the cadence rewards a fast, correct weekly answer over a deeply owned forecast model.

Channel or Partner Sales

Channel and partner motions add a wrinkle most postings never mention: attribution. When a deal closes partly through a partner and partly through a direct rep, "who gets credit" becomes a real analytical question with real comp consequences. A sales analyst here needs to understand the partner data feed as well as the direct CRM data.

Remote or Hybrid Environment

This is one of the more remote-friendly analytical roles going. Query writing, model building, and dashboard maintenance all work asynchronously. The exceptions are narrow: live forecast calls and quarterly business reviews benefit from real-time overlap with sales leadership's working hours, stated explicitly rather than left as "occasional availability."

Industry Considerations

The method barely changes across rows. What changes is which distortions to check for, and how much of the forecast comes from sales data versus a second system.

Compensation Guide

How the Federal Data Maps to This Title

There is no federal wage series for "Sales Analyst." The BLS doesn't track it as its own occupation, and the two closest matches price very differently, which is why this title's pay band splits so widely.

Market Research Analysts is the closer match for the reporting tier. BLS describes the occupation as one that "study[ies] consumer preferences, business conditions, and other factors to assess potential sales of a product or service," with a median annual wage of $78,760 as of May 2025 across 952,700 jobs. O*NET's task list names "forecast and track marketing and sales trends, analyzing collected data" directly, close to a reporting-tier analyst's week.

Financial Analysts is where the decision-support tier prices instead. BLS defines them as workers who "research and evaluate financial data, forecast future trends, and prepare reports containing recommendations for businesses and investors," with a median annual wage of $103,570 as of May 2025 across 443,100 jobs. That page publishes a nested set of figures, so quote the one you mean: $103,570 is the occupational group, and inside it BLS reports financial and investment analysts at $102,740 and financial risk specialists at $117,330. O*NET's companion profile lists "employ financial models to develop solutions to financial problems" as core work, close to what a forecast-owning sales analyst does, aimed at a pipeline instead of a portfolio.

Treat both figures as directional anchors, not a quote for this title. Use the Market Research Analysts median to sanity-check a reporting-tier offer and the Financial Analysts median for a decision-support offer.

Market Compensation by Experience Level

The ranges below are employer-set market planning bands built around the federal data above and standard seniority progression in analytical roles, not a salary-database quote. Validate locally before making an offer.

Factors that move a candidate within these bands: forecast ownership, SQL fluency versus spreadsheet-only skill, prior sales operations or FP&A experience, and whether they present directly to leadership or hand off through a manager. Variable compensation is common at some companies and absent at others; state which applies.

Metro Adjustment Guide

Cost of living moves these bands; treat the adjustment below as a planning heuristic, not a location-specific quote.

High-velocity SMB motions often price the role toward the reporting-tier band regardless of metro. A decision-support analyst presenting directly to a VP of Sales or CRO tends to close near the top of the senior band; that visibility is part of the price.

Experience Level Requirements Matrix

Interview Questions

Technical/Functional Questions

1. Variance Walkthrough: "Walk me through how you'd investigate a 15 percent drop in win rate last quarter." Look for a structured approach distinguishing a real trend from noise or a data problem.
2. Forecast Model Building: "How would you build a forecast model with limited historical data?" Look for a reasoned methodology, not a single trend line extended forward.
3. CRM Data Skepticism: "A deal has sat in 'Negotiation' for four months. What do you check before trusting that stage?" Look for specific investigative steps, not blind acceptance of the field.
4. Correlation vs. Causation: "Two reps hit quota this quarter after a new training program. Did the training work?" Look for awareness that correlation alone doesn't prove it.
5. Territory Analysis: "How would you evaluate whether a territory is understaffed versus underperforming?" Look for a method that separates capacity from execution.
6. Stale Statistic Check: "Tell me a sales statistic you've seen quoted often. Do you know which year or edition it's from?" "Reps sell under 30 percent of the time" is a good test case, since current data says 40 percent.

Behavioral Questions

1. Holding a Finding: "Tell me about a time a sales leader pushed back hard on your analysis." Look for holding the position on evidence, not caving to seniority.
2. Messy Data: "Describe a project where the CRM data was too unreliable to use as-is." Look for a specific workaround and honest communication.
3. Saying No: "Describe a time you told a stakeholder a requested number wasn't ready." Look for a clear reason and a path forward, not just a refusal.

Culture Fit Questions

1. Working With Sales Reps: "How do you build trust with reps whose numbers you're analyzing?" Look for a partnership framing, not an auditor-versus-rep dynamic.
2. Prioritization Under Pressure: "Three sales leaders want an urgent analysis the same week. How do you decide what's first?" Look for a clear prioritization method.
3. Staying Current: "How do you validate a statistic before using it in a recommendation?" Look for a specific habit, not "I read the news."

Evaluation Tips: Strong candidates name a specific deal, a specific number, and a specific outcome. Weak candidates describe their work in the passive voice, where analyses were run and reports were delivered, but nobody seems to have decided anything.

Hiring Tips

Quick Sourcing Guide

• FP&A and Finance Teams: Financial analysts moving toward the revenue side already have the modeling discipline this role needs
• Sales Operations Talent Pools: Candidates from sales ops backgrounds already understand CRM data structure, often the hardest thing to teach
• Business Analyst Pipelines: General business analysts with SQL and spreadsheet fluency transition in with light ramp-up
• RevOps Communities: Online RevOps groups skew toward people actively building this skill set

Red Flags to Avoid

• Can't Separate Scope From Seniority: A candidate who can't say whether they've done reporting-tier or decision-support work hasn't done much of either
• No Skepticism About CRM Data: Someone who treats every CRM field as gospel will hand you confident, wrong answers
• Repeats Stale Statistics Uncritically: Quoting an old industry figure as current, without checking the edition, may mean the same happens with your own numbers
• No Story About Influencing a Decision: Someone who describes running analyses but never one that changed what leadership actually did