that's actually not so bad. the interviewer was asking theory and procedure questions, not 'how would you write a regex for LaTeX to HTML parsing?' (god, i thought i asked bad questions!)
there's really no way to prepare, unless you're going to get a round of phone interviews, and you can brush up on the weaknesses that the first interviewer uncovered.
phone interviews, at least the way my company uses them, are just quick screens ( ~ 20 minutes ) to see how extensive someone's perl knowledge is. i ask questions about OO-perl ( and look for textbook answers - that at least shows that someone has read about it, if not worked with it), namespaces, use vs. require, module use ( this question does show a lot about coding style), and similar theory-based questions. and they seem to work just fine.
-
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.
|
