the LEGO Group Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 143 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at the LEGO Group.
the LEGO Group
Senior Software Engineer
Senior Difficult Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation
Interview formats
Technical Coding Presentation Behavioral
The whole thing took about 6 weeks. It started with a nice chat with HR, then a coding session where I paired with a senior engineer. After that, I talked to a director, then had a panel interview with some lead engineers. The final step was a presentation to a director about a small project they assigned. Everyone I met was great – really professional and clear about what they expected. It was a tough process, definitely harder than average, and took a lot of time. I didn't get an offer in the end, but it was a solid, respectful experience. It's a big time commitment, which might be tough if you're already swamped at work or need a job fast. It would have been easier if they'd given clearer info upfront about how much time it would take or maybe combined a couple of the rounds.
Confirmed questions1 question
- Can you tell me about any code analysis or static analysis tools you've used specifically for embedded software?
the LEGO Group
Software Engineer
Entry Average Neutral experience Accept offer 5 rounds
Interview process
Recruiter call Take home Group Presentation Onsite
Interview formats
Behavioral Technical Group Presentation
The whole hiring thing took about 3 months and had a few interviews. First was an online one where I had to record myself answering general questions about me. Then came an assessment day for everyone, split into groups. Before that, we got a small code repository to check out and figure out what to improve or change. We talked about this in groups with others, watched by the hiring folks. After that, there was a short time to chat with the hiring team and other candidates. The final interview was more standard, just me and two LEGO people. It was mostly about getting to know me and how I solve problems, with high-level tech questions.
Confirmed questions1 question
- How does the LEGO group align better with your career goals compared to your prior workplace?
the LEGO Group
Software Engineer
Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Case
My initial chat with the recruiter gave me a good idea of the overall interview steps, and my meeting with the manager felt pretty relaxed. Some questions I hadn't really prepared for, and I was worried I wouldn't be able to express my thoughts and opinions well enough to show I'd be a good colleague and person. The technical interview, which included a case study, was definitely the toughest part – it's been a while since I had to dive into so many new concepts so fast, but it paid off and I felt like I did well. I was also comfortable during the interview (which was in English, not my native language) and had enough time to cover what I needed to.
Confirmed questions1 question
- Can you share your contributions to fostering inclusivity at work?
the LEGO Group Software Engineer Interview Questions
Quoted word for word from the LEGO Group interview reports.
“How can your application be made technology agnostic by abstracting the integration to a Kafka event provider?”
Read reports →“Should change management be a responsibility of the software development team itself, or managed by a separate group?”
Read reports →“How would you feel if you were on a team composed entirely of Danes?”
Read reports →“What are the software mitigation strategies, technical considerations, and tradeoffs for supporting 2nd-source electronic components in a project?”
Read reports →“Could you outline the architecture for a social media platform, utilizing the C4 model for visualization?”
Read report →“How do you decide which type of test is appropriate for a given situation?”
Read report →“Suppose you submit a pull request and a senior colleague suggests many modifications. How do you deal with that?”
Read report →“If a product was behind schedule, would you prioritize rushing its development to meet the deadline?”
Read report →“Can you tell me about any code analysis or static analysis tools you've used specifically for embedded software?”
Read report →Formats, difficulty and experience
Across all 143 the LEGO Group interview reports.