Real, anonymous reports from people who interviewed for Software Engineer at Brooksource, newest first and distilled into what to expect across the loop.
I started with a recruiter outreach and did a phone screen to talk through my background and what I was looking for. After that, I had a second, simpler experience-focused interview with the same recruiter. The pacing felt straightforward and low-pressure, and it mostly served to align on the role and my fit.
My process began with a recruiter contact, and the first call was an intro that barely felt like an interview. It was more about learning what the opportunity was and getting enough context on my background to decide whether to move forward. Shortly after, I had a follow-up call that went a bit deeper but still felt like it was setting the stage for the real interviews.
The initial contact with the recruiter typically involves a straightforward phone screen focused on background and role alignment, with varying levels of professionalism and communication quality noted by candidates.
Candidates experience behavioral interviews that emphasize fit and communication, often feeling supportive and conversational, especially during discussions with team managers.
Technical interviews include practical problem-solving discussions rather than high-pressure coding challenges, with some candidates experiencing online assessments that are less interactive.
The overall interview process is generally described as organized and structured, with clear steps from recruiter to client interviews, though some candidates report frustrating delays and lack of follow-up.
While many candidates appreciate timely communication during the process, several report issues with lack of closure or follow-up after interviews, leading to a negative experience.
Candidates report a mix of positive and negative experiences, with some feeling well-prepared and respected, while others express frustration over unprofessional interactions and unclear outcomes.
