How to Solve Tabular Data Interpretation Problems
Solve tabular data interpretation problems — header scanning, existing totals, correct denominators — with a worked example and practice questions.
Expected Interview Answer
A tabular data interpretation problem is solved by first scanning row and column headers to understand what each cell represents, then extracting only the specific cells the question needs rather than reading the whole table linearly.
Tables pack more precision than graphs since every cell is an exact number, so the risk shifts from misreading a trend to misreading which row or column a value belongs to. Row-wise and column-wise totals are common traps — always check whether a “Total” row/column already exists before recomputing it yourself. Ratio and percentage-of-total questions require picking the correct denominator: percentage of a category within a row differs from percentage within the whole table. When two tables are given together, the real question usually tests linking a value from one table to a related value in the other, so identify the shared key (a company name, a year) before cross-referencing.
- Precise cell values remove trend-reading ambiguity that graphs introduce
- Recognizing existing totals avoids redundant, error-prone recomputation
- Correct denominator choice prevents the most common tabular DI mistake
AI Mentor Explanation
A scorecard table lists each batter’s runs, balls faced, and strike rate in separate columns, so misreading which column is strike rate versus runs is the classic scorecard-reading error. If asked for a batter’s contribution to the team total, you divide their runs by the team’s total runs — using the team total already printed at the bottom, not resumming every batter’s score yourself. Comparing two matches’ scorecards side by side means matching the same batter’s row across both tables using their name as the shared key.
Worked example
Marketing spend
- 25
Total spend (given row)
- 100
Percentage share
- 25/100 × 100
- = 25%
Step-by-Step Explanation
Step 1
Scan headers first
Identify what every row and column represents before reading any cell value.
Step 2
Locate the target cells
Extract only the specific cells the question needs, not the whole table.
Step 3
Check for existing totals
Use a printed Total row/column instead of resumming manually.
Step 4
Pick the correct denominator
Percentage-of-row differs from percentage-of-whole-table — match the question wording exactly.
What Interviewer Expects
- Correct identification of row vs column meaning before extracting values
- Use of existing total rows/columns instead of error-prone resummation
- Correct denominator choice for percentage and ratio questions
- Accurate cross-referencing between two related tables using a shared key
Common Mistakes
- Reading a value from the wrong row or column due to fast scanning
- Recomputing a total that was already given, introducing arithmetic errors
- Using the whole-table total as denominator when the question asked for a row-wise percentage
- Failing to match the correct shared key when cross-referencing two tables
Best Answer (HR Friendly)
“With tables I first scan the headers to understand what each row and column means, then I only pull the specific cells the question is asking about. I always check if there is already a total row or column before recalculating anything myself, since that is faster and avoids arithmetic slips. For percentage questions I am careful to pick the denominator the question actually specifies — row total versus grand total makes a big difference.”
Follow-up Questions
- How do you handle a table with merged or multi-level headers?
- What is the fastest way to find the second-highest value in a table column?
- How would you interpolate a missing cell value using the table's known totals?
- How do you approach a question spanning two related tables?
MCQ Practice
1. A table shows Region A sales = 60, Region B = 90, Total = 150. Region A's percentage share of total is?
60/150 × 100 = 40%.
2. A table has a printed "Total" row. What is the fastest way to verify a percentage-of-total question?
The printed total row is already correct and faster than recomputing.
3. Two tables share a "Year" column. To compare a value across both tables, you should?
Cross-referencing requires matching on the shared key, not assumed row order.
Flash Cards
First step reading a table for DI? — Scan row and column headers before extracting any cell value.
Why check for an existing Total row? — It avoids error-prone manual resummation.
Key trap in percentage-of-table questions? — Choosing the wrong denominator — row total vs grand total.
How to link two related tables? — Match rows using a shared key such as name or year.