Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

But I wasn't getting the impression that was the kind of coding being referred to by the OP. I've heard from other companies giving coding tasks that exceed the size of a whiteboard - but I've never heard of any research done about the value of this.
I've never asked them to write large projects in an interview, though I've sometimes asked to see some large projects they have written (e.g. a CPAN module).

As indicated in the root node, I feel the cost of hiring the wrong person is enormous and so I feel it is well worth doing much more than a simple one hour job interview. I prefer multiple one-on-one interviews with multiple interviewers. During these interviews, candidates will be asked to write code and solve problems. Also, cultural fit is assessed (often by asking behavorial questions). BTW, Google typically perform five one-on-one 45 minute interviews after you get through screening. To offset the high cost of multiple interviews, you need to find cheap ways to screen out the glaringly incompetent and the resume liars and simple coding questions are a good way to do that in my experience. I cannot rigorously prove that all this effort is worth the cost. More details of my preferred approach to interviewing can be found in On Interviewing and Interview Questions.


In reply to Re^4: Common Software Development Mistakes by eyepopslikeamosquito
in thread Common Software Development Mistakes by eyepopslikeamosquito

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (2)
As of 2022-05-27 03:49 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (94 votes). Check out past polls.

    Notices?