Data Analyst Job Description Template

In plain language: States the official job title, FLSA classification (exempt or non-exempt), employment type (full-time, part-time, contract), and department.

Common mistake: Using an informal working title instead of the official classification. Mismatched titles between the job description and payroll records create audit issues and undermine discrimination defense documentation.

In plain language: A 3–5 sentence overview of the role's purpose, its place in the organization, and the primary outcomes it is accountable for producing.

Common mistake: Writing a role summary that describes the team's function rather than the individual's accountability. The summary should make clear what this specific person is responsible for delivering.

In plain language: An itemized list of the role's essential functions — the recurring tasks the employee performs on a daily, weekly, or project basis.

Common mistake: Listing every conceivable task to create an exhaustive description. A list exceeding 12 bullet points obscures priorities — candidates cannot distinguish essential functions from marginal duties, making performance management harder later.

In plain language: The minimum educational background and years of experience the employer will not waive — used to screen applicants and defend hiring decisions.

Common mistake: Setting degree requirements that are not demonstrably job-related. Mandatory degree requirements for roles where skills can be demonstrated through experience risk EEOC scrutiny for disparate impact on protected groups.

In plain language: Desirable but non-mandatory qualifications — used to differentiate strong candidates without excluding otherwise qualified applicants.

Common mistake: Treating preferred qualifications as a second required list. Candidates who meet all preferred qualifications but lack one required item are screened out — while candidates missing all preferred items who meet requirements are advanced — making the distinction meaningless.

In plain language: Explicitly names the software, programming languages, platforms, and methodologies the employee is expected to use, allowing recruiters and hiring managers to objectively score candidates.

Common mistake: Listing tool names without proficiency levels. 'Experience with Python' covers a candidate who wrote three scripts and one who built production ML pipelines — adding Junior / Intermediate / Advanced removes ambiguity.

In plain language: Identifies who the role reports to, any direct reports it manages, and the internal stakeholders it collaborates with regularly.

Common mistake: Omitting the reporting structure entirely. Without it, candidates cannot assess career path or management context, leading to misaligned expectations and early attrition.

In plain language: States the salary band, bonus eligibility, benefits overview, work location (remote, hybrid, on-site), and any travel requirements.

Common mistake: Omitting the compensation range entirely. Several US states (California, Colorado, New York, Washington) and Canadian provinces now require salary ranges on job postings — omitting them creates compliance risk and reduces qualified applicant volume.

In plain language: A legally required or strongly recommended statement affirming the employer's commitment to non-discriminatory hiring and willingness to provide reasonable accommodations.

Common mistake: Using a generic boilerplate statement without updating it to reflect the employer's applicable jurisdiction. EEO language must reference protected classes recognized in the governing jurisdiction — federal, state/provincial, and local laws differ.

A data analyst job description is a formal document that defines the duties, required qualifications, tools, reporting structure, and employment conditions for a data analyst role. It is used as a recruiting tool, a legal reference document attached to employment agreements, and a performance management baseline. A well-drafted description protects the employer in disputes over role scope, compensation equity, and termination for cause.

At minimum: the official job title and FLSA or local-law classification, a role summary tied to business outcomes, a list of essential duties, a separate list of required and preferred qualifications, specific tools and proficiency levels, the reporting structure, the compensation range, the work location, and an equal opportunity statement. Missing any of these creates recruiting ambiguity or compliance exposure depending on jurisdiction.

A job description is generally considered a legal document when it is attached to or incorporated by reference into an employment contract. On its own, a job posting is typically not a binding offer. However, the duties listed in a signed, incorporated job description can be enforced in performance management, compensation disputes, and ADA accommodation proceedings. Employers should treat the approved description as a binding scope-of-work document from day one.

In a growing number of jurisdictions — including California, Colorado, New York, Washington, and several cities — salary ranges are legally required on job postings. Even where not mandated, including a range increases qualified applicant volume and reduces offer-stage negotiation time. Remote roles are subject to the pay-transparency laws of every state or province where the successful candidate may work, not just where the employer is headquartered.

SQL proficiency is the most universally required technical skill for data analyst roles, typically at an intermediate to advanced level. Python or R is commonly required or strongly preferred. Most employers also specify a BI tool such as Tableau, Power BI, or Looker, and a data warehouse platform such as Snowflake, BigQuery, or Redshift. Listing specific tools with proficiency levels allows structured, objective candidate scoring.

A junior data analyst description typically requires a bachelor's degree and 0–2 years of experience, emphasizes structured task completion under supervision, and lists foundational SQL and Excel skills. A senior description requires 5+ years of demonstrated impact, includes cross-functional stakeholder leadership, autonomous problem scoping, and often mentorship of junior analysts. The duties, required tools, and compensation bands should differ materially — using the same template for both creates misaligned hiring and pay-equity problems.

Yes — and it is best practice to do so. Attach the approved, signed job description as a schedule or exhibit to the employment contract, with the contract body referencing the schedule by name and date. This creates a clear, enforceable record of the employee's agreed duties and the employer's stated expectations, which supports performance management, IP assignment enforcement, and termination-for-cause documentation.

Review and update the job description at least once per year, aligned to the annual performance cycle. Update it immediately when the role's duties or tools change materially — for example, when a new BI platform is adopted or analytics scope expands to a new business unit. Obtain the employee's written acknowledgment of any material revision. A description that is more than 18 months out of date will undermine performance management and compensation-equity arguments.

In the US, employers covered by Title VII, the ADA, and the ADEA must include a statement affirming they do not discriminate on the basis of federally protected characteristics. Many states and cities protect additional classes — sexual orientation, gender identity, and others. In the UK, the Equality Act 2010 requires that postings do not discriminate on nine protected characteristics. In the EU, member-state transpositions of the Equal Treatment Directive apply. Review the applicable law for each jurisdiction where the posting appears.