Real, anonymous reports from people who interviewed for Software Engineer at BlackBerry, newest first and distilled into what to expect across the loop.
After a recruiter outreach, I was sent something that felt like a fundamentals prompt packaged as a PDF. The format was strict: I had to answer each question before moving on, so I couldn’t pace myself by skipping ahead. The questions were mostly “review your basics” style, covering things like how the stack works, heap versus code/data sections, and other core programming concepts.
My path felt a lot less cohesive than I expected. After the initial setup, I ended up in a technical-heavy process where the questions swung between very different areas, and the boundaries of what they wanted weren’t always clear. I had embedded-style software development prompts where C language basics came up, along with questions about implementing and reviewing what I’d written.
The interview process typically consists of multiple stages including an initial phone screen, technical assessments, and behavioral interviews, often spanning several weeks. Candidates noted that the timeline could feel drawn out and lacked cohesion, with varying lengths and formats across different interviews.
Candidates experienced a mix of technical questions that ranged from fundamental programming concepts to hands-on coding tasks, often emphasizing low-level memory management and practical problem-solving. The technical depth varied, with some interviews focusing on debugging and system design rather than traditional algorithm challenges.
Behavioral interviews were common, focusing on past experiences and how candidates fit within the team culture. Interviewers often asked about specific projects and technologies listed on resumes, aiming to assess both technical understanding and soft skills.
Some candidates reported completing take-home projects or assessments that were discussed in subsequent interviews, allowing for a deeper exploration of their technical choices and reasoning. This approach helped ground technical discussions in candidates' actual work.
The overall interview atmosphere was generally friendly and conversational, though some candidates noted variations in intensity and pressure. While many interviews felt relaxed, others were described as more demanding, particularly in technical depth and expectations.
Candidates often left interviews without offers, reflecting on the clarity of expectations and the depth of technical knowledge required. Many noted that preparation for specific technical areas was crucial, and some regretted not focusing more on certain topics like security or low-level programming.