
Elastic Path Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 9 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Elastic Path.
Software Engineer
The interview process was pretty quick and straightforward. It had three parts: First, an HR call to chat about my background and if I'd fit the team. Then, a call with the manager where we discussed team fit, followed by a coding exercise and a design question.
- Discuss your previous experience and how you'd fit the team.
- Evaluate your fit with the team.
- Complete a coding exercise.
Software Engineer
The hiring process is really slow, with long waits for feedback after each stage and ignored follow-ups. The skills test was pointless, asking about deprecated APIs, which doesn't really show what a candidate knows. After about four steps, they do an in-person interview, which was disorganized and the questions weren't very in-depth. It seems like they're more interested in buzzwords than actual software engineering skills. The problems given during the interview were easy and not challenging at all.
- Could you draw the UML diagram for a set of shapes, including some with specific functions?
Software Engineer
It started with an HR phone interview and then they quickly invited me for the in-person interview. This interview had two rounds, the first with the team Directors and the next with Sr Architecture and Sr developers. They asked about my technical experience during my current and past careers and also technical questions in depth about Java and software architecture of project I work on. Then, in a fast pace they invited me for the next technical interview which I would attend in the next week. I just can say they have an excellent work culture and you will realise it from the first impression! during the interview I felt like I was a part of their team and the way they asked me questions it wasn't like many other companies they just want to hire and that's all. They really want to know how much your personality is a good fit with their work culture and how much you are reliable and knowledgeable in the technical matters! They are looking for hiring talented technical buddies not just hiring someone to fill a position! Honestly, I have no doubts such a company with such a believe system like “value the team as well as value the customers” will gain many more success in the future than they reach now and I really want to be a part of!
- Can you elaborate on your experience with Java 8?
- What are your thoughts on software architecture and design?
- Could you describe the software architecture of a project you've worked on?
Elastic Path Software Engineer Interview Questions
Quoted word for word from Elastic Path interview reports.
“Could you explain the microservices architecture?”
Read reports →“Can you explain the differences between microservice and monolithic architectures?”
Read reports →“Solve a simple refactoring problem.”
Read reports →“Could you draw the UML diagram for a set of shapes, including some with specific functions?”
Read reports →“Can you review this code and identify any bugs?”
Read report →“What are your thoughts on software architecture and design?”
Read report →“Can you elaborate on your experience with Java 8?”
Read report →“How would you approach refactoring a task, and can you explain your solution?”
Read report →“Could you describe the software architecture of a project you've worked on?”
Read report →Formats, difficulty and experience
Across all 9 Elastic Path interview reports.