Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×
This discussion has been archived. No new comments can be posted.

Interviewing Software Engineers More

Interviewing Software Engineers

Comments Filter:
  • Get a Sodoku book and ask the Dev to explain his last project. While it's stuttering and umming you do the Sodoku.
    • Sodoku? Nothing but a depth first search on the solution tree.

      P.S. Most Sodoku puzzles have multiple solutions.

      As far as the original question: pry. Ask the person exactly what they did in the project, and exactly what they wrote. A lot of candidates are nothing more than buzzword spewing morons, or they're goons that try to take credit for other people's contributions.

      If it's for a specific platform, like Windows, ask them how they would go about doing a trivial application like a calculator or a rud

  • Moo (Score:2)

    by Chacham ( 981 ) *
    Any tips?

    If you do a good job, i may leave 15%.
  • I avoid the logic puzzles and open-ended "How many gas stations" crud.

    I always ask the candidate for the most recent tech book/magazine they've read or are currently reading. On rare occasions I get the die-hard born geek candidate. More often than not, they're normal people looking for a job. Unless they've got years of experience, I always ask "Why computer science? Why not accounting or architecture? Of all the things you could have chosen to do for the rest of your life, why programming computers?"

Slashdot Top Deals

A successful [software] tool is one that was used to do something undreamed of by its author. -- S. C. Johnson

Close