Real, anonymous reports from people who interviewed for Software Engineer at Inc. In, newest first and distilled into what to expect across the loop.
I went through an interview loop that was technically demanding and then derailed by poor HR communication, including ghosting and role/vacancy shifts.
I went through a fairly coding-heavy HackerRank experience with proctoring/time pressure and O(1)-style data-structure problems.
The interview process typically begins with a recruiter-led screen that focuses on the candidate's background, fit for the role, and logistics. This stage is crucial for setting expectations and assessing initial compatibility.
Candidates face a HackerRank or CodeSignal online assessment that includes timed LeetCode-style questions, often with a mix of easy to medium difficulty. Performance here is critical as it serves as a gatekeeper for advancing in the process.
Subsequent technical interviews often involve live coding sessions and problem-solving questions, with a strong emphasis on data structures and algorithms. Candidates should be prepared for both coding and conceptual discussions.
Interviews frequently include a system design component alongside behavioral questions, where candidates must demonstrate their understanding of design principles and cultural fit. This stage assesses both technical depth and interpersonal skills.
Candidates report issues with communication and follow-up from HR, including ghosting and unclear timelines. Consistent and clear communication is essential for a positive candidate experience.
The interview process can feel lengthy and drawn out, with candidates experiencing uncertainty about outcomes. Staying engaged and prepared across multiple formats is crucial for success.
