Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Well dont exagurate too much. i think it will backfire on you if you do so.

Normally when i wrote an application (mind you i mostly do this type of stuff on good old paper) it consisted of an application letter (where i found the ad, why i'm apllying for the job and why i think i might be the right one for them), my curriculum vitae, andadditional documents (like training certifications, references and such).

The magic normally is in the application letter itself. it is hte central partof your application. the better you understand what the company where you are apllying wants the better you can answer the question why you are exactly what they seek. Important here is to be honest. dont make claims you cant follow through instead list your strengths that apply and back them up with certificates or references if you have some. And dont try to get the application letter longer than max 2 pages. Most people wont read too long application letters. The font size schouldnt be to small either it should be easily readable. Letting a friend or realtive proofreadin git is always a good idea too.

And now good luck on the hunt :)

--
"WHAT CAN THE HARVEST HOPE FOR IF NOT THE CARE OF THE REAPER MAN"
-- Terry Pratchett, "Reaper Man"


In reply to Re^2: Always someone better than you? by Fengor
in thread Always someone better than you? by Ace128

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 goofing around in the Monastery: (5)
As of 2024-03-29 14:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found