Iamthefallen's Journal: Ask the dot: Interviewing

But this time I'm behind the desk rather than in front of it.

Or well, my desk is facing a wall, so technically I'll be behind the desk, and they'll be even further behind it.

We've opened up a position for a web developer and are starting to accept resumes. We have an idea of what we want but will hammer it out in more detail in the next few weeks before we bring people in.

The position is posted on careerbuilder (If you want a direct link, send me an email or ask in the journal, but obviously you can find it anyway with a minimum of detective work):

Applications Developer
 
[Company] has an entry-to-mid level web-based applications developer position available at its corporate office in Columbia, SC.
 
Candidate will be involved in application development with an emphasis on front-end web-based development. Please note this is NOT a web designer position.
 
The candidate must have 2+ years of full-time professional application development experience using Microsoft ASP/VB.NET, SQL Server, and Visual Studio. Experience with ASP.NET 2.0 and Visual Studio 2005 are preferred.
 
Education requirements include at least an associate degree in computer science, science or engineering.

Focus will initally be on producing ASP.Net pages/applications rapidly. Reporting experience (Report server, Crystal etc) would be great as would some basic system understanding. We're a small shop so you have to wear a couple hats in the IS dept. We're definitely not looking for an architect or senior developer, but some SE/SDLC experience would make my life easier.

The sysadmin and I will focus on the technical part of it, leave the stupid HR questions to the bossman hisself. Having never done this before, I'm not entirely sure what I should ask or test. I want to weed out the obvious bullshitters so essentially, if you can write basic CRUD stored procedures, and build ASP.net forms around them, you'd pass the technical part. An ability to solve problems, being a thinker and learner, is more important than being able to write code on a white board on demand.

So any suggestions out there on tests, questions, or approaches?

Is it a good idea to put them in front of a computer and ask them to produce a form? Do you throw them curve balls? Is it fair to give them a very difficult (Impossible?) task just to see how they handle it?

Most of my interviews have been fairly non-technical, I've never been asked to write code at an interview so I'm curious what those who have done that, or asked someone to do it, thinks about it.

Random opinions and other thoughts appreciated, thanks.

Sniff Test

[Shadow Wrought]

Just remember, if you don't like them in the interview, they're not going to get any better when you work with them. That likely has more meaning in the legal field, but still...

Two things

[BWJones]

Well, the approach I have always taken with interviewing has been twofold.

1) I evaluate their qualifications and their abilities (technical, writing etc...)

and perhaps more importantly,....

2) I sit down informally with them and just talk.... If I conclude this is a person that I would consider inviting to my home for dinner or if I would be interested in eating dinner at a restaurant with them, then they pass the test. If I don't want to eat dinner/lunch with them, then I don't want to work with them.

Not being an ASP/Microsoftie guy

[rk]

I can't speak to the kinds of specific technical questions you'd want to ask. I've got great ones for C, Perl, and Python programmers, though!

I like to sit down with a candidate and spend 15 minutes working on a difficult problem that neither of us knows the answer to[1]. The idea is to actually simulate working with this person, not to see if they're an ultra-genius. In my case, I like to see if this person will just give up or dig in and try to solve the problem, and if I can stand working with them.

Re:

[Iamthefallen]

It's better to hire someone who is sharp and a self-starter even if their technical skills are a little shaky.

That's exactly it. We're in a fairly unique business with some rather strange approaches to some things. There's no way we can find someone who understands the business and software development, so no matter what, there's going to be some significant ramp-up time.

random comments

[Red Warrior]

I don't like the idea of putting them (or being put) in front of a computer. I'd rather see some pseudocode or a verbal explanation. Why? They might be tripped up by an unfamiliar (to them) configuration. I've had that issue sitting at other's workstations in my group. I don't think it's right to have equipment issues impact the hiring decision. Unless they're being hired to troubleshoot, that is...

I don't like the idea of "impossible" tests to see what they will do. For the same reason I don't like "trick"

What I wish someone would ask me

[Com2Kid]

"Lets just cut all the BS out, what will your work be like"? That'd be my dream question, I'd get a job easily then, if anybody believed my answer. :)

Oh, and also sit down and chit chat a bit before hand about general technical topics. Have they experience with anything outside of what they were taught? Do they know about wikis? Could they argue /against/ using ASP on the server side? Make them then argue for using it. If someone cannot argue both sides of it, they probably don't have an understanding

Re:

[Iamthefallen]

You know what I want to ask?

What's your Slashdot UID.

Really.

It's surprising how many programmers I've worked with that aren't part of any online community except MySpace... Never heard of Fark, SomethingAwful, Slashdot, Penny Arcade, Think geek, User Friendly etc etc etc. I want someone who's interested in the world of computers and general life online. Someone who reads technical articles on Slashdot/Digg/Whatever for fun.

Re:

[Com2Kid]

When I go into interviews, no one there knows what /. is....

One interview last spring for a summer internship, I was denied the internship (as a programmer...) because I was "too technical".

Figure /that/ one out!

Re:

[TechnoLust]

I've been interviewing people, you might peruse my recent JEs for stuff I've written. Also, don't forget that most geeks have non-computer geek interests too. I've know guys that are into winemaking, cooking, and a LOT who are into music (music and math both being very math oriented). I always ask what people's hobbies/interests are.

Re:

[Bill Dog]

A great angle. You might consider approaching it in two parts:
1) Up-to-date broad knowledge of computer/tech "current events", and
2) Expanding in-depth knowledge of strategically-selected technologies.

Being an a-hole developer (as someone on /. really wants to think of me), I would hire someone like me, who is interested and tries to stay abreast of technology directions, and someone who also spends considerable time taking classes and reading technical books to advance his/her capabilities and take existin