Internia

Bell Interview Experiences

Software Developer

Winter 2026

Accepted

University of British Columbia · General Engineering

4th year · 3.7+ · 3 past internships

Pre-recordedTechnicalVirtualMultiple rounds

Codility OA two problems, graph and DP (kill me lol). Technical interview they went deep on one of my projects and then gave me a 2D array problem. Final round was another project discussion plus 3Sum wanting optimal O(n^2) which I thankfully knew.

Data Analyst

Winter 2026

Accepted

Queen's University · Commerce

3rd year · 3.3-3.6 · 1 past internship

Pre-recordedMultiple roundsBehavioral

Seemed like they wantedr someone comfortable with both SQL and Python. Video interview first, 3 questions. Then a phone interview and eventually a virtual panel. Why Bell and what data anaalytics experience I had. Background in marketing analytics from a class project came up a lot.

Software Developer

Fall 2024

No Offer

Toronto Metropolitan University · Computer Science

2nd year · 2.9-3.2 · 0 past internships

Pre-recordedMultiple roundsVirtualSlow process

2 coding questions and then a behavioral questionnaire where they give you scenarios and you pick how you'd respond. the actual interview was half behavioral half coding. they care a lot about innovation and customer experience so have stories ready about improving things and working on teams. coding part was a sliding window problem which I'd literally practiced the day before.

Network Engineer

Summer 2025

No Offer

Concordia University · Electrical Engineering

2nd year · 2.9-3.2 · 0 past internships

Pre-recordedMultiple roundsPoor Communication

Got through to the panel round but didn't advance, no explanation given. Video interview then a phone assessment. Questions on critical thinking and giving an example of working through a situation without full information.

DevOps Engineer

Summer 2026

No Offer

Université Laval · Computer Engineering

3rd year · 2.9-3.2 · 1 past internship

TechnicalVirtualMultiple roundsGhosted

Just a rejection email, no feedback. Questions were on jenkins pipelines, Ansible and cloud deployment patterns. Also a root cause analysis scenario for a production outage. Teams interview with the engineering team after a phone screen.

Related Companies