There was a screening process with the recruiter, followed by my first "code interview" with a Senior Manager. It was a good experience—more focused on code review and advice on how to improve, rather than strict problem-solving exercises.
Then came the second technical interview, and it was, without a doubt, the most bizarre interview I’ve had in my 20+ years in Software Engineering.
What I was expecting:
- Coding exercises to test different problem-solving scenarios
- Meaningful questions about optimizing LINQ queries
- Engineering problems designed for actual engineers
What they actually asked:
- "Describe what happens when you click on the UI, all the way to reaching a Controller."
- "What does 'https' mean?"
- "What is the difference between Single() and First()?"
- And here’s the best one: "When do you actually access the DB when executing a line like dbcontext.mytable?"
(What they really meant to ask was, "When is the data materialized?")
The worst part? They assumed I didn’t know the answers. Let me tell you this—if a group of Senior Developers doesn’t know how to conduct a proper interview, just run away from that place!
After 24 hours, I withdrew from the position. I couldn't care less if they were interested in me—I’m definitely not interested in working there
