Wex inc. Software Engineer Interview Guide

Candidates who interviewed for the Wex software engineer role describe two quite different experiences, so it helps to prepare for both. One candidate went through three conversations: an HR call on soft skills, a technical discussion with the team, and a final talk with the hiring manager. They report no live coding at any point. The technical conversation instead centered on real situations and challenges from past work, and this candidate received an offer. They also said the recruiter stated the required English level up front, so it is worth confirming that early.

Another candidate reports a more difficult path. After a recruiter phone screen about background and personal projects, they were asked about APIs that had been deprecated for years. They were then invited to an on-site that was scheduled on a Saturday, where an elimination-style data structures and algorithms problem, described as a medium-difficulty robot movement problem, was the deciding step. They did not solve it fully and did not receive an offer. They found the process disorganized.

Taken together, a sensible plan is to prepare specific stories about hard problems you have solved, with your actions and results, and also keep a few medium-level algorithm problems fresh in case your loop includes one. Because the two accounts differ, ask your recruiter what each stage will cover. Neither account reports an end-to-end timeline.