Candidates applying for Software Engineer roles take an average of 5 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Apollo.io overall takes an average of 29 days.
Common stages of the interview process at Apollo.io as a Software Engineer according to 4 Glassdoor interviews include:
Phone interview: 75%
Presentation: 25%
Here are the most commonly searched roles for interview reports -
Initially I had a coding test. It just had one program on hackerrank. The next round was phone interview. Again another programming question. The interviewer gave me a call half an hour late than the scheduled time and then tried to finish the interview sooner giving me 45 mins rather than an hour giving me less time to finish the question.
Interview questions [2]
Question 1
1. Coding test: To split a hexadecimal string so that the result of the split are both perfect squares. You need to return the number of splits?
We hold ourselves to a higher standard and we fell short of them during this interview. With this feedback we will learn from this experience and improve our process as we continue to grow and build a great team.
Other Software Engineer Interview Reviews for Apollo.io
There were total of four rounds
- first round consist of easy to medium leetcode question
- second round consist of React machine coding round
- third round consist of debugging round with react and redux
- fourth round consist of behaviour round
Initial screening through coderbyte. there were 3 question. two of them were problem solving & one from react. need to solve with in 50 min. all 3 questions. In order to move
to next round
Interview questions [1]
Question 1
Screening through coderbyte. there were 3 questions
I applied online. I interviewed at Apollo.io (San Francisco, CA)
Interview
The interview process was quite convoluted. It involved multiple rounds that seemed disorganized and redundant. First, I had a screening call with HR, which was followed by a technical assessment. The technical questions focused on coding challenges and system design, but after completing that round, I was unexpectedly asked to repeat some similar tasks in the second technical round. Moreover, I was introduced to an entirely different interviewer who seemed unaware of my previous discussions. There was also a lengthy discussion on data crawling methods, especially LinkedIn crawling, which felt out of scope for the role I applied for, and raised some legal and ethical questions. The entire process took several weeks with long gaps between communications, which made it hard to follow and frustrating.
Interview questions [1]
Question 1
Can you explain how you would set up a LinkedIn crawling system to collect large amounts of user data efficiently?