On Fri, 21 Sep 2007 15:18:30 +0100, Kevin Palmer <[EMAIL PROTECTED]> wrote:
>Ok,...My thoughts... > >I think it should be a balance of questions.. > >Generally when I interview i... > >1. Ask some questions to generate thought processes (I want to get an >idea of how logically the candidate thinks - this could involve writing >a simple string swap algorithm or perhaps be a small logical question..) >I think it's more about the thought processes behind it than the >knowledge of how to do it. I completely agree. > >2. Ask some selected questions of technologies I require for a >particular job (i.e. What does the candidate know about OLEDB?.. >ODBC?,.COM/ATL, Reflection, Sockets etc. etc.) I completely agree. > >3. Ask some OO design related questions... i.e. What OO concept would >you use to.... And how would you structure an application to ...... Yep > >The balance of these questions all depend on what type of employee you >want... If you need someone to build structured middleware apps then >more OO questions are advantagous and if you need someone to write >back-end code for a process-plant type system then more logical tests... > Yep. >Kev Yes....pretty much where I'm coming from....I posted the question mainly because I thought the examples of 1. I think are a bit low level and C like...asking someone to reverse a string in place...i.e. without allocating a new buffer etc to write it into would seem slightly odd from a C# programming perspective. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
