CBC

CBC's Interview Process (2026)

Blog / CBC's Interview Process (2026)

CBC's software engineer interview has three rounds, based on a senior candidate's September 2026 report on TechPrep: a technical design round, a product-focused behavioral round and a conversation with the manager or Agile lead. It tests practical API design and engineering judgment more than algorithm puzzles.

Technical Design Round (about 1 hour): A multi-part problem. First, design a new API and add it to an existing system, stating your assumptions: authenticated or unauthenticated access, traffic volume and idempotency. Next, walk through a Node.js app's middleware, controller, service and repository layers and write pseudocode for the endpoint. Then explain how you'd test it, including edge cases. It ends with a review of a related code snippet.
Product Lead Round (about 45 minutes): Behavioral questions with a product angle, such as how you prioritize tasks, what happens if you can't make a deadline and a time you disagreed with someone.
Manager or Agile Lead Round: A casual conversation about the team and the role, with a few high-level questions about past work. No technical questions.

The reported loop centres on API design, testing and code review, but other CBC roles may add coding or system design. Here's what to focus on:

Data Structures & Algorithms (DSA): Practical, medium-difficulty coding problems as a baseline.
System Design (High-Level Design): API assumptions, idempotency and media-scale system design.
Frontend and Full Stack: Node.js service layers, API testing, code review and frontend basics.
Behavioral and Culture Fit: Product-focused STAR questions on prioritization, deadlines and disagreement.

1. Data Structures & Algorithms (DSA)

The reported loop had no standalone algorithm round, so treat DSA as a baseline rather than the main event. Practical, medium-difficulty problems are the best fit, such as Two Sum, Merge Intervals, and tasks like Create a function to iterate through a nested object of arbitrary depth.Valid Parentheses is another good warm-up, especially for JavaScript-heavy roles.To cover the spread efficiently, work through our top 100 DSA questions with a focus on intervals, heaps, and arrays. Prioritize medium difficulty and practice explaining your reasoning out loud, since CBC interviewers value clear communication alongside correct solutions.

2. System Design (High-Level Design)

System design questions at CBC are grounded in the realities of a high-traffic, public-facing media platform. Expect questions about scalability, reliability, and security for products serving millions of Canadians.In the reported design round, the system-level thinking showed up through API assumptions: who can call the endpoint, how much traffic it gets and how to make it idempotent. For broader design practice that fits a media platform, work through Video Streaming and Sharing Platform (YouTube, Vimeo) and News Feed (Twitter, X), and Request Replaying / Idempotency for the idempotency piece.Practice working through end-to-end architectures using our HLD walkthroughs and get comfortable whiteboarding trade-offs using our System Design Whiteboard.

3. Frontend and Full Stack

The reported design round used a Node.js app, so be ready to explain how a request moves through middleware, a controller, a service and a repository, and why each layer exists. Brush up on Node.js and REST API design.Testing came up directly: how you'd test the API and which edge cases matter. Be ready to talk through unit versus integration tests and what you'd mock. The round also included a code review, so practice reading a snippet and calling out bugs, unclear naming and missing error handling.For frontend-leaning roles, the Debounced Search Bar question and React fundamentals are worth a look, and accessibility is a sensible area to revise for a public broadcaster.

4. Behavioral and Culture Fit

The product lead round was behavioral with a product focus. Reported questions included how you prioritize tasks, what happens if you can't make a deadline and a time you had to disagree with someone. Answer in STAR format and connect your decisions to product and user impact.The manager or Agile lead round was a lighter conversation about the team and your past work. Have a clear story about your recent projects and be ready to ask good questions about how the team works.Prepare your stories in advance using our Behavioral Playbook.

Conclusion

CBC's loop rewards practical engineering judgment: clear API assumptions, sensible layering, solid testing and a careful code review. Follow our CBC Interview Roadmap for a step-by-step plan that sequences your prep from DSA through system design, frontend, and behavioral. Go in with your STAR stories ready and a clear view of how you'd design, test and review an API.