CGI Software Engineer interview typically runs 3-4 rounds: assessment, technical, managerial, and HR. It usually takes 2-3 weeks and is often conversational, resume-focused, and fast-moving.
$98K
Avg. Base Comp
$114K
Avg. Total Comp
4-6
Typical Rounds
2-3 weeks
Process Length
We’ve seen CGI lean less on puzzle-heavy interviewing and more on whether candidates can speak fluently about the work they’ve already done. Multiple candidates said the questions stayed close to their CV, project history, and day-to-day backend experience, even when the topics were technical. That pattern shows up across Java, Spring Boot, microservices, SQL, and API questions: the bar is not just knowing the terms, but explaining how they fit together in real systems and tradeoffs.
A recurring theme is the company’s preference for practical depth over abstract theory. Candidates reported being pressed on Java fundamentals like memory, garbage collection, streams, multithreading, and serialization, but also on stack-specific details such as Spring dependency injection, Actuators, API security, Git workflows, and even SCD Type 2. We also saw a few interviews turn into on-the-spot design or code-along discussions, which makes it clear CGI is watching for clear reasoning under light pressure rather than polished memorization.
What tends to make or break candidates here is how directly they connect their background to the role. Our candidates repeatedly mentioned questions about internships, college projects, KPIs, CI/CD, and real project hurdles, plus some scenario-based managerial prompts. The strongest experiences came when interviewers felt like future teammates or mentors; the weakest came when answers were vague or overly generic. In other words, CGI seems to reward candidates who can be specific, grounded, and ready to discuss the actual systems they’ve touched.
Synthetized from 6 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Cgi process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Cgi
Given an integer N, write a function that returns all of the prime numbers up to N
| Question | |
|---|---|
| Sum to N | |
| Average Quantity | |
| Find the First Non-Repeating Character in a String | |
| Hurdles In Data Projects | |
| Foreign Key Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Largest Salary by Department | |
| Raining in Seattle | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Size of Joins | |
| P-value to a Layman | |
| First Touch Attribution | |
| The Brackets Problem | |
| Employee Project Budgets | |
| SELECTive Wine Connoisseur | |
| Get Top N Frequent Words | |
| Google Maps Improvement | |
| Sort Strings | |
| Top 5 Turnover Risk | |
| Over-Budget Projects | |
| Manager Team Sizes | |
| Target Indices | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
Candidates often start with an online test, which can include multiple-choice questions and, in some cases, logic or language sections. Experiences mention coding plus MCQ tests, as well as logic and French assessments before moving forward.
An initial HR or recruiter conversation follows for many candidates. This stage is usually a brief screening to discuss background, motivation, role fit, mobility, and basic resume details.
The first technical round is focused on core backend fundamentals and project experience. Candidates were asked about Java, Spring Boot, OOP, streams, multithreading, REST, SQL, security basics, and resume-based questions, with some interviews feeling like a screening and others going deeper into practical implementation.
Some candidates had a second technical discussion or client-style round, sometimes done as a code-along or scenario-based problem solving session. This round could include deeper questions on Java memory, garbage collection, Git workflows, microservices, AWS, Node.js, API security, or stack-specific topics tied to the team.
A managerial or techno-managerial round typically comes near the end and is often scenario-based. Interviewers asked how candidates would handle real workplace situations, work with non-technical stakeholders, and explain project decisions and past experiences clearly.
The final step is usually an HR discussion covering compensation, expected salary, current package, and negotiation. In some cases this was also the last formal conversation before the final decision.