Software Engineer applicants have rated the interview process at eBacon with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 64.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 7 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at eBacon overall takes an average of 10 days.
Common stages of the interview process at eBacon as a Software Engineer according to 2 Glassdoor interviews include:
Skills test: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
Awful so far...
No show on the interview. No email saying they couldn't make it. No anything. Pretty much much the worst possible look for a company. This is pretty hard to beat for anyone reading this.
Average interview
Application
I applied online. The process took 1 week. I interviewed at eBacon in Sep 2024
Interview
I had a screening interview with their recruiter, which was casual and great. I learned about the company and the culture. I was given the technical interview later that day and submitted my solution as well.
I got feedback the next day that they would not be moving forward, my code was critiqued on not being modular and they believed I did not understand Git due to misunderstanding their ask for committing my answer and sending a link, and not opening a PR instead. The feedback was fair and valid, outside of the Git part. The code problem was straightforward and relevant to the job of Payroll software and I believe any mid-level engineer would succeed.
I would recommend that they be more forward on what they are looking for in their solutions. The casual conversation and understanding I believe I had with the recruiter did not lead me to believe I had to overly orchestrate the solution, as I was told it should be completed within an hour. The level of technical expertise they sought is fair, but just a bit fuzzy on how they go about the conversation in leading into the technical and the level they are expecting.