comment on

As a person who has been hiring, firing, mentoring and generally driving techs crazy for too many years, I can give one fact and one strategy.

Fact: References are a burnt into 'Corporate Culture' and it ain't going away.

Strategy: Write your own reference template and ask former employers if they will read and sign. As an employer I like this as it saves me time. I often find with 'good' former employee's I edit UP reference that are to modest.

Outline your resposibilites and any projects you felt you excelled at and remember the Golden Rule of why Corporate USA hires someone . To either/and/or increase revenues, reduce costs, improve quality of product/service, create new product/service.

mitd-Made in the Dark
'Interactive! Paper tape is interactive!
If you don't believe me I can show you my paper cut scars!'

In reply to Re: At what stage in a job interview process should references come into play? by mitd
in thread At what stage in a job interview process should references come into play? by princepawn

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.


more useful options
	PerlMonks