
Foundry Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Foundry.
Software Engineer
I was contacted on LinkedIn, and after two positive video calls (an intro to Foundry and a tech call with the lead dev and a peer), I went to their London office for an on-site interview. The people there were very welcoming throughout. After a quick office tour, the technical interview began. It had two parts: first, a short written test with questions on the tech stack and project, which then led into a discussion with the dev lead and another dev. This was followed by a 'behavior and culture' interview with the same people, covering topics like my background and past failures. I also got to ask all my questions before we ran out of time. The tech and culture interviews combined lasted over two hours. Afterward, we had coffee, allowing me to see the area and wrap up the interview casually by discussing benefits and general details. It was a very pleasant experience, and my company contact was very responsive and adaptable.
- Can you explain the difference between virtualization and containerization?
Software Engineer
The first interview was on Hangouts, it had a chill vibe. We talked for about an hour about the company, its products, and future plans. We also discussed my past experiences, what I've accomplished, challenges I've faced, and how I approach problem-solving. It was a good conversation, and they answered all my questions, which felt positive. The second interview was at their London office. They showed me around the office (which is really nice) and explained the different teams. Following the office tour, I had a technical interview where we discussed my experience, I completed a technical test, and answered questions about how I would handle specific scenarios.
- How do you manage displaying a dashboard with multiple panels, each containing a lot of information, for a fast and fluid user experience?
Software Developer
The interview began with a phone call with someone from the dev team, followed by an in-person meeting. We first went over what the job entailed, and then discussed my past work. They checked my C++ skills by having me review and annotate a short, unusual piece of code. To wrap things up, I had a final meeting with some of the team, including the Product Manager. The whole thing took over two hours.
- What changes would you suggest for Nuke?
- What modifications would you propose for the C++ language if you were in charge of its design?
Foundry Software Engineer Interview Questions
Quoted word for word from Foundry interview reports.
“Could you explain delete/final and other C++11 keywords?”
Read reports →“Can you explain the difference between virtualization and containerization?”
Read reports →“What about (pure) virtual functions?”
Read reports →“Can you tell me about implicit/explicit constructors?”
Read reports →“What modifications would you propose for the C++ language if you were in charge of its design?”
Read report →“What changes would you suggest for Nuke?”
Read report →“How do you manage displaying a dashboard with multiple panels, each containing a lot of information, for a fast and fluid user experience?”
Read report →“Could you name any of their products you've seen showcased at a conference or exhibition?”
Read report →“Write a program to perform a specific task (details withheld due to NDA).”
Read report →Formats, difficulty and experience
Across all 8 Foundry interview reports.