WEX Software Engineer Interview Questions
& Process

So they had 2 rounds. First was a Technical Round where I was asked 2 DSA questions, pretty much like leetcode ones. One was hard, the minimum substring window, and the other was leetcode medium, Target Sum in Tree. I got both right, spent about 10 mins on each. Second round was Techno-managerial. They asked me questions based on my resume. Unfortunately, I didn't get through this round because my resume had a lot of ML/GenAI stuff, and they were looking for someone purely focused on development.

I went through two rounds of interviews. I wasn't a huge fan of the second interviewer; we had some communication issues. He also insisted I verbally outline every possible case before coding, which I found difficult as I think better while writing code, and he didn't seem to agree.

I applied online and heard back from the recruiter after about two weeks. First, there was a general HR call covering the basics. Then, I had a live coding exercise, which was described as a technical interview. I expected questions related to the job specs, but it turned out to be a LeetCode-style problem requiring an algorithm with a specific Big O time complexity. This type of question reminds me of my university Data Structures and Algorithms class from the 90s. While it's important to know these things, I haven't encountered many professional situations requiring such low-level algorithmic precision in my 20 years of experience, especially in low-latency environments. Frankly, if this is their daily work, it's not for me. I wouldn't have applied if I'd known about these LeetCode-style interviews beforehand, as I find them a waste of time. In my past experience as a hiring manager, these tests identified brilliant individuals who struggled with teamwork and communication. This isn't the best way to find good engineers because it's more like a university exam than a real-world problem. If you dislike Codility or LeetCode problems, don't bother with this company. I managed to find an algorithm within 80% of the time, but couldn't finish coding it due to time constraints. A crucial 'if' statement to prevent an infinite loop was missing, and the interviewer wouldn't let me add it, even though it would have made all test cases pass. Without it, the solution essentially fails.