
Geotab Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 77 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Geotab.
Software Developer Intern
The interview process had 2 parts. First, a 20-30 min HR chat, mostly behavioral questions like handling multiple deadlines. Then, a technical round with the hiring manager. They started with resume review and some easy behavioral questions. After that, there was a quick theory round covering databases, networking, multithreading, OOP design patterns, SOLID, and dependency injection. Finally, a coding round where I had to implement classes for a specific calculation, which wasn't too difficult. The whole thing took about 2 weeks.
- Can you explain SOLID principles?
- What is dependency injection?
- Could you describe the difference between async and sync operations?
Software Engineer
It started with a recruiter screen, pretty standard. Then there was an online assessment, like an IQ test, an hour long with 30 questions, which I found a bit odd. After that, a coding assessment was given with a week to complete. It involved building an ASP.NET backend and a React.js frontend that communicate via REST. The requirements were a bit vague about being 'production ready.' The final stage was supposed to be a panel defense of the coding assessment, similar to a dissertation defense, plus some live coding. However, the whole thing got cancelled the day before, and I just got a generic email saying they were thankful for my time, with some vague, possibly AI-generated feedback on the coding assessment.
- How much experience do you have with C#/.NET throughout your career?
Software Developer
So I interviewed for the Software (Full Stack) Developer role at Geotab. The process, while a bit long, was really smooth and organized, with five total rounds. First up was a phone chat with HR that touched on basic stuff like why Geotab, plus a few technical points. Then came a timed IQ test, about 40 logic and math problems, pretty challenging. Round three had me talking to two senior devs/team leads for an hour. We went over technical stuff relevant to the job and they threw some quick coding challenges at me in CoderPad. After that, I had a take-home assignment: refactoring some messy code. It was pretty straightforward and a good way to show what I could do. The last round was a panel with three senior developers/team leads. We mainly discussed the take-home project and did more coding challenges on CoderPad. Everyone was really nice and helpful throughout, especially the HR person who was always polite and quick to respond. Overall, it was a good experience.
- What are Promises in JavaScript?
Geotab Software Engineer Interview Questions
Quoted word for word from Geotab interview reports.
“What is the consequence of omitting 'var' when declaring a variable in a JavaScript function?”
Read reports →“What's the difference between a shallow copy and a deep copy?”
Read reports →“Can you add a button to a React app that will increment a counter when clicked?”
Read reports →“How would you write a simple SQL command to view specific columns in a table?”
Read reports →“Can you tell me the differences between unit testing and integration testing?”
Read report →“Could you describe the difference between async and sync operations?”
Read report →“Can you explain the use of native ES6 functions such as map and filter, and also questions about anonymous functions?”
Read report →“Tell me about the usage of native ES6 functions like map, filter, and anonymous functions.”
Read report →“Could you tell me what variable you used to enhance JVM garbage collection?”
Read report →Formats, difficulty and experience
Across all 77 Geotab interview reports.