Real, anonymous reports from people who interviewed for Software Engineer at Becton Dickinson, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role in a mid-level, team-and-manager workflow over roughly a month, with a lot of behavioral-to-fit questions and some light-to-moderate technical content, but logistics and timing issues showed up.
I experienced a generally professional, organized Software Engineer hiring flow that took about a month, with recruiter-led scheduling and clear step progression.
The interview process typically spans about a month and includes multiple rounds, often with a clear progression from recruiter screening to technical and behavioral interviews. However, candidates reported delays and communication issues that could extend the timeline significantly.
Candidates frequently encountered a strong emphasis on behavioral questions aimed at assessing fit, with prompts like 'tell me about a time' being common. This focus on interpersonal qualities often overshadowed technical depth in many interviews.
While some interviews included technical rounds, the depth varied, with many candidates reporting a mix of light to moderate technical questions, often centered around practical knowledge and specific technologies like SQL.
Several candidates experienced panel interviews, which could include multiple interviewers focusing on both behavioral and technical aspects, but some reported disengagement from panel members, impacting the overall experience.
Many candidates noted issues with follow-up communication, including delays in feedback and a lack of clarity after final rounds, leading to a feeling of being ghosted despite positive interactions during interviews.
Candidates suggested that aligning preparation with the specific technologies and behavioral themes emphasized in the interviews would be beneficial, particularly focusing on practical examples from their past experiences.