It was very long and drawn out, with lots of redundancy. I had to do a total of three coding interviews, plus a behavioral and project deep dive. I wish I would have been cut earlier so I could spend less of my time during the holidays interviewing. I spent a total of six hours on interviews that definitely could have been three or four (code, behavior, project). But they pay more than my current role, so I guess it's their loss too.
I don't think the SE IIs were the best choice for the coding interviews, especially since it was for their same position, and I found a lot of variance in "quality." The senior engineers were more helpful. I was told by one of my interviewers that a lot of people get tripped up by solving smaller problems and go for a built-out solution.
Tl;dr: Don't apply if you aren't good at coding interviews.
Create a checkers solution (3 part)
The following metrics were computed from 6 interview experiences for the Flexport Software Engineer II role in United States.
Flexport's interview process for their Software Engineer II roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Flexport's Software Engineer II interview process in United States.