Eversight Interview Questions
& Process

I applied to Eversight via referral and heard back from the recruiter. She was clear about the process, culture, and what they look for. The interview process is fully remote and includes 5 calls total: initial recruiter chat, a meeting with the hiring manager, and 3 more calls with sales leadership. They moved efficiently through stages, keeping me updated on feedback and accommodating my schedule, which sped things up. I got a decision within a week. They knew what they wanted and acted fast. Overall, a great experience.

It was a series of interviews over four weeks. I spoke with one of the founders (who would be my direct report), a Product Manager on the team, and the CTO. There was also a case study that I presented to them, plus five other department heads and team members in a remote panel. They also asked for work samples. Everyone was on time and friendly, which made for a relaxed atmosphere where I felt comfortable. The interviewers were genuine and clearly proud of their company. I really enjoyed the whole thing and came away with a lot of respect for the organization.

The interview process began with a Codility online assignment featuring questions of easy to medium difficulty, which were quite straightforward. This was followed by a phone interview where I was tested on Java keywords and asked an easy programming question. The onsite portion consisted of four interviews. These involved a mix of easy/medium programming questions, some design discussions, and behavioral questions. Fortunately, there were no difficult or dynamic programming problems. All interviews concluded with sufficient time for me to ask my questions. The entire process was remarkably swift, taking just over two weeks from the initial coding assignment to receiving and accepting the offer.

I was contacted via email by a recruiter. I haven't spoken to anyone directly, and I'm not even sure about the company's business or the technologies they use. They sent me a link to a Codility test, with instructions in a separate email. Unfortunately, Gmail filtered the instructions email to spam because my name was misspelled. This meant I didn't have the necessary information for the Codility test. The test itself had three exercises: a very simple algorithmic one, an easy algorithmic one with confusing instructions, and an easy SQL query. Since I missed the instructions email, I didn't allocate my time correctly across the exercises. I failed the second exercise because I spent too much time on the others. I doubt a human reviewed it, otherwise, they would have seen that the failed exercise had the correct algorithm and efficiency. It's frustrating to be rejected due to such a flawed process, but on the other hand, I wouldn't have accepted an offer from a company with such a poor hiring process. So, in the end, we both saved time.