What type of questions do they ask you interviewing for a C#.net programming job?

what kind of things should I be prepared for?

What type of questions do they ask you interviewing for a C#.net programming job?
Here are some of the things I have been asked multiple times (i.e. these questions tend to show up in many interviews):





What are some of the advantages of object-oriented programming, especially as it relates to .NET?





What is polymorphism?





How many objects can a class inherit from in .NET?





What is the syntax to inherit a class in c#?





What object do all objects descend from/inherit from/what is the base class of all classes?





What is an interface?





What is the difference between using StringBuilder vs the append operator?





What is the difference between a value type and a reference type?





What is a singleton?





What is an access modifier?





What is ViewState?





What is the difference between using DataReaders vs DataSets?





They will also usually ask questions about SQL:





Would you use in-line queries or stored procedures? Why?





What enhancements does SQL2005 make to stored procedures over 2000?





When should use use Views?





After that, they will usually ask about some of the projects you have worked on in the past, and ask you to describe in general terms how you solved a particular programming problem that frequently appears in that type of project.





Finally, some companies will have you write a code sample, or finish some problem, like a partially-completed project that won't compile. Sometimes they will also examine your code afterwards and have you defend your code and why you did things the way you did.





The most important thing is to be honest about what you do and don't know. If you don't know, say it immediately. If you try to fillibuster, or try to come up with some BS with "ah, um, herm" you will just sound like a fool. If you say "I am not sure about that." or "I'm sorry, I don't know." you will get much farther. Making up even one answer will pretty much kill any chances you might have had.
Reply:They'll probably ask you questions like what objects in the .net framework do what, and how are they used? What are some important considerations when choosing which objects to use?
Reply:The following should be answered by a junior developer. That is to say a developer with one - two years of experience.





Strictly C# questions:


- What is the base type of all classes in .NET


- What is an assembly


- How would you define the .NET framework


- Whats the difference between a value type and a reference type? Give me an example of each


- What is an enumeration? When would you use one?


- What is an ArrayList? What is a strongly typed collection?


- when is the virutal keyword used? the override keyword? can you give me an example?


- what is an abstract class?


- what does sealed mean?


- Can you tell me when is an object cleaned from memory?


- When would you use an indexer?


- What is a delegate? What is an event?


- What are Generics (new to .NET 2.0)





.NET Framework Questions:


- What is ADO.NET ? How is it different from ADO


- What is a DataReader? What is a DataTable? what is a DataSet?


- What is an SqlCommand object?


- What is connection pooling?


- Would you use DataSets in a web application? Why or why not?


- What is the impact of using DataSets in a web application


- Would you rather use an SqlDataAdapter to fill a DataTable or an SqlDataReader?





If you are applying for a job as a web developer you should expect questions related to the web (HTML, CSS, ASP.NET WebControls).





Same goes if the employer is looking for windows developers.





Hope my answer helps.
Reply:I work for a company currently hiring C#.net programmers.





The way the interview process works here is based on your resume. They start simple and work the way up through difficulty depending on how you answer a question.





Someone stating "I've worked with C-pound for two years" won't get very far. (C-Sharp not C-Pound) very indicative that the two years is not in a professional environment.





If you state you are familiar with Sql - they will ask you SQL questions to see how far your knowledge goes.





I mentioned I had knowledge in artificial intelligence and math so they asked me questions about AI and had me write programs that involved complicated math skills.





In short, don't lie on your resume... they'll ask you about it to see what you really know.
Reply:It is no different from a regular job interview, except they will most likely ask to see examples of your code. Some interviewers will do a technical interview, they will sit you down at a computer and present you will a problem to solve that you will have to write C# code for.
Reply:I'll assume that this is for an entry-level programming position. The short answer is it really depends on the company and the interviewer, but I can share my experiences from both sides of the table.





When interviewing for an entry level position, they don't really expect you to have too many answers under your belt. I've always been asked about projects I've worked on (if you're fresh from school, talking about school projects is fine). They'll also want to get to know your personality as it pertains to working in groups, individually, and how quickly you can pick up new skills.





If they decide to actually quiz you on specifics, it could go one of two ways - questions about .NET specifically, or questions about programming methodologies in general.


The answers already given mention quite a few things to check up on in C# specifically, and already knowing C# is helpful there. A review of the language basics before you go would be wise. Aside from that, what I've been asked frequently - and what I ask people I interview - are more general questions about programming and OOP in general. Maybe what kind of algorithm they'd use to solve a specific problem, what kind of design process they prefer to be involved in, etc. Perhaps have them write some simple example code in the language they're most comfortable with - like swapping a string in place for instance.





For the most part though, the interview will probably be more about you and your soft skills than any specific technical item.