Replies: 2 comments
When advertising a position, I ask for a web-based list of links to previous work, accompanied by a description of the applicant's involvement with each site.
e.g., Did you do the whole site? Shoot the photos? Write the copy? Design the logo? Do the programming? Do the coding? What role did you play on the web team?
I also want descriptions of previous web work even when the final product is no longer online.
I'm sure to have the applicant deconstruct some of his sites (and other unfamiliar sites too) during the interview and talk about them in-depth. Anyone can take a skills test. I want to see their mind run through an obstacle course.
Posted by Jack "No Interview For You!" Schonchin @ 01/11/2002 02:13 PM EST
We follow similar procedures in my day job and get a bit irritated when applicants are strangely vague about their exact involvement. We've also sometimes used simple coding tests when hiring and been stunned by the results - only something like 1 in 20 produced stuff that even worked.
At the same time, we've hired people with little or no portfolio and hopeless test results, simply because at interview it's been clear they're keen and quick to learn. Don't be too rigid or you'll miss some very talented people, and don't think a good portfolio will automatically get you the job.
Then there was the time we couldn't decide between two candidates for a temporary position and ended up flipping a coin...
Posted by Matt "heads they get hired..." Round @ 01/12/2002 07:13 AM EST