Real, anonymous reports from people who interviewed for Software Engineer at Flex, newest first and distilled into what to expect across the loop.
After applying, I went through an ATS resume screen and, once that cleared, HR reached out to schedule a phone screening. The phone screen covered details about my background and experience, and it felt pretty organized from the start. About a week later, I moved into the follow-up rounds where the technical side got tested. Those interviews weren’t overly drawn out, and the overall vibe stayed professional and calm.
I went through three total rounds and felt good about my performance in each one. The early and middle conversations went smoothly enough that I expected to hear back from real people afterward. Instead, I reached a final stage where there was still no meaningful response—then I was told no by an automated bot rather than a direct follow-up.
The interview process typically starts with a phone screen followed by technical interviews, often including a coding assessment and HR discussions. Candidates noted that the overall timeline felt efficient, with many reporting a duration of around three weeks from initial contact to final decision.
Candidates experienced various technical assessments, including live coding exercises, SQL queries, and discussions on projects and technologies relevant to the role. The technical rounds were often described as demanding, requiring a solid understanding of software engineering principles and practical problem-solving skills.
Behavioral interviews focused on candidates' past experiences and fit within the company culture, often utilizing structured storytelling techniques. HR rounds were generally described as polite and professional, aiming to clarify expectations and company policies.
While many candidates appreciated the clarity and professionalism during the interviews, some expressed frustration with the lack of meaningful feedback or closure after the process, particularly when decisions were communicated via automated messages.
The overall tone of the interviews was often described as friendly and low-pressure, with interviewers being approachable and supportive. However, there were instances where candidates felt the environment became tense or disorganized, particularly during technical assessments.
Candidates reflected on the importance of preparing for both technical and behavioral questions, emphasizing the need to be ready for a range of topics, including specific technologies and soft skills. Some wished they had practiced more coding under timed conditions.
