One Call Data Analyst Interview: Questions, Experience & Prep (2026)

One Call currently has 13 open Data Analyst roles, making it one of the more active hirers in this space right now. Candidates report that the interview process typically spans 2 to 4 rounds, covering SQL and analytics fundamentals, a business or data problem, and a final discussion with a manager or stakeholder. The role blends data wrangling with clear storytelling, so both technical skill and communication carry equal weight.

Salary bands for Data Analysts in India (based on knok jobradar data, July 2026):

With 319 Data Analyst openings tracked across India right now, there is real hiring momentum in this field. One Call's 13 open roles reflect active recruitment, so if you are targeting this company, now is a good time to apply.

These questions come up frequently in One Call Data Analyst interviews, based on what candidates report:

1. Walk me through a data project you owned end to end, from raw data to final recommendation.
2. Write a SQL query to find the top 5 customers by revenue in the last 30 days, and handle NULLs appropriately.
3. A dashboard you built is showing a sudden spike in a key metric. How do you investigate whether it is a real business event or a data issue?
4. How would you explain the difference between a LEFT JOIN and an INNER JOIN to a non-technical colleague?
5. Describe how you have used Excel, Python, or SQL to automate a repetitive reporting task.
6. A business team disagrees with the numbers in your report. How do you handle that situation?
7. What is the difference between a measure and a dimension in a BI tool like Power BI or Tableau?
8. How do you prioritise when you have three report requests from three different teams and a tight deadline?
9. Tell me about a time you found an insight in data that changed a business decision.
10. How would you design a data quality check for a pipeline that ingests customer transaction data daily?
11. What metrics would you track to measure the health of a customer support operation, and why?
12. Describe a situation where your analysis turned out to be wrong. What happened and what did you learn?

Q: Tell me about a time you found an insight in data that changed a business decision.

*Situation:* I was working on monthly sales reports for a retail client. The team assumed their top product category was performing well because total revenue looked fine.

*Task:* My job was to prepare a quarterly performance summary, but I noticed something unusual while cleaning the data.

*Action:* I broke revenue down by sub-category and layered in margin data. I found that one sub-category was generating high revenue but negative margin because of excessive discounting. I built a simple visual in Power BI and walked the sales head through it in a short meeting.

*Result:* The team revised their discounting policy for that sub-category. Candidates in similar roles report that showing a clear before-and-after impact in such situations tends to land well with interviewers.

---

Q: A dashboard you built is showing a sudden spike in a key metric. How do you investigate?

*Situation:* A weekly active users dashboard I maintained for an internal product team showed a sharp unexpected spike on a Tuesday with no campaign or product release scheduled.

*Task:* I needed to confirm whether this was real growth or a data pipeline issue before the leadership team acted on it.

*Action:* I checked the ETL logs first, then compared raw source data against what had landed in the warehouse. I also segmented the spike by region, device, and user type to see if it was isolated. The spike turned out to be a duplicate ingestion from a misconfigured job.

*Result:* I flagged it before anyone escalated, rolled back the duplicate records, and added a row-count validation step to the pipeline to catch this automatically going forward.

---

Q: Describe a situation where a business team disagreed with your numbers.

*Situation:* A marketing team insisted their campaign drove a large revenue lift, but my attribution model showed a much smaller number.

*Task:* I had to present my findings without dismissing their perspective or creating conflict.

*Action:* I scheduled a working session and walked them through my methodology step by step. I acknowledged the assumptions in my model, showed them where the difference came from (they were counting assisted conversions differently), and suggested we align on a single attribution definition going forward.

*Result:* We agreed on a shared definition, documented it, and both teams started reporting from the same source. Candidates report that showing collaborative problem-solving, rather than just defending your numbers, is something interviewers at companies like One Call respond well to.

The STAR method (Situation, Task, Action, Result) is your best structure for behavioural questions. Keep each component tight: one or two sentences on Situation and Task, three or four on Action (this is where your skill shows), and a concrete Result. If you do not have a number for the result, describe the outcome qualitatively.

For SQL and technical questions, think out loud. Interviewers typically care as much about how you approach a problem as whether you get the exact syntax right. State your assumptions, name the tables you would use, and walk through your logic before writing code.

For ambiguous business questions (such as 'what metrics would you track'), use a simple three-step structure: define the goal, break it into sub-goals, then pick one or two metrics per sub-goal and explain what a healthy value looks like versus an unhealthy one. This shows structured thinking, which data analysts are expected to apply across different business domains.

For disagreement or stakeholder questions, lead with curiosity, not defensiveness. Show that you verify your own work first, then invite the other party to walk through their numbers. Frame it as aligning on the truth together, not winning an argument.

Candidates who interview at One Call for Data Analyst roles typically report that the panel looks for a few things above all else.

SQL fluency at a practical level. You do not need to recite textbook theory. You need to write clean queries, handle edge cases like NULLs and duplicates, and explain your logic clearly. Window functions, CTEs, and aggregation are commonly tested areas.

Business curiosity. One Call interviewers reportedly ask why you chose a particular metric or approach. They want analysts who ask 'what decision will this data support?' before jumping into a spreadsheet. Linking your analysis to a business outcome in every answer goes a long way.

Clear communication. Data Analysts at One Call work closely with non-technical stakeholders. Interviewers look for candidates who can translate numbers into plain language. Avoid jargon in your answers, and when you do use a technical term, briefly explain it as if the listener is smart but not a data specialist.

Ownership mindset. Several candidates report that One Call values people who flag data issues proactively, follow up without being asked, and treat a broken report as their problem to fix rather than just to escalate.

Week 1: SQL and core analytics skills

Practise intermediate to advanced SQL: window functions (ROW_NUMBER, RANK, LAG), GROUP BY with HAVING, self-joins, and subqueries. Do at least one timed problem each day. Review how to handle NULLs, duplicates, and data type mismatches, as these come up frequently in technical rounds.

Week 2: Business problem-solving and BI tools

Pick two or three business domains such as e-commerce, customer support, or finance and practise building metric frameworks for each. If One Call's domain is healthcare or operations (candidates report this is common), look up the standard KPIs for that space. Refresh your Power BI or Tableau skills so you can speak confidently about how you have used them to answer real business questions.

Week 3: Behavioural stories and mock interviews

Write out four to six STAR stories covering: a complex analysis you led, a stakeholder disagreement you navigated, a data quality issue you caught, and a time you automated a repetitive task. Practise saying each one out loud in under three minutes. Do at least one mock interview with a peer or record yourself and replay it. Replace any vague language with specific actions and concrete outcomes.

On the day: Read the job description again the night before and map each key requirement to one of your STAR stories. Log in or arrive a few minutes early. Ask one or two thoughtful questions at the end, such as what the team measures success by or what the biggest data challenge is right now.

Skipping the business context in technical answers. Saying 'I would write a LEFT JOIN here' without explaining why loses points. Always connect your technical choice to what it achieves for the business question at hand.

Being vague about your own contribution. In team project stories, interviewers want to know what you specifically did. Replace 'we built a dashboard' with 'I designed the data model and built three views in Tableau while my teammate handled the ETL.'

Not validating your analysis before presenting. One Call interviewers reportedly pay close attention to candidates who mention data quality checks and sanity tests. If your answer jumps straight from 'I got the data' to 'I presented the result' with no validation step mentioned, it raises a flag.

Treating disagreements as debates to win. When asked about stakeholder conflict, answers that frame it as 'I proved them wrong' tend to land poorly. Frame the story around finding the truth together and agreeing on a shared source.

Ignoring the soft-skills rounds. Candidates sometimes over-prepare for SQL and under-prepare for managerial or 'tell me about yourself' conversations. Have a clear two-minute career story ready that connects your background directly to the Data Analyst role at One Call.

Not asking questions. Saying 'I have no questions' at the end signals low engagement. Prepare two genuine questions about the team's data stack, their biggest current challenge, or what success looks like in the first few months.