Real, anonymous reports from people who interviewed for Software Engineer at Front, newest first and distilled into what to expect across the loop.
The recruiter call came first, then I met with the hiring manager. After that, I went into a coding round that the recruiter had described as being more algorithms and LeetCode-style questions. What I walked into didn’t match that framing.
My process started with an HR conversation focused on questions tied to my CV. After that, I moved into a take-home exercise in JavaScript/TypeScript centered on async behavior and functions. The expectation felt like it was meant to test real-world correctness rather than memorized patterns.
The interview process typically begins with a recruiter call followed by a conversation with the hiring manager, focusing on the candidate's background and expectations for the role.
Candidates are often required to complete a take-home exercise that tests real-world coding skills, with a focus on practical applications rather than theoretical knowledge, though the clarity of instructions can vary significantly.
After submitting the take-home exercise, candidates typically participate in a code review session with engineers, which is more of a collaborative discussion rather than a high-pressure evaluation.
Following the technical rounds, candidates usually engage in behavioral interviews that assess cultural fit and communication style, often with the hiring manager or other team members.
Candidates report that the overall difficulty of the process is average, but feedback can sometimes feel subjective, particularly if instructions are vague or open to interpretation.
The interview process is generally structured with distinct phases, including initial conversations, technical assessments, and final interviews, but the timeline can vary widely based on the clarity of instructions and candidate performance.