What's important on a resume¦... 1

[edsongebo]

Most folks use the 'fudge' factor when writing their resume. Some don't and probably should. When is too much 'fudging' going to get you in trouble? If you’re in a position to review resume´s what are you looking for to help narrow down candidates? How do you decipher between “lies” and “factual”? Did you ever kick a resume´ to the curb only to find out that was ‘the guy’ you needed to hire? Let’s hear your experiences.

Edson-

 

[atlas06]

Landing the interview is essential in a resume, you want to present yourself in a verbage that the employer is looking for. People are like old whores, they want to hear they are pretty, so you want them to read what they want to hear. It is unfortunate, but that's what gets the interview.

A good reference of such language can be found in the adds in government positions identifyng duties, web sites of large firms can be good references.

Keep in mind, that your employer will be using your resume to get projects, so a well written resume with "government" style language that uses eloquent verbage describing your work is a plus.

You need to interview the company while being interviewed, and NEVER go an employee-owned company (partial or whole). As the work goes down, guess who gets the ax? the non-owner that you are of course.

You must find out who you will be reporting to, if you are a structural engineer, make sure that your boss will not be an architect. There is nothing worse than working for someone who cannot evaluate your work.

Remember, you never lie, you just stretch the truth.

 

[RDK]

Lying (or fudging) a resume is grounds for immediate dismissal even after long terms of service.

You will be found out sooner or later and could be dismissed effective right this minute.

Remember that when submitting a resume.

However a resume is not much of a tool in the hiring decision. I don’t put a lot of weight on the document other than to screen out candidates in the first go around. I talk to them face to face and can quickly determine who has good experience and who doesn’t. All it takes is a few simple and direct questions.

Everyone remembers the essential facts about every project that they have worked on. Just ask what was the exact span of a bridge and if they hesitate or say about xx metres, they weren’t in actual charge of the project.


Rick Kitson MBA P.Eng

Construction Project Management
From conception to completion

http://www.kitsonengineering.com

 

[looksatstars]

I wouldnt lie as well. You gonna lie about your qualifications for the job, its gonna come out when you start. After you have been working for a while, most employers expect you to hit the ground running so you better know how to do what you say you do.
I also bring in pictures or design portfolio, it makes your interview different and takes the edge off as they are usually pretty enthusiastic about the work you have done.

 

[Ashereng]

Everyone remembers the essential facts about every project that they have worked on. Just ask what was the exact span of a bridge and if they hesitate or say about xx metres, they weren’t in actual charge of the project.

I guess I would fail your interview then. I rarely remember any exact details of any project - after I finish them. Too many projects, not enough brain cells I guess. Sometimes, I can barely recall the location of my site. I consider myself lucky if I can recall the project name and the approximate year it happened in.

Or, maybe that is just my industry?

"Do not worry about your problems with mathematics, I assure you mine are far greater."
Albert Einstein
Have you read FAQ731-376 to make the best use of Eng-Tips Forums?

 

[whyun]

Ashreng, same here in the structural industry. At least I leave enough trail in my computer to track down any info on projects or who worked on them so I don't have to go to the archives.

Engineers are trained to know where to go to get information to solve problems, not necessarily to memorize everything. Or is it only in the U.S.? Some are inherently better at memorizing but most are not.

On resumes, long list of projects do not impress me much. Condensed list of projects describing the depth of involvement with each is more appealing.

 

[MikeHalloran]

I guess I'd fail Rick's test, too. In the past six years, I've done work for/on a little over 450 yachts. I remember some details of a few, especially the ones where things didn't go so well, but they're mostly just a big white blur.



Mike Halloran
Pembroke Pines, FL, USA

 

[ewh]

I'd also fail. Best I can do is tell you what project and what area of the project I worked on (unless it was really onerous, and got embedded into my memory).

 

[KENAT]

I'd be hosed. I can remember the drawing number for the PW II (UK) AEII, I looked at it so often, but I'll be darned If I remember exactly it's mass, length etc.

 

[HDS]

I've seen lots of resumes but HR has never given me a cover letter.

However, I still write them just in case. I take the add if there is one and respond to every item on it with my experience. If nothing else it makes me understand what they need and I am prepared to answer a phone call.

If I noticed an error of spelling or grammar it would be really big. However, I know a guy that sent out a hundred resumes for pubic policy positions. He was a Public Policy major in school.

 

[MikeHalloran]

I remember that Ford's basic part numbers for axle shafts are 4007 and 4016, or were, forty years ago. I can't remember which is left and which is right.

I don't remember the exact length difference between the l/r axle shafts in the '67 Econoline, with the offset pumpkin. I do remember that had it been a millimeter more, that crafty old Manufacturing Engineer and I (young and stupid) would not have been able to make the first dozen production axle housings by hacking existing machine tools in the middle of the night and restoring them in the morning.



Mike Halloran
Pembroke Pines, FL, USA