{"id":72578,"date":"2026-04-13T00:07:52","date_gmt":"2026-04-13T00:07:52","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/business-intelligence-analyst-role-blueprint-responsibilities-skills-kpis-and-career-path\/"},"modified":"2026-04-13T00:07:52","modified_gmt":"2026-04-13T00:07:52","slug":"business-intelligence-analyst-role-blueprint-responsibilities-skills-kpis-and-career-path","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/business-intelligence-analyst-role-blueprint-responsibilities-skills-kpis-and-career-path\/","title":{"rendered":"Business Intelligence Analyst: 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>Business Intelligence Analyst<\/strong> turns product, customer, financial, and operational data into <strong>trusted insights, dashboards, and decision support<\/strong> that drive measurable business outcomes. This role sits at the intersection of analytics, data engineering, and business operations\u2014ensuring leaders and teams can self-serve accurate metrics and confidently act on them.<\/p>\n\n\n\n<p>In a software or IT organization (typically SaaS, platforms, or internal IT product teams), this role exists because data is distributed across product telemetry, CRM, billing, support systems, and cloud platforms\u2014requiring a dedicated analyst to <strong>model key business questions into usable metrics<\/strong>, maintain reporting reliability, and translate findings into actions.<\/p>\n\n\n\n<p>The business value created includes <strong>faster decisions, clearer performance visibility, improved revenue and retention outcomes, reduced operational waste, and stronger metric governance<\/strong> (consistent definitions across teams). This is a <strong>Current<\/strong> role with mature, widely adopted practices in modern data stacks.<\/p>\n\n\n\n<p>Typical interactions include Product Management, Engineering, Revenue Operations, Customer Success, Finance, Marketing, Support, Security\/Compliance, and Data Engineering\/Analytics Engineering.<\/p>\n\n\n\n<p><strong>Seniority (conservative inference):<\/strong> Mid-level individual contributor (IC).<br\/>\n<strong>Typical reporting line:<\/strong> Reports to <strong>BI Manager<\/strong>, <strong>Analytics Manager<\/strong>, or <strong>Head of Data &amp; Analytics<\/strong> (depending on company size).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">2) Role Mission<\/h2>\n\n\n\n<p><strong>Core mission:<\/strong><br\/>\nDeliver reliable, decision-grade insights through governed metrics, intuitive dashboards, and analytical narratives that help the organization understand performance, identify opportunities, and take action\u2014without compromising data accuracy, privacy, or trust.<\/p>\n\n\n\n<p><strong>Strategic importance to the company:<\/strong><br\/>\n&#8211; BI enables the operating rhythm of a software business: forecasting, retention monitoring, product adoption, incident impact analysis, pipeline conversion, and unit economics.<br\/>\n&#8211; BI reduces \u201cmetric debates\u201d and aligns teams on what success looks like (north-star and supporting KPIs).<br\/>\n&#8211; BI supports scalable self-service analytics, reducing ad-hoc reporting load and improving decision velocity.<\/p>\n\n\n\n<p><strong>Primary business outcomes expected:<\/strong><br\/>\n&#8211; A trusted KPI layer with consistent definitions and documentation<br\/>\n&#8211; High adoption dashboards that inform priorities, investments, and corrective actions<br\/>\n&#8211; Proactive detection of performance risks (e.g., churn signals, funnel drops, uptime impact on renewals)<br\/>\n&#8211; Reduced time-to-insight for leaders and operators<br\/>\n&#8211; Improved data literacy and decision quality across teams<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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 standardize business metrics<\/strong> (e.g., ARR, NRR, activation, MAU, CAC, support deflection) in partnership with functional leaders; maintain a single source of truth for definitions.<\/li>\n<li><strong>Design BI reporting strategy<\/strong> for a domain (e.g., Product &amp; Growth, Revenue, Customer Health, Operations) including KPI hierarchy and dashboard portfolio.<\/li>\n<li><strong>Identify insight opportunities<\/strong> by monitoring trends, segment shifts, cohort performance, and funnel changes; propose hypotheses and measurement plans.<\/li>\n<li><strong>Guide decision-making with analytical narratives<\/strong>: write concise readouts that translate data into risks, opportunities, and recommended actions.<\/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>Deliver recurring business reporting<\/strong> (weekly\/monthly operational reviews, QBR support, board\/exec metric packs as needed).<\/li>\n<li><strong>Manage BI intake and prioritization<\/strong>: triage requests, clarify requirements, propose self-service alternatives, and maintain a transparent backlog.<\/li>\n<li><strong>Enable self-service<\/strong> by building curated dashboards, training stakeholders, and improving discoverability of datasets and definitions.<\/li>\n<li><strong>Monitor key dashboards for anomalies<\/strong> (spikes\/drops), validate data consistency, and escalate issues to Data Engineering\/Analytics Engineering when needed.<\/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 production-quality SQL<\/strong> to transform, aggregate, and validate data for reporting and analysis; ensure performance and correctness.<\/li>\n<li><strong>Build and maintain semantic layers \/ metric layers<\/strong> (tool-dependent): reusable measures\/dimensions, certified datasets, and governed KPI calculations.<\/li>\n<li><strong>Model data for BI consumption<\/strong> (often with analytics engineering partners): star schemas, conformed dimensions, and well-defined grains for facts.<\/li>\n<li><strong>Implement data validation checks<\/strong> relevant to BI outputs (row counts, freshness checks, reconciliation to source totals, outlier detection).<\/li>\n<li><strong>Develop lightweight automations<\/strong> (where appropriate) such as scheduled exports, alerting, and standardized reporting templates.<\/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=\"14\">\n<li><strong>Partner with Product and Engineering<\/strong> to interpret product telemetry, event data quality, and feature adoption analytics; advise on tracking plans.<\/li>\n<li><strong>Partner with Finance\/RevOps<\/strong> to align revenue metrics, forecasting inputs, and reconciliation between billing, CRM, and finance systems.<\/li>\n<li><strong>Support go-to-market analytics<\/strong>: pipeline conversion, win\/loss trends, territory performance, onboarding funnel, and customer health indicators.<\/li>\n<li><strong>Conduct stakeholder workshops<\/strong> to translate ambiguous questions into measurable definitions and actionable analyses.<\/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>Maintain reporting governance<\/strong>: certification of datasets, dashboard ownership, documentation, change control, and deprecation processes.<\/li>\n<li><strong>Ensure appropriate access controls<\/strong>: role-based access, PII handling, and audit-friendly reporting practices aligned with security\/compliance policies.<\/li>\n<li><strong>Promote data quality standards<\/strong> by documenting known limitations, preventing metric misuse, and supporting root-cause analysis of data discrepancies.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Leadership responsibilities (applicable without people management)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Lead through influence<\/strong>: align stakeholders on metric definitions, set expectations on feasibility\/timelines, and coach users on interpretation.<\/li>\n<li><strong>Mentor junior analysts (context-specific)<\/strong>: review SQL\/dashboards, share best practices, and contribute to analytics playbooks.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Review core dashboards for <strong>freshness<\/strong>, anomalies, or broken tiles; validate key metrics after major data pipeline deployments.<\/li>\n<li>Respond to questions in analytics channels (e.g., Slack\/Teams) and route requests into the intake process.<\/li>\n<li>Write and iterate on SQL queries to answer business questions; validate results against expected patterns and source systems.<\/li>\n<li>Make targeted improvements to dashboards: filter usability, drill-down paths, labeling, tooltips, and metric explanations.<\/li>\n<li>Clarify requirements with stakeholders: define the decision being made, the audience, time horizon, and preferred level of granularity.<\/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>Produce or refresh <strong>weekly business review<\/strong> content for a function (e.g., Product weekly metrics, Revenue funnel, Support performance).<\/li>\n<li>Attend backlog grooming with Data &amp; Analytics; estimate effort and negotiate scope\/timelines.<\/li>\n<li>Conduct at least one deeper-dive analysis (cohort, funnel, segmentation, attribution) and circulate insights.<\/li>\n<li>Validate and reconcile sensitive metrics (ARR movements, churn, renewals) with RevOps\/Finance counterparts.<\/li>\n<li>Perform lightweight data QA: top-line reconciliations, freshness checks, and sampling.<\/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>Support MBR\/QBR cycles: KPI packs, trend commentary, root-cause summaries, and action tracking.<\/li>\n<li>Refresh KPI definitions and documentation; review dashboard portfolio for usage and retire low-value artifacts.<\/li>\n<li>Contribute to roadmap planning for analytics improvements (new datasets, metric layer expansion, better tracking).<\/li>\n<li>Partner with Product\/Engineering on instrumentation audits and event taxonomy changes.<\/li>\n<li>Support forecasting and planning: historical baselines, seasonality patterns, and scenario analysis.<\/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 &amp; Analytics standup (or async updates)  <\/li>\n<li>BI intake triage \/ office hours  <\/li>\n<li>Stakeholder syncs (Product Ops, RevOps, Finance partner)  <\/li>\n<li>Monthly metric governance review (definitions, changes, deprecations)  <\/li>\n<li>Post-incident analytics review (when incidents affect customer experience or business outcomes)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Incident, escalation, or emergency work (relevant in many BI environments)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Respond to \u201cnumbers don\u2019t match\u201d escalations affecting exec reporting or revenue recognition inputs.<\/li>\n<li>Rapid assessment when dashboards break after schema changes; coordinate with Data Engineering for rollback\/fix.<\/li>\n<li>During critical business moments (end-of-quarter, major launch, pricing changes), provide near-real-time monitoring and validation.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Executive-ready KPI dashboards<\/strong> for key domains (Product, Revenue, Customer Health, Operations)<\/li>\n<li><strong>Metric definitions catalog<\/strong> (data dictionary \/ KPI glossary) with owners, calculation logic, grain, and caveats<\/li>\n<li><strong>Certified datasets \/ semantic layer objects<\/strong> (tool-specific: LookML models, Power BI datasets, Tableau data sources, dbt exposures)<\/li>\n<li><strong>Recurring reporting packs<\/strong> (weekly\/monthly) with narrative insights and action recommendations<\/li>\n<li><strong>Ad-hoc analyses<\/strong> documented as short memos: question, method, result, caveats, recommendation<\/li>\n<li><strong>Cohort and funnel analyses<\/strong> (activation, conversion, retention, onboarding)<\/li>\n<li><strong>Data quality and freshness checks<\/strong> tied to business-critical metrics<\/li>\n<li><strong>Dashboard governance artifacts<\/strong>: ownership registry, change logs, deprecation plans<\/li>\n<li><strong>Training artifacts<\/strong>: \u201cHow to use this dashboard,\u201d metric interpretation guides, office-hours playbooks<\/li>\n<li><strong>Instrumentation feedback<\/strong>: tracking plan improvements and event taxonomy suggestions (in partnership with Product\/Engineering)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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 (onboarding and baseline)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Understand company KPIs, business model, and operating cadence (weekly reviews, QBRs, planning cycle).<\/li>\n<li>Gain access to core systems (warehouse, BI tool, documentation, ticketing) and complete security training.<\/li>\n<li>Learn current metric definitions, dashboards, and known issues; identify \u201chigh pain\u201d reporting areas.<\/li>\n<li>Deliver 1\u20132 quick wins (e.g., fix a broken dashboard, improve a slow query, document a key KPI).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">60-day goals (ownership and reliability)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Take ownership of a defined reporting domain (e.g., Product Adoption metrics or Revenue funnel dashboards).<\/li>\n<li>Standardize 5\u201310 key metrics: definitions, calculations, owners, and dashboard usage guidelines.<\/li>\n<li>Reduce recurring \u201cnumbers mismatch\u201d issues in owned domain through reconciliation logic and documentation.<\/li>\n<li>Launch at least one improved dashboard or metric pack with clear adoption outcomes.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">90-day goals (impact and enablement)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implement a durable process for BI intake, prioritization, and stakeholder communication.<\/li>\n<li>Produce a recurring insight cadence (e.g., weekly product insights or monthly churn drivers) that influences decisions.<\/li>\n<li>Improve self-service: certify datasets, build guided dashboards, and run enablement sessions.<\/li>\n<li>Demonstrate measurable outcomes: reduced time-to-answer, higher dashboard adoption, fewer escalations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6-month milestones (scaling)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Expand semantic\/metric layer coverage and retire redundant dashboards.<\/li>\n<li>Establish governance routines: metric change control, dashboard ownership, certification criteria.<\/li>\n<li>Contribute to analytics roadmap planning (new datasets, improved instrumentation, better alerting).<\/li>\n<li>Build cross-functional credibility as a domain BI partner (stakeholders proactively engage BI early).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">12-month objectives (business outcomes)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create a stable, trusted KPI system for an organizational domain used in exec-level decisions.<\/li>\n<li>Improve decision velocity and operational efficiency through self-service and automation.<\/li>\n<li>Demonstrate attributable business value (examples: improved conversion visibility leading to funnel fixes; reduced churn via health insights; cost optimization via usage analytics).<\/li>\n<li>Mentor others and codify best practices into analytics playbooks.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Long-term impact goals (organizational maturity)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Drive a culture of <strong>metric discipline<\/strong>: consistent definitions, documented caveats, and governance.<\/li>\n<li>Enable \u201canalytics as a product\u201d thinking: high-quality data products with ownership, SLAs, and user experience.<\/li>\n<li>Increase organizational data literacy and reduce dependence on ad-hoc analyst support.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Role success definition<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stakeholders trust the numbers, use the dashboards, and make decisions faster with fewer debates.<\/li>\n<li>Key KPIs are consistent across tools and forums, with clear owners and documented logic.<\/li>\n<li>BI outputs are reliable, governed, and aligned to business priorities\u2014not just reactive reporting.<\/li>\n<\/ul>\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 performance risks\/opportunities and influences actions.<\/li>\n<li>Produces durable, reusable assets (certified datasets, metric layers) rather than one-off queries.<\/li>\n<li>Communicates clearly: concise narratives, transparent caveats, and actionable recommendations.<\/li>\n<li>Builds strong cross-functional partnerships and sets healthy boundaries through intake and prioritization.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">7) KPIs and Productivity Metrics<\/h2>\n\n\n\n<p>The following measurement framework is designed for enterprise practicality. Targets vary by company maturity, data quality, and stakeholder sophistication; benchmarks below are realistic starting points.<\/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>Dashboards delivered (count)<\/td>\n<td>Number of production dashboards released or materially improved<\/td>\n<td>Indicates delivery throughput<\/td>\n<td>1\u20133\/month (domain-dependent)<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Certified datasets \/ semantic objects added<\/td>\n<td>New governed datasets\/measures reusable across dashboards<\/td>\n<td>Scales BI impact; reduces duplication<\/td>\n<td>2\u20136\/quarter<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Insight memos \/ analyses delivered<\/td>\n<td>Completed analyses with documented method and recommendation<\/td>\n<td>Measures analytical contribution beyond reporting<\/td>\n<td>2\u20134\/month<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder requests completed<\/td>\n<td>Volume of completed BI tickets (weighted by complexity)<\/td>\n<td>Captures service productivity<\/td>\n<td>8\u201320\/month (varies)<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Time-to-first-response (BI intake)<\/td>\n<td>Time from request submission to clarification\/acknowledgement<\/td>\n<td>Improves stakeholder experience<\/td>\n<td>&lt; 2 business days<\/td>\n<td>Weekly<\/td>\n<\/tr>\n<tr>\n<td>Cycle time (request to delivery)<\/td>\n<td>End-to-end time for standard BI requests<\/td>\n<td>Measures execution efficiency<\/td>\n<td>Small: 3\u20137 days; Medium: 2\u20134 weeks<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Dashboard adoption (active users)<\/td>\n<td>Unique viewers or engaged users per dashboard<\/td>\n<td>Ensures deliverables are used<\/td>\n<td>&gt;60% of target audience within 60 days<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Dashboard engagement depth<\/td>\n<td>Repeat visits, drill interactions, subscriptions<\/td>\n<td>Indicates usefulness\/UX quality<\/td>\n<td>Trending upward; stable usage<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Data freshness SLA adherence<\/td>\n<td>Percent of refreshes meeting agreed SLA<\/td>\n<td>Reliability and trust<\/td>\n<td>95%+ for Tier-1 dashboards<\/td>\n<td>Weekly<\/td>\n<\/tr>\n<tr>\n<td>Dashboard breakage rate<\/td>\n<td>Incidents where dashboards fail due to schema\/logic changes<\/td>\n<td>Operational quality<\/td>\n<td>&lt;2 incidents\/month for owned assets<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Metric consistency score<\/td>\n<td>Alignment of core KPI values across reports\/tools after reconciliation<\/td>\n<td>Reduces \u201cdueling dashboards\u201d<\/td>\n<td>99%+ within defined tolerance<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Reconciliation pass rate (revenue metrics)<\/td>\n<td>Match rate between BI and finance\/CRM totals within tolerance<\/td>\n<td>Critical for revenue trust<\/td>\n<td>98\u201399% within tolerance<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Query performance (p95 load time)<\/td>\n<td>Typical load time for key dashboards<\/td>\n<td>User experience and adoption<\/td>\n<td>&lt;5\u201310 seconds for main pages<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Defect rate (post-release)<\/td>\n<td>Issues found after dashboard release (logic\/labeling)<\/td>\n<td>Quality of development<\/td>\n<td>&lt;5% of releases requiring hotfix<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Documentation completeness<\/td>\n<td>Percentage of certified metrics with definitions, owner, caveats<\/td>\n<td>Governance maturity<\/td>\n<td>90%+ for Tier-1 metrics<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Self-service success rate<\/td>\n<td>Percentage of questions answered by stakeholders without analyst intervention<\/td>\n<td>Scalability<\/td>\n<td>Increasing trend; +10\u201320% YoY<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Stakeholder satisfaction (CSAT)<\/td>\n<td>Survey score for BI support and usefulness<\/td>\n<td>Ensures partnership effectiveness<\/td>\n<td>4.2+\/5 or NPS positive<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Decision impact instances<\/td>\n<td>Count of documented decisions influenced by BI (roadmap, pricing, ops changes)<\/td>\n<td>Connects analytics to outcomes<\/td>\n<td>1\u20133\/quarter (documented)<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Improvement initiatives delivered<\/td>\n<td>Process\/tooling improvements (alerts, templates, governance)<\/td>\n<td>Innovation and maturity<\/td>\n<td>2\u20134\/quarter<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<tr>\n<td>Training sessions \/ office hours run<\/td>\n<td>Enablement activities delivered<\/td>\n<td>Increases adoption and literacy<\/td>\n<td>1\u20132\/month<\/td>\n<td>Monthly<\/td>\n<\/tr>\n<tr>\n<td>Cross-team collaboration score (qualitative)<\/td>\n<td>Peer feedback from Data Eng, Product, RevOps<\/td>\n<td>Prevents silos and friction<\/td>\n<td>Positive feedback trend<\/td>\n<td>Quarterly<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<p><strong>Notes on targets:<\/strong><br\/>\n&#8211; Early-stage environments may prioritize <strong>speed and foundational dashboards<\/strong>; later-stage enterprises prioritize <strong>governance, reconciliation, and reliability SLAs<\/strong>.<br\/>\n&#8211; Where possible, separate \u201cvanity output\u201d (number of dashboards) from \u201cvalue outcomes\u201d (adoption and decision impact).<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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<ol class=\"wp-block-list\">\n<li><strong>SQL (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Advanced querying, joins, window functions, CTEs, aggregation, performance-aware patterns.<br\/>\n   &#8211; <strong>Use:<\/strong> Building datasets, validating metrics, investigating anomalies, powering dashboards.  <\/li>\n<li><strong>BI dashboard development (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Designing interactive dashboards with filters, drilldowns, layout hierarchy, and clear labeling.<br\/>\n   &#8211; <strong>Use:<\/strong> Delivering self-service reporting to stakeholders and execs.  <\/li>\n<li><strong>Metric definition and data modeling fundamentals (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Understanding grain, dimensions vs measures, star schema concepts, slowly changing dimensions.<br\/>\n   &#8211; <strong>Use:<\/strong> Preventing incorrect aggregations; ensuring consistent KPIs.  <\/li>\n<li><strong>Data validation and QA (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Reconciliation techniques, sanity checks, outlier detection, sampling, and freshness checks.<br\/>\n   &#8211; <strong>Use:<\/strong> Maintaining trust in reporting, catching issues early.  <\/li>\n<li><strong>Spreadsheet and lightweight analysis skills (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Excel\/Google Sheets pivoting, logic, basic modeling; bridging ad-hoc analysis.<br\/>\n   &#8211; <strong>Use:<\/strong> Quick investigations, reconciliations, stakeholder-friendly exports.  <\/li>\n<li><strong>Analytics requirements gathering (Critical)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Translating business questions into measurable definitions and acceptance criteria.<br\/>\n   &#8211; <strong>Use:<\/strong> Preventing rework; ensuring deliverables match decisions.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Good-to-have technical skills<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Semantic\/metrics layer tooling (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> LookML\/MetricFlow\/Power BI modeling, Tableau data sources, or similar constructs.<br\/>\n   &#8211; <strong>Use:<\/strong> Reusable, governed measures; consistent KPIs across dashboards.  <\/li>\n<li><strong>dbt fundamentals (Important, common in modern stacks)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Reading\/understanding models, tests, exposures, documentation; contributing small changes.<br\/>\n   &#8211; <strong>Use:<\/strong> Partnering effectively with analytics engineers; improving model logic and tests.  <\/li>\n<li><strong>Event analytics concepts (Important in SaaS)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Event taxonomy, sessionization, identity resolution basics, funnel definition pitfalls.<br\/>\n   &#8211; <strong>Use:<\/strong> Product adoption, conversion funnels, feature impact.  <\/li>\n<li><strong>Basic statistics for business analysis (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Cohorts, variance, correlation, seasonality awareness, simple significance concepts.<br\/>\n   &#8211; <strong>Use:<\/strong> Avoiding false conclusions; robust insights.  <\/li>\n<li><strong>Data warehouse concepts (Important)<\/strong><br\/>\n   &#8211; <strong>Description:<\/strong> Partitioning\/clustering concepts, cost-aware querying, incremental refresh patterns.<br\/>\n   &#8211; <strong>Use:<\/strong> Dashboard performance and cost management.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Advanced or expert-level technical skills<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Performance optimization for BI workloads (Optional\/Advanced)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Tuning queries, aggregates, extracts; balancing freshness vs cost.<br\/>\n   &#8211; <strong>Importance:<\/strong> Optional (more critical in high-scale environments).  <\/li>\n<li><strong>Advanced metric governance (Important for mature orgs)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Versioning metrics, change control, certification rules, deprecations, auditability.  <\/li>\n<li><strong>Attribution and experimentation measurement (Context-specific)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Marketing attribution, A\/B test readouts, causal inference basics.  <\/li>\n<li><strong>Data observability concepts (Optional, increasing relevance)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Monitoring freshness\/volume anomalies; partnering with Data Eng on alerts.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Emerging future skills for this role (next 2\u20135 years)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>AI-assisted analytics workflows (Important, emerging)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> LLM copilots for SQL generation, dashboard summarization, anomaly explanation\u2014paired with rigorous validation.  <\/li>\n<li><strong>Metrics-as-code \/ governed metric stores (Important, emerging)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Centralized metric definitions deployed across tools; improved consistency and auditability.  <\/li>\n<li><strong>Privacy-aware analytics (Important, emerging)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Differential privacy concepts, stricter PII minimization, policy-driven access controls.  <\/li>\n<li><strong>Product analytics maturity (Important in SaaS)<\/strong><br\/>\n   &#8211; <strong>Use:<\/strong> Standard event schemas, identity graphs, behavioral cohorts, real-time monitoring for launches.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">9) Soft Skills and Behavioral Capabilities<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p><strong>Business framing and curiosity<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> BI is valuable only when tied to decisions and outcomes, not just numbers.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Asks \u201cwhat decision will this change?\u201d and \u201cwhat action will follow?\u201d<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Produces insights that lead to clear next steps and ownership.<\/p>\n<\/li>\n<li>\n<p><strong>Stakeholder management and expectation setting<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> BI demand often exceeds capacity; unmanaged requests become churn and rework.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Clarifies scope, negotiates timelines, offers alternatives (self-service, phased delivery).<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Stakeholders feel supported and informed; backlog is transparent and prioritized.<\/p>\n<\/li>\n<li>\n<p><strong>Analytical rigor and skepticism<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Small logic errors can create major business misdirection.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Validates with reconciliations, checks edge cases, documents caveats.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Finds issues before executives do; trust in BI increases over time.<\/p>\n<\/li>\n<li>\n<p><strong>Communication and data storytelling<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Insights must be understood and acted on by non-analysts.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Uses clear visuals, writes concise summaries, distinguishes signal vs noise.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Readouts are short, sharp, and decision-oriented; fewer follow-up clarifications needed.<\/p>\n<\/li>\n<li>\n<p><strong>Product mindset (analytics as a product)<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Dashboards are products with users, UX, adoption, and lifecycle needs.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Watches usage, iterates based on feedback, manages versions and deprecations.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Dashboards become widely used and trusted; duplicates are retired.<\/p>\n<\/li>\n<li>\n<p><strong>Collaboration with technical partners<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> BI depends on data models, pipelines, and tracking; success requires tight partnership.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Provides clear requirements to Data Eng, participates in schema change planning, gives actionable bug reports.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Fewer breakages, faster fixes, healthier relationships.<\/p>\n<\/li>\n<li>\n<p><strong>Attention to detail<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> Labeling errors, wrong filters, and inconsistent logic degrade trust quickly.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Checks filters, date logic, segments, and definitions; reviews dashboard UX.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Outputs are polished; stakeholders rarely find errors.<\/p>\n<\/li>\n<li>\n<p><strong>Resilience under ambiguity and pressure<\/strong><br\/>\n   &#8211; <strong>Why it matters:<\/strong> End-of-quarter, incidents, and exec asks can be time-sensitive and messy.<br\/>\n   &#8211; <strong>How it shows up:<\/strong> Stays calm, narrows the problem, communicates tradeoffs.<br\/>\n   &#8211; <strong>Strong performance:<\/strong> Delivers reliable answers quickly without sacrificing integrity.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">10) Tools, Platforms, and Software<\/h2>\n\n\n\n<p>Tooling varies by company. The following are realistic for a software\/IT organization; each item is labeled <strong>Common<\/strong>, <strong>Optional<\/strong>, or <strong>Context-specific<\/strong>.<\/p>\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 style=\"text-align: right;\">Primary use<\/th>\n<th>Commonality<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>BI &amp; visualization<\/td>\n<td>Tableau<\/td>\n<td style=\"text-align: right;\">Dashboards, self-service reporting<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>BI &amp; visualization<\/td>\n<td>Microsoft Power BI<\/td>\n<td style=\"text-align: right;\">Dashboards, semantic model, sharing<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>BI &amp; visualization<\/td>\n<td>Looker<\/td>\n<td style=\"text-align: right;\">Governed semantic layer + dashboards<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>BI &amp; visualization<\/td>\n<td>Mode \/ Hex<\/td>\n<td style=\"text-align: right;\">SQL + notebook-style analysis and sharing<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Data warehouse<\/td>\n<td>Snowflake<\/td>\n<td style=\"text-align: right;\">Central analytics warehouse<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Data warehouse<\/td>\n<td>BigQuery<\/td>\n<td style=\"text-align: right;\">Warehouse on GCP<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Data warehouse<\/td>\n<td>Amazon Redshift<\/td>\n<td style=\"text-align: right;\">Warehouse on AWS<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Data transformation<\/td>\n<td>dbt<\/td>\n<td style=\"text-align: right;\">Transformations, tests, documentation<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Orchestration<\/td>\n<td>Airflow<\/td>\n<td style=\"text-align: right;\">Pipeline scheduling (viewing\/triage)<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Orchestration<\/td>\n<td>Prefect \/ Dagster<\/td>\n<td style=\"text-align: right;\">Workflow orchestration<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Data integration<\/td>\n<td>Fivetran<\/td>\n<td style=\"text-align: right;\">ELT ingestion from SaaS sources<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Data integration<\/td>\n<td>Stitch \/ Airbyte<\/td>\n<td style=\"text-align: right;\">ELT ingestion<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Product analytics<\/td>\n<td>Amplitude<\/td>\n<td style=\"text-align: right;\">Event analytics, funnels, cohorts<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Product analytics<\/td>\n<td>Mixpanel<\/td>\n<td style=\"text-align: right;\">Event analytics, funnels, cohorts<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Product analytics<\/td>\n<td>GA4<\/td>\n<td style=\"text-align: right;\">Web analytics<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Data catalog \/ governance<\/td>\n<td>Alation \/ Collibra<\/td>\n<td style=\"text-align: right;\">Catalog, lineage, governance<\/td>\n<td>Optional (more enterprise)<\/td>\n<\/tr>\n<tr>\n<td>Data catalog<\/td>\n<td>Atlan<\/td>\n<td style=\"text-align: right;\">Discovery, lineage, collaboration<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Data quality \/ observability<\/td>\n<td>Monte Carlo<\/td>\n<td style=\"text-align: right;\">Data incidents, freshness\/volume anomalies<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Data quality<\/td>\n<td>Great Expectations<\/td>\n<td style=\"text-align: right;\">Data tests (often via Eng)<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>Data quality<\/td>\n<td>dbt tests<\/td>\n<td style=\"text-align: right;\">Validations tied to models<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Collaboration<\/td>\n<td>Slack \/ Microsoft Teams<\/td>\n<td style=\"text-align: right;\">Stakeholder comms, intake<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Documentation<\/td>\n<td>Confluence \/ Notion<\/td>\n<td style=\"text-align: right;\">KPI glossary, runbooks, documentation<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Ticketing \/ ITSM<\/td>\n<td>Jira<\/td>\n<td style=\"text-align: right;\">Intake management, delivery tracking<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Ticketing \/ ITSM<\/td>\n<td>ServiceNow<\/td>\n<td style=\"text-align: right;\">Enterprise request and incident workflows<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Source control<\/td>\n<td>GitHub \/ GitLab<\/td>\n<td style=\"text-align: right;\">Version control for dbt\/BI assets (where applicable)<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Security &amp; access<\/td>\n<td>Okta \/ Entra ID<\/td>\n<td style=\"text-align: right;\">SSO, RBAC<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Spreadsheets<\/td>\n<td>Excel \/ Google Sheets<\/td>\n<td style=\"text-align: right;\">Analysis, reconciliations, exports<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Financial systems<\/td>\n<td>NetSuite<\/td>\n<td style=\"text-align: right;\">Finance reporting reconciliation<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>CRM<\/td>\n<td>Salesforce<\/td>\n<td style=\"text-align: right;\">Pipeline, accounts, opportunity analysis<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>Customer support<\/td>\n<td>Zendesk \/ ServiceNow CS<\/td>\n<td style=\"text-align: right;\">Ticket metrics, support analytics<\/td>\n<td>Common<\/td>\n<\/tr>\n<tr>\n<td>CDP<\/td>\n<td>Segment<\/td>\n<td style=\"text-align: right;\">Event collection and routing<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Experimentation<\/td>\n<td>Optimizely \/ LaunchDarkly<\/td>\n<td style=\"text-align: right;\">Feature flags, experiments<\/td>\n<td>Context-specific<\/td>\n<\/tr>\n<tr>\n<td>Communication<\/td>\n<td>Google Slides \/ PowerPoint<\/td>\n<td style=\"text-align: right;\">Exec readouts<\/td>\n<td>Common<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">11) Typical Tech Stack \/ Environment<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Infrastructure environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud-first environment (AWS\/Azure\/GCP) with a centralized data platform.<\/li>\n<li>BI tools deployed as managed cloud services; SSO-integrated.<\/li>\n<li>Access governed via RBAC and data classification policies (especially where PII exists).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Application environment (data sources)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SaaS product telemetry (events, logs, feature flags) and platform data (usage, latency, uptime).<\/li>\n<li>Go-to-market systems: CRM (Salesforce), marketing automation, billing\/subscription management, support desk.<\/li>\n<li>Finance systems (ERP) and payment processors (context-specific).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Data environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud data warehouse (Snowflake\/BigQuery most common).<\/li>\n<li>ELT ingestion tools pulling from SaaS sources.<\/li>\n<li>Transformation layer with dbt and a curated set of marts (e.g., <code>product_mart<\/code>, <code>revenue_mart<\/code>, <code>customer_mart<\/code>).<\/li>\n<li>BI semantic layer (LookML\/Power BI model\/Tableau published data sources) with certified metrics.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security environment<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data classification (PII, sensitive, internal) and enforced access controls.<\/li>\n<li>Audit logging for data access (more common in enterprise or regulated contexts).<\/li>\n<li>Secure sharing patterns (row-level security, masked fields, restricted datasets).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Delivery model<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mix of planned roadmap work and intake-driven requests.<\/li>\n<li>Lightweight agile practices common: Kanban for BI intake; sprint alignment with analytics engineering where needed.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Agile or SDLC context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>BI development lifecycle typically includes: requirements \u2192 query\/model \u2192 dashboard \u2192 QA\/reconciliation \u2192 stakeholder review \u2192 production release \u2192 monitoring\/iteration.<\/li>\n<li>Change control becomes more formal as the company scales (certification, versioning, governance approvals).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scale or complexity context<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Moderate-to-high query volumes and many stakeholder groups.<\/li>\n<li>Complexity often comes from identity resolution (users\/accounts), subscription lifecycle logic, and reconciling revenue sources.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Team topology<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>BI Analyst sits in Data &amp; Analytics, partnered closely with:<\/li>\n<li>Analytics Engineers \/ Data Engineers (models\/pipelines)<\/li>\n<li>Data Product Manager (optional, in mature orgs)<\/li>\n<li>Domain stakeholders (Product, RevOps, Finance)<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Product Management:<\/strong> feature adoption, onboarding funnel, retention cohorts, product health.<\/li>\n<li><strong>Engineering leadership:<\/strong> telemetry quality, incident impact, operational performance metrics.<\/li>\n<li><strong>Revenue Operations (RevOps):<\/strong> pipeline health, conversion rates, territory\/segment performance, CRM hygiene.<\/li>\n<li><strong>Sales leadership:<\/strong> quota attainment, pipeline coverage, deal cycle analytics, win\/loss drivers.<\/li>\n<li><strong>Customer Success:<\/strong> health scores, renewal risk indicators, adoption-based playbooks.<\/li>\n<li><strong>Support\/Service Operations:<\/strong> ticket volumes, response times, backlog, deflection, CSAT.<\/li>\n<li><strong>Finance:<\/strong> ARR\/NRR, billing reconciliation, forecasting inputs, unit economics.<\/li>\n<li><strong>Marketing\/Growth:<\/strong> acquisition funnel, campaign attribution (context-specific), lifecycle engagement.<\/li>\n<li><strong>Security\/Compliance:<\/strong> access controls, PII governance, audit readiness (context-specific).<\/li>\n<li><strong>Data Engineering \/ Analytics Engineering:<\/strong> model changes, pipeline incidents, schema evolution.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">External stakeholders (if applicable)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Vendors\/partners<\/strong> providing tooling (BI platform support, data catalog, observability).<\/li>\n<li><strong>Customers (indirectly)<\/strong> when BI informs customer-facing reporting or usage insights.<\/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>Data Analyst (domain-focused)<\/li>\n<li>Analytics Engineer (dbt\/modeling)<\/li>\n<li>Data Engineer (pipelines)<\/li>\n<li>Data Scientist (advanced modeling\/experiments)<\/li>\n<li>Data Product Manager (data roadmap and adoption)<\/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>Data ingestion reliability (ELT tools, APIs)<\/li>\n<li>Event instrumentation quality (tracking plan adherence)<\/li>\n<li>Source system hygiene (CRM fields, billing statuses)<\/li>\n<li>Data model consistency (conformed dimensions, identity mapping)<\/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>Executives and functional leaders (decision-making)<\/li>\n<li>Operators (RevOps, CS Ops, Support Ops) executing workflows<\/li>\n<li>Product teams (roadmap and experiments)<\/li>\n<li>Finance (reconciliations and planning)<\/li>\n<li>Sometimes customer-facing reporting (context-specific)<\/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>Co-definition of requirements, metrics, and acceptance criteria.<\/li>\n<li>Iterative development: prototypes \u2192 stakeholder feedback \u2192 refinement.<\/li>\n<li>Joint ownership of trust: BI owns presentation and KPI logic; Data Eng\/AE owns pipelines\/models (may vary).<\/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>BI Analyst proposes metric logic and dashboard design, but <strong>metric definitions<\/strong> typically require domain owner alignment (Finance for revenue, Product for adoption).<\/li>\n<li>Data platform changes require Data Engineering\/AE approval and deployment processes.<\/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>Data accuracy disputes or reconciliation failures: escalate to Analytics Manager and relevant domain owner (Finance\/RevOps).<\/li>\n<li>Warehouse\/performance\/cost issues: escalate to Data Platform\/Engineering.<\/li>\n<li>Access\/security conflicts: escalate to Security\/Compliance and Data leadership.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Dashboard UX patterns: layout, drill paths, filters, labeling, explanation text.<\/li>\n<li>Analytical methods for standard questions (cohort definitions, segmentation approach), within established standards.<\/li>\n<li>Prioritization recommendations for the BI backlog (within agreed capacity allocation).<\/li>\n<li>Documentation format and training materials for owned assets.<\/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 certified KPI logic that affect multiple teams (requires review and communication plan).<\/li>\n<li>Introducing new shared datasets or modifying model grains that impact multiple dashboards.<\/li>\n<li>Adoption of new BI conventions (naming standards, certification criteria).<\/li>\n<li>Deprecation of widely used dashboards (requires migration plan).<\/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>Changes impacting executive reporting packs and board-level KPIs.<\/li>\n<li>Access policy changes involving PII or sensitive datasets.<\/li>\n<li>Vendor selection, new tool procurement, or major license expansions (budget authority typically sits with leadership).<\/li>\n<li>Major reporting governance policies (SLAs, audit processes).<\/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> Typically none; may provide ROI justification and usage data for renewals.  <\/li>\n<li><strong>Architecture:<\/strong> Influences BI semantic layer and reporting design; platform architecture decisions sit with Data Platform leadership.  <\/li>\n<li><strong>Vendor:<\/strong> Provides evaluation input; final decision by leadership\/procurement.  <\/li>\n<li><strong>Delivery:<\/strong> Owns delivery for BI assets in scope; coordinates dependencies with Data Eng\/AE.  <\/li>\n<li><strong>Hiring:<\/strong> May participate in interviews; rarely final decision authority at this level.  <\/li>\n<li><strong>Compliance:<\/strong> Must follow policies; may help document controls and support audits.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>3\u20136 years<\/strong> in BI, analytics, or data analysis roles in software\/IT or similarly data-rich environments.<\/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 in a relevant field (Analytics, Information Systems, Computer Science, Statistics, Economics, Engineering) is common.  <\/li>\n<li>Equivalent practical experience is often acceptable, especially with strong portfolio evidence.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Certifications (relevant but not mandatory)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Optional\/Common:<\/strong> <\/li>\n<li>Microsoft Power BI Data Analyst (PL-300)  <\/li>\n<li>Tableau certifications (Desktop Specialist \/ Certified Data Analyst)  <\/li>\n<li>Google Data Analytics (entry-level; less differentiating at mid-level)  <\/li>\n<li><strong>Context-specific (cloud\/warehouse):<\/strong> <\/li>\n<li>Snowflake SnowPro (useful in Snowflake-heavy shops)  <\/li>\n<li>Google Cloud data certifications (if BigQuery\/GCP-centric)<\/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>Data Analyst, Reporting Analyst, Product Analyst, Revenue Operations Analyst<\/li>\n<li>BI Developer (visualization-focused)<\/li>\n<li>Analytics Engineer (lighter, especially if moving toward BI partnering)<\/li>\n<li>Finance\/RevOps analyst with strong SQL transitioning into BI<\/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>Understanding of common SaaS\/IT metrics (ARR, NRR, churn, activation, DAU\/WAU\/MAU, pipeline conversion).  <\/li>\n<li>Comfort working across multiple systems (CRM, billing, support, product telemetry).  <\/li>\n<li>Depth in a specific domain is helpful but not always required; ability to learn quickly is essential.<\/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>No people management required.  <\/li>\n<li>Expected to demonstrate <strong>influence, ownership, and stakeholder leadership<\/strong> (driving alignment on definitions and adoption).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Junior Data Analyst \/ Reporting Analyst<\/li>\n<li>Operations Analyst (RevOps\/CS Ops) with SQL exposure<\/li>\n<li>Product Support Analyst or Implementation Analyst (with analytics responsibilities)<\/li>\n<li>Finance analyst moving into BI (especially for revenue analytics)<\/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>Senior Business Intelligence Analyst<\/strong> (greater domain ownership, governance leadership, exec support)<\/li>\n<li><strong>Analytics Engineer<\/strong> (more transformation\/modeling ownership)<\/li>\n<li><strong>Data Product Manager (Analytics)<\/strong> (data product strategy, roadmap, adoption)<\/li>\n<li><strong>Product Analyst \/ Growth Analyst<\/strong> (deep product experimentation and adoption analytics)<\/li>\n<li><strong>Data Scientist (applied)<\/strong> (if building deeper statistical\/ML skills)<\/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>RevOps Analytics \/ GTM Analytics Lead<\/strong> (commercial performance and forecasting analytics)<\/li>\n<li><strong>Customer Insights \/ CS Ops Lead<\/strong> (health scoring, renewal analytics)<\/li>\n<li><strong>BI Platform Lead<\/strong> (governance, performance, self-service enablement)<\/li>\n<li><strong>Analytics Enablement \/ Data Literacy Lead<\/strong> (training, adoption, operating model)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Skills needed for promotion (to Senior BI Analyst)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ownership of a KPI domain end-to-end (definitions, governance, and adoption).<\/li>\n<li>Stronger metric governance and change management (communication plans, versioning).<\/li>\n<li>Demonstrated impact: documented decisions influenced and measurable improvements.<\/li>\n<li>Better technical breadth: semantic layer mastery, performance tuning, deeper modeling understanding.<\/li>\n<li>Mentorship and standard-setting across BI practices.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How the role evolves over time<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Early stage: heavy dashboard building, \u201cfirst source of truth,\u201d rapid iteration.  <\/li>\n<li>Growth stage: standardization, semantic layer, governance, reduction of ad-hoc.  <\/li>\n<li>Enterprise stage: reconciliation rigor, auditability, SLAs, formal change control, role specialization.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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 requirements:<\/strong> stakeholders ask for \u201ca dashboard\u201d without defining the decision or action.<\/li>\n<li><strong>Data quality issues upstream:<\/strong> missing events, CRM hygiene gaps, inconsistent billing statuses.<\/li>\n<li><strong>Metric disputes:<\/strong> multiple definitions of \u201cactive user,\u201d \u201cchurn,\u201d or \u201cpipeline\u201d across teams.<\/li>\n<li><strong>Context loss:<\/strong> dashboards lack interpretation guidance and get misused or misunderstood.<\/li>\n<li><strong>Competing priorities:<\/strong> end-of-quarter asks and exec escalations disrupt planned work.<\/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 analytics engineering capacity to create clean models; BI analyst forced into repeated ad-hoc transformations.<\/li>\n<li>Slow access approvals or restrictive security policies without clear processes.<\/li>\n<li>Overreliance on a single analyst for institutional knowledge.<\/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>Dashboard sprawl:<\/strong> many similar dashboards with conflicting logic and no ownership.<\/li>\n<li><strong>SQL copy-paste culture:<\/strong> repeated logic across queries leading to inconsistencies.<\/li>\n<li><strong>\u201cLooks right\u201d validation:<\/strong> insufficient reconciliation and QA, especially for revenue metrics.<\/li>\n<li><strong>Vanity metrics:<\/strong> focusing on easily measured metrics rather than decision-grade KPIs.<\/li>\n<li><strong>Overbuilding:<\/strong> complex dashboards that users can\u2019t interpret or don\u2019t adopt.<\/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>Weak SQL and inability to validate results confidently.<\/li>\n<li>Poor communication: unclear assumptions, hidden caveats, slow stakeholder updates.<\/li>\n<li>Lack of prioritization discipline: constantly reactive, minimal durable assets.<\/li>\n<li>Insufficient product mindset: dashboards released without iteration, documentation, or adoption follow-through.<\/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>Leaders make decisions based on incorrect or inconsistent metrics (strategy misalignment).<\/li>\n<li>Reduced trust in the data platform; teams revert to spreadsheets and shadow reporting.<\/li>\n<li>Slower response to churn risks, funnel drops, or operational issues.<\/li>\n<li>Increased cost due to inefficient reporting, duplicated work, and poor self-service.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Broader scope (BI + data modeling + some ingestion troubleshooting).  <\/li>\n<li>More ad-hoc and rapid iteration; fewer governance controls.  <\/li>\n<li><strong>Mid-size scale-up:<\/strong> <\/li>\n<li>Clear domain ownership; partnership with analytics engineers; growing metric governance.  <\/li>\n<li>Focus on semantic layer and reducing dashboard sprawl.  <\/li>\n<li><strong>Enterprise:<\/strong> <\/li>\n<li>Strong governance, audit readiness, reconciliation rigor, access controls.  <\/li>\n<li>Often specialized into product BI, revenue BI, finance BI, or operations BI.<\/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>B2B SaaS (common default):<\/strong> heavy emphasis on subscription lifecycle, product adoption, CRM\/billing reconciliation.  <\/li>\n<li><strong>IT services \/ managed services:<\/strong> utilization, SLA performance, incident analytics, project margins.  <\/li>\n<li><strong>Platform\/marketplace:<\/strong> supply-demand metrics, liquidity, trust\/safety metrics (context-specific).<\/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>Core competencies remain consistent; differences appear in:<\/li>\n<li>Data privacy requirements (e.g., GDPR-like constraints)  <\/li>\n<li>Localization and multi-currency reporting  <\/li>\n<li>Regional GTM structures and segmentation<\/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> event telemetry, funnels, cohorts, activation and retention analytics are central.  <\/li>\n<li><strong>Service-led:<\/strong> operational KPIs (delivery velocity, utilization, SLA adherence), project profitability, capacity planning.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Startup vs enterprise (operating model implications)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Startup:<\/strong> speed, pragmatic definitions, less formal change control.  <\/li>\n<li><strong>Enterprise:<\/strong> formal metric ownership, certification, audit trails, and stricter access governance.<\/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> stronger emphasis on access logs, segregation of duties, data retention policies, approved reporting logic.  <\/li>\n<li><strong>Non-regulated:<\/strong> more flexibility, but still needs strong internal governance for trust.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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 (now and increasing)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Drafting SQL queries from natural language prompts (requires expert validation).<\/li>\n<li>Generating first-pass dashboard layouts and descriptions.<\/li>\n<li>Automated anomaly detection and alerting on KPI shifts or data freshness.<\/li>\n<li>Summarizing dashboard changes and producing templated weekly narratives.<\/li>\n<li>Automated documentation drafts (column descriptions, metric logic explanations).<\/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><strong>Metric governance and alignment:<\/strong> negotiating definitions across Finance, RevOps, Product\u2014this is a social\/organizational challenge.<\/li>\n<li><strong>Judgment and context:<\/strong> understanding why a metric changed and what action is appropriate.<\/li>\n<li><strong>Data trust validation:<\/strong> reconciliation, edge-case reasoning, and sense-checking against operational reality.<\/li>\n<li><strong>Storytelling and influencing decisions:<\/strong> tailoring message to audience, highlighting tradeoffs and risks.<\/li>\n<li><strong>Ethics and privacy:<\/strong> ensuring AI-assisted workflows don\u2019t expose sensitive data or violate policies.<\/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>BI analysts will spend less time on first-draft queries and more time on:<\/li>\n<li>Validation and governance (\u201ctrust engineering\u201d for metrics)<\/li>\n<li>Defining reusable metric assets (metrics-as-code, semantic governance)<\/li>\n<li>Proactive insight generation (monitoring, detection, and action loops)<\/li>\n<li>Enablement: training stakeholders to responsibly use AI-generated insights<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">New expectations caused by AI and platform shifts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stronger emphasis on <strong>data lineage, transparency, and reproducibility<\/strong> (so AI outputs can be audited).<\/li>\n<li>Increased need for <strong>standard KPI layers<\/strong> to prevent AI from generating inconsistent metric interpretations.<\/li>\n<li>Higher stakeholder expectations for speed (\u201cnear real-time answers\u201d)\u2014requiring clearer SLAs and prioritization.<\/li>\n<li>Greater responsibility to establish \u201csafe self-serve analytics\u201d patterns that prevent misuse of sensitive data.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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 correctness<\/strong>\n   &#8211; Joins, window functions, time-series logic, handling duplicates, slowly changing dimensions.\n   &#8211; Ability to reason about grain and avoid double counting.<\/li>\n<li><strong>Dashboard design and UX judgment<\/strong>\n   &#8211; Can the candidate build intuitive, decision-oriented dashboards?\n   &#8211; Do they know when a dashboard is the wrong solution?<\/li>\n<li><strong>Metric thinking and governance<\/strong>\n   &#8211; How they define metrics, handle disputes, and document assumptions.<\/li>\n<li><strong>Analytical reasoning<\/strong>\n   &#8211; Hypothesis formation, segmentation, cohort thinking, interpreting causal vs correlational signals.<\/li>\n<li><strong>Stakeholder communication<\/strong>\n   &#8211; Requirements gathering, expectation setting, writing and presenting insights.<\/li>\n<li><strong>Data quality mindset<\/strong>\n   &#8211; Reconciliation methods, QA checklists, how they respond to \u201cnumbers don\u2019t match.\u201d<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Practical exercises or case studies (enterprise-realistic)<\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>SQL exercise (60\u201390 minutes)<\/strong>\n   &#8211; Provide tables such as <code>subscriptions<\/code>, <code>invoices<\/code>, <code>events<\/code>, <code>accounts<\/code>.\n   &#8211; Ask for metrics like NRR, churn rate, activation conversion, and a reconciliation check.\n   &#8211; Evaluate correctness, readability, and handling of edge cases.<\/li>\n<li><strong>Dashboard critique + redesign (45\u201360 minutes)<\/strong>\n   &#8211; Provide a flawed dashboard (too many charts, unclear KPIs, misleading filters).\n   &#8211; Ask the candidate to propose improvements: KPI hierarchy, layout, labels, definitions, drill paths.<\/li>\n<li><strong>Metrics definition workshop (role-play, 30\u201345 minutes)<\/strong>\n   &#8211; Stakeholders disagree on \u201cactive customer.\u201d\n   &#8211; Candidate must facilitate alignment: clarify purpose, propose definitions, document tradeoffs.<\/li>\n<li><strong>Insight memo writing (async, 60 minutes)<\/strong>\n   &#8211; Provide a dataset extract and ask for a 1-page memo: findings, confidence, caveats, recommended actions.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Strong candidate signals<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Talks naturally about <strong>grain<\/strong>, <strong>definitions<\/strong>, and <strong>reconciliation<\/strong>.<\/li>\n<li>Uses structured thinking: decision \u2192 KPI \u2192 segment \u2192 trend \u2192 root cause \u2192 action.<\/li>\n<li>Demonstrates empathy for users and a product mindset about dashboards.<\/li>\n<li>Comfortable saying \u201cno\u201d or \u201cnot yet\u201d with alternatives and rationale.<\/li>\n<li>Evidence of shipped, adopted BI assets and how adoption was measured.<\/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>Over-focus on visualization aesthetics without metric rigor.<\/li>\n<li>Cannot explain metric logic or validate results beyond \u201cit looks right.\u201d<\/li>\n<li>Treats every request as a dashboard request (lack of problem framing).<\/li>\n<li>Avoids stakeholder conversations; prefers to \u201cjust build what they asked for.\u201d<\/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>Cannot reconcile revenue-related metrics or dismisses reconciliation as \u201cfinance\u2019s problem.\u201d<\/li>\n<li>Poor handling of PII\/security considerations or casual attitude to data access.<\/li>\n<li>Consistently blames upstream systems without proposing mitigations or clear bug reports.<\/li>\n<li>Inability to explain query logic clearly or repeated confusion about duplicates and joins.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Scorecard dimensions (use for structured evaluation)<\/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 (example)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>SQL &amp; data reasoning<\/td>\n<td>Correct, efficient queries; strong grain awareness<\/td>\n<td style=\"text-align: right;\">25%<\/td>\n<\/tr>\n<tr>\n<td>BI dashboard craft<\/td>\n<td>Clear KPI hierarchy, usability, and decision orientation<\/td>\n<td style=\"text-align: right;\">20%<\/td>\n<\/tr>\n<tr>\n<td>Metrics &amp; governance<\/td>\n<td>Defines metrics well; documents; manages change<\/td>\n<td style=\"text-align: right;\">15%<\/td>\n<\/tr>\n<tr>\n<td>Analytical thinking<\/td>\n<td>Sound interpretation, segmentation, hypothesis testing<\/td>\n<td style=\"text-align: right;\">15%<\/td>\n<\/tr>\n<tr>\n<td>Communication<\/td>\n<td>Clear narratives; expectation setting; stakeholder empathy<\/td>\n<td style=\"text-align: right;\">15%<\/td>\n<\/tr>\n<tr>\n<td>Quality mindset<\/td>\n<td>QA, reconciliation, incident response maturity<\/td>\n<td style=\"text-align: right;\">10%<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator\" \/>\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>Field<\/th>\n<th>Summary<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Role title<\/td>\n<td>Business Intelligence Analyst<\/td>\n<\/tr>\n<tr>\n<td>Role purpose<\/td>\n<td>Convert multi-source company data into trusted metrics, dashboards, and insights that improve decision-making and business performance in a software\/IT organization.<\/td>\n<\/tr>\n<tr>\n<td>Top 10 responsibilities<\/td>\n<td>1) Standardize KPI definitions; 2) Build\/maintain dashboards; 3) Deliver recurring reporting; 4) Create certified datasets\/semantic measures; 5) Perform deep-dive analyses (cohorts\/funnels\/segments); 6) Ensure data QA and reconciliations; 7) Run BI intake and prioritization; 8) Enable self-service with documentation\/training; 9) Partner on instrumentation and telemetry quality; 10) Govern dashboard lifecycle (ownership, certification, deprecation).<\/td>\n<\/tr>\n<tr>\n<td>Top 10 technical skills<\/td>\n<td>SQL; BI tool development (Tableau\/Power BI\/Looker); data modeling fundamentals (grain\/star schema); metric definition\/governance; reconciliation and QA methods; semantic layer concepts; dbt literacy; cohort\/funnel analytics; warehouse cost\/performance awareness; documentation practices for analytics assets.<\/td>\n<\/tr>\n<tr>\n<td>Top 10 soft skills<\/td>\n<td>Business framing; stakeholder management; analytical rigor; data storytelling; product mindset; collaboration with data engineering; attention to detail; resilience under pressure; prioritization discipline; learning agility.<\/td>\n<\/tr>\n<tr>\n<td>Top tools or platforms<\/td>\n<td>Snowflake\/BigQuery; Tableau\/Power BI\/Looker; dbt; Salesforce; Zendesk\/ServiceNow CS; Jira; Confluence\/Notion; Excel\/Google Sheets; Fivetran (or similar); Slack\/Teams.<\/td>\n<\/tr>\n<tr>\n<td>Top KPIs<\/td>\n<td>Dashboard adoption; data freshness SLA adherence; metric consistency score; reconciliation pass rate; cycle time (request to delivery); dashboard breakage rate; stakeholder CSAT; documentation completeness; decision impact instances; query performance (p95 load time).<\/td>\n<\/tr>\n<tr>\n<td>Main deliverables<\/td>\n<td>KPI dashboards; certified datasets\/semantic objects; metric glossary; weekly\/monthly reporting packs; insight memos; cohort\/funnel analyses; data QA checks; governance artifacts (ownership\/change logs); enablement\/training materials.<\/td>\n<\/tr>\n<tr>\n<td>Main goals<\/td>\n<td>30\/60\/90-day onboarding to ownership; 6-month scaling governance and self-service; 12-month establishment of trusted KPI system with measurable adoption and decision impact.<\/td>\n<\/tr>\n<tr>\n<td>Career progression options<\/td>\n<td>Senior BI Analyst; Analytics Engineer; Data Product Manager (Analytics); Product\/Growth Analyst; BI Platform Lead; RevOps Analytics Lead; (with added skills) Data Scientist (applied).<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>The **Business Intelligence Analyst** turns product, customer, financial, and operational data into **trusted insights, dashboards, and decision support** that drive measurable business outcomes. This role sits at the intersection of analytics, data engineering, and business operations\u2014ensuring leaders and teams can self-serve accurate metrics and confidently act on them.<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[24453,6516],"tags":[],"class_list":["post-72578","post","type-post","status-publish","format-standard","hentry","category-analyst","category-data-analytics"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/72578","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=72578"}],"version-history":[{"count":0,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/72578\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=72578"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=72578"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=72578"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}