Real, anonymous reports from people who interviewed for Software Engineer at WebMD Medscape, newest first and distilled into what to expect across the loop.
After applying, I started with a recruiter screen, then the process moved pretty quickly into an online assessment. The assessment felt on the easier side: it leaned heavily on SQL multiple-choice questions, and it didn’t try to trick me with abstract theory.
My process started with a technical flow that felt like it was designed to dig into both day-to-day engineering and how I think about systems. I had multiple rounds, beginning with an interview led by a lead developer where the questions ranged from C# and .NET MVC/Core into topics like microservices versus monolith, OOP basics (like abstract classes versus interfaces), access modifiers, and dependency injection. We also covered practical API concepts—routing, versioning, rate limiting, and even performance tuning—and I was asked to write MVC-style code on a notes app for get/post flows with hardcoded product details.
The interview process typically begins with a recruiter screen followed by a technical assessment, which is usually straightforward and focused on SQL and coding skills, leading into multiple technical rounds and concluding with an HR conversation.
Technical interviews often include hands-on problem solving, algorithm/data structure questions, and scenario-based discussions, with some candidates experiencing a shift in difficulty from earlier to later rounds.
Candidates frequently report a lack of communication regarding next steps after interviews, leading to frustration and uncertainty about their status in the hiring process.
Interviews often emphasize the company's culture and management style, with some candidates noting a strict 'no excuses' philosophy that shapes expectations around performance and accountability.
Candidates experience a variety of interview styles, including technical questions, behavioral assessments, and even management-focused discussions, which can create a more rounded evaluation but also lead to confusion about expectations.
Candidates express a desire to better prepare for the specific technologies and frameworks used by the company, as well as to anticipate the intensity and depth of questioning during technical rounds.