Top 100+ Data Analyst Interview Questions and Answers (2026 Guide)

If you're preparing for a job in analytics, you already know the hardest part isn't learning SQL or Power BI — it's walking into the interview room and proving it under pressure. That's exactly what Data Analyst interview questions and answers should help you do, and it's exactly what this guide is built for.

Demand for Data Analysts in India keeps climbing every year, but so does the number of candidates applying for every open role — which means interviews have gotten more competitive, not less. Most candidates who fail don't fail because they lack ability; they fail because they never practiced explaining their reasoning out loud, never touched a real SQL editor under time pressure, or walked in with a generic, copy-pasted project nobody could ask a follow-up question about.

This guide fixes that. It's the most complete, structured collection of Data Analyst interview questions available — over 100 questions across Excel, SQL, Power BI, statistics, real business scenarios, case studies, HR, and company-specific rounds — with the reasoning behind each answer, not just the answer itself.

What Are the Most Important Data Analyst Interview Questions?

The most important Data Analyst interview questions cover four areas: SQL (joins, GROUP BY, window functions), Excel (VLOOKUP/XLOOKUP, Pivot Tables, SUMIFS), Power BI (DAX, CALCULATE, data modeling), and scenario-based business reasoning (e.g., "sales dropped, what would you investigate?"). Together these make up roughly 80% of real interview questions asked.

Data Analyst Interview Process Explained

Before the questions themselves, it helps to understand the shape of the process — most companies in India follow a version of the same sequence, though the emphasis shifts by company type.

Resume screening — An ATS (applicant tracking system) or recruiter scans for relevant keywords (SQL, Power BI, Excel, specific tools mentioned in the job description) and a coherent project history. This is where a strong, keyword-aware resume and a clear portfolio link matter most.

Aptitude round — Common at IT services companies (TCS, Infosys, Wipro, Cognizant, Capgemini) as a high-volume filter. Usually an online test covering logical reasoning, basic quantitative aptitude, and sometimes verbal ability — rarely data-analytics-specific.

Technical round — The core of the process. Usually covers SQL (live query writing), Excel, and sometimes Power BI or a basic statistics question, either as a single combined round or split into separate SQL/Excel/BI rounds at larger companies.

SQL round — Often run separately at product companies and Big Tech, sometimes on a shared coding platform (HackerRank, CoderPad) rather than verbally. Expect 2-4 questions of increasing difficulty — a basic filter/aggregate query, then a join-heavy query, then often a window-function question.

Excel round — Common at IT services and consulting firms, sometimes a live screen-share task ("build a pivot table summarizing this data") rather than a Q&A format.

Power BI round — Increasingly common as more roles are titled "BI Analyst" or explicitly require Power BI. Expect DAX questions, data modeling questions, and often a walkthrough of a dashboard you've built.

Managerial round — Tests business judgment and stakeholder scenarios — how you'd handle conflicting requirements, a tight deadline, or a wrong number found after a report was already shared.

HR round — Tests communication, motivation, and cultural fit — rarely technical. Covers standard behavioral questions and salary expectations.

Example hiring flows at MNCs: TCS and Infosys typically run aptitude → technical → HR, often completed in a single day for campus hiring. Accenture and Capgemini often add a case-study element to the technical round given their client-facing project structure. Deloitte, EY, and KPMG (the "Big 4") lean heavily on case-study and business-reasoning rounds alongside standard SQL/Excel questions, reflecting their consulting-first culture. Product companies and Big Tech (Amazon, Flipkart, Microsoft) typically run more technical rounds (2-3) with fewer aptitude-style filters, and weight live SQL performance and portfolio depth most heavily.

📋 Not sure your current skill level matches what these rounds expect? The Data Analyst Roadmap 2026 lays out exactly what "interview-ready" looks like at each stage of learning.

Basic Data Analyst Interview Questions

These fundamentals show up in nearly every interview, often as the opening questions before the round gets more technical. Get comfortable explaining each of these in your own words, not memorized definitions.

1. What is Data Analysis?

Simple Answer: Data analysis is the process of inspecting, cleaning, and interpreting data to find useful insights that support a business decision.

Detailed Explanation: It typically involves collecting data, cleaning it (removing errors, duplicates, and inconsistencies), exploring it to find patterns, and presenting findings in a way a non-technical audience can act on — usually through a dashboard, report, or written recommendation.

Interviewer's Intent: Checking whether you understand analysis as a full process, not just "making charts."

Common Mistakes: Describing only the tools ("I use Excel and SQL") instead of the actual process and purpose.

2. What is the difference between Data Analysis and Data Analytics?

Simple Answer: Data analysis is the specific process of examining a dataset; data analytics is the broader discipline that includes analysis, plus the tools, techniques, and systems used to generate insights at scale.

Detailed Explanation: In practice, most companies use the terms interchangeably, but analytics often implies a more systematic, ongoing function (dashboards, pipelines, forecasting) versus a one-off analysis exercise.

Interviewer's Intent: Testing precision of vocabulary and whether you've thought about scope, not just semantics.

Common Mistakes: Overcomplicating the answer — a short, clear distinction is better than a long, vague one.

3. What does a Data Analyst actually do day to day?

Simple Answer: A Data Analyst pulls data (usually with SQL), cleans and shapes it, builds or updates dashboards/reports, and communicates findings to stakeholders who use them to make decisions.

Detailed Explanation: A representative week includes writing SQL queries against a company database, cleaning data in Excel or Python, updating a Power BI dashboard, running basic statistical checks, and presenting findings in plain English in a meeting.

Interviewer's Intent: Checking that you understand the real job, not just the job title.

Common Mistakes: Only mentioning tools without describing the actual workflow or business purpose.

4. What is the difference between structured and unstructured data?

Simple Answer: Structured data fits neatly into rows and columns (like a spreadsheet or SQL table); unstructured data doesn't have a predefined format (like emails, images, or free-text reviews).

Detailed Explanation: Most Data Analyst work focuses on structured data because it's directly queryable and analyzable with standard tools; unstructured data usually needs additional processing (text mining, NLP) before it can be analyzed the same way.

Interviewer's Intent: Confirming basic data literacy before deeper technical questions.

Common Mistakes: Confusing "unstructured" with "messy structured data" — messy data still has rows and columns, just with quality issues.

5. What is data cleaning and why is it important?

Simple Answer: Data cleaning is the process of fixing or removing incorrect, incomplete, duplicate, or inconsistent data before analysis.

Detailed Explanation: Includes handling missing values, removing duplicates, standardizing formats (dates, currencies, text casing), and catching outliers that may be data-entry errors. Skipping this step is the most common reason an analysis produces a wrong or misleading conclusion.

Interviewer's Intent: Testing whether you understand that "garbage in, garbage out" applies directly to your own work.

Common Mistakes: Treating data cleaning as a minor step rather than often the majority of the actual work.

6. What is the difference between a Data Analyst and a Data Scientist?

Simple Answer: A Data Analyst answers business questions using existing data (dashboards, reports); a Data Scientist builds predictive models using machine learning.

Detailed Explanation: Data Analysts rely mainly on SQL, Excel, and BI tools with lighter statistics; Data Scientists need deeper programming, statistics, and ML expertise to build systems that predict future outcomes, not just describe past ones.

Interviewer's Intent: Testing whether you understand the role's actual boundaries — important if the job title is ambiguous.

Common Mistakes: Claiming the roles are interchangeable, or implying one is simply "better" than the other. See the full Data Analyst vs Data Scientist comparison for the complete breakdown.

7. What is the difference between a Data Analyst and a Business Analyst?

Simple Answer: A Data Analyst focuses on analyzing data directly (SQL, dashboards); a Business Analyst focuses more on bridging business needs with technical/process solutions, often with less hands-on data work.

Detailed Explanation: There's significant overlap, and many companies use the titles loosely — the safest approach is to ask what the specific role actually does day-to-day if it's ambiguous in the job description. See the Business Analyst vs Data Analyst salary comparison for how pay differs between the two.

Interviewer's Intent: Checking self-awareness about role boundaries, especially if you're applying to a title-ambiguous posting.

Common Mistakes: Giving a textbook definition without acknowledging real-world overlap.

8. What is Exploratory Data Analysis (EDA)?

Simple Answer: EDA is the process of exploring a dataset to understand its structure, spot patterns, and identify issues before doing a deeper, more formal analysis.

Detailed Explanation: Typically includes checking data types, looking at summary statistics, visualizing distributions, and identifying missing values or outliers — it's the "getting to know the data" phase that happens before you try to answer a specific business question.

Interviewer's Intent: Checking whether you have a disciplined process rather than jumping straight to conclusions.

Common Mistakes: Skipping EDA in your own project explanations, which signals you may skip it in real work too.

9. What are the key skills required for a Data Analyst?

Simple Answer: Excel, SQL, a BI tool (Power BI or Tableau), basic statistics, and clear business communication — with Python as a valuable addition.

Detailed Explanation: Technical skill alone isn't enough; the ability to translate a business question into an analysis and translate the answer back into a plain-English recommendation is what separates a hireable candidate from a purely technical one.

Interviewer's Intent: Checking whether you know what "well-rounded" looks like for this specific role.

Common Mistakes: Listing only tools, omitting communication and business-reasoning skills entirely.

10. What is the difference between primary and secondary data?

Simple Answer: Primary data is collected firsthand for a specific purpose (a survey you ran); secondary data is existing data collected by someone else for a different original purpose (a public dataset or another team's database).

Detailed Explanation: Most Data Analyst work involves secondary data — company databases, third-party datasets — so understanding its limitations (context you don't fully control) matters.

Interviewer's Intent: Basic data-literacy check, often asked early to gauge foundational knowledge.

Common Mistakes: Confusing this with structured/unstructured data — they're unrelated distinctions.

More foundational questions you should be ready for:

Excel Interview Questions for Data Analysts

Excel questions are rarely asked as pure definitions — expect a live scenario ("how would you find the total sales for this region using this data?") more often than a textbook question. Here are the ones asked most consistently.

1. What is the difference between VLOOKUP and XLOOKUP?

Example: =VLOOKUP(A2, Sheet2!A:D, 3, FALSE) looks up the value in A2 within Sheet2's first column and returns the value from the 3rd column.

=XLOOKUP(A2, Sheet2!A:A, Sheet2!C:C) performs the same lookup but can search in any direction, doesn't break if columns are inserted, and defaults to an exact match without needing FALSE.

Why it matters: XLOOKUP is more flexible and less fragile — knowing why it's an improvement (not just that it exists) is what interviewers actually listen for.

2. How does INDEX-MATCH compare to VLOOKUP?

Example: =INDEX(C:C, MATCH(A2, A:A, 0)) finds the row where A2 matches column A, then returns the corresponding value from column C.

Why it matters: Unlike VLOOKUP, INDEX-MATCH can look to the left of the lookup column and doesn't break when columns are inserted or reordered — a common follow-up question is "why would you use INDEX-MATCH over VLOOKUP?"

3. What's the difference between SUMIF and SUMIFS?

Example: =SUMIF(A:A, "Delhi", B:B) sums column B where column A equals "Delhi" — one condition only.

=SUMIFS(B:B, A:A, "Delhi", C:C, ">1000") sums column B where column A is "Delhi" AND column C is greater than 1000 — multiple conditions.

Why it matters: SUMIFS is SUMIF's multi-condition version; mixing up their argument order (SUMIF puts the sum range last, SUMIFS puts it first) is a very common live-test mistake.

4. What's the difference between COUNTIF and COUNTIFS?

Example: =COUNTIF(A:A, "Active") counts rows where column A equals "Active."

=COUNTIFS(A:A, "Active", B:B, ">50") counts rows meeting both conditions at once.

Why it matters: Same single-vs-multiple-condition logic as SUMIF/SUMIFS — interviewers often ask both back-to-back to check consistency of understanding.

5. How do you build a Pivot Table and when would you use one?

Example: Selecting a sales dataset, inserting a Pivot Table, dragging "Region" to Rows, "Sales" to Values (set to Sum), and "Product Category" to Columns instantly summarizes total sales by region and category.

Why it matters: Pivot Tables are the fastest way to summarize large datasets without writing formulas — expect a live task like "summarize this data by region and month" in an Excel round.

6. What is Conditional Formatting used for?

Example: Highlighting all cells in a "Revenue" column that are below target in red using a rule like Cell Value < 50000.

Why it matters: It's used to make outliers or exceptions visually obvious in a report without needing a separate chart — commonly tested with "how would you flag underperforming products in this sheet?"

7. What is Data Validation used for?

Example: Restricting a "Status" column to only accept values from a dropdown list (Active, Inactive, Pending) using Data → Data Validation → List.

Why it matters: Prevents data-entry errors at the source — a good answer connects this back to data quality, tying Excel skill to the broader data-cleaning discipline.

8. What is Power Query and how is it different from formulas?

Example: Using Power Query to combine 12 monthly sales CSVs into a single clean table automatically, with the transformation steps saved and re-runnable every time new files are added.

Why it matters: Power Query is Excel's built-in ETL tool — it handles repeatable, larger-scale data cleaning that would be tedious or fragile with manual formulas, and is increasingly expected knowledge for analyst roles.

9. How do you remove duplicate values in Excel?

Example: Selecting the data range, then Data → Remove Duplicates, choosing which columns define a "duplicate" row.

Why it matters: A simple but frequently tested task — the follow-up question is often "how would you check before removing them, to make sure you're not deleting valid data?"

10. What is Goal Seek / What-If Analysis used for?

Example: Using Goal Seek to find what sales volume is needed to hit a ₹10 lakh revenue target, given a fixed price per unit.

Why it matters: Tests whether you know Excel beyond reporting — into light scenario modeling, which comes up in finance-adjacent analyst roles.

11. How would you build a simple dashboard in Excel?

Example: Combining a Pivot Table, a Pivot Chart, and slicers on one sheet so a user can filter by region or time period and see the summary update instantly.

Why it matters: Tests whether you understand dashboard design (clarity, interactivity) not just individual Excel features in isolation.

12. How do you handle a large dataset that makes Excel slow?

Example: Converting ranges to Excel Tables, avoiding volatile functions (like OFFSET or NOW()) in large ranges, and using Power Query or a database (SQL) instead of Excel once row counts approach Excel's practical limits.

Why it matters: Shows awareness of Excel's limits and when to reach for a different tool — a mature, senior-level answer.

More Excel questions to be ready for:

📊 Want a structured, hands-on way to master these Excel skills instead of piecing them together? The DataVix Data Analyst course covers Excel end-to-end, from VLOOKUP to full dashboard builds, with real project practice.

SQL Interview Questions for Data Analysts

SQL interview questions for Data Analysts almost always involve writing a live query, not just explaining a concept. Practice typing these out, not just reading them — muscle memory matters under interview pressure. If you need more hands-on practice before your interview, SQLabHub.com is a solid free resource for drilling joins, subqueries, and window functions.

1. Write a query to find all customers from Delhi with orders above ₹5000.

SELECT customer_name, order_amount
FROM orders
WHERE city = 'Delhi' AND order_amount > 5000;

Explanation: WHERE filters rows before any aggregation happens — this is the most basic filtering pattern in SQL.

Real Business Use Case: Identifying high-value customers in a specific region for a targeted marketing campaign.

2. Write a query to find total revenue by region.

SELECT region, SUM(order_amount) AS total_revenue
FROM orders
GROUP BY region
ORDER BY total_revenue DESC;

Explanation: GROUP BY collapses rows into groups (one per region) so the aggregate function SUM can calculate a total for each group.

Real Business Use Case: A standard input for a quarterly business review comparing regional performance.

3. What's the difference between WHERE and HAVING?

SELECT region, SUM(order_amount) AS total_revenue
FROM orders
GROUP BY region
HAVING SUM(order_amount) > 100000;

Explanation: WHERE filters individual rows before grouping; HAVING filters groups after aggregation — you can't use an aggregate function like SUM() inside WHERE.

Real Business Use Case: Finding only the regions that crossed a revenue threshold, not filtering individual orders.

4. Write a query to find the top 5 highest-spending customers.

SELECT customer_id, SUM(order_amount) AS total_spent
FROM orders
GROUP BY customer_id
ORDER BY total_spent DESC
LIMIT 5;

Explanation: ORDER BY ... DESC sorts from highest to lowest, and LIMIT restricts the output to a specific number of rows.

Real Business Use Case: Identifying VIP customers for a loyalty program.

5. Write a query using CASE WHEN to categorize customers by spend.

SELECT customer_id,
  CASE
    WHEN total_spent > 50000 THEN 'High Value'
    WHEN total_spent BETWEEN 10000 AND 50000 THEN 'Mid Value'
    ELSE 'Low Value'
  END AS customer_segment
FROM (
  SELECT customer_id, SUM(order_amount) AS total_spent
  FROM orders GROUP BY customer_id
) t;

Explanation: CASE WHEN works like an IF-ELSE chain inside SQL, letting you create categorical labels from numeric data.

Real Business Use Case: Segmenting customers for a marketing team without needing a separate BI tool step.

6. Explain the difference between INNER JOIN, LEFT JOIN, and FULL OUTER JOIN.

SELECT o.order_id, c.customer_name
FROM orders o
LEFT JOIN customers c ON o.customer_id = c.customer_id;

Explanation: INNER JOIN returns only matching rows in both tables; LEFT JOIN returns all rows from the left table plus matches from the right (NULL if no match); FULL OUTER JOIN returns all rows from both, matched where possible.

Real Business Use Case: LEFT JOIN is used here to keep every order even if the customer record is missing, useful for spotting data-quality issues.

7. Write a self-join query to find employees and their managers.

SELECT e.employee_name, m.employee_name AS manager_name
FROM employees e
LEFT JOIN employees m ON e.manager_id = m.employee_id;

Explanation: A self-join joins a table to itself, treating it as two logical tables (e for employee, m for manager) using aliases.

Real Business Use Case: Building an org-chart-style report or analyzing team structures directly from an employee table.

8. Write a subquery to find customers who spent above the average.

SELECT customer_id, SUM(order_amount) AS total_spent
FROM orders
GROUP BY customer_id
HAVING SUM(order_amount) > (SELECT AVG(order_amount) FROM orders);

Explanation: The subquery calculates the overall average first, and the outer query compares each customer's total against it.

Real Business Use Case: Flagging above-average spenders for a retention or upsell campaign.

9. Rewrite the above using a CTE (Common Table Expression) for readability.

WITH customer_totals AS (
  SELECT customer_id, SUM(order_amount) AS total_spent
  FROM orders
  GROUP BY customer_id
)
SELECT * FROM customer_totals
WHERE total_spent > (SELECT AVG(total_spent) FROM customer_totals);

Explanation: A CTE (WITH ... AS) creates a named, temporary result set that can be referenced multiple times in the main query — making multi-step logic far more readable than nested subqueries.

Real Business Use Case: Any multi-step business logic (e.g., calculating a metric, then filtering on it) that would otherwise require a deeply nested query.

10. Write a query using ROW_NUMBER() to remove duplicate records.

WITH ranked AS (
  SELECT *, ROW_NUMBER() OVER (PARTITION BY customer_email ORDER BY order_date DESC) AS rn
  FROM customers
)
SELECT * FROM ranked WHERE rn = 1;

Explanation: ROW_NUMBER() assigns a unique sequential number within each partition (here, each email); keeping only rn = 1 keeps the most recent record per customer.

Real Business Use Case: Deduplicating a customer table where the same person signed up multiple times with slightly different records.

11. What's the difference between RANK() and DENSE_RANK()?

SELECT sales_rep, total_sales,
  RANK() OVER (ORDER BY total_sales DESC) AS rank_val,
  DENSE_RANK() OVER (ORDER BY total_sales DESC) AS dense_rank_val
FROM rep_sales;

Explanation: RANK() skips numbers after a tie (1, 2, 2, 4); DENSE_RANK() doesn't skip (1, 2, 2, 3) — the difference only shows up when there are ties.

Real Business Use Case: Ranking sales reps for a leaderboard, where how ties are handled affects bonus eligibility cutoffs.

12. Write a query to calculate a running total of monthly sales.

SELECT month, monthly_sales,
  SUM(monthly_sales) OVER (ORDER BY month) AS running_total
FROM sales_summary;

Explanation: A window function with SUM() OVER (ORDER BY ...) calculates a cumulative total without collapsing rows the way GROUP BY would.

Real Business Use Case: Tracking cumulative revenue progress toward an annual target on a live dashboard.

13. What's the difference between UNION and UNION ALL?

SELECT customer_id FROM online_orders
UNION
SELECT customer_id FROM store_orders;

Explanation: UNION combines results from two queries and removes duplicates; UNION ALL combines them and keeps all rows, including duplicates — and is faster since it skips the deduplication step.

Real Business Use Case: Combining online and in-store customer lists into one unified list, using UNION specifically to avoid double-counting the same customer.

14. What is a stored procedure and why would a Data Analyst use one?

CREATE PROCEDURE GetMonthlySales (@Month INT)
AS
BEGIN
  SELECT region, SUM(order_amount) AS total_sales
  FROM orders
  WHERE MONTH(order_date) = @Month
  GROUP BY region;
END;

Explanation: A stored procedure is a saved, reusable block of SQL code that can accept parameters — here, calling EXEC GetMonthlySales 7 returns July's regional sales without rewriting the query each time.

Real Business Use Case: Automating a recurring report that different stakeholders request monthly, reducing manual query-writing.

15. Write a query to find the second-highest salary in a table.

SELECT MAX(salary) AS second_highest_salary
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

Explanation: The subquery finds the overall highest salary, and the outer query finds the highest value that's still below it — one of the most classic SQL interview questions across all data roles.

Real Business Use Case: A stand-in for any "find the Nth highest/lowest value" business question, such as identifying the second-best-performing product.

More SQL questions to be ready for:

🗄️ SQL is the single most important skill in this entire guide. Practice for free on SQLabHub.com, or get a fully structured SQL curriculum with real interview-style practice inside the DataVix Data Analyst course.

Power BI Interview Questions

Power BI interviews test both technical DAX/modeling knowledge and your ability to explain design decisions — expect both types of questions, often mixed together.

1. What is DAX?

Answer: DAX (Data Analysis Expressions) is the formula language used in Power BI to create calculated columns, measures, and custom calculations across your data model — similar in spirit to Excel formulas, but built for relational, multi-table data.

2. What's the difference between a Calculated Column and a Measure?

Example: A calculated column Profit = Sales[Revenue] - Sales[Cost] is computed row-by-row and stored in the table. A measure Total Profit = SUM(Sales[Revenue]) - SUM(Sales[Cost]) is calculated dynamically based on the current filter context (e.g., whichever region/date range is selected on the report).

Why it matters: Measures are generally preferred for aggregations because they respond to filters and don't bloat the data model's size the way calculated columns can.

3. What does CALCULATE do, and why is it considered Power BI's most important function?

Example: Total Sales 2025 = CALCULATE(SUM(Sales[Amount]), Sales[Year] = 2025) overrides the normal filter context to force the calculation to only consider rows from 2025, regardless of what's selected elsewhere on the report.

Why it matters: CALCULATE is the only DAX function that can modify filter context directly, making it the foundation for almost every advanced DAX pattern (time intelligence, ranking, comparisons).

4. What does the FILTER function do?

Example: High Value Sales = CALCULATE(SUM(Sales[Amount]), FILTER(Sales, Sales[Amount] > 10000)) sums only the rows where the sale amount exceeds ₹10,000.

Why it matters: FILTER builds a custom table of rows matching a condition, often used inside CALCULATE for logic too complex for a simple filter argument.

5. What is a star schema, and why is it preferred in Power BI?

Answer: A star schema has one central fact table (e.g., Sales) connected to multiple dimension tables (e.g., Customers, Products, Dates) via relationships, forming a star shape. It's preferred because it simplifies relationships, improves query performance, and makes DAX calculations more predictable compared to a highly normalized (snowflake) or flat, single-table structure.

6. How do relationships work in Power BI (1:many, many:many)?

Answer: A one-to-many relationship (most common) means one row in a dimension table (like Products) can relate to many rows in a fact table (like Sales). Many-to-many relationships are possible but should be used carefully, since they can create ambiguous filter paths and unexpected results if not modeled deliberately.

7. What are time intelligence functions, and can you give an example?

Example: YTD Sales = TOTALYTD(SUM(Sales[Amount]), 'Date'[Date]) calculates a running year-to-date total based on the report's active date filter.

Why it matters: Time intelligence functions (TOTALYTD, SAMEPERIODLASTYEAR, DATEADD) are used constantly in business dashboards for trend and period-over-period comparisons — expect at least one question on this.

8. What is Power Query, and how is it different from DAX?

Answer: Power Query is used before data enters the model — for cleaning, transforming, and shaping raw data (merging tables, splitting columns, removing errors). DAX operates after the data is loaded, for calculations and aggregations within the model. A common way to explain it: Power Query answers "how do I get and clean the data," DAX answers "how do I calculate something from the data I already have."

9. What is Row-Level Security (RLS) in Power BI?

Answer: RLS restricts what data different users can see within the same report based on their role — for example, a regional manager only sees their own region's data, even though everyone is viewing the same published dashboard. It's set up using DAX filter expressions applied to specific roles.

10. What is incremental refresh, and why does it matter?

Answer: Incremental refresh configures a dataset to only reload new or changed data (e.g., the last 30 days) instead of the entire history every time, dramatically improving refresh speed and reducing load on the source system for large datasets.

11. What's the difference between Slicers and Filters in Power BI?

Answer: Slicers are visual, on-report filter controls that end users interact with directly (dropdowns, buttons, date ranges). Filters (in the Filters pane) can be applied at the visual, page, or report level and are typically set up by the report builder rather than the end user, though both ultimately restrict what data is shown.

12. How would you optimize a slow Power BI dashboard?

Answer: Common techniques include reducing the number of visuals per page, replacing calculated columns with measures where possible, using a proper star schema instead of a flat table, limiting high-cardinality columns, applying incremental refresh for large datasets, and disabling unnecessary interactions between visuals.

More Power BI questions to be ready for:

📈 Building real dashboards — not just watching tutorials — is what actually prepares you for these questions. The DataVix course includes hands-on Power BI projects reviewed by mentors, so you walk into interviews with something real to explain.

Statistics Interview Questions for Data Analysts

Statistics questions for Data Analyst roles are usually kept practical — you're expected to understand and apply concepts, not derive formulas from scratch.

A common follow-up across all of these: "Explain [concept] to me like I'm not technical." Practice this specifically — the ability to translate statistics into plain language is tested as often as the statistics themselves.

Scenario-Based Data Analyst Interview Questions

Scenario questions test structured thinking more than a single "correct" answer. Interviewers are grading your process — how you break down an ambiguous problem — not whether you guess the exact right cause on the first try.

1. "Sales dropped suddenly last month. What would you analyze?"

Thought Process: Start by confirming the drop is real (not a data or reporting error), then segment it — by region, product, channel, and customer type — to isolate where the drop is concentrated rather than assuming a single company-wide cause.

Structured Answer: "First, I'd verify the numbers against the source system to rule out a tracking issue. Then I'd break the drop down by region, product category, and sales channel to see if it's broad or concentrated. I'd also check for external factors — a pricing change, a stockout, a marketing budget cut, or a seasonal pattern from the prior year."

Business Explanation: Jumping to a single explanation without segmenting first is the most common failure mode — the real cause is often isolated to one segment, not the whole business.

2. "Customer churn increased. What would you investigate?"

Thought Process: Define churn clearly first (what counts as "churned"?), then look at cohort-level patterns — are newer or older customers churning more, and did anything change around the time churn started rising?

Structured Answer: "I'd start by confirming how churn is defined and measured, then segment churned customers by signup cohort, plan type, and usage level before they left. I'd also check for a correlated change — a price increase, a product change, or a support/quality issue — around the same time churn started rising."

Business Explanation: Churn is rarely one cause — showing you'd separate "who is churning" from "why" demonstrates structured, not surface-level, thinking.

3. "The dashboard numbers don't match the source data. What do you do?"

Thought Process: Treat this as a debugging problem — trace the data from source to dashboard step by step rather than guessing.

Structured Answer: "I'd first check if it's a filter or date-range mismatch, since that's the most common cause. Then I'd check the underlying query or data model for a join issue (like a many-to-many relationship inflating counts) or a refresh that hasn't run recently. I'd document the root cause once found so it doesn't reoccur."

Business Explanation: This tests calm, methodical debugging — panicking or immediately blaming the data source without checking your own report first is a red flag to interviewers.

4. "A marketing campaign's ROI declined. How would you investigate?"

Thought Process: Break ROI into its components (cost and return) and check both sides separately before assuming the campaign itself failed.

Structured Answer: "I'd separate the cost side (did ad spend or CPC increase?) from the return side (did conversion rate or average order value drop?). I'd also check for channel mix changes and whether the decline is company-wide or specific to one campaign or audience segment."

Business Explanation: Interviewers want to see you decompose a vague metric like "ROI" into its measurable drivers instead of treating it as one opaque number.

5. "A stakeholder asks for a metric that doesn't exist in your current data. What do you do?"

Thought Process: Clarify the underlying business question first — sometimes an existing metric already answers it, just phrased differently.

Structured Answer: "I'd ask what decision this metric is meant to support, since that often reveals an existing metric that already answers the real question. If it genuinely doesn't exist, I'd scope what new data collection or tracking would be needed, and give a realistic timeline instead of promising an instant answer."

Business Explanation: Shows you manage stakeholder expectations honestly rather than overpromising or building something that doesn't actually solve their problem.

6. "You find an error in a report after it's already been sent to leadership. What do you do?"

Thought Process: Prioritize speed and transparency over trying to quietly fix it unnoticed.

Structured Answer: "I'd flag it immediately to whoever sent it, explain the specific error and its impact on the conclusions, and send a corrected version as fast as possible. I'd also do a quick root-cause check to prevent the same mistake in future reports."

Business Explanation: Interviewers are testing integrity and ownership here more than technical skill — hiding or downplaying an error is treated as a serious red flag.

7. "Two departments report different numbers for the same metric. How do you resolve it?"

Thought Process: Assume different definitions or data sources before assuming either team made an error.

Structured Answer: "I'd compare how each team defines and calculates the metric — different date ranges, filters, or source systems are the most common cause of this. Once I identify the discrepancy, I'd propose a single agreed-upon definition and source of truth going forward."

Business Explanation: This tests whether you understand that "wrong numbers" are often actually "differently defined numbers" — a very common real-world analyst problem.

8. "A dashboard is loading too slowly for users. What would you check?"

Thought Process: Separate potential causes into data volume, model design, and visual complexity.

Structured Answer: "I'd check the data model first — whether it's using a proper star schema, whether calculated columns could be replaced with measures, and whether the dataset is larger than it needs to be. I'd also check the number of visuals on a single page and whether incremental refresh or aggregation tables could help."

Business Explanation: Shows practical, hands-on BI tool knowledge beyond just building dashboards — you also know how to fix them.

9. "You're handed a dataset with no context. Where do you start?"

Thought Process: Understand the data before analyzing it — structure, source, and business meaning of each field.

Structured Answer: "I'd start with exploratory analysis — checking column names, data types, ranges, and missing values — then ask whoever provided it what business process generated the data and what question they're actually trying to answer, since that shapes the entire analysis approach."

Business Explanation: Tests discipline against jumping straight into charts without first understanding what the data actually represents.

10. "Leadership wants an answer today, but a proper analysis would take a week. What do you do?"

Thought Process: Communicate a fast, clearly-labeled preliminary answer while being explicit about its limitations.

Structured Answer: "I'd deliver a quick, directional answer today based on the most relevant available data, clearly labeled as preliminary, along with a timeline for the fuller analysis. I wouldn't present a rushed number with false confidence, since a wrong quick answer is worse than an honest, caveated one."

Business Explanation: Tests whether you can balance business urgency with analytical honesty — a genuinely senior-level judgment call.

More scenarios worth practicing out loud:

🎯 Scenario questions are won through practice, not memorization. Talk through these out loud with a friend or mentor before your interview — DataVix mentors run mock interview sessions specifically for this.

Real-World Case Study Questions

Case studies go one level deeper than scenario questions — they usually involve a specific industry context and expect you to outline a fuller analysis approach, sometimes with a follow-up SQL or Excel task attached.

E-commerce: "Cart abandonment rate has risen to 70% over the last quarter. Walk me through your analysis." A strong approach: segment abandonment by device type, payment method, and funnel step to find where users actually drop off; check for a correlated change (a checkout redesign, a new payment gateway, added shipping costs); and quantify the revenue impact to prioritize the fix.

Finance: "The bank wants to reduce loan default rates. How would you use data to help?" A strong approach: analyze historical defaults against applicant attributes (income, credit history, loan amount, tenure) to identify the strongest risk indicators, check for any recent shift in the applicant pool's risk profile, and propose a scorecard or threshold the credit team could use going forward.

Healthcare: "Patient readmission rates within 30 days have increased. What would you look at?" A strong approach: segment readmissions by diagnosis, department, and discharge process, check whether specific conditions or a specific care team correlate with higher readmission, and cross-reference with any recent policy or staffing changes.

Retail: "A retailer wants better demand forecasting to reduce stockouts and overstock. How would you approach it?" A strong approach: analyze historical sales patterns by SKU and location, account for seasonality and promotions, compare current forecast accuracy against actuals to quantify the gap, and recommend a more granular (store-level, not just company-level) forecasting approach if the data supports it.

SaaS: "Monthly Recurring Revenue (MRR) growth has slowed despite steady new signups. What's your analysis?" A strong approach: break MRR growth into its components — new MRR, expansion MRR, and churned MRR — since slowing growth despite steady acquisition usually points to rising churn or shrinking expansion revenue, not a signup problem at all.

🏢 Case studies reward practical project experience. Build at least one industry-specific project (retail, SaaS, or finance) and be ready to walk through it — the Data Analyst Roadmap lists exactly which project types recruiters respond to best.

Power BI Project Interview Questions

Once you mention a Power BI project on your resume or portfolio, expect these follow-ups — they test depth, not just that the dashboard exists.

• "Explain your dashboard." Walk through the business question it answers, the KPIs shown, and how a user would actually use it — not just a visual description of the charts.
• "Why did you choose these specific KPIs?" Be ready to justify each metric's relevance to the business question, not just that it was "interesting to visualize."
• "What challenges did you face building this?" Have a real, specific answer — a data quality issue, a modeling decision, or a stakeholder requirement change — not a generic "none, it was smooth."
• "How did you optimize performance?" Reference specific techniques: measures over calculated columns, star schema, reduced visual count, or incremental refresh.
• "How did you structure your data model?" Be able to describe the relationships between your tables and why you modeled them that way (star schema logic).
• "How did you handle changing requirements mid-project?" Show adaptability — describe a specific change and how you adjusted the model or visuals without starting over.
• "How did you validate that your numbers were accurate?" Mention cross-checking against the source data or a second calculation method — shows rigor, not blind trust in the tool.
• "Did your dashboard handle any sensitive data securely?" Even for portfolio projects, mention awareness of RLS or data anonymization concepts.
• "How did stakeholders actually use this dashboard?" If it's a real project, describe the decision it informed; if it's a portfolio project, describe the intended use case realistically.
• "What would you improve if you rebuilt it today?" Always have an honest answer — it signals self-awareness and continuous improvement, both valued traits.

Data Analyst HR Interview Questions

HR rounds test communication and cultural fit, not technical skill — but a weak HR round can still cost you an otherwise-strong technical performance.

1. "Tell me about yourself."

Strong Sample Answer: "I have a background in [your degree/field], and over the past [timeframe] I've built strong skills in SQL, Excel, and Power BI through structured coursework and real projects — including [one specific project]. I'm particularly drawn to roles where I can turn messy data into clear business recommendations, which is exactly what excites me about this position."

2. "Why Data Analytics as a career?"

Strong Sample Answer: "I enjoy the mix of logical problem-solving and real business impact — I like that a well-structured SQL query or dashboard can directly change a decision someone makes. It's also a field where the demand for genuinely skilled people keeps growing, which matters to me for long-term career stability."

3. "Why should we hire you?"

Strong Sample Answer: "Beyond the core SQL, Excel, and Power BI skills the role needs, I bring [a specific differentiator — a relevant project, industry knowledge, or communication strength] and a genuine habit of double-checking my own numbers before presenting them, which I think matters a lot in this kind of role."

4. "What are your strengths?"

Strong Sample Answer: "I'm detail-oriented with data — I catch inconsistencies before they become a bigger issue — and I'm comfortable explaining technical findings to non-technical stakeholders in plain language, which I think is just as important as the technical analysis itself."

5. "What are your weaknesses?"

Strong Sample Answer: "Earlier on, I sometimes spent too long polishing a dashboard's visual design before sharing an initial version for feedback. I've since gotten better at sharing rougher drafts earlier to get direction faster, which has made my actual work more efficient." (Pick a real, specific weakness with a concrete improvement — avoid clichés like "I'm a perfectionist.")

6. "Where do you see yourself in 5 years?"

Strong Sample Answer: "I'd like to grow from hands-on analysis into owning a full reporting area or leading a small analytics function, while continuing to deepen my technical skills — this role feels like a strong foundation for that path."

7. "Why do you want to leave your current job / What's this employment gap about?"

Strong Sample Answer: "I'm looking for a role with more hands-on data work and growth opportunity than my current position offers." (For a gap: be honest and brief — "I used this time to build my SQL, Excel, and Power BI skills through structured learning and real projects," pointing to your portfolio as proof.)

8. "Describe a time you handled a tight deadline."

Strong Sample Answer: Use the STAR method (Situation, Task, Action, Result): briefly set up the situation, explain what you specifically did to prioritize and deliver, and end with the outcome — even for a coursework or portfolio project if you lack formal work experience.

9. "Describe a conflict with a team member or stakeholder and how you resolved it."

Strong Sample Answer: Pick a real (even minor) example — a disagreement over which metric mattered most, or a request you had to push back on — and focus on how you communicated and reached a resolution, not on assigning blame.

10. "Do you have any questions for us?"

Strong Sample Answer: Always have 2-3 ready: "What does success look like in this role in the first 90 days?", "What tools and data sources would I be working with day-to-day?", or "What's the biggest data challenge the team is currently facing?" — asking nothing signals low genuine interest.

More HR questions to prepare for:

💬 HR rounds are won with preparation, not charisma alone. Practice these out loud at least once before your interview — even reading them silently isn't enough to build real fluency.

Data Analyst Interview Questions for Freshers

If you have no formal work experience, interviewers adjust their expectations — but they also probe your portfolio and fundamentals more deeply to compensate for the lack of a work history to evaluate.

For candidates with no experience: Expect more time spent on your portfolio projects than a typical experienced-hire interview. Be ready to explain every decision in your project — why you chose that dataset, why you used a particular SQL approach, why you visualized it that way. A vague or memorized explanation is the fastest way to lose credibility here.

For college students: Interviewers understand you may not have used Power BI or SQL in a professional setting — focus on demonstrating you learned it properly through structured coursework and applied it to a real (even if self-initiated) project, not just watched tutorials.

For career switchers: Be ready for a version of "why the switch?" and answer it confidently and specifically — connect your prior experience to transferable skills (business context, domain knowledge, communication) rather than treating your previous career as irrelevant. A career switcher with strong domain knowledge (finance, healthcare, retail) combined with solid SQL/Excel/Power BI skills is often a stronger candidate than a pure fresher, not a weaker one — say so if it's true for you.

What freshers get asked more of: basic SQL (joins, GROUP BY), Excel fundamentals, and a detailed project walkthrough. What freshers get asked less of: advanced window functions, DAX depth, and stakeholder-management scenarios — though it's still worth being able to speak to these at a basic level.

🎓 Starting from zero? The Data Analyst Roadmap 2026 is built exactly for this — a step-by-step path from no experience to interview-ready, and the Data Analyst Salary in India guide shows realistic fresher offers by background and city.

Data Analyst Interview Questions for Experienced Professionals

With 2+ years of experience, interviews shift from "can you do the basics" to "can you own outcomes and navigate ambiguity."

Stakeholder management: "How do you handle conflicting requirements from two different stakeholders?" A strong answer describes clarifying the underlying business goal behind each request, finding common ground or a prioritization framework, and communicating trade-offs transparently rather than trying to please everyone.

Dashboard optimization: "Tell me about a time you improved a slow or poorly-adopted dashboard." Expect this to test both technical optimization (data model, DAX efficiency) and design judgment (why users weren't engaging with it in the first place).

Data governance: "How do you ensure the reports you build are accurate and consistent over time?" A strong answer covers documentation practices, a single source of truth for key metric definitions, and validation habits (cross-checking numbers against source systems).

Business impact: "Describe a time your analysis directly influenced a business decision." This is the single most important question for experienced candidates — have a specific, quantified example ready (e.g., "this analysis led to a change that improved X by Y%"), not just a description of the analysis itself.

Experienced candidates are also expected to speak to mentoring or reviewing junior team members' work, prioritizing across multiple concurrent requests, and pushing back constructively when a stakeholder's ask isn't the right analytical approach.

Company-Specific Data Analyst Interview Questions

Every company runs a slightly different process — here's what to expect at some of the most common hirers of Data Analysts in India.

Accenture — Aptitude test, followed by a technical round covering SQL and Excel with an embedded business case study, then an HR round focused on client-facing communication (since most analyst work here is on client projects). Sample questions: "Write a query to find top-performing clients," "How would you present a data-quality issue to a client without alarming them?"

Deloitte — Case-study-heavy process reflecting its consulting culture; expect a structured business problem alongside SQL/Excel fundamentals. Sample questions: "A client's revenue is declining — how would you investigate?", "Walk me through how you'd structure a data-quality audit."

EY — Similar to Deloitte, with strong emphasis on business reasoning and risk/audit-adjacent scenarios alongside technical basics. Sample questions: "How would you detect anomalies in a financial dataset?", "Explain a time you had to simplify a complex finding for a non-technical audience."

KPMG — Strong BFSI (banking, financial services) and risk-analytics focus; expect scenario questions tied to compliance or financial reporting alongside SQL/Excel. Sample questions: "How would you flag unusual transaction patterns?", "What's your approach to validating third-party data?"

Infosys — Aptitude round (often via Infosys's own assessment), then a technical interview covering SQL joins/aggregations, Excel, and sometimes a basic Python question, followed by HR. Sample questions: "Write a query using GROUP BY and HAVING," "What's the difference between VLOOKUP and INDEX-MATCH?"

TCS — TCS NQT (aptitude test), then a technical round testing SQL fundamentals, Excel, and basic statistics, followed by a separate HR round — generally foundational rather than advanced for entry-level hiring. Sample questions: "Explain JOIN types with an example," "What is a Pivot Table used for?"

Wipro — Aptitude and technical rounds similar to TCS/Infosys, with an increasing focus on Power BI/Tableau given Wipro's growing BI project work. Sample questions: "Explain the difference between a measure and a calculated column," "Write a query to find duplicate records."

Cognizant — Technical round covering SQL, Excel, and often a light case-study component, given Cognizant's strong healthcare and BFSI client base. Sample questions: "How would you analyze patient/claims data for anomalies?", "Explain window functions with an example."

Capgemini — Aptitude and technical rounds with a case-study element similar to Accenture, reflecting its consulting-plus-delivery model. Sample questions: "Walk me through how you'd approach an unfamiliar client dataset," "Write a SQL query to calculate month-over-month growth."

What's consistent across all of them: every company tests SQL fundamentals and Excel basics in some form, and every company's HR round tests communication over technical depth — the differentiator is how much of the process leans toward case-study/business reasoning (Big 4 and consulting) versus straightforward technical testing (product-adjacent IT services roles).

🏆 Research the specific company's industry focus before your interview — a BFSI-heavy firm like KPMG expects different scenario framing than an e-commerce-adjacent product company. The Data Analyst Roadmap covers how to tailor your portfolio toward a target industry.

Common Data Analyst Interview Mistakes to Avoid

Poor communication. Many technically strong candidates fail interviews because they can't explain their reasoning clearly to a non-technical interviewer — practice explaining your SQL queries and dashboard decisions in plain English, out loud, not just in your head.

Weak or generic projects. A project built from a pre-cleaned Kaggle dataset with no real business question behind it is instantly recognizable to experienced interviewers and rarely survives a follow-up question. Build projects around a specific, real business question instead.

Memorizing answers instead of understanding concepts. Memorized answers fall apart the moment an interviewer asks a natural follow-up or slightly rephrases the question — understanding the underlying logic well enough to adapt it is what actually holds up under pressure.

Lack of real SQL practice. Watching SQL tutorials without writing queries yourself is the single most common gap between candidates who feel prepared and candidates who actually perform well live. Practice typing real queries against real (or realistic) data regularly, not just reading syntax.

Lack of business understanding. Candidates who can write correct SQL but can't explain why a business would care about the result struggle in case-study and scenario rounds — always connect a technical answer back to the business impact.

30-Day Data Analyst Interview Preparation Plan

Use this as a realistic, day-by-day structure if you have roughly one month before your interview and can dedicate 2-3 hours a day.

Week 1 — Excel and SQL Fundamentals

• Days 1-2: Review core Excel functions — VLOOKUP, XLOOKUP, INDEX-MATCH, SUMIFS, COUNTIFS.
• Days 3-4: Practice Pivot Tables, conditional formatting, and data validation on a real dataset.
• Days 5-6: SQL basics — SELECT, WHERE, GROUP BY, HAVING, ORDER BY, CASE WHEN.
• Day 7: Review the week — redo 5 Excel and 5 SQL questions from this guide from memory.

Week 2 — Advanced SQL and Power BI

• Days 8-9: SQL joins — INNER, LEFT, self-joins — with real practice queries.
• Days 10-11: Window functions — ROW_NUMBER, RANK, DENSE_RANK, running totals.
• Days 12-13: Power BI fundamentals — data modeling, star schema, basic DAX (CALCULATE, FILTER).
• Day 14: Build or update one Power BI dashboard from a real dataset end-to-end.

Week 3 — Statistics, Scenarios, and Portfolio

• Days 15-16: Review core statistics concepts — mean/median/mode, standard deviation, correlation.
• Days 17-18: Practice 10 scenario-based questions out loud, using the structured-answer format from this guide.
• Days 19-20: Polish your portfolio — ensure each project has a clear business question and written recommendation.
• Day 21: Update your resume with specific, quantified project outcomes.

Week 4 — Mock Interviews, HR, and Company Research

• Days 22-23: Do 2-3 full mock interviews (technical + HR) with a friend, mentor, or recording yourself.
• Days 24-25: Prepare your HR answers — "Tell me about yourself," strengths/weaknesses, salary expectations.
• Days 26-27: Research your target company's industry and recent projects; tailor your scenario answers accordingly.
• Days 28-29: Redo your weakest topic area from Weeks 1-3 based on mock interview feedback.
• Day 30: Light review only — re-read your project talking points and get rest before the interview.

📅 Want this exact plan with structured lessons, real projects, and mentor-led mock interviews instead of self-guided prep? See the full DataVix curriculum — it's built around this same sequence.

Free Data Analyst Interview Preparation Checklist

Use this checklist in the final week before your interview.

Technical Readiness

• ✅ Comfortable writing SQL joins, GROUP BY, and window functions from scratch
• ✅ Can explain VLOOKUP vs. XLOOKUP vs. INDEX-MATCH without hesitation
• ✅ Built at least one real Power BI/Tableau dashboard with DAX measures
• ✅ Can explain mean, median, correlation, and hypothesis testing in plain English

Portfolio Readiness

• ✅ At least 3 projects using real, messy datasets — not pre-cleaned CSVs
• ✅ Each project has a clear business question and a written recommendation
• ✅ Can explain every technical decision in each project confidently
• ✅ Portfolio is easy to access (GitHub, portfolio site, or shareable PDF)

Communication Readiness

• ✅ Practiced explaining a technical finding to a "non-technical stakeholder"
• ✅ Prepared structured answers for at least 10 scenario-based questions
• ✅ Rehearsed "Tell me about yourself" and strengths/weaknesses out loud
• ✅ Have 2-3 thoughtful questions ready to ask the interviewer

Logistics Readiness

• ✅ Resume updated with specific, quantified project outcomes
• ✅ Researched the target company's industry and recent data-related news
• ✅ Reviewed the company-specific process notes for your target employer
• ✅ Rested and prepared — no cramming the night before

Want to Ace Your Data Analyst Interview?

Reading 100+ questions is a strong start, but real interview confidence comes from doing, not just reading. Here's the fastest path to being genuinely ready:

• Excel — Master VLOOKUP/XLOOKUP, Pivot Tables, and SUMIFS/COUNTIFS through hands-on practice, not just reading formulas.
• SQL — Write real queries daily, covering joins, GROUP BY, and window functions until they're second nature.
• Power BI — Build a full dashboard from a real dataset, including DAX measures and a proper data model.
• Projects — Build 3-4 portfolio projects, each answering a specific business question with a written recommendation.
• Interview Preparation — Practice scenario-based and HR questions out loud, not silently in your head.

This is exactly the sequence taught inside the DataVix Data Analyst course — Excel, SQL, Power BI, and Python, built around real projects and reviewed by mentors, with dedicated interview preparation and mock interviews included.

🚀 Ready to stop guessing and start preparing with a real structure? Enroll in the DataVix Data Analyst course — one-time fee, lifetime access, real project reviews, mentor support, and placement guidance. Or start with the free Data Analyst Roadmap and Salary Guide to plan your path first.

Frequently Asked Questions

How many interview rounds are there for a Data Analyst job? Most companies run 3-5 rounds: resume/aptitude screening, a technical round, sometimes a case study, a managerial round, and a final HR round.

Is SQL mandatory for a Data Analyst interview? Yes, in almost every case — SQL is the most consistently tested skill across Data Analyst interviews in India.

Can I become a Data Analyst without coding? Yes. SQL is a query language, not traditional programming, and most beginners become comfortable with it within a few weeks without any prior coding background.

What questions are asked in Power BI interviews? DAX (CALCULATE, FILTER, time intelligence), calculated columns vs. measures, data modeling (star schema), Power Query, and a walkthrough of your own dashboard project.

How do I prepare for a Data Analyst interview in 30 days? Follow a phased plan: Week 1 Excel/SQL basics, Week 2 advanced SQL/Power BI, Week 3 statistics/scenarios/portfolio, Week 4 mock interviews and HR prep — the full day-by-day plan is above.

What is the salary after getting hired as a Data Analyst? Fresher salaries typically range ₹4-7 LPA, rising to ₹16-28+ LPA at senior levels — see the complete Data Analyst Salary in India guide.

Are Data Analyst interview questions and answers available as a PDF? This guide works as your complete reference and can be saved as a PDF directly from your browser to study offline.

What are the most common Excel questions asked in interviews? VLOOKUP vs. XLOOKUP, INDEX-MATCH, SUMIFS/COUNTIFS, Pivot Tables, conditional formatting, and Power Query.

What SQL topics should I focus on the most before an interview? Joins, GROUP BY with aggregates, window functions, CTEs, and subqueries cover roughly 80% of real interview questions.

How difficult are Data Analyst interviews for freshers? Moderately difficult but learnable — they test fundamentals and your ability to explain your portfolio, not years of experience.

What is asked in a Data Analyst HR interview round? "Tell me about yourself," "Why Data Analytics," strengths/weaknesses, salary expectations, and behavioral questions about deadlines or conflict.

How do I answer scenario-based Data Analyst interview questions? Use a structured process: clarify the business question, outline your analysis steps, and end with how you'd communicate the finding.

Do I need a portfolio to get a Data Analyst job? Yes, strongly recommended — a portfolio of 3-4 real projects is often probed more deeply than your resume itself.

What is the aptitude round in a Data Analyst interview? An online logical/quantitative reasoning test, common at IT services companies like TCS and Infosys, used to filter high-volume applicant pools.

How long does a typical Data Analyst interview process take? Most processes take 2-4 weeks, though Big Tech and top product companies can take 4-6 weeks with additional rounds.

What is the most asked SQL interview question for Data Analysts? Variations of "find the second-highest value" and "use a window function to rank records within a group" are the most consistent.

Is a certification required to clear a Data Analyst interview? No — certifications help a resume pass screening but rarely influence the actual interview outcome compared to a strong portfolio.

What is asked in an Accenture Data Analyst interview? An aptitude test, a technical round with SQL/Excel and a business case study, and an HR round focused on client communication.

What is asked in a TCS Data Analyst interview? TCS NQT aptitude test, a technical round on SQL fundamentals, Excel, and basic statistics, followed by an HR round.

What is asked in an Infosys Data Analyst interview? An aptitude round, a technical interview on SQL joins/aggregations and Excel, sometimes basic Python, followed by HR.

What is asked in a Deloitte Data Analyst interview? A case-study-heavy process alongside standard SQL/Excel questions, reflecting Deloitte's consulting-first culture.

How do I explain a project in a Data Analyst interview? Structure it as: the business question, your data/tools, your analysis steps, the key insight, and the measurable impact.

What mistakes should I avoid in a Data Analyst interview? Memorizing answers, weak/generic projects, skipping real SQL practice, poor communication, and lack of business understanding.

Can a fresher clear a Power BI interview round? Yes, if they can build and confidently explain at least one real end-to-end dashboard, including their KPI and modeling choices.

What statistics knowledge is needed for a Data Analyst interview? Descriptive statistics, correlation vs. causation, basic hypothesis testing, and sampling bias — deep statistical theory is rarely required.

How do I answer "Tell me about yourself" as a Data Analyst? Structure it in three parts: your background, your relevant skills/projects, and why you're excited about this specific role — under 90 seconds.

What is the difference between technical and HR rounds? Technical rounds test whether you can do the job (SQL, Excel, Power BI); HR rounds test communication and cultural fit.

Should I memorize answers before a Data Analyst interview? No — memorized answers fall apart under natural follow-up questions; understand the concept well enough to explain it in your own words.

What is a case study round in a Data Analyst interview? A realistic business problem you're asked to investigate, testing structured thinking and business judgment over a single correct answer.

How many SQL questions are typically asked in one interview? Most technical rounds include 2-4 SQL questions of increasing difficulty, often solved live on a shared screen or coding platform.

What is the best way to practice SQL before an interview? Practice on real, messy-feeling datasets — SQLabHub.com offers free hands-on query practice for exactly this.

What should I do if I don't know the answer to a question in an interview? Say so honestly, then reason through it out loud with what you do know — structured honesty consistently outperforms a confident guess.

📚 Keep preparing with the rest of the DataVix guide library — the Data Analyst Roadmap, the Salary Guide, and Data Analyst vs Data Scientist — or enroll in the DataVix course to prepare with mentor support from day one.