Data Science & Analytics Topics
Statistical analysis, data analytics, big data technologies, and data visualization. Covers statistical methods, exploratory analysis, and data storytelling.
Engineering and Business Outcomes
How engineering work and technical decisions translate into measurable business outcomes and how to demonstrate that linkage. Topics include mapping architecture choices, reliability, performance improvements and developer productivity initiatives to business metrics such as revenue, customer engagement, time to market, cost reduction and customer satisfaction. Candidates should be able to identify engineering metrics to track including latency, availability, error and incident rates, cycle time and deployment frequency, explain instrumentation strategies to capture signals, design measurement plans and experiments to establish causal impact, and attribute observed changes to specific engineering efforts. This topic also covers communicating technical tradeoffs and impact to nontechnical stakeholders, choosing appropriate granularity for measurement, and describing concrete initiatives with their measurement approach and quantified business impact.
Analytical Background
The candidate's approach to analytical, evidence-based problem solving: how they take an ambiguous question, break it into testable pieces, gather and examine relevant information or data, choose appropriate methods to reach a conclusion, and turn that conclusion into a concrete recommendation or decision. This can show up as quantitative work (statistics, data analysis, experimentation, dashboards) or as qualitative and domain-specific analysis (reviewing logs or incidents, case or contract research, market or process analysis, root-cause investigation). Draw on academic projects, internships, or professional work. Focus on the end-to-end path: how the question or hypothesis was framed, what evidence was examined and with what tools or methods, what trade-offs were considered, and how the resulting insight changed a real decision or outcome.
Data Investigation and Root Cause Analysis
Techniques and a structured process for diagnosing an unexpected change in a metric, dataset, or system signal using quantitative evidence complemented by qualitative signals. Candidates should demonstrate how to validate that an observed change is a real signal and not noise, or a reporting, instrumentation, or pipeline problem, by checking data quality, event or record counts, sampling, schema stability, and pipeline or data-flow integrity. Describe slicing and decomposition strategies such as cohort or population segmentation, geography and platform segmentation, feature-level analysis, time series decomposition to separate trend and seasonality, funnel and velocity analysis, retention analysis, and variance analysis. Explain how to form, prioritize, and test hypotheses; design diagnostic queries and tests using structured query language or equivalent tooling; and correlate the change with plausible triggers such as releases or deployments, configuration or schema changes, experiments, campaigns, upstream system incidents, or external events. Include how to combine quantitative findings with qualitative evidence such as interviews, logs, session or trace replay, support tickets, or incident timelines to strengthen causal inference. Finally, cover communicating concise findings and actionable recommendations to stakeholders, creating reproducible queries and monitoring dashboards, alerts, or runbooks, and mentoring others on a systematic investigation approach. This applies broadly to investigating anomalies in business metrics, product data, system or service health signals, financial figures, or model performance, not only one of these domains.