Barco Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 24 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Barco.
Barco
Senior Software Engineer
Senior Average Neutral experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Technical Coding System Design
It was a 2-round process, and both rounds were purely technical. The first round focused heavily on Data Structures and Algorithms (DSA) along with frontend technologies like Javascript and Angular. The second round was more of a System Design interview combined with a Javascript-focused segment.
Confirmed questions6 questions
- Can you explain Javascript closures and provide an example?
- What happens with the 'const' keyword in nested objects, and what is a Deep Freeze object?
- Could you detail the Javascript Event Loop, call stack, microtask queue, and callback queue?
Barco
Software Engineer
Mid Average Positive experience Decline offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Coding Behavioral
It was a DSA-heavy interview with resume-based and behavioral questions. Honestly, it was easier than other companies of this level. Some people had different experiences though, so it really depends on who you get.
Confirmed questions3 questions
- Any questions about your resume?
- What are some behavioral questions?
- Can you tell me about React.js?
Barco
Software Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Phone screen
Interview formats
Technical Behavioral
The interview process involved three levels: L1 focused on C++ basics and some advanced concepts, conducted by a lower-experience interviewer. L2 also covered C++ basics and advanced concepts, but was led by a higher-experience interviewer, with little perceived difference from L1. L3 involved managerial questions like 'why do you want to switch?' along with some technical questions. I liked the interviewers and how they assessed concepts. However, I disliked the overall process because I interviewed twice, months apart. Both times, I stated my expectations upfront, but after completing all rounds, they backed off when discussing expectations. This implies a fault on my end when it isn't. They should be direct and state if they cannot meet my expectations, instead of saying they'll get back to me and then not calling.
Confirmed questions3 questions
- Brush up on C++ basics.
- Work on C++ modern version features.
- There were a few questions that tested in-depth knowledge on concepts which only comes from working significantly in some good projects.
Barco Software Engineer Interview Questions
Quoted word for word from Barco interview reports.
“Can you find the largest repeating substring in a string?”
Read reports →“What are the differences between buildroot and yocto?”
Read reports →“What is the difference between multiprocessing and multithreading?”
Read reports →“How is the Singleton Pattern implemented in Angular?”
Read reports →“What happens with the 'const' keyword in nested objects, and what is a Deep Freeze object?”
Read report →“Can you explain what buildroot is?”
Read report →“Can you explain Javascript closures and provide an example?”
Read report →“What are Directives in Angular, and can you give an example?”
Read report →“Could you detail the Javascript Event Loop, call stack, microtask queue, and callback queue?”
Read report →Formats, difficulty and experience
Across all 24 Barco interview reports.