Practice · Data analysts

Data analyst interviews, from SQL to the story

Analyst interviews mix technical questions with “what would you tell the business?”. Mockinto rehearses both, using the tools and projects on your own résumé.

Get 10 free credits See a sample report

An example question

“Weekly sign-ups dropped 20% last week. Talk me through how you would find out why.”

A strong answer checks the data first, then splits the drop by source, device or region before suggesting a cause.

Example written by the Mockinto team. Your interview’s questions are written for your résumé or job description.

What you will practise

Topics that come up for data analysts

Questions follow the skills in your résumé or the job description, so these are typical areas rather than a fixed script.

01 SQL: joins, grouping, window functions, explained in words
02 Excel or Google Sheets: lookups, pivots, charts
03 Dashboards and the BI tool on your résumé
04 Metrics, funnels and A/B test basics
05 Turning numbers into a recommendation
06 HR questions for early-career candidates

How to prepare with Mockinto

Rehearse, read the report, rehearse again

How a session works

Upload your résumé as a PDF or paste the job description. Mockinto writes about 30 questions for that role, a mix of HR, experience, aptitude and technical questions, and you answer each one out loud. When you finish, you get a report with an overall score out of 100, a score for each skill and feedback on every answer.

Say the query, then the insight

Interviewers often ask you to describe a query aloud. Practising it helps you explain the logic in the order the database runs it, then say what the result means.

Use the feedback

Each answer gets notes on what worked and what to improve. Rework the weakest answers and run another interview to check they are clearer.

What you get back

A report on every answer

Sample report · illustrative data, not a real candidate

Overall score

68 out of 100

Role: Backend developer, fresher
Questions: 30
Built from: A sample résumé (Java, Spring Boot, MySQL)

Skill scores

Java and Spring Boot 74/100
Databases and SQL 61/100
API design 70/100

Summary. Clear on core Java and REST basics. Answers on databases stayed general: name the index or the query plan you would check. HR answers were honest but long; lead with the result. One question was skipped and scored zero.

Q1 HR Tell me about yourself. 7/10

Your answer (transcript)

“I am a final-year computer science student. I built a library management system in Spring Boot for my college, and I interned for two months at a small fintech where I wrote REST endpoints…”

What went well

Opens with who you are and two concrete projects. The internship gives the interviewer something to ask about.

What could be better

At nearly three minutes it runs long. End with one line on why this role, and cut the list of college clubs.

A model answer

I am a final-year computer science student who builds backend services. At college I built a library system in Spring Boot and MySQL, and at my internship I wrote REST endpoints for a fintech app. I want a junior backend role where I can ship APIs and learn how production systems run.

Q7 Technical How would you speed up a slow query that filters orders by customer and date? 5/10

Your answer (transcript)

“I would first check if there is an index. If not, I would add an index on the customer column. I would also try to fetch fewer columns…”

What went well

Checks indexing first, which is the right instinct, and mentions selecting fewer columns.

What could be better

Say how you would confirm the cause, for example with EXPLAIN, and consider one composite index on customer and date rather than a single column.

A model answer

I would start with EXPLAIN to see whether the query scans the whole table. If it does, I would add a composite index on customer and order date, in that order, so the filter and the sort can both use it. I would select only the columns I need, then run EXPLAIN again to confirm the plan changed.

This is a sample built by the Mockinto team from illustrative data to show the report format. It is not a real candidate’s result, and the answers are written for the example.

Questions

Data analysts: common questions

Pricing

10 free credits at sign-up, enough to analyse your résumé and run a shorter mock interview. Then ₹10 a credit, with a 30-question interview typically about 11 credits.

See pricing

Do I need to write SQL during the interview?

No. Answers are spoken. You may be asked to describe how you would write a query, which is a common interview format.

Is it suitable for freshers?

Yes. Questions follow your résumé, so a fresher’s résumé with coursework and internships produces questions about those.

How much does it cost?

Every new account gets 10 free credits, which are enough to analyse your résumé and run a shorter mock interview. After that you buy credits at ₹10 each; a 30-question interview typically uses about 11 credits and purchased credits never expire.

All practice pages · How it works

Your next interview is a rehearsal. Make it a good one.

10 free credits at sign-up: enough to analyse your résumé and run a shorter mock interview. No card, no subscription.