{"id":75055,"date":"2026-04-16T11:46:42","date_gmt":"2026-04-16T11:46:42","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/senior-data-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path\/"},"modified":"2026-04-16T11:46:42","modified_gmt":"2026-04-16T11:46:42","slug":"senior-data-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/senior-data-specialist-role-blueprint-responsibilities-skills-kpis-and-career-path\/","title":{"rendered":"Senior Data Specialist: Role Blueprint, Responsibilities, Skills, KPIs, and Career Path"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">1) Role Summary<\/h2>\n\n\n\n<p>The <strong>Senior Data Specialist<\/strong> is a senior individual contributor in the <strong>Data &amp; Analytics<\/strong> function who ensures that enterprise data is <strong>trusted, well-defined, discoverable, governed, and usable<\/strong> for analytics, product decision-making, and operational reporting. This role bridges technical data work (SQL, data quality, lineage, metadata, access controls) with business clarity (definitions, metrics, documentation, stakeholder alignment), reducing ambiguity and preventing costly misinterpretation of data.<\/p>\n\n\n\n<p>In a software\/IT organization\u2014typically operating a SaaS product with multiple systems (application databases, CRM\/billing, support tooling, telemetry)\u2014this role exists because data is only valuable when it is <strong>consistent, compliant, and reliably consumable<\/strong> across teams. The Senior Data Specialist creates business value by <strong>improving decision velocity<\/strong>, reducing data incidents, preventing rework, enabling self-service analytics, and supporting audit-ready governance.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Role horizon:<\/strong> Current (established, widely adopted in modern data organizations)<\/li>\n<li><strong>Typical interaction teams:<\/strong> Data Engineering, Analytics Engineering, BI\/Analytics, Product Management, Finance\/RevOps, Customer Success Ops, Security\/GRC, Platform\/Cloud Ops, and occasionally external auditors or vendors.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">2) Role Mission<\/h2>\n\n\n\n<p><strong>Core mission:<\/strong><br\/>\nEnsure the organization\u2019s critical datasets, metrics, and analytical outputs are <strong>accurate, standardized, well-documented, compliant, and reliably delivered<\/strong> to downstream consumers\u2014so teams can make decisions confidently at scale.<\/p>\n\n\n\n<p><strong>Strategic importance to the company:<\/strong><br\/>\nAs software companies grow, the number of systems, data producers, and data consumers increases rapidly. Without strong data stewardship and operational rigor, \u201cone version of the truth\u201d collapses into conflicting dashboards, untrusted metrics, and escalating governance risk. The Senior Data Specialist prevents this by institutionalizing <strong>data quality management, metric integrity, metadata discipline, and accountable ownership<\/strong>.<\/p>\n\n\n\n<p><strong>Primary business outcomes expected:<\/strong>\n&#8211; Increased trust in data products (dashboards, KPIs, curated datasets, semantic models)\n&#8211; Reduced time-to-answer for business questions through better discoverability and definitions\n&#8211; Lower operational risk via governance controls, audit trails, and privacy-by-design\n&#8211; Improved efficiency by reducing duplicate data work and preventing repeated data incidents<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3) Core Responsibilities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Strategic responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Define and operationalize critical data domains<\/strong> (e.g., customer, subscription, usage, revenue) by clarifying entities, ownership, and canonical definitions.<\/li>\n<li><strong>Establish metric integrity practices<\/strong> (North Star, KPI definitions, calculation logic, metric change control) to prevent inconsistent reporting.<\/li>\n<li><strong>Drive data product thinking<\/strong> for shared datasets: treat curated tables, semantic layers, and dashboards as products with SLAs, documentation, and lifecycle ownership.<\/li>\n<li><strong>Prioritize data quality investments<\/strong> with stakeholders using impact-based frameworks (business criticality, incident history, regulatory exposure).<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Operational responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"5\">\n<li><strong>Run data quality operations<\/strong>: monitor quality signals, triage anomalies, coordinate fixes, and document post-incident learnings.<\/li>\n<li><strong>Own the \u201cdata intake\u201d process<\/strong> for analytics requests and dataset changes: clarify requirements, validate feasibility, and steer work to the right teams.<\/li>\n<li><strong>Maintain a backlog of data quality, metadata, and standardization improvements<\/strong> and deliver consistently against it.<\/li>\n<li><strong>Support release\/change management<\/strong> for analytics assets (dashboards, models, curated tables) to reduce breakages and improve communication.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Technical responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"9\">\n<li><strong>Write and review complex SQL<\/strong> for validation, reconciliation, profiling, and building curated datasets (often in partnership with analytics\/data engineers).<\/li>\n<li><strong>Implement and maintain data tests<\/strong> (schema tests, freshness tests, volume checks, referential integrity, business rule validations).<\/li>\n<li><strong>Perform root cause analysis<\/strong> for data discrepancies across pipelines, warehouses, and BI layers, including source-system behavior.<\/li>\n<li><strong>Design and maintain metadata assets<\/strong>: data dictionaries, metric catalogs, lineage documentation, ownership tags, data classification tags.<\/li>\n<li><strong>Partner on semantic modeling<\/strong> (e.g., metrics layer \/ BI semantic models) to ensure consistency, performance, and business alignment.<\/li>\n<li><strong>Enable data access controls<\/strong>: collaborate on role-based access, row\/column-level security patterns, and compliant sharing mechanisms.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Cross-functional or stakeholder responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"15\">\n<li><strong>Facilitate alignment workshops<\/strong> for definitions and metrics (e.g., \u201cWhat is an active customer?\u201d \u201cHow do we define churn?\u201d) and translate outcomes into documented, testable logic.<\/li>\n<li><strong>Train and enable data consumers<\/strong> (analysts, PMs, operators) on data literacy, metric usage, and how to find\/interpret data assets.<\/li>\n<li><strong>Communicate data incidents and changes<\/strong> clearly to stakeholders, including scope, impact, workaround, and remediation timelines.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Governance, compliance, or quality responsibilities<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"18\">\n<li><strong>Support governance frameworks<\/strong> (data classification, retention, consent, audit logs) and align with Security\/GRC requirements (e.g., SOC 2, ISO 27001, GDPR\/CCPA practices as applicable).<\/li>\n<li><strong>Ensure traceability and auditability<\/strong> for key metrics and reporting used in executive, financial, or customer-facing contexts.<\/li>\n<li><strong>Promote accountable ownership<\/strong> by implementing RACI for datasets and enforcing stewardship practices.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership responsibilities (appropriate to \u201cSenior\u201d IC scope)<\/h3>\n\n\n\n<ol class=\"wp-block-list\" start=\"21\">\n<li><strong>Mentor peers and raise the quality bar<\/strong> through reviews of SQL, documentation, testing patterns, and stakeholder communication.<\/li>\n<li><strong>Lead small cross-functional initiatives<\/strong> (e.g., a \u201cRevenue Metrics Standardization\u201d project) without direct people management authority.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">4) Day-to-Day Activities<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Daily activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitor data quality alerts (freshness, volume anomalies, failed tests) and triage issues.<\/li>\n<li>Investigate discrepancies reported by business users (dashboard mismatch, metric drift, missing data).<\/li>\n<li>Write SQL to validate pipelines, reconcile totals across systems, and pinpoint failure points.<\/li>\n<li>Update data catalog entries: definitions, owners, sensitivity labels, links to dashboards or models.<\/li>\n<li>Answer stakeholder questions: \u201cWhich table should I use?\u201d \u201cWhat\u2019s the official churn metric?\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Weekly activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Run or participate in a <strong>data quality triage<\/strong> meeting: review incidents, assign owners, track remediations.<\/li>\n<li>Conduct stakeholder syncs with Product\/Finance\/RevOps to refine metric definitions or evaluate changes.<\/li>\n<li>Review pull requests for analytics models or semantic layer changes (where the operating model supports peer review).<\/li>\n<li>Deliver enablement: short trainings, office hours, or \u201chow-to\u201d guides for self-service usage.<\/li>\n<li>Maintain the backlog: prioritize improvements, clarify acceptance criteria, and unblock dependencies.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Monthly or quarterly activities<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Perform <strong>domain-level quality reviews<\/strong>: profiling, completeness checks, and coverage for critical fields.<\/li>\n<li>Refresh and audit metric catalogs: validate that definitions match implementations in BI and transformation layers.<\/li>\n<li>Participate in quarterly planning to align data quality and governance investments with business priorities.<\/li>\n<li>Produce a <strong>data trust report<\/strong>: trends in incidents, top recurring root causes, and areas of risk.<\/li>\n<li>Review access patterns and permissions with Security\/GRC (especially for sensitive datasets).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recurring meetings or rituals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data Quality Triage (weekly)<\/li>\n<li>Data Governance\/Stewardship Council (biweekly or monthly, depending on maturity)<\/li>\n<li>Stakeholder office hours (weekly)<\/li>\n<li>Sprint planning \/ Kanban replenishment (weekly)<\/li>\n<li>Cross-team release notes review for analytics changes (weekly or biweekly)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Incident, escalation, or emergency work (when relevant)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Participate in severity-based incident response for critical metrics (e.g., revenue reporting inaccuracies).<\/li>\n<li>Coordinate a temporary rollback or \u201cdata freeze\u201d on impacted dashboards.<\/li>\n<li>Communicate incident scope and status to exec stakeholders when business impact is high.<\/li>\n<li>Ensure post-incident actions are captured (tests added, monitoring improved, documentation updated).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5) Key Deliverables<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Curated datasets \/ data marts<\/strong> (domain-aligned, documented, tested; may be built directly or co-developed with analytics engineering)<\/li>\n<li><strong>Metric definitions &amp; calculation specifications<\/strong> (single source of truth; versioned; linked to implementations)<\/li>\n<li><strong>Data dictionaries &amp; business glossaries<\/strong> (field-level definitions, allowed values, example usage)<\/li>\n<li><strong>Data quality test suites<\/strong> (schema, freshness, business-rule validations; automated and observable)<\/li>\n<li><strong>Reconciliation and validation reports<\/strong> (e.g., warehouse vs billing system totals; month-end close support)<\/li>\n<li><strong>Data lineage documentation<\/strong> (source-to-report mapping for critical dashboards\/metrics)<\/li>\n<li><strong>Access control and data classification documentation<\/strong> (who can access what; sensitivity labeling)<\/li>\n<li><strong>Data incident runbooks and postmortems<\/strong> (root cause, remediation, prevention actions)<\/li>\n<li><strong>Enablement artifacts<\/strong> (training decks, onboarding guides, office-hours FAQs)<\/li>\n<li><strong>Governance process artifacts<\/strong> (RACI, change control steps, approval workflows for metric changes)<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6) Goals, Objectives, and Milestones<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">30-day goals (orientation and baseline establishment)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Understand business model, key revenue\/usage flows, and the most critical KPIs.<\/li>\n<li>Map primary source systems (application DBs, billing, CRM, support, telemetry) to the warehouse\/lakehouse.<\/li>\n<li>Review existing documentation quality: catalogs, definitions, lineage, and dashboard inventories.<\/li>\n<li>Identify top recurring data incidents and known \u201ctrust gaps.\u201d<\/li>\n<li>Build relationships with key stakeholders: Data Engineering, Analytics, Finance\/RevOps, Product Ops, Security\/GRC.<\/li>\n<\/ul>\n\n\n\n<p><strong>Success indicators (30 days):<\/strong>\n&#8211; Can independently navigate warehouse schemas and key dashboards.\n&#8211; Produces an initial \u201ccritical metrics and datasets\u201d inventory with owners and known issues.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">60-day goals (early wins and operational rhythm)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implement or strengthen automated tests for 1\u20132 critical domains (e.g., subscription &amp; revenue, usage telemetry).<\/li>\n<li>Standardize definitions for a small set of high-impact metrics (e.g., active customers, churn, ARR\/MRR).<\/li>\n<li>Establish a consistent triage and communication mechanism for data issues (ticketing, severity, SLAs).<\/li>\n<li>Deliver first enablement session\/office hours and publish \u201chow we define and find X\u201d guidance.<\/li>\n<\/ul>\n\n\n\n<p><strong>Success indicators (60 days):<\/strong>\n&#8211; Measurable reduction in recurring issues for the targeted domain(s).\n&#8211; Stakeholders report improved clarity and reduced time spent debating definitions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">90-day goals (scaling trust and governance)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Expand quality monitoring to additional critical assets (executive dashboards, finance reporting, product analytics).<\/li>\n<li>Implement or refine change control for metric logic updates (versioning, approvals, release notes).<\/li>\n<li>Improve catalog completeness: ownership, definitions, sensitivity classification for priority datasets.<\/li>\n<li>Document and socialize a sustainable operating model: how issues are raised, prioritized, resolved, and prevented.<\/li>\n<\/ul>\n\n\n\n<p><strong>Success indicators (90 days):<\/strong>\n&#8211; Clear improvements in test coverage, documentation coverage, and incident response time.\n&#8211; Increased adoption of standardized datasets\/metrics (reduced \u201cshadow SQL\u201d and duplicate dashboards).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6-month milestones (institutionalization)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data domain stewardship is functioning with clear RACI and consistent governance routines.<\/li>\n<li>Critical dashboards\/metrics are backed by documented logic, lineage, and automated tests.<\/li>\n<li>A measurable \u201cdata trust\u201d baseline exists (incident frequency, time-to-detect, time-to-resolve, stakeholder satisfaction).<\/li>\n<li>Access patterns for sensitive data are audited and aligned with security requirements.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12-month objectives (enterprise-grade maturity)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Achieve high reliability for key data products (agreed SLAs for freshness\/accuracy).<\/li>\n<li>Reduce major data incidents and improve prevention through systematic root-cause remediation.<\/li>\n<li>Mature self-service analytics with high discoverability and consistent metric semantics.<\/li>\n<li>Support audit readiness for reporting and privacy\/compliance obligations (as applicable).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Long-term impact goals (beyond 12 months)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data becomes a competitive advantage: faster experimentation, more accurate forecasting, better product decisions.<\/li>\n<li>The organization operates with a consistent semantic layer and measurable trust across domains.<\/li>\n<li>Data governance becomes \u201cbuilt-in\u201d rather than \u201cbolted-on,\u201d enabling scale without chaos.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Role success definition<\/h3>\n\n\n\n<p>This role is successful when <strong>leaders and practitioners consistently use the same trusted metrics and datasets<\/strong>, data incidents are <strong>rare and quickly resolved<\/strong>, and critical reporting has <strong>traceability, documentation, and appropriate controls<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What high performance looks like<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Proactively identifies risk areas before they become incidents.<\/li>\n<li>Converts ambiguous business questions into precise, testable data definitions.<\/li>\n<li>Establishes lightweight governance that accelerates rather than blocks delivery.<\/li>\n<li>Produces durable improvements (tests, lineage, catalogs, processes) instead of one-off fixes.<\/li>\n<li>Earns stakeholder trust through clarity, reliability, and follow-through.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">7) KPIs and Productivity Metrics<\/h2>\n\n\n\n<p>The Senior Data Specialist should be measured using a balanced framework that includes <strong>outputs, outcomes, quality, reliability, efficiency, and stakeholder trust<\/strong>. Targets vary by maturity; example benchmarks below assume a mid-sized SaaS organization with an established warehouse and BI footprint.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Metric name<\/th>\n<th>What it measures<\/th>\n<th>Why it matters<\/th>\n<th>Example target \/ benchmark<\/th>\n<th>Frequency<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Critical asset documentation coverage<\/td>\n<td>% of Tier-1 datasets\/metrics with complete definitions, owners, and usage notes<\/td>\n<td>Discoverability and consistency reduce rework and misinterpretation<\/td>\n<td>85\u201395% for Tier-1 assets<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Data quality test coverage (Tier-1)<\/td>\n<td>% of Tier-1 tables\/metrics protected by automated tests<\/td>\n<td>Prevents regressions; lowers incident rate<\/td>\n<td>80%+ of Tier-1 assets with tests<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Test pass rate (Tier-1)<\/td>\n<td>% of scheduled test runs passing<\/td>\n<td>Indicates ongoing health and stability<\/td>\n<td>98%+ pass rate (excluding known\/managed issues)<\/td>\n<td>Weekly<\/td>\n<\/tr>\n<tr>\n<td>Freshness SLA attainment<\/td>\n<td>% of Tier-1 datasets meeting freshness SLAs<\/td>\n<td>Ensures operational trust and decision timeliness<\/td>\n<td>95\u201399% SLA attainment<\/td>\n<td>Weekly<\/td>\n<\/tr>\n<tr>\n<td>Data incident rate (Tier-1)<\/td>\n<td>Count of incidents affecting critical reporting<\/td>\n<td>Direct measure of trust and reliability<\/td>\n<td>Downward trend quarter-over-quarter<\/td>\n<td>Monthly\/Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Mean time to detect (MTTD)<\/td>\n<td>Time from issue occurrence to detection<\/td>\n<td>Faster detection reduces downstream impact<\/td>\n<td>&lt; 2 hours for Tier-1 (mature org); &lt; 1 day (less mature)<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Mean time to resolve (MTTR)<\/td>\n<td>Time from detection to remediation\/containment<\/td>\n<td>Minimizes business disruption<\/td>\n<td>&lt; 1 day for high severity; &lt; 3 days overall average<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Recurrence rate<\/td>\n<td>% of incidents repeating within 90 days<\/td>\n<td>Measures effectiveness of prevention actions<\/td>\n<td>&lt; 10\u201315%<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Reconciliation accuracy (finance-aligned)<\/td>\n<td>Alignment between warehouse metrics and source-of-record totals<\/td>\n<td>Prevents financial misstatement and exec mistrust<\/td>\n<td>Variance within agreed tolerance (e.g., &lt;0.5\u20131%)<\/td>\n<td>Monthly (close)<\/td>\n<\/tr>\n<tr>\n<td>Metric definition adherence<\/td>\n<td>% of dashboards using canonical metrics rather than custom logic<\/td>\n<td>Reduces metric drift and inconsistent narratives<\/td>\n<td>80%+ adoption for Tier-1 metrics<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Self-service success rate<\/td>\n<td>% of stakeholder questions answered using documented assets without custom data pulls<\/td>\n<td>Indicates maturity of discoverability and enablement<\/td>\n<td>Increasing trend; 60\u201375%+<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Time-to-answer (standard questions)<\/td>\n<td>Average time to answer recurring business questions<\/td>\n<td>Reflects efficiency from good data products<\/td>\n<td>Reduce by 20\u201340% over 6\u201312 months<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Catalog search-to-use conversion<\/td>\n<td>% of catalog searches resulting in asset usage<\/td>\n<td>Measures practical discoverability<\/td>\n<td>Increasing trend<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Access request cycle time<\/td>\n<td>Time to approve\/fulfill data access requests<\/td>\n<td>Balances speed with compliance<\/td>\n<td>1\u20135 business days depending on sensitivity<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Sensitive data exposure exceptions<\/td>\n<td>Count of policy exceptions or improper access<\/td>\n<td>Compliance and security protection<\/td>\n<td>Near zero; all exceptions documented<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder satisfaction (data trust)<\/td>\n<td>Survey score from key consumers on data reliability and clarity<\/td>\n<td>Captures perceived trust, not just technical signals<\/td>\n<td>4.0+\/5 average for Tier-1 stakeholders<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Enablement throughput<\/td>\n<td># of trainings\/office hours, adoption of guides, attendance<\/td>\n<td>Reinforces consistent usage and literacy<\/td>\n<td>1\u20132 sessions\/month + ongoing office hours<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Backlog burn-down (quality\/governance)<\/td>\n<td>Delivery rate for planned improvements<\/td>\n<td>Demonstrates execution<\/td>\n<td>70\u201385% of committed items delivered<\/td>\n<td>Sprint\/Monthly<\/td>\n<\/tr>\n<tr>\n<td>Change failure rate (analytics releases)<\/td>\n<td>% of changes causing incidents or rollbacks<\/td>\n<td>Measures discipline and release quality<\/td>\n<td>&lt; 5\u201310% depending on maturity<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Cross-team cycle time for fixes<\/td>\n<td>Time to coordinate fix across DE\/AE\/BI<\/td>\n<td>Reveals operating model friction<\/td>\n<td>Downward trend; defined SLAs by severity<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">8) Technical Skills Required<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Must-have technical skills<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Advanced SQL (Critical)<\/strong> <\/li>\n<li><strong>Description:<\/strong> Complex joins, window functions, CTEs, incremental logic validation, reconciliation queries, performance-aware querying.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Validate pipelines, reconcile metrics, build\/inspect curated datasets, debug discrepancies.<\/p>\n<\/li>\n<li>\n<p><strong>Data quality engineering concepts (Critical)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Data testing types (schema, freshness, volume, referential integrity, business rules), anomaly detection basics, quality dimensions (accuracy, completeness, timeliness).  <\/li>\n<li>\n<p><strong>Use:<\/strong> Create and maintain automated tests and monitoring for critical data products.<\/p>\n<\/li>\n<li>\n<p><strong>Data modeling literacy (Important)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Understanding of dimensional modeling, normalized vs denormalized patterns, slowly changing dimensions, event modeling basics.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Ensure curated datasets are understandable, stable, and usable for BI\/product analytics.<\/p>\n<\/li>\n<li>\n<p><strong>Metadata, documentation, and lineage practices (Critical)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Data dictionaries, business glossaries, ownership tags, lineage mapping, versioning of definitions.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Prevent metric drift; enable discoverability and auditability.<\/p>\n<\/li>\n<li>\n<p><strong>BI\/semantic layer fundamentals (Important)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Measures vs dimensions, semantic model design principles, metric governance, dashboard performance considerations.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Align canonical metrics with BI implementations; reduce inconsistent dashboards.<\/p>\n<\/li>\n<li>\n<p><strong>Access controls and data privacy fundamentals (Important)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> RBAC basics, least privilege, row\/column-level security patterns, handling PII.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Ensure compliant sharing and protect sensitive data.<\/p>\n<\/li>\n<li>\n<p><strong>Data pipeline debugging &amp; systems thinking (Critical)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Tracing issues across sources, ingestion, transformations, and BI layers; log\/alert interpretation.  <\/li>\n<li><strong>Use:<\/strong> Root cause analysis and coordination of fixes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Good-to-have technical skills<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Python for data analysis\/automation (Important)<\/strong> <\/li>\n<li>\n<p><strong>Use:<\/strong> Profiling datasets, lightweight automations, anomaly detection prototypes, API pulls for reconciliation.<\/p>\n<\/li>\n<li>\n<p><strong>dbt or similar transformation framework (Important, common in modern stacks)<\/strong> <\/p>\n<\/li>\n<li>\n<p><strong>Use:<\/strong> Add tests, review model logic, enforce conventions, contribute documentation.<\/p>\n<\/li>\n<li>\n<p><strong>Workflow orchestration familiarity (Optional to Important depending on org)<\/strong> <\/p>\n<\/li>\n<li><strong>Examples:<\/strong> Airflow, Dagster, Prefect  <\/li>\n<li>\n<p><strong>Use:<\/strong> Understand scheduling dependencies and failure modes for incident troubleshooting.<\/p>\n<\/li>\n<li>\n<p><strong>Data catalog\/governance platform experience (Important where adopted)<\/strong> <\/p>\n<\/li>\n<li><strong>Examples:<\/strong> Alation, Collibra, Atlan, Microsoft Purview  <\/li>\n<li>\n<p><strong>Use:<\/strong> Stewardship workflows, glossary management, discovery enablement.<\/p>\n<\/li>\n<li>\n<p><strong>Observability tooling for data (Optional)<\/strong> <\/p>\n<\/li>\n<li><strong>Examples:<\/strong> Monte Carlo, Bigeye, Datadog data monitors  <\/li>\n<li><strong>Use:<\/strong> Faster detection and impact analysis.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Advanced or expert-level technical skills<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Metric governance and semantic architecture (Critical for senior performance)<\/strong> <\/li>\n<li><strong>Description:<\/strong> Designing canonical metric layers, handling metric versioning, change control, and metric lineage.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Prevent executive reporting disputes; scale consistent analytics.<\/p>\n<\/li>\n<li>\n<p><strong>Performance optimization in warehouses (Important in scale contexts)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Partitioning\/clustering concepts, query optimization, cost governance.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Improve dashboard performance and reduce compute costs.<\/p>\n<\/li>\n<li>\n<p><strong>Advanced reconciliation and auditability techniques (Important)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Reproducible reconciliations, tolerance thresholds, audit trails, \u201csource of truth\u201d mapping.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Finance-aligned reporting, compliance readiness.<\/p>\n<\/li>\n<li>\n<p><strong>Data classification and policy enforcement patterns (Optional, context-specific)<\/strong> <\/p>\n<\/li>\n<li><strong>Use:<\/strong> Stronger governance in regulated environments or large enterprises.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Emerging future skills for this role (2\u20135 years)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>AI-assisted data stewardship (Important, emerging)<\/strong> <\/li>\n<li><strong>Description:<\/strong> Using AI to draft definitions, detect anomalies, suggest lineage, and summarize incidents\u2014while validating correctness.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Scale documentation and triage without sacrificing accuracy.<\/p>\n<\/li>\n<li>\n<p><strong>Policy-as-code for data governance (Optional, emerging)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Codifying access policies, classification, and retention rules into automated checks.  <\/li>\n<li>\n<p><strong>Use:<\/strong> Reduce manual governance overhead.<\/p>\n<\/li>\n<li>\n<p><strong>Data contract practices (Important, emerging-to-common)<\/strong> <\/p>\n<\/li>\n<li><strong>Description:<\/strong> Formal expectations between producers and consumers (schemas, SLAs, breaking-change rules).  <\/li>\n<li><strong>Use:<\/strong> Prevent upstream changes from silently breaking downstream reporting.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9) Soft Skills and Behavioral Capabilities<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Analytical rigor and skepticism<\/strong> <\/li>\n<li><strong>Why it matters:<\/strong> Data issues often hide behind plausible numbers; the role must validate truth, not assume it.  <\/li>\n<li><strong>On the job:<\/strong> Cross-checks, reconciliations, sensitivity to edge cases, careful interpretation.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> Spots inconsistencies early and proves\/quantifies issues with evidence.<\/p>\n<\/li>\n<li>\n<p><strong>Business translation and clarity<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> The value comes from aligning people around definitions and outcomes, not just building artifacts.  <\/li>\n<li><strong>On the job:<\/strong> Converts vague questions into precise metrics, definitions, and acceptance criteria.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> Stakeholders repeat back definitions consistently; fewer follow-up debates occur.<\/p>\n<\/li>\n<li>\n<p><strong>Stakeholder management without authority<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> The role depends on influencing data producers and consumers across teams.  <\/li>\n<li><strong>On the job:<\/strong> Negotiates priorities, sets expectations, escalates appropriately, and maintains trust.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> Progress continues even when priorities conflict; partners feel supported, not blocked.<\/p>\n<\/li>\n<li>\n<p><strong>Structured problem solving and root cause discipline<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> Fixing symptoms creates repeated incidents; durable fixes require root cause resolution.  <\/li>\n<li><strong>On the job:<\/strong> Incident analysis, \u201c5 whys,\u201d causal mapping, prevention actions.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> Recurrence rates drop; fixes include monitoring\/tests\/documentation updates.<\/p>\n<\/li>\n<li>\n<p><strong>Communication under ambiguity and during incidents<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> Data incidents cause executive anxiety; communication must be calm, factual, and frequent.  <\/li>\n<li><strong>On the job:<\/strong> Status updates, impact statements, workaround guidance, timelines.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> Stakeholders understand what\u2019s affected and what\u2019s being done without panic.<\/p>\n<\/li>\n<li>\n<p><strong>Documentation discipline and attention to detail<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> Inconsistent definitions and undocumented logic are a primary cause of data mistrust.  <\/li>\n<li><strong>On the job:<\/strong> Maintaining glossaries, dictionaries, lineage maps, and release notes.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> Documentation remains current and is actively used.<\/p>\n<\/li>\n<li>\n<p><strong>Pragmatism and prioritization<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> Perfect governance can paralyze delivery; the best approach is risk-based and iterative.  <\/li>\n<li><strong>On the job:<\/strong> Tiering assets, focusing on high-impact datasets, defining \u201cgood enough\u201d controls.  <\/li>\n<li>\n<p><strong>Strong performance:<\/strong> High-risk areas are protected first; stakeholders feel speed improves, not slows.<\/p>\n<\/li>\n<li>\n<p><strong>Mentorship and quality leadership (Senior IC)<\/strong> <\/p>\n<\/li>\n<li><strong>Why it matters:<\/strong> Senior specialists multiply impact by raising standards across the function.  <\/li>\n<li><strong>On the job:<\/strong> Reviews, coaching, templates, best-practice sharing.  <\/li>\n<li><strong>Strong performance:<\/strong> Peers adopt consistent patterns; quality improves without centralized policing.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10) Tools, Platforms, and Software<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Tool \/ platform<\/th>\n<th>Primary use<\/th>\n<th>Common \/ Optional \/ Context-specific<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Cloud platforms<\/td>\n<td>AWS \/ Azure \/ GCP<\/td>\n<td>Host data infrastructure and services<\/td>\n<td>Context-specific (depends on company)<\/td>\n<\/tr>\n<tr>\n<td>Data warehouse \/ lakehouse<\/td>\n<td>Snowflake \/ BigQuery \/ Redshift \/ Databricks<\/td>\n<td>Core analytics storage and compute<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Data transformation<\/td>\n<td>dbt<\/td>\n<td>Transformations, tests, documentation generation<\/td>\n<td>Common (modern stacks)<\/td>\n<\/tr>\n<tr>\n<td>Orchestration<\/td>\n<td>Airflow \/ Dagster \/ Prefect<\/td>\n<td>Scheduling, dependencies, pipeline operations<\/td>\n<td>Common to Optional<\/td>\n<\/tr>\n<tr>\n<td>BI \/ analytics<\/td>\n<td>Looker \/ Tableau \/ Power BI<\/td>\n<td>Dashboards, semantic models, self-service analytics<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Data quality testing<\/td>\n<td>Great Expectations \/ dbt tests<\/td>\n<td>Automated validations and quality gates<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Data observability<\/td>\n<td>Monte Carlo \/ Bigeye \/ Datadog<\/td>\n<td>Monitoring freshness, anomalies, lineage impact<\/td>\n<td>Optional (maturity-dependent)<\/td>\n<\/tr>\n<tr>\n<td>Data catalog \/ governance<\/td>\n<td>Alation \/ Collibra \/ Atlan \/ Purview<\/td>\n<td>Glossary, discovery, stewardship workflows<\/td>\n<td>Optional to Common (enterprise)<\/td>\n<\/tr>\n<tr>\n<td>Ticketing \/ ITSM<\/td>\n<td>Jira \/ ServiceNow<\/td>\n<td>Issue intake, incident tracking, SLAs<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Collaboration<\/td>\n<td>Slack \/ Microsoft Teams<\/td>\n<td>Stakeholder comms, incident channels<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Documentation<\/td>\n<td>Confluence \/ Notion \/ SharePoint<\/td>\n<td>Definitions, runbooks, governance docs<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Source control<\/td>\n<td>GitHub \/ GitLab \/ Bitbucket<\/td>\n<td>Version control for analytics code and docs<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>CI\/CD<\/td>\n<td>GitHub Actions \/ GitLab CI \/ Azure DevOps<\/td>\n<td>Automated tests and deployment for analytics assets<\/td>\n<td>Optional to Common<\/td>\n<\/tr>\n<tr>\n<td>IDE \/ notebooks<\/td>\n<td>VS Code \/ Jupyter<\/td>\n<td>SQL\/Python development and analysis<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Query tools<\/td>\n<td>DataGrip \/ DBeaver<\/td>\n<td>SQL development and exploration<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Identity &amp; access<\/td>\n<td>Okta \/ Azure AD<\/td>\n<td>RBAC integration, identity management<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Security \/ privacy<\/td>\n<td>OneTrust (privacy), DLP tooling<\/td>\n<td>Privacy workflows and controls<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Product analytics (if applicable)<\/td>\n<td>Amplitude \/ Mixpanel<\/td>\n<td>Event tracking governance and metric alignment<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>CRM \/ billing systems (sources)<\/td>\n<td>Salesforce \/ Stripe \/ Zuora<\/td>\n<td>Source-of-record reconciliation and definitions<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">11) Typical Tech Stack \/ Environment<\/h2>\n\n\n\n<p><strong>Infrastructure environment<\/strong>\n&#8211; Cloud-first environment (AWS\/Azure\/GCP), with managed data services.\n&#8211; Separation of environments: dev\/staging\/prod (varies by maturity).\n&#8211; Emphasis on cost governance for warehouse compute.<\/p>\n\n\n\n<p><strong>Application environment<\/strong>\n&#8211; SaaS application databases (PostgreSQL\/MySQL), microservices emitting events, logs, and telemetry.\n&#8211; Multiple operational systems: CRM, billing, marketing automation, support tooling.<\/p>\n\n\n\n<p><strong>Data environment<\/strong>\n&#8211; Central warehouse\/lakehouse containing:\n  &#8211; Ingested raw\/staged data\n  &#8211; Modeled\/curated layers (data marts)\n  &#8211; Semantic models for BI\n&#8211; Transformations managed via dbt or equivalent.\n&#8211; Data quality tests integrated into pipelines and\/or CI.<\/p>\n\n\n\n<p><strong>Security environment<\/strong>\n&#8211; RBAC integrated with identity provider.\n&#8211; Sensitive data handling practices: PII tagging, restricted datasets, audit logs.\n&#8211; Compliance context may include SOC 2 controls; privacy obligations may include GDPR\/CCPA depending on customer base.<\/p>\n\n\n\n<p><strong>Delivery model<\/strong>\n&#8211; Agile or Kanban-based delivery for analytics work.\n&#8211; Mix of planned improvements (governance\/quality initiatives) and reactive support (incidents, stakeholder questions).<\/p>\n\n\n\n<p><strong>Scale \/ complexity context<\/strong>\n&#8211; Moderate-to-high complexity due to multiple systems and evolving product instrumentation.\n&#8211; High impact of metric correctness on executive decisions (growth, churn, revenue performance).<\/p>\n\n\n\n<p><strong>Team topology<\/strong>\n&#8211; Senior Data Specialist operates as a senior IC within Data &amp; Analytics:\n  &#8211; Closely partnered with Analytics Engineering (modeling\/testing), Data Engineering (pipelines), BI\/Analytics (dashboards), and Governance\/Security functions.\n  &#8211; Often acts as a \u201cdomain steward\u201d for one or more critical domains.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">12) Stakeholders and Collaboration Map<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Internal stakeholders<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Head of Data &amp; Analytics \/ Director of Data<\/strong> (typical reporting chain oversight)  <\/li>\n<li>Collaboration: priorities, governance posture, escalation support.<\/li>\n<li><strong>Analytics Engineering \/ Data Modeling team<\/strong> <\/li>\n<li>Collaboration: tests, curated datasets, semantic consistency, reviews.<\/li>\n<li><strong>Data Engineering<\/strong> <\/li>\n<li>Collaboration: pipeline reliability, source ingestion changes, incident remediation.<\/li>\n<li><strong>BI Analysts \/ Analytics team<\/strong> <\/li>\n<li>Collaboration: canonical dashboards, metric definitions, training, adoption.<\/li>\n<li><strong>Product Management &amp; Product Operations<\/strong> <\/li>\n<li>Collaboration: product metrics, event definitions, experimentation analytics.<\/li>\n<li><strong>Finance \/ RevOps<\/strong> <\/li>\n<li>Collaboration: revenue metrics, month-end reconciliation, KPI governance.<\/li>\n<li><strong>Security \/ GRC \/ Privacy<\/strong> <\/li>\n<li>Collaboration: access controls, classification, audit readiness, compliance workflows.<\/li>\n<li><strong>Customer Success Ops \/ Support Ops<\/strong> <\/li>\n<li>Collaboration: customer health metrics, operational reporting, definitions for retention signals.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">External stakeholders (as applicable)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Auditors (SOC 2 \/ ISO) or consultants<\/strong> <\/li>\n<li>Collaboration: evidence of controls, reporting traceability, governance artifacts.<\/li>\n<li><strong>Vendors<\/strong> (catalog, observability, BI tools)  <\/li>\n<li>Collaboration: configuration best practices, integrations, feature enablement.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Peer roles<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Senior Data Analyst, Analytics Engineer, Data Engineer, Data Governance Lead (if present), BI Developer.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Upstream dependencies<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Source system owners (application services, CRM admin, billing ops)<\/li>\n<li>Instrumentation quality (event tracking)<\/li>\n<li>Data engineering SLAs for pipeline changes and bug fixes<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Downstream consumers<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Executive dashboards and board reporting<\/li>\n<li>Finance reporting and forecasting<\/li>\n<li>Product analytics and experimentation<\/li>\n<li>Operational teams (RevOps, Support, CS)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Nature of collaboration<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High-touch alignment for definitions and changes to critical metrics.<\/li>\n<li>Shared ownership model: the Senior Data Specialist often owns \u201cwhat it means and how it\u2019s validated,\u201d while engineering partners own \u201chow it\u2019s piped and deployed,\u201d depending on structure.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical decision-making authority<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Authority over definitions, documentation standards, quality rules, and stewardship workflows (within agreed governance).<\/li>\n<li>Influence\u2014not unilateral control\u2014over upstream changes; escalates when critical assets are at risk.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Escalation points<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Repeated upstream breakages affecting Tier-1 assets \u2192 escalate to Data Engineering lead and Data leadership.<\/li>\n<li>Disputes over definitions (e.g., churn) \u2192 escalate to domain executives (e.g., CFO\/VP Product) with proposed decision options.<\/li>\n<li>Sensitive data access concerns \u2192 escalate to Security\/GRC immediately.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13) Decision Rights and Scope of Authority<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can decide independently<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data quality rules and tests for assigned domains (within established standards).<\/li>\n<li>Documentation structure for definitions, dictionaries, and runbooks.<\/li>\n<li>Triage prioritization for minor-to-moderate issues within agreed SLAs.<\/li>\n<li>Recommendations for canonical datasets and dashboards (what should be used).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Requires team approval (Data &amp; Analytics)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Changes to canonical metric definitions that affect multiple teams.<\/li>\n<li>Deprecation of widely used datasets\/dashboards.<\/li>\n<li>New governance workflows that change how work is requested or approved.<\/li>\n<li>Adjustments to Tiering (what is Tier-1\/Tier-2) and associated SLAs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Requires manager\/director\/executive approval<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Commitments that change external reporting timelines or financial reporting logic.<\/li>\n<li>Significant changes to access policy that affect broad user groups.<\/li>\n<li>Vendor selection or purchase decisions (though the role may evaluate and recommend).<\/li>\n<li>Resourcing decisions (adding headcount, forming a governance council, shifting team ownership).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Budget, architecture, vendor, delivery, hiring, compliance authority<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Budget:<\/strong> Usually no direct budget ownership; may influence tool spend through evaluation.<\/li>\n<li><strong>Architecture:<\/strong> Strong influence on semantic and governance architecture; final approval typically with data leadership\/architecture forum.<\/li>\n<li><strong>Vendor:<\/strong> Contributes requirements, POCs, and scoring; procurement approval elsewhere.<\/li>\n<li><strong>Delivery:<\/strong> Can lead small initiatives and coordinate deliveries; does not own engineering roadmap but shapes priorities.<\/li>\n<li><strong>Hiring:<\/strong> Participates in interviews and defines evaluation criteria for data quality\/governance competencies.<\/li>\n<li><strong>Compliance:<\/strong> Ensures adherence in data practices; compliance sign-off rests with Security\/GRC and leadership.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14) Required Experience and Qualifications<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Typical years of experience<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>6\u201310 years<\/strong> in data\/analytics roles, with at least <strong>2\u20134 years<\/strong> focused on data quality, governance, analytics engineering, or stewardship at scale.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Education expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Bachelor\u2019s degree commonly in Information Systems, Computer Science, Statistics, Data Analytics, or similar.  <\/li>\n<li>Equivalent practical experience acceptable in many software organizations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certifications (relevant but rarely mandatory)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Optional (context-specific):<\/strong><\/li>\n<li>Cloud fundamentals (AWS\/Azure\/GCP)<\/li>\n<li>Data governance certs (e.g., DAMA\/CDMP) \u2014 more common in regulated enterprises<\/li>\n<li>Security\/privacy awareness training (internal programs, GDPR fundamentals)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Prior role backgrounds commonly seen<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Senior Data Analyst who moved into governance\/quality ownership<\/li>\n<li>Analytics Engineer specializing in testing and documentation<\/li>\n<li>BI Developer with strong semantic modeling and metric governance experience<\/li>\n<li>Data Engineer with strong business-facing skills and interest in stewardship<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Domain knowledge expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Software\/SaaS business model familiarity helpful:<\/li>\n<li>Subscriptions, usage telemetry, customer lifecycle, funnel metrics, churn\/retention, ARR\/MRR logic<\/li>\n<li>Comfort working across disparate systems and imperfect instrumentation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership experience expectations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not a people manager role by default.  <\/li>\n<li>Expected to lead through influence: mentoring, driving standards, and running cross-functional working sessions.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">15) Career Path and Progression<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Common feeder roles into this role<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data Analyst (mid-level to senior)<\/li>\n<li>Analytics Engineer<\/li>\n<li>BI Developer \/ BI Analyst<\/li>\n<li>Data Operations Analyst \/ Data Quality Analyst<\/li>\n<li>Data Engineer (with strong analytics\/governance orientation)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Next likely roles after this role<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Lead Data Specialist \/ Data Governance Lead<\/strong> (broader stewardship scope, cross-domain governance)<\/li>\n<li><strong>Principal Data Specialist<\/strong> (enterprise-wide metric architecture, stewardship strategy, high-impact domains)<\/li>\n<li><strong>Analytics Engineering Lead<\/strong> (if moving deeper into modeling\/engineering leadership)<\/li>\n<li><strong>Data Product Manager (Analytics\/Data Platform)<\/strong> (if shifting toward product ownership for data products)<\/li>\n<li><strong>Data Platform\/Quality Program Manager<\/strong> (operational scaling and process ownership)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Adjacent career paths<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Security\/Privacy-focused data governance<\/strong> (data protection, compliance operations)<\/li>\n<li><strong>Revenue analytics \/ Finance analytics specialist<\/strong> (deep domain specialization)<\/li>\n<li><strong>Product analytics specialization<\/strong> (event governance, experimentation enablement)<\/li>\n<li><strong>Data reliability engineering (DRE)<\/strong> (stronger operational\/observability focus)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Skills needed for promotion (Senior \u2192 Lead\/Principal)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Domain-spanning stewardship (not just one area)<\/li>\n<li>Proven reduction in incident recurrence and improved reliability outcomes<\/li>\n<li>Stronger architecture influence (semantic layer, metric governance frameworks)<\/li>\n<li>Mature stakeholder influence at director\/executive level<\/li>\n<li>Ability to define standards and have other teams adopt them with minimal friction<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How this role evolves over time<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Early: focus on definitions, documentation, triage, and immediate trust gaps.  <\/li>\n<li>Mid: formalize governance routines, scale quality controls, establish change management.  <\/li>\n<li>Mature: influence enterprise metric architecture, data contracts, and platform-level quality automation.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16) Risks, Challenges, and Failure Modes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Common role challenges<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Ambiguous definitions:<\/strong> Stakeholders disagree; historical dashboards conflict.<\/li>\n<li><strong>Upstream instability:<\/strong> Source systems change without notice; instrumentation is inconsistent.<\/li>\n<li><strong>Fragmented ownership:<\/strong> Nobody \u201cowns\u201d certain datasets; responsibility falls through cracks.<\/li>\n<li><strong>Tool sprawl:<\/strong> Multiple BI tools or duplicated dashboards cause confusion.<\/li>\n<li><strong>Balancing speed vs governance:<\/strong> Too much process slows teams; too little causes mistrust.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Bottlenecks<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Limited data engineering capacity to fix root causes quickly.<\/li>\n<li>Lack of executive sponsorship for standardizing metrics (\u201ceveryone has their own number\u201d culture).<\/li>\n<li>Incomplete metadata and lineage, making impact analysis slow.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Anti-patterns<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Document-only governance<\/strong> without enforcement (definitions exist but aren\u2019t used).<\/li>\n<li><strong>Heroic manual reconciliation<\/strong> repeated every month instead of automation.<\/li>\n<li><strong>Dashboard proliferation<\/strong> without canonical sources.<\/li>\n<li><strong>Quality theater:<\/strong> Lots of tests, but not on the right assets or without clear SLAs.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common reasons for underperformance<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Strong technical skills but weak stakeholder influence, resulting in unused standards.<\/li>\n<li>Over-engineering governance frameworks without prioritizing high-impact domains.<\/li>\n<li>Inability to do root cause analysis across systems (stops at surface symptoms).<\/li>\n<li>Poor communication during incidents, eroding trust.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Business risks if this role is ineffective<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incorrect executive decisions due to inconsistent metrics.<\/li>\n<li>Revenue reporting errors, delayed close, or audit challenges.<\/li>\n<li>Data privacy incidents from improper access or unmanaged sensitive data.<\/li>\n<li>Slower product iteration due to mistrusted experimentation\/analytics.<\/li>\n<li>Higher operational costs from repeated rework and duplicated analytics effort.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">17) Role Variants<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">By company size<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Startup \/ early growth:<\/strong> <\/li>\n<li>More hands-on building of curated tables and dashboards.  <\/li>\n<li>Less formal governance; focus on quick standardization of core metrics.<\/li>\n<li><strong>Mid-size scale-up:<\/strong> <\/li>\n<li>Strong emphasis on data quality operations, cataloging, and metric governance.  <\/li>\n<li>More cross-functional facilitation and domain stewardship.<\/li>\n<li><strong>Large enterprise:<\/strong> <\/li>\n<li>Heavier governance tooling, formal stewardship councils, audit evidence production.  <\/li>\n<li>More specialization (data governance office, separate data quality engineering).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">By industry<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>SaaS \/ software (default):<\/strong> metrics around ARR\/MRR, usage, activation, retention, support burden.  <\/li>\n<li><strong>Fintech\/healthcare (regulated):<\/strong> stronger privacy controls, audit trails, data retention requirements, stricter access workflows.  <\/li>\n<li><strong>E-commerce:<\/strong> order\/revenue reconciliation complexity, marketing attribution governance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">By geography<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Varies mainly by privacy and data residency rules (e.g., GDPR).  <\/li>\n<li>Multinational contexts require clearer classification, retention, and cross-border sharing controls.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Product-led vs service-led company<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Product-led:<\/strong> heavier product analytics, event governance, experimentation metrics, telemetry quality.  <\/li>\n<li><strong>Service-led:<\/strong> heavier operational reporting, utilization metrics, project accounting, client reporting governance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup vs enterprise operating model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Startup:<\/strong> fewer tools, more manual processes, faster iterations, higher ambiguity tolerance.  <\/li>\n<li><strong>Enterprise:<\/strong> formal approvals, catalog\/governance platforms, clear RACI, audit readiness expectations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Regulated vs non-regulated environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Regulated:<\/strong> stricter access controls, evidence management, retention policies, data minimization practices.  <\/li>\n<li><strong>Non-regulated:<\/strong> lighter governance, but still needs strong metric integrity to scale.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">18) AI \/ Automation Impact on the Role<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Tasks that can be automated (partially or substantially)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Drafting initial dataset\/metric descriptions from schemas and query history (requires review).<\/li>\n<li>Auto-suggesting lineage and impact analysis using warehouse query logs and orchestration metadata.<\/li>\n<li>Anomaly detection on freshness\/volume\/distribution shifts with automated alerting.<\/li>\n<li>Generating reconciliation templates and checks (still needs domain-specific tolerances).<\/li>\n<li>Summarizing incidents and producing first-draft postmortems (human validates accuracy).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Tasks that remain human-critical<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Resolving semantic disputes (e.g., churn logic) and securing stakeholder alignment.<\/li>\n<li>Determining business impact and prioritization (risk-based judgment).<\/li>\n<li>Designing governance that fits culture and delivery model (pragmatic tailoring).<\/li>\n<li>Final accountability for correctness of definitions, documentation, and compliance alignment.<\/li>\n<li>Handling sensitive data decisions and exceptions with appropriate scrutiny.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How AI changes the role over the next 2\u20135 years<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Higher expectations for speed and scale:<\/strong> Documentation and catalog upkeep will be expected to stay current with less manual effort, enabled by AI-assisted stewardship.<\/li>\n<li><strong>Shift from creation to validation:<\/strong> The Senior Data Specialist will spend less time writing first drafts and more time validating, curating, and enforcing standards.<\/li>\n<li><strong>Better proactive detection:<\/strong> AI-enhanced observability will increase early detection, shifting focus toward prevention and systemic fixes.<\/li>\n<li><strong>Increased governance importance:<\/strong> As AI models consume enterprise data, the cost of poor definitions and low-quality data rises; stewardship becomes more central to risk management.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">New expectations caused by AI, automation, or platform shifts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ability to evaluate AI-generated definitions and detect subtle inaccuracies.<\/li>\n<li>Familiarity with data provenance needs for AI\/ML use cases (lineage, consent, permitted use).<\/li>\n<li>Greater emphasis on data contracts and \u201cpolicy-aware\u201d data products.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">19) Hiring Evaluation Criteria<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What to assess in interviews<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>SQL depth and diagnostic ability<\/strong>: Can they reconcile inconsistent numbers and trace issues across layers?<\/li>\n<li><strong>Data quality mindset<\/strong>: Do they understand quality dimensions and how to operationalize them (tests, monitoring, SLAs)?<\/li>\n<li><strong>Metric governance capability<\/strong>: Can they define metrics precisely and prevent drift across dashboards?<\/li>\n<li><strong>Documentation and stewardship discipline<\/strong>: Have they built catalogs\/glossaries\/runbooks that people actually use?<\/li>\n<li><strong>Stakeholder influence<\/strong>: Can they facilitate definition alignment and drive adoption without formal authority?<\/li>\n<li><strong>Incident handling<\/strong>: Can they communicate clearly and run effective postmortems with preventive actions?<\/li>\n<li><strong>Security\/privacy awareness<\/strong>: Do they understand least privilege and handling of sensitive data?<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Practical exercises or case studies (recommended)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>SQL reconciliation exercise (60\u201390 minutes):<\/strong><br\/>\n  Provide two tables (e.g., subscriptions and invoices) with intentional inconsistencies and ask the candidate to:  <\/li>\n<li>quantify the discrepancy,  <\/li>\n<li>identify likely root causes (duplicates, missing joins, timing issues),  <\/li>\n<li>propose tests to prevent recurrence.<\/li>\n<li><strong>Metric definition case (30\u201345 minutes):<\/strong><br\/>\n  Ask them to define \u201cActive Customer\u201d and \u201cChurn\u201d for a SaaS product with edge cases (paused subscriptions, downgrades, trial users).<br\/>\n  Evaluate clarity, assumptions, and ability to turn definitions into testable logic.<\/li>\n<li><strong>Data incident scenario (30 minutes):<\/strong><br\/>\n  Simulate an executive dashboard mismatch. Candidate drafts: impact statement, immediate actions, stakeholder update, and prevention plan.<\/li>\n<li><strong>Documentation review (take-home or live):<\/strong><br\/>\n  Provide a poorly documented dataset and ask them to write a short data dictionary entry and usage guidance.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Strong candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explains trade-offs and prioritization clearly (risk-based governance).<\/li>\n<li>Uses structured reconciliation approaches and validates assumptions.<\/li>\n<li>Demonstrates that they can get adoption (examples of deprecated dashboards, standardized metrics).<\/li>\n<li>Talks in terms of outcomes: reduced incidents, improved close, faster decision cycles.<\/li>\n<li>Comfortable partnering with engineering and business teams; does not default to blame.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Weak candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Treats documentation\/governance as \u201cextra\u201d rather than core deliverables.<\/li>\n<li>Focuses on building dashboards without ensuring definitional consistency.<\/li>\n<li>Cannot explain how they\u2019d prevent recurrence beyond \u201cbe more careful.\u201d<\/li>\n<li>Over-rotates on tools instead of principles and operating model.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Red flags<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dismissive attitude toward privacy\/security controls or least privilege.<\/li>\n<li>Cannot communicate clearly about data issues to non-technical stakeholders.<\/li>\n<li>Repeated reliance on manual monthly heroics with no attempt to automate or standardize.<\/li>\n<li>Overconfidence without validation (assumes \u201cwarehouse is source of truth\u201d without reconciliation).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scorecard dimensions (with suggested weighting)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Dimension<\/th>\n<th>What \u201cmeets bar\u201d looks like<\/th>\n<th style=\"text-align: right;\">Weight<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>SQL &amp; reconciliation<\/td>\n<td>Can diagnose discrepancies and produce correct, efficient queries<\/td>\n<td style=\"text-align: right;\">20%<\/td>\n<\/tr>\n<tr>\n<td>Data quality engineering<\/td>\n<td>Proposes appropriate tests\/monitors; understands SLAs and incident ops<\/td>\n<td style=\"text-align: right;\">20%<\/td>\n<\/tr>\n<tr>\n<td>Metric governance &amp; semantics<\/td>\n<td>Creates crisp definitions; anticipates edge cases; prevents drift<\/td>\n<td style=\"text-align: right;\">15%<\/td>\n<\/tr>\n<tr>\n<td>Documentation &amp; stewardship<\/td>\n<td>Produces clear dictionaries\/glossaries; emphasizes discoverability<\/td>\n<td style=\"text-align: right;\">10%<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder management<\/td>\n<td>Aligns teams, communicates clearly, drives adoption<\/td>\n<td style=\"text-align: right;\">15%<\/td>\n<\/tr>\n<tr>\n<td>Incident response &amp; RCA<\/td>\n<td>Structured approach, prevention-focused, calm communication<\/td>\n<td style=\"text-align: right;\">10%<\/td>\n<\/tr>\n<tr>\n<td>Security\/privacy fundamentals<\/td>\n<td>Applies least privilege, understands sensitive data handling<\/td>\n<td style=\"text-align: right;\">5%<\/td>\n<\/tr>\n<tr>\n<td>Senior IC leadership<\/td>\n<td>Mentors, sets standards, leads initiatives without authority<\/td>\n<td style=\"text-align: right;\">5%<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">20) Final Role Scorecard Summary<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Summary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Role title<\/td>\n<td>Senior Data Specialist<\/td>\n<\/tr>\n<tr>\n<td>Role purpose<\/td>\n<td>Ensure enterprise data, metrics, and analytical outputs are trusted, well-defined, discoverable, governed, and reliably delivered for decision-making and operations.<\/td>\n<\/tr>\n<tr>\n<td>Top 10 responsibilities<\/td>\n<td>1) Define critical data domains; 2) Standardize KPI\/metric definitions; 3) Implement\/maintain data quality tests; 4) Triage and resolve data incidents; 5) Perform reconciliations with source systems; 6) Maintain catalog\/glossary\/lineage; 7) Enable self-service analytics adoption; 8) Support access controls and classification; 9) Run change control for metric\/reporting updates; 10) Mentor peers and lead stewardship initiatives.<\/td>\n<\/tr>\n<tr>\n<td>Top 10 technical skills<\/td>\n<td>1) Advanced SQL; 2) Data quality testing patterns; 3) Root cause analysis across pipelines; 4) Metadata\/catalog\/lineage management; 5) Metric governance\/semantic modeling; 6) Data modeling literacy; 7) BI fundamentals; 8) Access control &amp; privacy basics; 9) dbt familiarity; 10) Python for profiling\/automation.<\/td>\n<\/tr>\n<tr>\n<td>Top 10 soft skills<\/td>\n<td>1) Analytical rigor; 2) Business translation; 3) Stakeholder influence; 4) Structured problem solving; 5) Incident communication; 6) Documentation discipline; 7) Pragmatic prioritization; 8) Conflict resolution on definitions; 9) Ownership and follow-through; 10) Mentorship\/quality leadership.<\/td>\n<\/tr>\n<tr>\n<td>Top tools or platforms<\/td>\n<td>Warehouse\/lakehouse (Snowflake\/BigQuery\/Redshift\/Databricks); dbt; BI (Looker\/Tableau\/Power BI); data quality (Great Expectations\/dbt tests); orchestration (Airflow\/Dagster); catalog (Alation\/Collibra\/Atlan\/Purview); Jira\/ServiceNow; GitHub\/GitLab; Confluence\/Notion; Slack\/Teams.<\/td>\n<\/tr>\n<tr>\n<td>Top KPIs<\/td>\n<td>Documentation coverage (Tier-1); test coverage and pass rate; freshness SLA attainment; incident rate; MTTD\/MTTR; recurrence rate; reconciliation accuracy; canonical metric adoption; access request cycle time; stakeholder satisfaction (data trust).<\/td>\n<\/tr>\n<tr>\n<td>Main deliverables<\/td>\n<td>Curated datasets\/data marts; metric definitions\/specifications; data dictionaries\/glossaries; automated test suites; lineage documentation; reconciliation reports; access\/classification documentation; incident runbooks\/postmortems; enablement materials; governance workflows\/RACI.<\/td>\n<\/tr>\n<tr>\n<td>Main goals<\/td>\n<td>30\/60\/90 days: baseline trust gaps, implement tests on key domains, standardize top metrics, establish triage cadence and documentation improvements. 6\u201312 months: institutionalize governance, reduce incidents and recurrence, improve self-service adoption, strengthen compliance readiness.<\/td>\n<\/tr>\n<tr>\n<td>Career progression options<\/td>\n<td>Lead Data Specialist \/ Data Governance Lead; Principal Data Specialist; Analytics Engineering Lead; Data Product Manager (Data\/Analytics); Data Reliability\/Quality program leadership; domain specialization (Revenue\/Product analytics).<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>The **Senior Data Specialist** is a senior individual contributor in the **Data &#038; Analytics** function who ensures that enterprise data is **trusted, well-defined, discoverable, governed, and usable** for analytics, product decision-making, and operational reporting. This role bridges technical data work (SQL, data quality, lineage, metadata, access controls) with business clarity (definitions, metrics, documentation, stakeholder alignment), reducing ambiguity and preventing costly misinterpretation of data.<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[6516,24508],"tags":[],"class_list":["post-75055","post","type-post","status-publish","format-standard","hentry","category-data-analytics","category-specialist"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75055","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=75055"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75055\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=75055"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=75055"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=75055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}