Data Visualization Specialist Job Description Template

Dashboard Building · 22%
The role must independently produce reliable dashboards and reports in production BI/visualization tooling. Evaluated in Round 1.

• Weak: Builds basic visuals but struggles to implement required filters, refresh behavior, or layout consistency.
• Meets the bar: Builds dashboards that match requirements, including correct filters, clear metric presentation, and maintainable structure.
• Strong: Delivers well-structured dashboards with thoughtful interaction design and consistent metric behavior across views.

Visualization Best Practices · 18%
Clear chart selection and visual hierarchy directly impact stakeholders’ ability to interpret metrics correctly. Evaluated in Round 1.

• Weak: Chooses charts that obscure comparisons or trends; layout makes it hard to identify the key message.
• Meets the bar: Selects appropriate chart types and uses layout/visual hierarchy to support the intended decision or story.
• Strong: Designs highly readable visuals that prevent common misinterpretations and guide attention to the right signals.

Metric Validation · 18%
Ensuring metric definitions and visualization logic are correct is essential to dashboard trust. Evaluated in Round 2.

• Weak: Responds to discrepancies without a systematic approach to isolate root causes (filters, grain, definitions, logic).
• Meets the bar: Validates metric logic end-to-end and documents what was changed to resolve mismatches.
• Strong: Proactively defines metric requirements, catches edge cases early, and verifies consistency across multiple dashboard consumers.

Stakeholder Narratives · 16%
Stakeholders need more than visuals; they need a clear explanation of meaning, caveats, and implications. Evaluated in Round 2.

• Weak: Explains visuals with limited context; fails to address why trends changed or how to interpret them correctly.
• Meets the bar: Produces clear explanations that connect visuals to decisions and includes necessary caveats.
• Strong: Crafts concise, decision-oriented narratives and anticipates stakeholder questions and misreads.

Accessibility and Readability · 10%
Accessible, readable visuals reduce misinterpretation and broaden effective usage. Evaluated in Round 2.

• Weak: Uses color/contrast or dense labeling that makes key information hard to read for some users.
• Meets the bar: Applies accessible color/contrast, readable typography, and clear legends/labels.
• Strong: Designs visuals that remain understandable across accessibility needs and different viewing contexts.

Cross-Functional Iteration · 10%
The role requires independent work on defined tasks while iterating based on stakeholder feedback. Evaluated in Round 3.

• Weak: Requests frequent clarification late in the process or dismisses feedback without incorporating it.
• Meets the bar: Gathers requirements early, iterates based on feedback, and communicates progress and tradeoffs.
• Strong: Leads productive feedback loops, clarifies ambiguity, and aligns stakeholders on metric/visual intent.

Operational Reliability · 6%
Dashboards must remain dependable; reliability practices support trust and usability. Evaluated in Round 3.

• Weak: Addresses issues reactively without preventing recurrence.
• Meets the bar: Troubleshoots refresh/performance issues and documents what was resolved.
• Strong: Implements or advocates for preventative checks and monitoring patterns that reduce repeated failures.