Dear technical screeners,
Interviewees know how to find C# Interview Questions lists, too.
And while we might not be looking-up the answers as you ask the questions, we just might have been studying that page for the past day and a half, waiting for your call.
Thanks,
Mr Cleek
I am hoping against hope never to need to learn C#.
C#’s not bad.
it’s close enough to C++ that it’s easy to pick up. and it’s got a bunch of neat stuff of its own, too. i still prefer C++, but i haven’t seen a single C++ job since i’ve been looking.
Say, is it better to write C# or C??
I mean, or C♯
i believe the former is acceptable, though it’s pronounced like the latter.
I am desperate for another C++ programmer but will have to wait at least 6 months before I’m allowed to look.
“C Sharp.” That’s good to know. I bet calling it “C pound” would spell a premature end of the interview.
“C octothorpe” or “C tic-tac-toe” might get a laugh.
What is it with the # key being called ‘pound’ in the US? It confuses us Brits who know the pound as £.
beats me… esp when we don’t have an ‘ounce’ symbol to go along with it.
“octothorpe” is an awesome term to know. Thanks!
There’s got to be crossover potential here between “Jim Thorpe All-American” and “Octopussy”, I’m just not sure how to work it…
That’s actually a pretty good list of questions. At least they’re generally relevant in the real world.
Other stuff I’ve asked and answered as C# questions with some practical relevance are:
Explain how the C# garbage collector works. What are the garbage collection “generations”, and why are they needed?
What is a strong-named assembly, why and how do you create one.
What are the options for interoperation between a managed and an unmanaged environment. How are these different if the unmanaged code is COM.
What are application domains and contexts.
What does it mean for an object to be “context bound”.
Pseudocode how a class would implement IDisposable and explain the implementation.
Pseudocode a singleton implementation and explain.
C# is a perfectly good language. I miss C++ sometimes, but what I mostly miss is Unix. All of the Windows OS’s seem heavyweight and overbuilt in comparison. Although at this point, were I to move back to Unix, I’d probably have to relearn everything.
Further nerdness…
Another topic I expect C# interviewees to be able to discuss intelligently is the use of events and delegates in asynchronous operations, especially I/O and distributed function calls.
That also gets into threading and techniques for synchronization.
Good luck cleek, hope you find something really good and interesting!
those are pretty tough questions, IMO.
i will research them, and blow the socks off the next interviewer i encounter.
well, maybe not ‘blow’. i’m not that desperate. i’ll impress his socks off . yeah, that’s the ticket.
They’re a little advanced but are all actually really useful for building C# stuff in the real world.
If you have the time to dig in, I think you’ll enjoy it. In a sort of geeky way, natch.
Most of this stuff is discussed pretty thoroughly on the MSDN doc pages. I can point you to some other resources if that’s helpful, lemme know if so.