Slashdot Mirror


Resume Tips For Jobs

JerseyTom writes "SAGEWire reports that with the economy speeding up, more and more people are freshening up their resumés. They've printed an article by Tom Limoncelli, co-author of TPoSaNA, that offers specific advice for geeks writing resumes." 'Course, I'm not sure how much I believe the economy speeding up - but still good information.,

3 of 452 comments (clear)

  1. Don't... by squaretorus · · Score: 5, Interesting

    1: Try and sound interesting in your Hobbies / Interests section, you'll just come across as a twat. Be honest. And DON'T mention Stanley Kubrick. Everyone does that!

    2: Go too far ahead in 'Career Objectives'. Think 2 or 3 years, not 10!

    3: Forget to spell check the thing.

  2. some tips - by EnderWiggnz · · Score: 4, Interesting

    DO NOT put an "Objective" section at the top of your resume, they're all bullshit, never relevant and only limiting, and when you hand someone your resume, your objective is simple - TO GET A JOB FROM THEM.

    You have 2-4 inches to catch someone's eye - if you've got a college degree put it there, and next, put your most relevant work experience.

    customize your resume for the job you're applying for.

    --
    ... hi bingo ...
  3. Tips from a Chief Architect/Tech Officer by tizzyD · · Score: 4, Interesting
    Having been a CTA and CTO for many companies including IBM and many start-ups, I wanted to share a few ideas for good resumes.
    1. Make it look nice. If it looks like crap, I think your code looks like crap. Marketing is critical here.
    2. Don't include every technology you've ever touched. If you do, I love calling people on their tech knowledge. You've used Intermedia, interesting. Tell me, what's the function of a stemmer and how does it work in Intermedia? Don't be too agressive. You cannot know everything.
    3. If you put multiple tools or editors down, make sure you know them. I used to ask people what they liked about a Visual Cafe over JBuilder, and, more importantly, why. If they used BEA and Websphere, great, tell me why I would use one or the other. If you can't do that, then you don't know the tools.
    4. IMHO Certifications quite frankly are crap. They show you can take tests, not that you understand the tools or languages. Mention them later, not at the top.
    5. A style note: use verbs!!!! Developed, Created, Architected, Designed, Coded, Documented etc. Do not use sentences. I was responsibile for is a banned phrase.
    If you have any other questions or comments, just let me know. Hope it helps.
    --
    ...tizzyd