CGI Product Analyst interview typically runs 2 rounds: assessment centre with a group task and an individual interview. It usually takes one day and feels laid back and chatty.
$58K
Avg. Base Comp
$110K
Avg. Total Comp
2
Typical Rounds
1-2 weeks
Process Length
Our candidates report that CGI’s Product Analyst process is less about flashy technical depth and more about whether you can keep a conversation moving when the room goes quiet. In one assessment, the group exercise became awkward because other candidates barely contributed, and the person who advanced was the one who naturally filled the silence and kept the discussion productive. That tells us CGI is watching for steady facilitation and composure under low-energy dynamics, not just who has the loudest ideas.
The individual conversation seems similarly conversational on the surface, but the signal is in how you frame challenge. Multiple candidates describe a long, chatty interview packed with standard prompts, with the standout question centered on a difficult situation and how they handled pressure. We’ve seen that CGI appears to value clear problem-solving narratives and a calm, structured way of explaining what you did, why you did it, and what changed as a result. The content may feel ordinary, but the evaluation is in the detail and coherence.
A recurring theme is the company’s tone: the recruiters and interviewers are described as genuinely lovely and the day as laid back, yet the experience still rewards candidates who can create momentum without being pushed. That combination means the non-obvious make-or-break factor is often not polish, but presence — being able to contribute meaningfully, keep answers grounded, and avoid sounding rehearsed when the conversation stretches on.
Synthetized from 1 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.
The assessment centre was the main part of the process and it was split into a group task and an individual task. The whole day felt very laid back, which was nice, and the recruitment team and interviewers were genuinely lovely throughout. That said, the group exercise was a bit awkward because the other people there were so quiet and barely pitched in, so it was hard to get much of a discussion going. I ended up doing a lot of the talking just to keep things moving, which made it feel less like a natural group activity and more like trying to fill the silence.
The individual interview felt much more straightforward, although it seemed to go on forever. It honestly felt like they asked about 40 questions, even though the actual content was pretty standard. The main question I remember was about explaining a time I dealt with something challenging, so it was mostly behavioural and focused on how I handled pressure and problem-solving rather than anything technical. I wasn’t offered the job, and I did ask for feedback afterwards because they said they would provide it, but I never heard back, which was disappointing. My main takeaway would be to prepare a few solid behavioural examples and be ready for a long, chatty interview format rather than anything especially technical.
Prep tip from this candidate
Prepare a strong example for “a time you dealt with something challenging,” and be ready to keep a group exercise moving if the other candidates are quiet. The individual round sounded long and very behavioural, so have several concise stories ready rather than one polished answer.
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
Find the average yearly purchases for each product
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Foreign Key Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Employee Salaries | |
| Closest SAT Scores | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Largest Salary by Department | |
| First Touch Attribution | |
| Experiment Validity | |
| Project Budget Error | |
| Decreasing Comments | |
| First to Six | |
| Impression Reach | |
| Bank Fraud Model | |
| SELECTive Wine Connoisseur | |
| Raining in Seattle | |
| Top 3 Users | |
| 500 Cards | |
| Google Maps Improvement | |
| Top 5 Turnover Risk | |
| Assumptions of Linear Regression | |
| Over-Budget Projects | |
| Size of Joins |
Synthesized from candidate reports. Individual experiences may vary.
Candidates are invited to an assessment centre rather than going through a long technical screen. Based on the experience shared, this appears to be the main evaluation point in CGI’s process for Product Analyst roles.
The first exercise is a group activity where candidates discuss and work through a prompt together. The experience described was very laid back and collaborative, with the interviewers observing how candidates communicate and contribute in a team setting.
Candidates then complete a one-on-one interview that is largely behavioural and chatty in format. The questions focus on handling challenges, pressure, and problem-solving, and the interview can feel quite long with many standard behavioural questions.