Mly,

Glad to hear the screening interview went well, and that you're getting some great advice in this thread.

Regarding getting your new, improved resume into the hands of the next person you are scheduled to speak with:

While I would normally not send such a follow up email to a screener, I think given the quality of your old resume you should consider sending your most recent contact an email like this:

"thank you for taking the time to speak with me on Friday. (insert something here about either learning about the role, or something you feel was specific to you that you got to convey to them, or about the company.) I'm excited to speak with x on Monday, and learn more about the position, and Semens. For x's convenience, please find attached my most recent resume(, and cover letter).

Best,
Mly"

Citanul,

SIEMENS.

Your friend,

Howard

I learned at an early age that the best way to get along with other people is to take their side i.e. look at things from their perspective. Thus, I've always done well in job interviews.

The first thing you do is research the company's history. I interviewed for one job in Dallas, several years ago, and I went online to research the company the night before. I learned they just opened a London office that year. My interviewer had just come from London the previous day, so I asked him about the restaurants in the neighborhood the London office was located. It was a small thing, but it showed that my interest was in the company's objectives and not my own.

Also, most companies will have a core belief or set of values. Incorporate that into a few of your answers somehow, without sounding insincere. Example, I once worked for a company who stressed safety. I told the interviewer that I've changed all of my passwords to phrases that remind me of safety because I want to always have safety on my mind.

For these two questions. I think El Diablo answered them very well. My responses would of been something like. How do I handle conflict? Honestly, I don't encounter very much conflict. I think that's because I have a reputation as a very understanding and supportive co-worker. I think those are essential characteristics, which every member of a successful team must share. The few times that I have experienced conflict with a co-worker I've just taken more time to work through that issue with them. Those have always been the times I've grown the most. I've never had to take a conflict to a superior, but if I ever encountered a conflict that I couldn't resolve on my own, I would follow the proper protocols to resolve the conflict. I would look forward to that opportunity as well to develop another tool for conflict resolution.

Essentially, you tell people what they want to hear, but you mix in your own truth as well. Example, you've said that you enjoy challenging work projects. Take that principle outside of just work projects. I'm always up for the challenge of improving my conflict resolution skills. Even if you don't enjoy something, state that you would enjoy the challenge of it, etc.

What kind of boss or co-worker have you had the least success with? I've never failed to meet expectations due to a poor working relationship with a co-worker. I'm a strong believer that one cannot happen without the other. However, in rare instances I've worked with a co-worker who didn't share the company's ideals. In those cases, I've always tried to encourage that co-worker with the benefits of my company's ideals and work those principles into how we can achieve our objective.

You've got a little brown on your nose.

Those answers suck. Interviewers are looking for specific answers.

E.g. while working at company A on project X, I experienced issues with the client over timescales. This was resolved by Y, and i learned B, C, and D

Those answers are pretty bad Puddin. Too vague, too much rambling, and way too much bull****.

Conflict questions are softballs you can typically answer very quickly with a real-life example. They're designed to identify people who don't actually have the skills to handle basic interpersonal conflict, and so they may not actually know how to answer.

"I would follow protocols" and your philosophies and your recollection of your own reputation don't show them that you do. If you tend to be long-winded naturally, which I am, practice answering these types of questions in four sentences.

Sentence one for me was something like, "I've worked in relatively high-conflict positions with difficult people before, especially in the military and on casino floors where they're not hard to come by." [It's fluff, but one sentence worth & most interviewers seem to get that and nod.] Then I'd just cap it with a specific canned example from a more recent job that demonstrates that I'm not one of those difficult people.

And that's it. Interviewer checks off and moves on.

Too vague? I'm not going to share something specific from my own work history on publicly searchable internet forum. I was just sharing some general ideas, mostly off the top of my head.

The words I chose may not be the best, but I've never lost out on a job I really wanted. Maybe it's more of an in-person type of thing. It may sound like b.s. in print, but I've always thought the reason I did well at job interviews is because they left feeling that I genuinely cared about the company's future as much as I did my own.

If you've never lost a job you really wanted you are applying for the wrong jobs.

I'm not a PE yet. PE ITT is for Project Engineer. Ive just submitted my application, and hopefully Ill be taking the exam in Feb. Most of my jobs were not PE stamped, but I am the engineer on record.

Agree on not making mistakes. My major mistake was leaving a thermowell off of a vessel nozzle.....it was major because the unit was about to ship, and it cost tons of monies to have the vessel fixed re-certified.

No pipe stess analysis

MLYLT,

Goodness gracious. You toss around the letters PE in your original post as if you are in fact a PE. PE stand for PROFESSIONAL ENGINEER, and nothing else. It sure as f*ck doesn't stand for "project engineer." PE means professionally registered in a US state, by an examination administered by a state, and it is illegal to call yourself a PE if you are not in fact registered. It's not illegal in this forum, but on any document associated with compensation you receive for your work, you cannot refer to yourself as a PE. Shame on you for not knowing that. What in the world were you thinking with that post? It is completely misleading, and more importantly, it exposes your apparent ignorance regarding the profession of engineering.

Lol, I know the the rules. My second sentence of the original post states that I am a Project Engineer, and thereafter PE is used as an abbreviation of that for tt. Maybe you should pay more attention to the details. I of course am not calling myself a Professional Engineer on any documents without having my license. And, this really bothers me too. They had a guy calling himself an Engineer at this last company; he had no degree, and was ****ing a lot of **** up.

Sorry, but I'm gathering there is something not right with you. Hope I'm wrong about that though, and you land a job next week.

This type of thing will rub people the wrong way. Also, it appears you are the one who needs to be more detail oriented.

MLYLT,

Sparks is right, period. That's like me writing a post about business and mentioning somewhere that I'm a major business analyst, then later referring to myself as an MBA.

My qualifications to comment are I have lots of PE friends, and my dad is a PhD in civil engineering who has been in charge of some of the deepest deep sea drilling projects in the world with a very fancy sounding engineer title working for Bechtel, Fluor, etc.

How so? You have to work 4 yrs before you can apply for your PE license. Nothing wrong with me because I don't have it; its just the rules.

Engineer on record? WTF is that? It is dangerously close to the legal phrase "engineer of record" and if you used that nonsense term as part of your work, it could easily lead to disciplinary action by the Board of Engineers in your state against the principal PE at the company you work for. This is getting embarrassing now.

The problem isn't that you don't have it; it's that the abbreviation you use for "project engineer" is confusingly similar to the term of art "PE," which stands for something different.

+1, it comes across as very deceptive, and you should know this. Honestly this little debacle makes me doubt your credibility surrounding your story from your previous employers.

Really? Who all was confused by my original post about me being a project engineer? Where in my resume did I used Professional Engineer or PE? I explicitly show EIT on my resume.

Im not trying to be deceptive at all.

If, in your field, one abbreviation is used to denote something specific and significant, you should not use that abbreviation to refer to anything else, particularly not on a resume.

I don't think your intent was to deceive, but I can see why it is causing some raised eyebrows in this thread.

Since we seem to have lots of engineers ITT. Can i confirm that not knowing what "Continuous improvement " is in an engineering / manufacturing context is unusual.

/dogpile

Probably best to have a native English speaker review your full resume before sending it out again, OP.

It's the reaction she has that strikes me as odd. Only she knows if her intent was to deceive but I completely agree with you here. And el Diablo with his mba example. This should be common sense. And to someone who it is not common sense it makes you begin to question other things they have described.

I think El D knows what he's talking about, having a dad who's a Porta-Potty Head Director in civil engineering.