Convoy Software Engineer Interview Questions
& Process

I applied online and a recruiter got in touch quickly. We had a brief call where they told me about the company's growth, its direction, and new technical leaders. Then, I had a phone screen with an engineer. It was helpful for me to see if Convoy was a good fit, and we found we'd worked at the same place before. The coding challenge was straightforward, taking about ten minutes to discuss and code. We then spent another twenty minutes talking about how to make the code production-ready, potential scaling issues, and identifying bottlenecks. The next part was an onsite interview, which included four hour-long sessions: two coding interviews, one problem-solving interview, and one system design interview. The technical problem-solving was pretty standard, similar to LeetCode or HackerRank problems, and studying engineering blogs from other companies would have been enough prep. What was different was that over half of each interview focused on behavioral questions. This was actually the tougher part, in my opinion. You need to be ready to talk about everything on your resume and really understand the company's values. They went deep into each project I'd done, my specific contributions, the choices I made, my biggest wins, and how I worked with others. I left feeling more drained and challenged than from any other interview, like my entire career was on display. But I was also really inspired. Each interviewer was clearly passionate about the company's mission, their work, and maintaining the company's high standards, both technically and culturally. A few days later, I had a final hour-long interview with an engineering director. This was purely behavioral, focusing again on my resume. We discussed my contributions, strengths, weaknesses, and my views on management for each role. It was also valuable to hear about his experiences at the company and his plans for future growth. Later that day, I received an offer.

The first part was a mix of behavioral questions using the STAR method and some Leetcode questions. Then there was a second round with a technical deep dive and systems dive, plus another behavioral interview. The interviewers were prepared, friendly, and made it a good experience.

It started with a technical screen, followed by a final round that included technical and system debugging interviews. While the interviewers were great, the recruiters were slow with offers, making me wait over a month for a decision after the final round. To make things worse, about two months later, they ended up rescinding most of the offers.