Real, anonymous reports from people who interviewed for Software Engineer at Bell, newest first and distilled into what to expect across the loop.
My first step was a two-stage flow. I started with a technical take-home assessment, which set a heavier tone right away compared to the rest of the process. The next day I had a “vibe check” with the whole team, and the discussion was mostly behavioral—how I’d work, what I’d learned from past experiences, and how I communicate.
This interview was the least professional experience I’d had in software. The hiring manager didn’t even look at my resume, and instead kept talking about himself—what he’d done before and even that he was trying to get out of software. He spoke negatively about other teams he worked with.
The interview process typically begins with a video or recorded interview, followed by live interactions that may include behavioral and technical discussions. Candidates can expect a mix of formats, including one-on-one and panel interviews, with some processes being more structured than others.
Many interviews emphasize behavioral questions to assess fit and communication style, often asking about past experiences and problem-solving approaches rather than technical depth. Candidates should prepare to discuss their motivations for joining Bell and how their experiences align with the role.
Technical evaluations vary widely, with some candidates facing coding challenges or project-based assessments, while others encounter light technical discussions. It's important to be prepared for both practical coding tasks and conceptual discussions related to cloud technologies or software engineering fundamentals.
The overall atmosphere of interviews can range from relaxed and informal to more intense and structured, depending on the interviewer and format. Some candidates reported feeling undervalued or confused about the evaluation criteria, highlighting the importance of clear communication throughout the process.
Candidates reflected on the importance of being prepared for both technical and behavioral questions, with a focus on clarity in communication and demonstrating relevant experience. Some wished they had asked more questions or engaged more deeply during the interviews to better showcase their fit.
Feedback can be inconsistent, with some candidates receiving little to no information on why they were not selected. This lack of clarity can lead to frustration, so candidates should be proactive in seeking feedback when possible to improve future applications.