Menu

Post image 1
Post image 2
1 / 2
0

I used to fail .NET interviews for not giving the “expected answer”

DEV Community·Ayman Atif·27 days ago
#yx3YH3Zx
Reading 0:00
15s threshold

I’m a .NET developer. I can build production-ready applications, APIs, and work with databases. In the past, I kept failing interviews and getting rejected or ignored, mostly because I wasn’t giving the “expected answer”. I could solve problems in real code, but I struggled to explain things in the structured way interviewers wanted. I thought performance should matter more than theory, but interviews don’t really work like that. You have to answer first, then prove yourself later. I even got hired once just because I memorized definitions and answered correctly, even though I wasn’t actually strong in what they asked. I had to learn everything on the job and eventually resigned after a short time. Now, after going through many interviews, I understand the process much better. I know what they are looking for, how questions are framed, and what kind of answers they expect. Still, it’s interesting how different real-world development is from interview performance.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More