Recruiter Communication & Process Clarity
Candidates reported mixed experiences with recruiter communication, ranging from supportive and clear to chaotic and unprofessional, which impacted their overall impression of the process.
Real, anonymous reports from people who interviewed for Software Engineer at Infoblox, newest first and distilled into what to expect across the loop.
I interviewed for the Software Engineer role with an accelerated, in-person-heavy loop that felt chaotic and got extended unexpectedly.
I interviewed for a Software Engineer position through a multi-step pipeline (aptitude/online + recruiter + coding + several interviews) that was consistently followed by silence.
Candidates reported mixed experiences with recruiter communication, ranging from supportive and clear to chaotic and unprofessional, which impacted their overall impression of the process.
The interview process typically included multiple technical rounds, often with a mix of coding, algorithms, and systems design questions, but the depth of questioning varied across interviews.
Many candidates faced mandatory cognitive or aptitude assessments early in the process, which were described as critical for advancing, often leading to a focus on time management during interviews.
The interview format varied from compressed single-day sessions to multi-week processes with back-to-back interviews, affecting candidates' preparation and stress levels.
Some candidates experienced behavioral interviews that focused on cultural fit and communication skills, which were often separate from the technical assessments.
Feedback after interviews was often lacking or delayed, leaving candidates uncertain about their performance and the reasons for their outcomes, which contributed to a negative experience.