Real, anonymous reports from people who interviewed for Software Engineer at WePay, newest first and distilled into what to expect across the loop.
After the recruiter call, I ended up walking through a pretty standard flow: a phone screening followed by a couple of technical rounds and then a hiring-manager-style conversation at the end. The technical portion felt like coding interview fundamentals rather than anything exotic—an easy to medium kind of problem where I had to actually talk through my thinking while I worked.
My process started with some confusing signals about what I was walking into. I was told the phone screen would be algorithmic and more like a LeetCode-style round, but the actual practical work ended up being front-end related with JS/HTML/CSS. The question itself wasn’t hard, but the mismatch was unsettling.
The interview process typically starts with an online assessment, followed by a recruiter screening, technical phone interviews, and an onsite interview that includes multiple coding and design rounds. The overall timeline can vary, often stretching from days to weeks depending on scheduling.
Candidates can expect a mix of coding challenges during technical interviews, often including LeetCode-style problems and algorithmic questions that require clear explanation of thought processes. The difficulty can range from easy to medium, with some reports indicating a focus on depth and specific problem-solving approaches.
Behavioral interviews are integrated into the process, with an emphasis on communication skills and how candidates articulate their thought processes during technical rounds. Interviewers often assess fit and clarity of expression, which can significantly influence outcomes.
Several candidates reported issues with communication and logistics, including missed calls, unclear instructions, and inconsistent feedback throughout the process. This can lead to frustration and uncertainty about evaluation criteria and next steps.
Onsite interviews typically involve multiple rounds that assess coding, system design, and behavioral aspects, with some candidates noting a high-pressure environment and specific expectations for problem-solving approaches. The experience can vary widely based on interviewer dynamics and clarity of questions.
Candidates often leave the process feeling uncertain about their performance due to the lack of clear feedback and communication regarding outcomes. Many expressed that even strong technical performances did not guarantee offers, highlighting the subjective nature of evaluations.