Get tailored insights about working at Eleos in one quick step.
Eleos interview questions
based on 3 ratings - Updated Jan 2, 2025
Easyinterview difficulty
Mixedinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
3 interviews
Eleos interviews FAQs
Glassdoor users rated their interview experience at Eleos as 33.3% positive with a difficulty rating score of 1.67 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for VHA and Senior Full Stack Developer rated their interviews as the hardest, whereas interviews for VHA and Sales Consultant roles were rated as the easiest.
The hiring process at Eleos takes an average of 1 day when considering 3 user submitted interviews across all job titles. To compare, the average duration of hiring at similar companies like BlackRock, Inc. is 14 days, Fabricated Software, Inc. is 2 days, and Apple Inc. is 21 days. Candidates applying for Senior Full Stack Developer had the quickest hiring process (on average 1 day), whereas Senior Full Stack Developer roles had the slowest hiring process (on average 1 day).
I applied online. The process took 1 day. I interviewed at Eleos (Tel Aviv-Yafo)
Interview
The interview was on Zoom and felt very informal. The interviewer was sitting on his couch at home, occasionally shifting his laptop (which was apparently on his lap), and he spoke at length about himself, particularly about his military reserve service, something that didn’t interest me and didn’t seem relevant to the interview.
Overall, most of the interview was fine, but then came a point where the interviewer asked me to talk about "the hardest problem I've ever solved during my years as a programmer."
I presented a system I built a few years ago, and to put it mildly, he didn’t like it. At that moment, he stopped being nice and started speaking to me in a tone that was insulting and overly direct, which didn’t seem appropriate for an interview.
He began talking about how "he knows what kind of programmer I am" and that he couldn’t understand why I showed him that system I built, claiming there were poor solutions I had implemented.
I was very embarrassed at that moment. Then he started telling me that he believed I wouldn’t pass the backend test, which is the next step in the process.
He said I had no understanding of trade-offs, even though we didn’t discuss that in the context of the system, and I didn’t understand how it was relevant to a system I designed years ago.
Interview questions [1]
Question 1
To tell about myself, projects I've done in my work years and technologies from a Product Manager standpoint and from an Architect standpoint.
Pretty straight forward and easy, mostly about why I wanted to work with them and how my skills apply to the position offered. Everything was done online or over the phone. Only needed to go in office to sign the contract.
Very informal, completely remote. I was going to be hired under a sales consultant to gather leads for them. Expectation was to have x amount of leads generated per week leading to y amount of sales. Commission based on leads that go to sale.