Real, anonymous reports from people who interviewed for Software Engineer at Flexport, newest first and distilled into what to expect across the loop.
After a recruiter call, I got pulled into a fairly structured sequence. The recruiter was friendly and clearly walked through the company, the role, and the team, then asked me to share about myself and a recent project I’d worked on.
A recruiter reached out and then sent me an invitation to schedule a phone interview via Coderpad. The whole coding screen was about an hour long. I got through the process, but it dragged out after that—I was rejected roughly three weeks later. What stood out was how straightforward the scheduling and live coding part felt, followed by the slow, quiet wait that ended with no conversation or offer.
The interview process typically begins with a recruiter call, followed by multiple technical rounds focusing on coding and design, and often concludes with a behavioral or hiring manager interview. Candidates noted varying timelines, with some experiencing a quick progression while others faced delays and a lack of clarity on next steps.
Candidates encountered a mix of coding challenges, often resembling LeetCode problems, with some focusing on data structures and algorithms while others incorporated real-world scenarios. The coding rounds were generally described as demanding but constructive, with interviewers fostering a friendly atmosphere.
For many candidates, system design was a critical component, especially for senior roles, with tasks requiring thoughtful architecture and state management. Feedback indicated that performance in system design significantly influenced overall outcomes, and candidates were expected to demonstrate a polished approach.
Behavioral interviews often revolved around past experiences, conflict resolution, and teamwork, with interviewers seeking to understand candidates' thought processes and decision-making. The atmosphere was generally conversational, but some candidates reported feeling pressured or receiving vague feedback.
Candidates expressed mixed feelings about the overall experience, with some appreciating the friendly interviewers while others noted a lack of closure or feedback after interviews. Many reported feeling uncertain about their performance and the reasons for rejections, highlighting the need for clearer communication.
The difficulty of interviews varied, with some candidates finding the challenges manageable while others felt overwhelmed, particularly in system design. Overall, candidates were expected to perform at a high level, with a strong emphasis on both coding accuracy and the ability to articulate thought processes.
