Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

I'm often called upon to interview people for various technical positions. Whether we're hiring specifically for engineers or not, candidates should be able to be able to problem-solve and think logically. In fact, some of the best answers I've gotten have come from self-professed non-programmers.

I generally ask an "algorithm" question that can get progressively harder as I change inputs on them. I don't make the candidate code in a particular language (in fact, I encourage them to use pseudo-code). I'm only really interested in how they come up with the algorithm. As an example, I usually ask the candidate to reverse individual words in a sentence, maintaining word order (e.g., "THIS IS A SENTENCE" produces "SIHT SI A ECNETNES"). If they nail that, I change the input to "This is a sentence." and ask them to keep the capitalization and punctuation positions the same (e.g. "Siht si a ecnetnes."). And so on... I thought of a couple last night which I'll try out in the next few interviews (I'll post them if there's enough interest, otherwise just /msg me if you're curious).

Does anyone have any other interesting questions along these lines? I'm getting kind of tired of asking the same couple of questions. :-)


In reply to Algorithm questions... by myocom

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 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?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (7)
As of 2024-04-18 03:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found