I used to fail .NET interviews for not giving the “expected answer”, now I understand them better

I used to fail .NET interviews for not giving the “expected answer”, now I understand them better

posted 1 min read

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 the 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 ended up learning 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.

3 Comments

2 votes
1
2

More Posts

The Senior Angular Take‑Home That Made Me Rethink Tech Interviews

Karol Modelskiverified - Apr 2

Optimizing the Clinical Interface: Data Management for Efficient Medical Outcomes

Huifer - Jan 26

The Audit Trail of Things: Using Hashgraph as a Digital Caliper for Provenance

Ken W. Algerverified - Apr 28

AI Reliability Gap: Why Large Language Models are not for Safety-Critical Systems

praneeth - Mar 31

I Wrote a Script to Fix Audible's Unreadable PDF Filenames

snapsynapseverified - Apr 20
chevron_left

Related Jobs

View all jobs →

Commenters (This Week)

2 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!