
Eleks Software 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
Which role are you interviewing for?
12 roles · 24 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Eleks Software.
Front End Developer
They asked a lot about general knowledge including patterns, algorithms, and data structures. Also, JS fundamentals, Angular, and RxJS. Basically, a front-end developer should know a lot, but the salary is lower than average on the market.
- Can you explain the difference between Subject and Observer in RxJS?
- Could you describe some design patterns you've implemented?
- What are your thoughts on algorithm complexity?
Senior Software Engineer
The interview process was good, covering general software engineering topics and computer science fundamentals, not just tech specific to the role. I interviewed with a PM about my background and how I work, and also had a customer-facing interview that involved solving coding problems. I received quick feedback.
- Questions about Databases?
- Questions about Architecture?
- Questions about .net?
Product Designer
The interview process involved three stages: an HR call, a technical interview with Oleg, and a final interview with higher management. The HR interview was standard and relaxed. However, the technical interview with Oleg was quite unpleasant. He was very cold and exclusively asked questions from a pre-defined list, stating he had to get through them. His demeanor was offensive, and since he would be the direct manager, I wouldn't recommend this company.
- Can you describe your design process?
- How do you determine when a project is finished?
- What is your approach to collaborating with developers?
QA Engineer
So the interview itself was okay, the questions they asked were spot on and I have no complaints about that part. What I wasn't too thrilled about was the reason I didn't get the job. Throughout the entire interview process, I asked them repeatedly if the job was for manual testing or automation testing, and each time they told me it was a manual testing position. They didn't ask me a single question about automation during the interview, even though I have experience in that area. Then, one of the reasons they gave for rejecting me was that they were looking for someone with more automation skills? So, even though the position was supposed to be manual, they didn't ask me one question about automation, and then I got rejected because of my automation skills?
- Can you walk me through your resume and elaborate on your experience in each of your previous positions?
- Please provide details about your experience in each job listed on your CV.
- Is this role focused on manual testing or automation testing?
Eleks Software Interview Questions
Quoted word for word from Eleks Software interview reports.
“Describe Django middleware.”
Read reports →“What is FAT?”
Read reports →“Reverse a single linked list and write the code on your PC.”
Read reports →“Could you explain the difference between WeakMap and Map?”
Read reports →“Can you explain generators in Python?”
Read report →“Can you explain the difference between Subject and Observer in RxJS?”
Read report →“Can you explain what an init container does in Kubernetes and give an example of when it would be useful?”
Read report →“Can you explain the async await mechanism in C#?”
Read report →“Can you write a python script using spark and hive for big data?”
Read report →Formats, difficulty and experience
Across all 24 Eleks Software interview reports.