@stackupdev
Senior Engineer C#
Nothing here yet.
Nothing here yet.
Some great questions here for beginners. For a dot net developer these days, say in a two-hour-long interview, the first 45 minutes would be dedicated to OOPS and Core C# concepts. So these sets of questions are going to come in handy every time for everyone. Would like to add that if one now has say greater than 5 years of experience, most of the C# part of the interview will revolve around few topics like: A much detailed comparison between Interface & Abstract, when & when not to use any of those How overriding would behave based upon the way an object is created. Directly, using the parent class, etc. It revolves more around which method will be called if the object is created this way Thread questions come up less these days as most modern applications rely on async-await. Real-life examples really help showcase that one understands how asynchronous programming works. In terms of design pattern, the question I have recently faced was more problem-oriented with the solution is figuring out which design pattern solves the problem. LINQ and Lambda functions are also very much asked as they are the go-to implementation style these days