I had a more engineering-deep interview path that leaned heavily into web back-end and database topics. The technical discussions covered things like API work and status codes, plus core C#/.NET Core and ASP.NET Core concepts. I also got pulled into database specifics—SQL Server, Entity Framework Core, stored procedures, and even related tooling—along with LINQ and stored-procedure style thinking.
There was a strong practical feel to it: we talked about joins and optimization, and the questions tied back to building and debugging real requests rather than abstract theory. I remember going through an interview cadence that included a phone technical coding round, then additional technical discussion with a team lead, and a later interview with a different interviewer who continued probing the same general thread.
> 1 year
Difficult Negative Parsippany, NJ
The process felt oddly performative to me, and the details matched that frustration. My first step went well over Zoom and felt like a genuine conversation. That made me optimistic enough that when the recruiter invited me for an onsite, I budgeted real time and money for travel to Parsippany.
At the onsite, the tone shifted sharply right when the manager joined. The interview turned hostile and disrespectful in a way that stood out as unprofessional, especially when I tried asking questions. After that, two developers joined for their rounds back-to-back—both seemed more approachable, but I could tell they were exhausted and just going through the motions.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
