General Motors Of Canada logo
General Motors Of CanadaSoftware Engineer
Updated May 15, 2026

General Motors Of Canada Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at General Motors Of Canada, newest first and distilled into what to expect across the loop.

Get your personalized General Motors Of Canada Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
5 months ago
Average Positive United States

I interviewed for a Software Engineer role at General Motors of Canada and hit a fairly standard “OA → multiple 45-minute technical rounds → final manager” flow that felt average overall and focused on coding plus debugging.

OA (online assessment) — I started with an OA containing a mix of easy/medium-level LeetCode questions in some paths.
5 months ago
Average Positive Dublin, Dublin

I interviewed for a Software Engineer role at General Motors of Canada, and the process felt mostly behavioral with some light technical probing over a few weeks to a couple months.

Recruiter screen / housekeeping — I started with a short recruiter-style chat to cover my background and motivations.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Online Assessment (OA)

Candidates typically start with an online assessment that includes a mix of LeetCode-style coding questions, often varying in difficulty from easy to medium-hard. This stage is crucial as it serves as a gatekeeper for advancing to further technical rounds.

LeetCodecoding assessmentgatekeeper

Technical Rounds

The interview process often includes multiple technical rounds, which may consist of live coding, debugging, and system design discussions, with varying levels of difficulty depending on the team. Candidates should be prepared for both coding exercises and theoretical questions.

live codingdebuggingsystem design

Behavioral Interviews

Behavioral interviews are a significant part of the process, often structured around STAR-based questions that assess past experiences, teamwork, and problem-solving skills. Candidates should prepare to articulate their experiences clearly and connect them to the role.

STARbehavioralproblem-solving

Communication and Coordination

Candidates have noted inconsistencies in communication and scheduling throughout the interview process, which can lead to confusion and delays. It's advisable to follow up proactively for updates on the status of applications and interviews.

communicationschedulingfollow-up

Panel Interviews

Some candidates experience panel interviews that involve multiple interviewers, focusing on both technical and behavioral questions. Preparation for diverse questioning styles and dynamics is essential for success in these settings.

panel interviewmultiple interviewersdiverse questioning

Overall Experience and Outcome

The overall interview experience can vary significantly, with some candidates finding the process organized and others feeling it was unprofessional or confusing. Candidates should be prepared for a range of outcomes, including delays and potential cancellations.

experience variabilityoutcome uncertaintyprofessionalism