BlackBerry software engineer interviews, as candidates describe them, are conversational and centered on your projects, with basic coding and language-fundamentals questions plus behavioral discussion.
$103K
Avg. Base Comp
$118K
Avg. Total Comp
Not reported
Typical Rounds
2-3 weeks
Process Length
Candidates describe BlackBerry software engineer interviews as relaxed and centered on your own project experience. Several reports say the interviewer or hiring manager asked about specific projects, what the candidate built, and the technical decisions behind them. One candidate who did not receive an offer described follow-up questions on architecture decisions and how they approached hard problems. Pick two or three projects from your resume and be ready to go deep on any of them.
Technical questions are described as fundamentals-level. Reported topics include reversing a string, a debugging exercise, binary search on a whiteboard, removing duplicates from a list and how to test it, and sorting a binary tree. Language questions also appear, such as Java versus C or C++, Java try-catch behavior, and classes versus structs. One QNX-related testing role reportedly focused on Linux and POSIX theory and a take-home C/C++ assessment. The language to review probably depends on the team.
Behavioral questions come up repeatedly, especially how you handled a disagreement or conflict, and why you want to work at BlackBerry. Reported formats vary: a 30-minute video call, a single manager conversation, a phone screen followed by an on-site, and a roughly two-hour in-person visit with a manager and two developers. One candidate said the questions felt scattered, so keep your answers clear and self-contained. Reported process lengths were about two to three weeks. Several of these accounts come from internship, co-op, or university-recruiting interviews, so senior roles may differ.
Synthesized from 8 candidate 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 Blackberry process.
I had a 30-minute video interview with the team that felt pretty straightforward overall. The interviewer started with a quick introduction and asked me to talk about myself, then we moved into some technical questions. There was a simple algorithm problem — something basic like reversing a string — followed by a debugging question where I had to spot and fix issues in code. The technical bar didn't feel particularly high, which made sense given this was an internship role. They also threw in a behavioral question about a time I disagreed with someone and how I handled it, which felt like a natural conversation rather than a grilling. The whole thing wrapped up in about half an hour. The vibe was relaxed and the engineers seemed genuinely interested in understanding how I think rather than trying to trip me up. If you're prepping for this, don't overthink it — they're looking for someone who can code at a basic level and communicate reasonably well about their thought process.
Prep tip from this candidate
Focus on simple algorithm questions like string reversal and basic debugging skills rather than complex data structures — the bar is straightforward for this role. Be ready to discuss how you handle disagreements or conflicts in a team setting.
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 Blackberry
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report applying through university recruiting, an internal careers site, or a recruiter. One QNX-related candidate said the online application required a detailed employment history and a recruiter call covering location and compensation. Expect logistics to vary by route and team.
Some candidates describe a phone or video conversation before or instead of an on-site. One intern's 30-minute video call with the team began with an introduction, then moved to a basic coding question, a debugging question, and a behavioral question. Others went straight to an on-site, so this step may not apply to every team.
Candidates report that much of the interview focused on past projects, the technical decisions behind them, and why they chose BlackBerry. One candidate who was not offered a role described detailed follow-ups on architecture decisions. Prepare specific examples and be ready to explain your own contribution.
Reported technical questions were basic: string reversal, debugging, binary search, deduplication, tree sorting, and Java, C, or C++ concepts. One QNX-related role reportedly emphasized Linux and POSIX theory and a take-home C/C++ assessment. The exact mix probably depends on the team and the language they use.
One candidate described a roughly two-hour in-person visit with a hiring manager and two developers, mixing behavioral and technical questions. Another described a day-long on-site that ended without an offer. One candidate received an offer a few days after the interviews, and another had to follow up after a week before hearing back three days later.
