CBC/Radio-Canada logo

CBC/Radio-Canada Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 11 interview experiences · FREE TO READ

2.2 Rounds average
Average Typical difficulty
36.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at CBC/Radio-Canada.

Showing 3 of 11
CBC/Radio-Canada logo
CBC/Radio-Canada

Software Developer

Engineering · a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Technical screen
Interview formats
Behavioral Technical Coding

It was supposed to be a 4-step process. The first step was a general 30 min. get to know you interview which went really well. The second step was a technical assignment. It was sent to me without warning at around 4:30pm on a Friday and due by end of day on Monday, which pretty much ruined my weekend and made me cancel all my plans. The assignment was to implement a microservice and include unit tests and documentation detailing the design choices, assumptions and tradeoffs. Maybe not a big deal if you've worked with microservices before, but this was my first time. And, considering the job description didn't mention microservices, I was surprised. I did research over the weekend, learned about microservices and managed to complete it. I was then invited to the third round which was supposed to be a behavioural interview. When I showed up remotely, I was told they were combining the third and fourth round into one interview. So, I would be having my technical interview, which I wasn't expecting until round four. My prep was for behavioural questions, not technical. I wasn't too concerned and proceeded. For the technical part, I was asked a bunch of technical questions. No mention of the assignment and none of the questions related to it. Then there was a coding question. This is where it fell apart. The interviewer kept disrupting me and wouldn't let me finish my thoughts or code. I'd write a couple of lines and he'd say "that's not going to work." I'd delete it and start again, and by line three or four he'd say "that's wrong." When I'd pause to think, he'd ask "what are you doing, what are you trying to do?" I'd say "I'm thinking" and start typing again. He asked me to explain my thoughts and as I started, he'd cut me off mid-sentence to tell me what to do. I'd respond "that is what I am trying to explain to you if you would let me." The entire coding part was a disaster. He was so disruptive I couldn't think, constantly saying "that's not right", "that's wrong" etc., making me feel stupid. The tension was building, and I had to bite my tongue. Eventually, I ignored him and finished the coding. There might have been a couple of syntax errors, but the logic was correct, though he insisted it was incorrect. I walked him through the code line by line, explaining the logic multiple times before he accepted it. We never got to running the code. I became so frustrated that I told them I don't think working with him would be the right environment for me and withdrew from the process.

Confirmed questions1 question
  • Given strings with letters and numbers (like "1ed2", "ge6us4dh89"), can you extract the first and last digits from each string, combine them, and then sum up all the digits found in all strings? Finally, print the total sum.
CBC/Radio-Canada logo
CBC/Radio-Canada

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding

I had 3 interviews for the Senior Software Engineer role. First was an initial phone interview. Second, an online home test with JS and React challenges. Third, a video interview with the team I'd be joining.

Confirmed questions1 question
  • How do you stay current with new technologies?
CBC/Radio-Canada logo
CBC/Radio-Canada

Senior Software Developer

Engineering

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Panel Background check Offer
Interview formats
Technical Behavioral

I applied maybe 2-3 months ago and then got an email for an interview the very next day at 1 PM, without them even asking if I was free. It was a panel interview and the interviewers didn't seem super prepped. I felt like I did pretty well, but 10 days later, the recruiter apologized for the lack of communication and said I'd hear back in a few days. A whole month went by and still nothing. The HR team was really bad, and they didn't even mention salary at all before the interview. I didn't get a strong vibe about the team from that one hour, but the HR people were just awful.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

CBC/Radio-Canada Software Engineer Interview Questions

Quoted word for word from CBC/Radio-Canada interview reports.

Given strings with letters and numbers (like "1ed2", "ge6us4dh89"), can you extract the first and last digits from each string, combine them, and then sum up all the digits found in all strings? Finally, print the total sum.

Read reports

What is your self-rated skill level (1-5) for technologies like Swift and Objective-C?

Read reports

Can you tell me about a time you had a disagreement with a coworker?

Read reports

Can you share an example of when you worked as part of a team?

Read report

Describe how you would handle a stressful work scenario.

Read report

Can you describe your previous roles and responsibilities?

Read report

Formats, difficulty and experience

Across all 11 CBC/Radio-Canada interview reports.

Interview formats

Technical 42.3%
Behavioral 34.6%
Coding 19.2%
Presentation 3.8%

Interview difficulty

Easy 36.4%
Average 63.6%
Difficult 0%

Candidate experience

Negative 54.5%
Positive 36.4%
Neutral 9.1%