Showing posts with label lessons learned. Show all posts
Showing posts with label lessons learned. Show all posts

Tuesday, March 31, 2015

Editing a resume

A couple quick thoughts on resume editing:

Don't include your salary history.
It's nobody else's business what you made. Even if you were government-employed, and your pay is a matter of public record, make people ask you for that information. Think of it this way - if you don't include it, and they ask, and they already know the answer (maybe they had that same job at that same pay grade, for example), and you tell them what they already know, then you've proven once again how honest and upstanding you are!

Don't include your references.
This is putting the cart before the horse, and exposes your friends and contact list to potentially needless phone calls, *especially* if you put your resume on a publically searchable website.

Employers care about the five W's , yes, but only after they've either skimmed your information or had it electronically scored, or both. I do suggest you address these things in your resume, sure, but do it as story telling, not as facts and figures.

  • who
  • when
  • why
  • where
  • how much

So, what's the point? Why do any of this at all? Why not just keyword up a version? Well, yes, and I recommend a keyword heavy version from a text-only resume point of view where you know your information is going to get scanned by searches (e.g. Monster, etc.).

But in general, think about it from a hiring manager's point of view. He wants to know within seconds whether or not you can

  • stop his pain
  • stop his groups pain
  • solve a problem
  • save the business money above what it costs him to hire you

If you're going to craft a traditional resume, in any of its forms, then consider how you can tell a 2-3 sentence story for each position you've held, that answers one of these things.

That said, the most important resume I have is my satisfied customers and my testimonials on my LinkedIn profile.

The social network portion of your job hunt can't be overlooked - you know you're getting Googled before the interview, so make that work for you !



Tuesday, October 8, 2013

In another time, and another place . . .

Being an engineer really is like being an artisan class. 

If we were in ancient Greece, though, would that make us landowners?

Since we're not, are there any lessons we can learn from Sparta? Two things spring to mind, from recent life lessons:

1. Focus
The classes were separated by function. Say what you will about classes, there still would have been great shoemakers, good shoemakers, and just-ok shoemakers within the trade class. The goal, I think, of every engineer, is to be the best within their class or specialty. Which brings me to . . .

2. Specialize
The idea of being both a shoemaker and a then a sandal repair specialist might seem silly to us (I mean, really. Beach sandals are like a $1) but if you needed your sandals repaired TODAY so you could march to war tomorrow, would you go to the just-ok maker, for the just-ok price? Or would you pay the higher price for the greater speed and quality of the specialist across town?

I have, and continue, to drive across town for quality. Do you?