Skip to main content

How Not to Get Hired

Image
By
Just a tip from a hiring manager here.  If your resume starts out with the heading "SUMMMARY", I'm highly likely to toss it in the trash.  Not because I want to hire people who can use spell checkers, but because to me it indicates that you either can't or won't be bothered with details.  Or that you consider how you present information unimportant.

If you're in the top 1% of coders, maybe you can get away with this.  Otherwise, please run a spell checker on your resume before sending it in.

(I'm a really nice guy so I finished reading the resume; the rest was just as bad, though.)

Comments

  1. dossyshiobaraJune 10, 2005 at 7:18 PM

    John,

    I bet that resume also claimed "Excellent attention to detail" and "Excellent oral and written communication skills."  *chuckle*

    I swear, I'm about ready to create a new web startup: The Résumé Hall of Shame.  (Yes, resumehallofshame.com is still available, muwhahaa.)

    ReplyDelete

Post a Comment

Popular posts from this blog

The problem with creation date metadata in PDF documents

By
Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

http://www.msnbc.com/rachel-maddow/watch/maddow-to-news-orgs-heads-up-for-hoaxes-985491523709

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…
Post a Comment
Read more

Personal Web Discovery (aka Webfinger)

By
There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

…
13 comments
Read more
By
The hill outside Google HQ, about a 270 degree panorama.
1 comment
Read more