ASP.NET C# Developer interview

[Izi]

So I have to interview a C# developer next Tuesday to fill an intermediate ASP.NET Developer role. The role will include developing website using ASP.NET, C#, WebForms and MS SQL Server. Front end CSS/HTML is not important.

I have never done this before so can some kind peeps help me put some questions together? What are your personal experiences of interviews?

Obviously I will be look for the obvious understandings of OOP, good application structure, SVN use and testing etc, but should I actually give the person a small test? What else should I do?

Thanks in advance!

 

[Spyhop]

Do any coding test on an actual computer, ideally their own laptop if possible because they will be comfortable with the dev environment. Writing code with a pen on a whiteboard in interviews is contrived nonsense IMO

 

[Tripnologist]

I would definitely come up with a task for them to complete for you.

Do give advance warning that they will be required to code something but don't tell them what it is until they're about to start. I'd also allow them to bring in their code library.

Pros of this are:

- You'll be able to get an idea of their existing knowledge and skills by seeing how much or little they have to reference Google.

- Even if they have to look a lot of things up, the speed at which they find the information they require and put it to use will tell you how resourceful they can be when confronted with something they don't know how to do.
(Let's be honest here, in the real world, this happens quite a lot.)

- Some people may think that allowing the code library is kind of cheating, but which would you prefer, an employee who's prepared and can streamline his work, or one who will have to write everything from scratch because they haven't taken the time to prepare?

 

[brainchylde]

- You'll be able to get an idea of their existing knowledge and skills by seeing how much or little they have to reference Google.

DOn't get hung up on this - no-one can know everything. If they start googling how to write a loop then you can get worried but googling say, methods contained in some .NET class, I would say is fine and normal behaviour. Google can be a great time saver, even for your most advanced developer.

 

[Makhaira]

Don't forget to assess them as a person too in the interview - just because someone ticks the boxes for having the skills does not mean that you want them working at your company.

Consider also quizzing them about your company - have they made the effort to do any research, do they understand the field you work in, and what your customers and competitors are doing? What are their expectations of the role, and their longer term aims, etc.

Remember that you are recruiting an individual, not a skill, so there is much more to consider than just their coding ability.

 

[Tripnologist]

DOn't get hung up on this - no-one can know everything. If they start googling how to write a loop then you can get worried but googling say, methods contained in some .NET class, I would say is fine and normal behaviour. Google can be a great time saver, even for your most advanced developer.

That's why I added in the next point. There is nothing wrong with using Google to find the solution to problems, I do it all the time, but what does matter is how quick they're able to find the information they need and put it into use.

 

[Randomface74]

I like giving them bits of example code and saying "what's wrong with this?"

 

[Izi]

Great advice people, thanks.

I think I might ask them to build a very small web app. Something which should only take an hour or two, is that fair? How long have you been kept at interviews for in the past?

 

[Makhaira]

Great advice people, thanks.

I think I might ask them to build a very small web app. Something which should only take an hour or two, is that fair? How long have you been kept at interviews for in the past?

Can be all day affairs, depends on the company. Just make it clear before they arrive how long they will be there.