
The Workshop 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 The Workshop.
Software Developer
The interview process was quite short, with 3 stages. First, there was a 30-min HR screening call. Then, a 1-hour online meeting with HR to discuss my experience and learn about the company. Finally, a technical interview with 3 developers, covering general knowledge, specific library/framework questions, and a 1-hour live coding task in plain JS. I got an offer from HR a few days later for the Málaga team. The whole thing took a week.
- Tell me about your studies and experience.
- What value do you think you can bring to the company?
- How do you handle stressful situations?
Software Engineer
Started with a phone call to chat about my career goals, current job, skills, salary, and benefits. Then, I had a technical phone interview with a solutions architect where we dove into the tech stack I've used, other languages I know, and I answered some quick questions about web development. The last part was in Malaga, where they covered my travel costs. We talked more about the offer and they showed me around the offices. Finally, I met with my recruiter, a tech lead, and a solutions architect for a session involving questions and solving problems on a whiteboard.
- Explain how to dynamically create components in Angular and provide real-world examples from your experience.
- Write a function that takes an index and returns the corresponding Fibonacci number.
Senior Software Engineer
So, first up was a recruiter call where we talked about my experience and it seemed to go alright. Then came the second round, a phone technical interview, but honestly, it was a mess. The audio was terrible, the interviewer had a thick accent, and worst of all, it wasn't really an interview. They didn't ask about my technical skills or experience at all, just threw some basic Java questions at me. I messed up one about Thread States, which is why I didn't get the job, but it's something you can easily find online and doesn't show what I can really do. The whole thing didn't even try to gauge my actual experience or how much I know. Total waste of time, poorly run.
- What interview?
The Workshop Software Engineer Interview Questions
Quoted word for word from The Workshop interview reports.
“Write a function that takes an index and returns the corresponding Fibonacci number.”
Read reports →“Write a function to calculate the nth Fibonacci number.”
Read reports →“What is the difference between an interface and an abstract class?”
Read reports →“What's the difference between an abstract class and an interface?”
Read reports →“What are the different types of partitions?”
Read report →“Can you list the different kinds of Java exceptions?”
Read report →“Is a snowflake schema preferable to a Star Schema?”
Read report →“Describe collections and the implementations of lists, maps, and sets.”
Read report →“Could you outline the differences between Spring and Spring Boot?”
Read report →Formats, difficulty and experience
Across all 24 The Workshop interview reports.