Real, anonymous reports from people who interviewed for Software Engineer at Reply, newest first and distilled into what to expect across the loop.
I interviewed for a Reply entry-level Software Engineer role with average difficulty over a short timeline, involving both live coding and a longer take-home task.
I interviewed for a Reply Software Engineer role with an overall average difficulty and a multi-step path across a couple of days/weeks.
The interview process typically begins with an HR screen where candidates discuss their background, motivations, and fit for the role. This step is often informal and focuses on aligning expectations and interests.
Candidates can expect a technical evaluation that may include live coding, take-home tasks, or scenario-based questions focusing on basic programming concepts rather than deep algorithm challenges. The technical depth varies, but it generally assesses practical skills and understanding.
After the technical evaluations, candidates often engage in follow-up discussions with managers or partners to assess cultural fit and collaboration style. These conversations typically focus on the candidate's approach to learning and problem-solving.
The interview process is generally structured and spans several days or weeks, with clear communication throughout. While most candidates find the experience supportive, some report issues with scheduling and follow-up.
Many candidates express a desire for more timely feedback and clearer communication, especially after completing technical tasks. Some report feeling ghosted or receiving inconsistent follow-up after interviews.
The overall difficulty of the interview process is often described as easy to average, with a focus on fit and basic technical knowledge rather than high-pressure challenges. Candidates should prepare for a mix of light technical questions and HR discussions.
