BBC Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 88 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at BBC.
BBC
Software Engineer
Mid Average Positive experience Decline offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Coding Behavioral
The BBC Software Engineer interview was a really positive experience. It felt organized and efficient, and they were great about respecting my time. Communication was always super clear. The technical part was cool - a pair-programming session using their GitHub code, focusing on actual engineering stuff and design talks, not just random algorithms. Behavioral interviews were also good, lined up with BBC values. The culture seemed professional and open. Overall, a solid hiring process.
Confirmed questions1 question
- Could you explain the purpose of the Singleton annotation?
BBC
Software Engineer
Intern Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Behavioral Technical
So my application process was pretty long. First, my application got automatically rejected by the system based on what I put in. I got the rejection email at midnight, but I really thought I was eligible, so I reached out to them. Eventually, I got a human to look at it and moved on to the next stage. That stage was a 2-3 hour behavioral test. I passed that, and then I had to write about why I wanted to apply to the BBC. But after I finished that, I got another email saying I wasn't successful and wouldn't be moving forward. I didn't get any feedback after doing multiple tests.
Confirmed questions1 question
- What makes you want to join the BBC?
BBC
Software Engineer
Senior Average Negative experience Decline offer 2 rounds
Interview process
Technical screen Recruiter call Background check Offer
Interview formats
Coding Technical Behavioral
The process was mostly one long technical assessment centre, about 3 hours. It started with a coding test for the first 1.5 hours, where I had to code a solution into an existing codebase. I got to pick the language and set up my own IDE beforehand. Two interviewers were there to help out. Then, the second half was a technical interview with about 10 questions focused on my past experiences and projects, and my problem-solving methods. The interviewers were good and friendly, making it feel comfortable. The main issue was after the assessment centre with the recruiter. I didn't hear back when they said I would. It was really hard to get hold of the recruiter, they didn't reply for days. They also never clarified which specific jobs I applied for they were considering offering me before talking to the hiring manager. That chat was a waste of time because the job wasn't one I'd applied for, and the hiring manager didn't seem to know. I had to talk to another manager on a different team to find out the role didn't match my applications. The whole thing took weeks, and I spent a lot of time on the assessment centre and chasing the recruiter, only to be offered a job I didn't apply for and didn't want.
Confirmed questions2 questions
- Can you share details about your past projects and your approach to solving issues?
- Describe your methodology for tackling and resolving problems based on your previous work.
BBC Software Engineer Interview Questions
Quoted word for word from BBC interview reports.
“Can you convert digits to Roman numerals in the programming language you prefer?”
Read reports →“Can you explain the difference between an RDBMS SQL based database and a NoSQL database?”
Read reports →“When you choose a language, library, or framework, what are its pros and cons?”
Read reports →“In a scenario where a project deadline is unachievable, what actions would you take?”
Read reports →“What does diversity and inclusion mean to you? How would you promote, celebrate, or encourage it in this role if hired?”
Read report →“How do you handle situations where you disagree with a proposed implementation method, but the team has already decided on that approach?”
Read report →“How did you make sure that your software met the requirements and was of good quality?”
Read report →“Could you tell us which role you're interested in: App, Web, or Backend? Since we don't offer a backend test because you likely haven't covered it yet, please complete one of the other available tasks.”
Read report →“What are your strategies for promoting Diversity, Equity, and Inclusion (DEI) in a work environment?”
Read report →Formats, difficulty and experience
Across all 88 BBC interview reports.