Had a phone screen scheduled.
The phone screen was a little disorganized. I was never told how it would work – if someone would call me, use Hangouts, or something else. The interviewer contacted me a little before the interview asking if I had Skype, to which I said no. He then just called me on my cell.
The phone screen started with a discussion about a project that I "iterated" on a couple of times. That took about 10 minutes. Afterwards, I was asked a technical coding question, which I wrote up using CodeShare. CodeShare made it really easy for me to write the code and have the interviewer review what I was writing. I explained my thought process as I was writing the code.
The technical question wasn't hard, but I didn't think through all the different test scenarios, so I had to rework a portion of my code.
What are some things you don't like about JavaScript?
What are some things you don't like about Ruby?
The following metrics were computed from 28 interview experiences for the Flexport Software Engineer role in San Francisco, California.
Flexport's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Flexport's Software Engineer interview process in San Francisco, California.