Real, anonymous reports from people who interviewed for Software Engineer at Webmd, newest first and distilled into what to expect across the loop.
After I applied, I got a recruiter call and then the process moved pretty quickly into an online assessment. The test mixed multiple-choice questions and a few hands-on coding items; one screen in particular was centered on SQL, while other versions leaned into DSA-style questions. I remember having to draw or explain something visually during the coding part, and the flowchart requests made it feel less like just typing code and more like communicating how I was thinking.
My process felt short and straightforward. I started with a recruiter-to-assessment flow: first there was an aptitude-style round, then a technical session where the prompt was described as easy LeetCode-style work—either completing code or debugging it. The whole vibe was lighter than many technical screens I’ve done before, and the interview didn’t drag.
The interview process typically begins with a recruiter call followed by an online assessment that includes multiple-choice questions and hands-on coding tasks, often focusing on SQL and data structures. Candidates should prepare for a mix of aptitude and technical questions, with an emphasis on practical problem-solving.
Candidates can expect multiple technical interviews that focus on resume-related topics, practical coding problems, and system design questions. The difficulty is generally average, with a mix of algorithmic and scenario-based questions, so practicing LeetCode-style problems and system design is advisable.
The final stages usually include a behavioral interview with HR, focusing on cultural fit, communication style, and logistical details about the role. Candidates should be prepared to discuss their past experiences and how they align with the company's values.
Onsite interviews can vary significantly, with some candidates reporting a structured day of back-to-back interviews while others experienced a more conversational style. It's important to be ready for both technical assessments and discussions about past projects.
Candidates often report a lack of clear communication regarding the outcome of their interviews, with some experiencing long delays before receiving feedback. It's beneficial to follow up proactively after the interview to seek clarity on next steps.
The overall experience can feel rushed, with some candidates noting that the quick pace leaves little room for recovery after technical assessments. Being prepared for a fast-moving process and managing expectations around the timeline is crucial.