Tell me about yourself for a data analyst interview

A tooling list is not an answer. Name the decision your analysis changed and the number attached to it.

Build your answer

Target role The job you are interviewing for. Years of experience Years in this kind of work. Use 0 for a first role or a career change. Current role or background A field, a path, or a short phrase.

Win 1 Include a number. Win 2 Optional. Win 3 Used in the long version.

Key strength One habit, not five adjectives. Why this company or role A reason that would be wrong for a different employer.

Runs in your browser. Nothing you type is uploaded.

30-second version

About 35 seconds · 88 words

A short cut for a recruiter screen.

Stop after one result. A short screen does not need the second story.

60-second version

About 57 seconds · 142 words

The default. Present, then past, then future.

If they lean in, drop the second result and spend the time on how the first one happened. Leave duties from the job description out.

90-second version

About 90 seconds · 224 words

A longer cut when they ask you to walk through it.

I'm looking for a data analyst role. For the past 3 years I've worked as a data analyst on a lifecycle marketing team. Before that, this is the work that got me here. One result was found that trial emails were firing a day late, and the fix lifted activation 9%. I also replaced three conflicting revenue definitions with one finance signed off on. I then cut a weekly stakeholder meeting from 50 minutes to 20 by leading with the decision. None of that is a title. It is the work I can walk through. The through-line is writing the metric definition before I write the query. The future I'm aiming at is a data analyst role, because this team sits next to the product decision, not only the dashboard. The first thing I'd measure is the constraint the team already feels. The numbers in those results are ones I can defend, including what I owned. The data analyst role is the move, and the results are how I know I can do the work. I can say any of those results more slowly, with the owner and the number intact. I would use the same judgment on the next data analyst problem. The work I want next is still data analyst work: a clear owner, a number, and a decision I can explain.

They can interrupt. Go present, then proof, then why this role. When they ask, go from the headline number to the decision you made.

When you can say the minute without the page, practice it live with Luna. It hears the question and helps you keep a line. 24 hours free.

How to answer it for this role

"I use SQL, Python, and Tableau" is a skills line for the resume. In the spoken minute, say who asked the question and what they did differently after your work. An analyst who saved a team from a bad launch is more interesting than an analyst who built a dashboard nobody opened.

Be precise about the grain of the data and honest about causality. "Churn was higher in month two for annual plans, so we changed the email" is a result if you know they changed it because of you. "I found an insight" is not.

Match the future beat to their stack only if you have used it. Wanting to learn a warehouse is fine. Claiming fluency you will be asked to demonstrate in the technical screen is not.

What to emphasize

The decision, not the chart.
The stakeholder who acted.
One metric definition you can explain without notes.

What to leave out

A list of tools as the whole past.
Over-claiming a causal result from a slice.

Sample 60-second answer

This is the sample loaded into the builder above. About 57 seconds, 142 words. Replace every fact with yours before you practice it.

I'm looking for a data analyst role. For the past 3 years I've worked as a data analyst on a lifecycle marketing team. Before that, this is the work that got me here. One result was found that trial emails were firing a day late, and the fix lifted activation 9%. I also replaced three conflicting revenue definitions with one finance signed off on. The through-line is writing the metric definition before I write the query. The future I'm aiming at is a data analyst role, because this team sits next to the product decision, not only the dashboard. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the data analyst work, the proof, and the reason.

The 30-second cut is about 35 seconds. The longer cut is about 90 seconds. Both use the same facts in the same order. Read the longer structure guide if you want the timing rules in full: how long the answer should be.

Tips before you say it

Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Other roles

Questions people ask

Should I mention SQL in the opener?

One clause is enough if the job is technical. The proof is still the decision. You will write queries in the screen.

What if my work was mostly reporting?

Pick the report that changed a meeting. "Finance stopped using the old revenue definition after the weekly note" is a result. "I refreshed 12 dashboards" is a task.

How do I talk about a career switch into analytics?

Name the old job, then one analysis you already did in it. Operators, nurses, and salespeople often have stronger domain data stories than a tools course.