READ. UNDERSTAND. PRACTICE.
Prepare for your next interview.
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
20,926 resources · Page 825 of 872
Interview questions · Splunk
Career Motivation & Core Behaviors
Practice Splunk Product Manager behavioral interviews on software-engineering-to-PM transition, technical strengths, time-pressure delivery, missed expectations, and proud deliverables. The solution emphasizes enterprise data products, metrics, guardrails, customer impact, and learning mechanisms.
Interview questions · Capital One
Choose and justify ML algorithms for tabular prediction
This question evaluates a candidate's competency in model selection for tabular regression—weighing trade-offs among linear/regularized regression, decision trees, Random Forest, and XGBoost—along with skills in preprocessing, categorical handling, missingness, latency and memory constraints, instance-level explainability, fairness checks, calibration, and experiment design. It belongs to the Machine Learning domain and is commonly asked to assess both conceptual understanding of model behavior and bias–variance trade-offs and practical application skills in validation strategy, performance/latency measurement, and production-ready explainability and robustness.
Interview questions · Roblox
Choose best/worst actions under OA pressure
This question evaluates judgment and leadership competencies in data science — including risk assessment, stakeholder impact analysis, integrity under time pressure, and handling failing tests and collaborator input — and falls under the Behavioral & Leadership category.
Interview questions · Thumbtack
Choose clustering vs regression; explain KNN
This question evaluates model selection between clustering and regression given partially labeled outcomes, familiarity with clustering algorithms (K-Means, Hierarchical/Agglomerative, DBSCAN/HDBSCAN, Gaussian Mixture Models), K-Nearest Neighbors behavior, evaluation metrics, hyperparameters, and deployment considerations for a Data Scientist role in Machine Learning. It is commonly asked to assess judgment on supervised versus unsupervised approaches, trade-offs driven by label availability, objective and cost of errors, algorithmic assumptions, scalability, and practical deployment techniques, and the level spans both conceptual understanding and practical application.
Interview questions · Amazon
Choose regularization norms and model formulations
This question evaluates understanding of regularization norms (L0, L1, L2, L∞), objective formulations for linear and logistic regression, and practical competencies in handling collinearity, outliers, feature scaling, and optimization difficulty.
Interview questions · Meta
Choose threshold under asymmetric costs
This question evaluates cost-sensitive classification, operating-threshold selection, score calibration, drift monitoring, and experiment and guardrail design competencies within the Machine Learning domain.
Interview questions · First American
Clarify Ambiguous Requirements and Resolve Team Conflicts
This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Clarify Ambiguous Requirements and Resolve Team Conflicts states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
Interview questions · Fanatics
Clarify employment type at Microsoft
This question evaluates a candidate's ability to clearly articulate employment arrangements and the degree of ownership, accountability, performance evaluation, and measurable impact on projects, reflecting leadership, communication, and product-stewardship competencies.
Interview questions · Amazon
Clarify internship availability and conversion
This question evaluates a candidate's clarity about availability, logistical constraints, and intent to convert an internship into a full-time role, testing communication of exact dates, work authorization, relocation, and academic conflicts.
Interview questions · Meta
Clarify scope and align to mission
This question evaluates a data scientist's product sense, leadership and stakeholder-alignment skills, including scope clarification, mission translation, metric definition, and collaborative communication.
Interview questions · Apple
Clarify status, education, and multi-role strategy
This question evaluates a candidate's ability to document and communicate U.S. work authorization details, resolve resume inconsistencies, articulate multi-level role positioning, and demonstrate minicase availability and preparation—assessing attention to detail, clarity of communication, stakeholder coordination, and practical readiness for data-science interviews. Commonly asked in Behavioral & Leadership screens for Data Scientist roles to verify eligibility, alignment with role expectations, and logistical readiness, it tests both conceptual understanding of career-leveling and contingency planning and practical application of documentation, messaging, and time-management.
Interview questions · Reddit
Collaborate with PM and Eng as DS
This question evaluates a data scientist's cross-functional collaboration, prioritization, ownership, stakeholder management, and influencing skills when engaging with product managers and engineers.
Interview questions · Reddit
Communicate and de-risk a non-experimental launch
This question evaluates a data scientist's competency in interpreting causal-inference results from a Synthetic Control, communicating evidence strength and residual risks to executives and skeptical partners, structuring rollout governance and rollback criteria, and managing bias control, dissent and cross-functional accountability.
Interview questions · TikTok
Communicate technical impact under skeptical stakeholders
This question evaluates a data scientist's ability to communicate technical impact to skeptical stakeholders and demonstrate causal evidence for improvements, testing competencies in experiment design, causal inference, metrics-driven evaluation, and technical leadership expressed through design choices and risk trade-offs.
Interview questions · Meta
Communicate trade-offs and influence launch
This question evaluates product judgment, experimentation interpretation, and cross-functional leadership skills for a data scientist, focusing on communicating trade-offs between per-account metric lifts and cross-account cannibalization; Category: Behavioral & Leadership, Domain: data science and product experimentation.
Interview questions · Amazon
Communicating Top-Down Change
Practice communicating top-down operational change across peer managers, direct-report managers, and front-line employees. The solution covers safety, efficiency, cost goals, audience-specific messaging, pilots, feedback loops, metrics, guardrails, and sustainment.
Interview questions · PayPal
Compare final, finally, finalize
This interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Compare final, finally, finalize states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
Interview questions · LinkedIn
Compare heap and stack memory
This question evaluates understanding of memory management concepts including stack versus heap allocation, object lifetimes, allocation and free behavior, access patterns, performance characteristics, and thread visibility within the Coding & Algorithms domain.
Interview questions · Meta
Compare Instagram vs. Facebook using causal experiments
This question evaluates causal inference, experimentation design, metric engineering, and ecosystem-level impact assessment skills for a Data Scientist in the Analytics & Experimentation domain, with emphasis on defining a single-objective OEC that prevents pure cannibalization and on measuring cross-app effects via randomized rollouts.
Interview questions · Thumbtack
Compare list/dict; parse JSON/CSV at scale
This question evaluates understanding of Python data structures (list vs dict), algorithmic time and memory complexity, ordering guarantees in CPython, large-scale parsing and streaming of JSON/CSV, and robust data-cleaning and error-handling strategies.
Interview questions
Compare LLN and CLT with heavy tails
This question evaluates understanding of probabilistic limit theorems and heavy-tailed behavior, specifically the assumptions and convergence guarantees of the Law of Large Numbers and the Central Limit Theorem when applied to Pareto-like distributions.
Interview questions · Apple
Compare Normal vs Poisson; test dispersion and approximate tails
This question evaluates a data scientist's competency in statistical inference for count data, covering MLE and asymptotic variance estimation, Wald confidence intervals, tests for equidispersion versus overdispersion, Normal approximation with continuity correction for Poisson tails, and model selection diagnostics.
Interview questions · Capital One
Compare solar vs biomass paybacks and recommend
This question evaluates quantitative financial modeling, scenario analysis, and decision-making skills for a Data Scientist role by requiring calculation of annual profit and payback periods, incorporation of carbon credits, and comparative output analysis; it tests the Statistics & Math domain and emphasizes practical application of numerical analysis rather than purely conceptual theory. It is commonly asked to gauge proficiency in applying statistical and mathematical techniques to real-world energy investment problems, performing sensitivity and scenario analyses, and integrating non-financial considerations such as supply risk, permitting complexity, and scalability into evidence-based comparisons.
Interview questions · Fidelity
Compare Spring and Spring Boot
Compare Spring and Spring Boot evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.