Key Requirements for a Struct. Eng's Resume

[asixth]

Hi guys

I will be looking for new work very shortly and would like to know what are the key components to include on a structural engineers resume.

I was thinking that the set-out of the resume should follow:

1. Personal Details
2. Position applying for
3. Previous employers and notable jobs with previous employers including: project, cost of project and responsibilities.
4. Any professional affiliations
5. Extra curricular workshops/seminars
6. Education
7. Personal references from previous employers.

Can people please leave advice on how a professional structural engineers resume should be constructed.

 

[Lion06]

Good questions. I'd also ask how you handle references if you've only had one employer.

 

[Qshake]

First, good luck to you.

I focus on:

Project Experience, with a view toward progressive responsibility either during a long project or over the course of several projects.

Education, I look for basics (Analysis, steel, concrete, prestressed) and then look for advanced coursework such as dynamics, advanced mechanics of materials or elasticity, etc.

Self-Development is next - Do you attend seminars to improve your skill set etc.

I don't look at personal details nor references. HR looks at references.

Regards,
Qshake

Eng-Tips Forums:Real Solutions for Real Problems Really Quick.

 

[Lion06]

QShake-
Thanks for the input. Do you expect to see classes listed? Do you like to see this for undergrad and grad classes or just grad classes? I've typically only put my degree, but I haven't updated my resume since I graduated 4 years ago.

 

[IRstuff]

I'm not an SE, but I think that generic reume principles apply, always. For a new graduate, a listing of upper level course names would be sufficient. However, you've been working for a while, however short, so the course material is completely subordinated by any job-related information you might put down, unless there's some rationale that would make sense to include.

Your resume is a marketing document. As such, you need to at each item with an eye toward why that item is important for the reader to know. As with Powerpoint presentations, "horse" charts are not terribly information. ("Horse" charts are charts that just sit there with some level of information, but nothing on the chart explains or justifies its inclusion in the chart deck)

Therefore, any course material you care to list should be evoking some sort of positive response from the reader. Likewise, the project and task items should show to the reader that you are well-qualified for the job you're applying for. To that end, you should also evaluate what your long-term goals are; you've included cost and project headings, implying that you'd like to move into management, or at least, show that you can manage some level of project. If this is what you want, then go for it. If not, then adjust the resume accordingly.

Do you have your EIT? That ought certainly rank high in the list.

TTFN

FAQ731-376

 

[TDAA]

If you are pretty new, you typically have the education before your experience.

List your EIT, or other main accomplishments/designations following your education

I assume you don't mean a discussion about your dog for the personal details, but this is more your contact information.

I leave the position applied for on the cover letter. That part is not something you have done (or at least not worth bragging about applying for a position). This leaves more room for other information, and the critical "white space" that gives a readers eyes some rest.

I would keep the notable job information brief (summarized), with possibly more detail on something considered most notable. I have done some "notable projects" pages as attachments, when I found them appropriate. Yes, they did get printed, and were in the interviewers' hands when I interviewed.

Good luck, and thanks for reminding me to get back on my resume for updates.

 

[JAE]

asixth - as one who is in a hiring position at times (for structural engineers), when I look at a resume it is very much with an eye to MY needs as a department head. I'm looking for someone who would come in and

1. Have abilities that match what we do in our department
2. Require minimal training to get up and running with projects.
3. Has a good work ethic and passion for engineering.

Item 1 - Usually this means an accredited degree, some project experience that is similar to our own projects, some knowledge of engineering software (either exactly the same programs or at least similar programs), and personal communication skills for report writing, emails, letters, and just good "connecting" skills with other humans. Applicants with a PhD say, in some specialized arena that has nothing to do with our consulting business is of no use to me. I was often a bit wary of PhD's going into general structural consulting anyway.

Item 2 - Harder to identify - but the idea that the person is a self-learner and anxious to contribute to a team is what I would look for. I don't mean by this item that I don't do mentoring - everyone needs mentoring always - even myself - but I would consider a negative someone coming from ground zero with no experience at all.

Item 3 - Again - harder to see in an interview or on a resume - but if the person sees the job as an engineer as a job and not a career, that would be a negative with me. I don't mean to say that you shouldn't be a well rounded person and have non-engineering activities and interests. I would look out for an attitude that I'll show up at 8am and leave at 5pm and I'll not bother to consider continuing education, self-study, etc. Staying after work sometimes to read up on something I just don't understand is a good quality in an engineer in my book.

 

[Lion06]

JAE-
I always appreciate the input from a person in a hring position.

I'm all over your item #2, but I would ask how important item #3 actually is and how you ascertain this during an interview. Truth be told, I prefer to be in the office no more than 9 hours per day. I do, however, work from home quite a bit in the evenings and weekends. I never let my work fall behind, but don't always like to do it from the office. I have a young family, and I hate getting home with 1.5 hours to eat dinner and see them before it's their bedtime.

 

[B16A2]

I can usually judge #2 and #3 by how excited and engaging the interviewee is in describing experiences that support #1.

Dont list classes on your resume, this is what a transcript is for if we request it.

Focus on communicating your experience.

 

[msquared48]

In mine, I also have an Executive Summary of position specific qualifications that are substantiated later in the resume. A single page is best, but with more experience, that is hard to achieve in reality.

Oh, and JAE hates to read, so keep it short.

Mike McCann
MMC Engineering
Motto: KISS
Motivation: Don't ask

 

[Qshake]

Asixth - I would not list all courses just the relevant courses.

If you are applying for a position that specified certain work (concrete over steel or vice versa) then you'd want to show this. If you are applying for a more general position, the more breadth you show is better. And one succint way to do that is through coursework.

As to your philosophy, english, history, basketweaving, those are for transcripts along with incidental CE courses such as Wastewater or Fluid Mechanics.

Here in the midwest, we have universities where it is not uncommon for CE students to chose either Concrete or Steel deisgn at an undergraduate level. So i like it when resumes offer me a glimpse of serious structural coursework.


Regards,
Qshake

Eng-Tips Forums:Real Solutions for Real Problems Really Quick.

 

[JAE]

My Item 3 above - yes - hard to find out in a short interview.

I don't mean by this that I expect engineers to be a slave to their careers and live an unbalanced life. Not at all. I am, in fact, very pro-family and would never want to lose myself in my profession.

Having said that, there's the reverse of slaving yourself, timewise, to engineering.

I've seen cases where young engineers start a new job, very green, and the senior engineer mentors a bit and perhaps points out a lack of knowledge or experience in a certain area....as a structural example, let's say the engineer doesn't quite "get" how concrete columns are designed.

I would expect the young engineer to take some extra time, study up on calculation methods and the code, better understand it - ask a few more questions, etc. - perhaps a little on their own time. Perhaps early in their career it occurs more often as they are trying to integrate themselves with high enough levels of knowledge to make themselves valuable to an employer

Instead, I sometimes have seen an expectation that they are only devoted to their profession while "at work" - 8 to 5 - and expect the only knowledge gain will take place by senior engineers spoon feeding them.

 

[Qshake]

Agree with JAE above on wanting some autonomy in an engineer to increase their knowledge. SO yes, I do look for engineers that are excited about their work.

Regards,
Qshake

Eng-Tips Forums:Real Solutions for Real Problems Really Quick.

 

[Lion06]

I do a ton of reading on engineering outside of work. When I go on trips - I take engineering texts with me. When I have free time at home - I'm on Eng-Tips. I also attend a lot of local SEA conferences.

 

[rowingengineer]

StructuralEIT,
This would be something you want to let your possible future employer know, he really can't ask you, but you sure can tell him. He probably doesn’t even know about engtips, but he can look it up, try to have an example of how you studying made you a better engineer.

Asixth,
I normally wouldn't bother to read a reference, but will contact a referee to discuss ensure someone thinks your competent.

I also agree with JAE, with regards to study.


Arguing with an engineer is like wrestling with a pig in mud. After a while you realize that they like it

 

[IRstuff]

Just bear in mind that most companies have a policy against giving anything other than straight employment history.

We once (many blue moons ago) had the occasion to hire an engineer; we got rave references. After the fact, it was clear that they lied through their teeth for the opportunity to be rid of this engineer, who couldn't tell one end of a shift register from the other.

TTFN

FAQ731-376

 

[asixth]

With referees, how many should be included and how far back should I look at including. For example, along the way I have held 3 engineering related jobs.

1. My first while I was a student in 2006-07
2. Another was working at my old university for a professor after graduation from 2007-08
3. My current position from 2008 onwards.

Should I include a referee from all 3 employers and should this be included on a resume or should I submit referees during a job interview.

In my experience with job interviews, I have found that if you are asked to come in for an interview it means they are seriously considering offering a position. But I haven't sat in a job interview since 2007 and there has since been a global meltdown (Oct '08) which has seen a decrease in demand for structural engineers.

What items don't employers like to see on a resume?

 

[Qshake]

Most resumes I read say references available on request. Rarely do I as an interviewing and hiring manager ask for references....the HR group has to do something!

So I would take along a copy of your references for the instance someone asks for them.

What I don't like to see on resumes is the following:

1. A litany of jobs held with 1 or 2 years between them.
2. A litany of projects worked on with only minor experience gained from each one. On this one I've seen some who insist they've gained valuable experience when in reality they've computed quantities or bar list or shop drawings for rebar and moved to next project for same. I'd rather read one paragraph outlining what was learned as a result of working several projects than reading several projects worth of description only to discover they didn't really do anything.
3. Management aspirations for graduates out for less than 5 years. These types have their eye on the forest and sometimes that good but when you're hiring for details (trees) you don't need someone focused on management and neglecting the details.
4. Don't fluff up your resume, I like honesty and would rather someone be honest about the work they did than tell me at 2 years out of school they were project manager for a 110 story building. Sure it may happen; just not very likely.

I hope these help.


Regards,
Qshake

Eng-Tips Forums:Real Solutions for Real Problems Really Quick.

 

[JAE]

Qshake - good stuff.

Also - on references.
One thing you can do is ask the applicant this question:

[blue]"If we called all of your references, tell me one good thing and one negative thing that they would say about you."[/blue]

It's an awkward question, and maybe a little unfair to ask, but it gets them thinking about themselves perhaps a little more objectively and sometimes does provide you with a little insight.

 

[IRstuff]

I wouldn't spend paper on actual references, just note that they are available. If you don't interview well, references won't matter. If you do interview well, references are not necessarily needed.

TTFN

FAQ731-376