Real, anonymous reports from people who interviewed for Software Engineer at Evernote, newest first and distilled into what to expect across the loop.
My experience started with a recruiter touchpoint that felt straightforward, and then the technical portion began fairly quickly. In the first round I had to jump into a live coding challenge where the focus was on core JavaScript fundamentals. I also remember the interviewer trying to gauge English proficiency as part of the evaluation, likely because of the role and office context.
I ended up going through a longer, more structured loop. After an HR-style conversation about my background and what I wanted, the process moved quickly into a live-ish coding stage that was scheduled as a LeetCode medium problem. From there it escalated into three back-to-back technical rounds: a system design discussion, a debugging-focused round, and then another coding round that was LeetCode hard.
The interview process typically begins with a recruiter phone screen that focuses on the candidate's background and interests, followed by a technical screen that may include coding questions. Candidates noted that the recruiter interactions were generally positive, though some experienced delays in scheduling subsequent rounds.
Candidates can expect multiple technical coding rounds, often involving live coding challenges that focus on core programming skills, including JavaScript and Java. The difficulty of these coding problems varies, with some candidates facing LeetCode-style questions that can be challenging under tight time constraints.
The interview process includes system design discussions and debugging exercises, which are designed to assess real-world coding and problem-solving skills rather than just algorithmic knowledge. Candidates appreciated the hands-on nature of these rounds, which felt more relevant to the actual job.
Behavioral interviews are typically conducted towards the end of the process, focusing on cultural fit and collaboration skills. Candidates reported that these interviews often felt less technical and more about assessing interpersonal dynamics within the team.
Several candidates experienced issues with communication and logistics throughout the interview process, including delays in scheduling, unclear feedback, and a lack of updates. This aspect significantly impacted their overall impression of the company, regardless of their technical performance.
While many candidates found the interview process structured and respectful, several did not receive offers, often feeling that the decision was influenced by factors beyond their technical abilities. The overall experience varied, with some candidates feeling positive despite not receiving an offer, while others left frustrated by the process.