
Geotab Data Analyst Intern Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Geotab.
Data Analyst Intern
So the whole thing was 3 rounds. First up was a quick chat with a recruiter about my background, why I'm interested, and just general fit. Then I had a live coding session in CoderPad with a senior analyst, where I had to do 5 SQL problems. They were about joins, aggregations, window functions, and figuring out overlapping intervals, all in MySQL. The last round was a 45-minute behavioral chat with two senior data analysts. We really dug into my past projects, covering stuff like pipeline architecture, why I designed dashboards a certain way, how I picked metrics, making sure things were fault-tolerant, and how I'd optimize SQL queries (like looking at query plans, using CTEs versus subqueries, partitioning, and slot contention). They left the last 15 minutes for my questions. I heard back about their decision pretty quickly, within a few days after the final interview.
- Can you walk us through your data pipeline project, explaining how it all fits together from data ingestion to the dashboard?
- What were your strategies for handling late-arriving data?
- Which Airflow operators did you employ in your project?
Big Data Intern
First, we said hello and then I was asked some questions. Some of them were technical and some were not. I was asked to introduce myself first. Then, I had to talk about a project I worked on. After that, the technical questions began. The HR person then asked me what I knew about the company. Finally, they asked if I had any questions for them.
- Can you talk about your project experience?
- What are your thoughts on the company?
- Can you tell me about the role?
Data Analyst Intern
First, there was an HR screening with intro, behavioral questions about projects, and some basic technical stuff like SQL joins, indexes, and a bit of Python. After about 3 days, I got an invite for the second round, a coding round on Google Meet using a CoderPad link where I had to share my screen. It had 5 intermediate SQL questions based on Geotab fleet data, focusing on window functions, COALESCE, basic CTEs, AVG, and ROUND. It lasted 1 hour. About a week later, I got the invite for the final round, a 45-minute session with the hiring manager and a senior team member. It was mostly a resume deep dive, asking about my projects and decisions, and they also reviewed my GitHub. It was a really nice vibe, everyone was welcoming. I got an offer, but I'd already accepted another, so I declined.
- Can you tell me about SQL indexes and joins?
- What are the disadvantages of using indexes?
- Do you consider Python a functional programming language?
Geotab Data Analyst Intern Interview Questions
Quoted word for word from Geotab interview reports.
“What are the disadvantages of using indexes?”
Read reports →“Do you consider Python a functional programming language?”
Read reports →“Can you explain the difference between a method and a function, and what types of output they produce?”
Read reports →“Can you explain the difference between a left join and an inner join?”
Read reports →“Can you tell me about SQL indexes and joins?”
Read report →“How did you determine the most suitable visualization types for your dashboard?”
Read report →“How did you make decisions about which metrics to include on the dashboard?”
Read report →“What's another way to solve the coding problem you were given?”
Read report →“Which Airflow operators did you employ in your project?”
Read report →Formats, difficulty and experience
Across all 11 Geotab interview reports.