During the search period, your son needs to be busy writing OSS. Patches, documentation, etc. will all buy him some good 'street cred'.
This is one of the neat win/win things about OSS. He gets credibility, the community gets a few patches and maybe some better documentation. Depending on the work, it could even be part of a portfolio and would certainly be resume-worthy.
I would be *very* interested in a candidate who had spent time productively
helping others this way.
Update: I struck 'helping others', because it sounded like working on OSS is purely altruistic, and I don't think that's actually correct. Everybody gets a benefit, even the author, so it's far from selfless. As a matter of fact, I find it completely acceptable to do it for selfish reasons (self-education, self-enrichment, improve employment prospects, search for glory, software *exactly* how you want it, whatever floats your boat.)
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.