HRGen.ai

Free, ready to customize

Data Analyst Job Description Prompt

A useful data analyst job description explains which decisions the analysis supports, not simply which dashboards the person will build. Use this prompt to define the business questions, source systems, reporting audience, and level of analytical independence. It helps distinguish recurring reporting from exploratory investigation and keeps data engineering or advanced modeling requirements from slipping into the role without explanation. Candidates should see how their work will become a recommendation someone can act on.

Free to copy. No sign-up required.

Go to the copy-ready prompt

Start with the right scope

Clarify whether this analyst supports one function or serves several teams, and whether datasets arrive ready to use. Extracting and checking operational data is different from designing a company-wide data platform. Explain who owns pipelines, metric definitions, and access approvals. Ask the prompt to prioritize query skills, sound interpretation, and communication around the actual decision context. Any expectation for statistical modeling, experimentation, or production automation should be explicit rather than hidden behind a broad analytics title.

Confirm these details with your hiring manager

  1. Name the decisions and teams this analyst supports, including examples of recurring questions.
  2. Explain data access, quality limitations, and whether engineering colleagues own ingestion and transformation.
  3. Specify the reporting cadence and level of statistical analysis actually needed.

Copy, customize, draft

Your ATS-ready Data Analyst prompt

Copy the prompt below, replace the bracketed details, and paste it into your preferred AI tool. It creates a first draft for review, rather than a finished job offer.

Act as an experienced HR copywriter. Draft an ATS-friendly Data Analyst job description using plain language, standard headings, and concise bullet points. Separate required competencies from optional skills. Avoid tables, graphics, vague personality labels, and unsupported claims. Do not claim compatibility with every applicant tracking system.

COMPANY CONTEXT TO COMPLETE
Company: [Company name and what it does]
Location and work arrangement: [Location; on-site, hybrid, or remote]
Schedule and employment type: [Hours, time zone, employment type]
Reporting line: [Manager and team]
Culture: [Observable working practices]
Approved compensation and benefits: [Pay range and confirmed benefits]
Application process: [Application link and accommodation contact]

ROLE PURPOSE
Turn business questions into clear, reliable analysis that helps colleagues make informed decisions. You will work with operational data, investigate patterns, maintain useful reporting, and communicate what the evidence supports. In partnership with business stakeholders, you will define measures, check data quality, and explain findings with enough context for others to understand both the recommendation and its limitations.

CORE RESPONSIBILITIES TO ADAPT
- Clarify stakeholder questions and define measures that match the business decision.
- Query, combine, and validate data from approved sources before analysis or reporting.
- Build and maintain reports with clear definitions, appropriate comparisons, and documented assumptions.
- Investigate patterns, explain limitations, and present findings to technical and nontechnical audiences.
- Work with data owners to identify quality issues and improve repeatable analytical workflows.

REQUIRED CORE COMPETENCIES
- Ability to query and analyze structured data using SQL or a comparable method relevant to the role.
- Experience checking accuracy, completeness, and consistency before drawing conclusions.
- Ability to explain analytical findings and distinguish evidence from assumptions.
- Practical skill using spreadsheets or a reporting tool to answer a business question.

OPTIONAL NICE-TO-HAVE SKILLS
- Experience with the organization’s business intelligence platform.
- Familiarity with a scripting language for repeatable analysis.
- Knowledge of the business domain or experimentation methods relevant to the team.

TOOLS TO CONFIRM
Examples only: SQL, Excel or Google Sheets, Power BI or Tableau, and Python when scripting is part of the role. Specify actual sources and acceptable equivalents. Treat these as examples. Include only tools the hiring manager confirms, and distinguish day-one requirements from tools that can be learned.

ROLE-SPECIFIC HIRING CONTEXT
Clarify whether this analyst supports one function or serves several teams, and whether datasets arrive ready to use. Extracting and checking operational data is different from designing a company-wide data platform. Explain who owns pipelines, metric definitions, and access approvals. Ask the prompt to prioritize query skills, sound interpretation, and communication around the actual decision context. Any expectation for statistical modeling, experimentation, or production automation should be explicit rather than hidden behind a broad analytics title.

PROPOSED SUCCESS MILESTONES FOR REVIEW
Day 30: By day 30, document key sources and metric definitions while reproducing an established report accurately.
Day 90: By day 90, complete a scoped analysis that answers an agreed stakeholder question and explains its limitations.
Year 1: By year one, maintain trusted reporting and demonstrate how recurring analyses have informed documented business decisions.

Before drafting, identify any missing information that changes the scope of this role. Retain clear bracketed placeholders for unanswered factual details. Do not invent salary, benefits, quotas, team size, certifications, degrees, or years of experience. Use inclusive, job-related language. Output a role overview, role details, responsibilities, required competencies, optional skills, proposed milestones, and how to apply. Finish with a short hiring-manager review checklist.

See the result

Sample Data Analyst job description

Illustrative sample, not a live AI result or an open vacancy. Confirm the role’s actual requirements, tools, and proposed milestones before publishing.

Data Analyst

Role overview

Turn business questions into clear, reliable analysis that helps colleagues make informed decisions. You will work with operational data, investigate patterns, maintain useful reporting, and communicate what the evidence supports. In partnership with business stakeholders, you will define measures, check data quality, and explain findings with enough context for others to understand both the recommendation and its limitations.

Role details

Company
[Company name]
Location
[Location and work arrangement]
Schedule
[Employment type and hours]
Reports to
[Manager and team]
Compensation
[Approved pay range and benefits]

Key responsibilities

  • Clarify stakeholder questions and define measures that match the business decision.
  • Query, combine, and validate data from approved sources before analysis or reporting.
  • Build and maintain reports with clear definitions, appropriate comparisons, and documented assumptions.
  • Investigate patterns, explain limitations, and present findings to technical and nontechnical audiences.
  • Work with data owners to identify quality issues and improve repeatable analytical workflows.

Required core competencies

  • Ability to query and analyze structured data using SQL or a comparable method relevant to the role.
  • Experience checking accuracy, completeness, and consistency before drawing conclusions.
  • Ability to explain analytical findings and distinguish evidence from assumptions.
  • Practical skill using spreadsheets or a reporting tool to answer a business question.

Nice-to-have skills

  • Experience with the organization’s business intelligence platform.
  • Familiarity with a scripting language for repeatable analysis.
  • Knowledge of the business domain or experimentation methods relevant to the team.

Proposed success milestones

  • Day 30: By day 30, document key sources and metric definitions while reproducing an established report accurately.
  • Day 90: By day 90, complete a scoped analysis that answers an agreed stakeholder question and explains its limitations.
  • Year 1: By year one, maintain trusted reporting and demonstrate how recurring analyses have informed documented business decisions.

How to apply

Submit [application materials] through [application process]. For application accommodations, contact [designated contact].

Refine the Data Analyst draft

Confusing analysis with platform ownership

An analyst may clean and combine data without owning ingestion infrastructure, warehouse administration, or production pipelines. State where analytical preparation ends and engineering responsibility begins. If both are part of the role, explain their relative emphasis and support. This avoids attracting candidates for a reporting opportunity that is actually an engineering vacancy and makes the required capabilities more credible to people reading the posting.

Promising certainty from incomplete data

A strong analyst explains what a dataset can support and where uncertainty remains. Avoid language that demands definitive answers to every business question or treats correlation as proof of cause. Ask the prompt to include validation, assumptions, and stakeholder interpretation as responsibilities. Useful output may be a qualified recommendation or a request for better measurement, rather than a confident conclusion the available evidence cannot justify.

Measuring success by dashboard volume

A large number of reports is not evidence of useful analytical work. Describe outcomes in terms of reliable definitions, relevant questions, and decisions informed by the work. Before adding a turnaround target or adoption measure, agree how it will be tracked and what dependencies apply. The sample milestones should encourage trustworthy work, not reward publishing more charts without checking whether anyone needs them.

Questions before you publish

Do I need to require Python?

Only require Python when the regular work depends on scripting, automation, or analysis that your team actually performs in it. Many reporting roles rely primarily on SQL, spreadsheets, and a business intelligence platform. Describe the workflows first, then select the tools needed to complete them. Familiarity with another language may be transferable, so decide whether exact-tool experience is essential before making it a screening requirement.

How do I describe data quality responsibilities?

Explain the checks the analyst performs and the route for resolving issues they cannot fix directly. For example, the role might reconcile totals, document missing values, and flag inconsistent definitions to source-system owners. Avoid making the analyst personally responsible for every upstream defect. Candidates should understand both their responsibility to identify limitations and the colleagues who control changes to the underlying systems.

Should the description include example business questions?

Yes, a small number of genuine examples helps applicants understand the analytical context. You might mention investigating a change in renewal behavior, tracking operational turnaround time, or comparing campaign performance, depending on the team. Use examples your organization actually needs answered. They should illustrate the work without revealing sensitive data or implying that every question already has a clean, immediately available dataset.