Bringing samples of work to an interview? 3

[red92s]

I have an upcoming interview for a product engineering role. I'm currently in a similar role (but an unrelated industry). My skillset and experience level (~5 years) are well aligned with their requirements. From an earlier phone interview it sounds like a good fit both personally, and professionally. A stated responsibility of the position is "Hands-on involvement in all product phases from design to production & end-user support". Would it be advisable to select an example of past products I've launched where I handled many of the same tasks I'd be asked me manage in the new role?

I would not roll a suitcase full of parts into the office and start spreading stuff out on the hiring managers desk. I'm talking about one small (handheld) assembly.

I'd omit anything potentially confidential or proprietary. This would be a currently-available consumer good, and supporting documentation that is freely distributed via the web(installation manuals, sales brochures, spare parts and service guides, etc). Essentially a portfolio of the "public" deliverables associated with a product.

My thought process here is that I'd be able to show examples of my work, rather than just discussing them (which I'm certainly capable of doing, as well).

Any input is much appreciated.

 

[berkshire]

As long as it is in the public domain and not subject to a NDR agreement I think you are safe.
Brochures work as well.
B.E.

The good engineer does not need to memorize every formula; he just needs to know where he can find them when he needs them. Old professor

 

[MikeHalloran]

I have on occasion brought physical samples of my work, including a few for which I made the drawing and produced the first prototype by myself.

I can't say that the samples by themselves closed the sale.

In fact, sometimes it took too much interview time to explain what they did, how they did it and how they were produced, to people who eventually admitted that they didn't understand squat about what I do anyway.

If you've produced a drawing that's beautiful for art's sake, it may have a larger impact than samples or photographs, at least among people who can actually read a drawing.


I.e., if the interview is scheduled for a short duration, don't bring samples. If the duration is open ended, bring them in your pocket, but if it's going well without them, don't drag them out.

My resume includes color photographs of some of the samples, so I like to be prepared to produce them if the subject comes up, but the subject doesn't always come up.



Mike Halloran
Pembroke Pines, FL, USA

 

[red92s]

Thanks for the quick feedback. I think you've echoed what I was already assuming about it being a good idea to read the situation, pace, and background of the person I'm speaking with. Being relativity early-career I wanted to make sure I wasn't going to be breaching some code of interview conduct.

 

[racookpe1978]

On the other hand, I was scheduled for an interview with my current boss (and his boss) at a airport hotel a few years ago.

I was a bit early, and got bored waiting for them, so I was in the lobby, looking intently at the welds on the artsy-fartsy steel "artwork" scattered around, when I remarked something to effect of "I don't like that style, it's stronger and easier if he had done it this a way" to a pair of on-lookers.

Sure enough - they were the two interviewers. Considering they agreed with me, and were impressed that I could and did weld myself, that I was self-confident enough to make corrections and comments about somebody's else's work, and that I was detailed enough to look underneath another person's steel artwork to analyze that welding and design ... They did immediately hire me. With a considerable raise.

So, if you DO decide to bring something, (1) be absolutely sure you are "right" in all aspects of your opinion of your product, what you did/did not do to make it, (2) that you are technically right in ALL regards, (3) that you are NOT bringing a competitive product NOR criticizing their own product in ANY way ... (4) that the issue of proprietary data does NOT and CANNOT come up, it may be worth doing. Or having with you as a sample.

But consider that, if they see you display one of your former bosses' products to them during a hiring interview, will they trust that you will not "borrow" one of THEIR products to demo to a future boss, a future client, or a future rival? Seems risky.

Just use your hands. Use something you machined/designed/built/recommended/funded/contributed to for your church or your charity or local scout troop or local school.

 

[patprimmer]

All the above is excellent advice.

It depends a heck of a lot on who is interviewing you. Do not bore them if it's over their head. Certainly let them see your skill if they will understand and are interested.

Regards
Pat
See FAQ731-376 for tips on use of eng-tips by professional engineers &

http://eng-tips.com/market.cfm

for site rules

 

[TED7]

Make sure you take something "shiny" for HR types. I took 3 drawings from a university project part (2 detailed and one GA) and for some reason unknown to me at the time I decided as I still had the CAD models, to make a render of it in Blender. The HR guy loved this for some reason, whether or not it had any benefit I do not really know but it gave him something to look at and diverted his attention from me and stopped him asking stupid questions for a while.

Designer of machine tools - user of modified screws

 

[TheTick]

I have taken samples to interviews, with mostly positive results, though it did backfire on me once.

If you bring samples, be prepared with your story for each sample. What is significant about this piece? What challenges were presented and overcome? What was your contribution to solving problems with this piece?

Another reason to have a good story for each piece prepared is to keep the interview on track and out of the weeds. I had one interview go bad because the interviewers got so distracted by shinies that they forgot to ask me any in-depth engineering questions. To cover their tracks, the wrote in their summary to my agency that they thought I was lacking in core technical areas (areas which I excel in, but they never asked me about).

 

[IRstuff]

Make sure it is, in fact, YOUR work.

I've caught a SENIOR manager lying about his contribution to a project that I was personally and intimately involved in. I didn't call him on that, but he didn't get the job, either.

TTFN
faq731-376

 

[HDS]

Good advice every where. It has worked well for me when I made cell phones. When I made parts 8 feet across I just brought a 1 page portfolio with pictures.

It can make it easier for someone to remember you and understand what you really did.

 

[KENAT]

I think having them available is probably a good thing on balance.

However, knowing whether or not to pull them out of your bag/how to talk about them etc. may be more significant.

I've been giving a few interviews lately and had at least one guy who was over eager just to show his PowerPoint presentation of his Phd thesis summary.

Another though managed to bring out samples of work (documentation) to demonstrate answers for various questions and this came across pretty well.

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​

 

[patprimmer]

8' across is a BIG cell phone ;-)

Regards
Pat
See FAQ731-376 for tips on use of eng-tips by professional engineers &

http://eng-tips.com/market.cfm

for site rules

 

[btrueblood]

Those original Motorolas were sure heavy...

I once was given a rocket engine reaction chamber that had "energetically disassembled" itself during a test. It was not wholly my design, but its method of disassembly was instructive of how wall penetrations for instrumentation weaken said wall. Took it with me to a few 5th-grade class "show and tell" presentations over the years, and have joked with others that I should take it to interviews too...but never had the cojones.

Pictures work better than objects, and I have interviewed where I pointed to things on the previous employer's website. Also have a few paper drawings that I've done for my own use, which (hopefully) show that I know how to do that too.

 

[IRstuff]

Sounds like the perfect prop for "What was a significant design failure during your career, and what did you learn from it?"


TTFN
faq731-376

 

[HDS]

The 8 foot across part were for the corded cell phones we used have back in the day...

Actually they were at the next job making car parts.

I have had HR people ask me to bring in examples because they knew their engineers would ask better questions about a product than a person.

It can be hard to figure out what someones real contribution was to something. The visual aids can help to tell the story.

 

[TheTick]

I have one plastic part that I call my "pocket resume". It's only 50mm lng, but has all kinds of interesting features on it.

 

[pierdesign]

This is a common question: suitability of interview show-and-tell.

Firstly, it is interesting that engineers seemingly rarely have a portfolio, instead relying on employment history, sometimes project name and select particulars, or similar minimal detail. A designers life is his/her portfolio, some use work samples only while foregoing itemizing employment history.

Ideally, you should have some publicly showable work samples, almost anything is fine including drawings, sketches, reports, etc. Collected in a presentable format, not all loose and messy.

It has been established that a job interview is not public disclosure and therefore suitability of showing work samples is acceptable. There has been discussion that it is probably unwise to show current work if you are interviewing with a competitor or somewhat related industry. Otherwise, it's acceptable, although I would preface it by identifying current work and mentioning privacy. Also, there is always individual circumstance, only you know those particulars.

 

[moltenmetal]

I'm involved in hiring engineers from time to time, and I agree with pierdesign completely. An engineer SHOULD have a portfolio rather than merely relying on a resume. Whether or not you open that portfolio will depend on what questions you're asked, who is doing the asking etc.

When showing that portfolio, you'd better be absolutely truthful about your involvement in the work, because I WILL catch you out if you're taking responsibility for work you're not competent to do.

It amazes me how few engineers present in 2nd interviews with a portfolio or even a single example of something they've done before.

 

[patprimmer]

I strongly disagree with pierdesign on only one aspect. The rest is spot on.

It has been established that a job interview is not public disclosure and therefore suitability of showing work samples is acceptable

If you did confidential or sensitive or innovative work for me and betrayed the confidence before the work was in the public domain no matter where you betrayed the confidence or why, I would have your sorry a$$ in a sling so fast, you would likely never work in that field again. You cannot betray a confidence unless under a court order to do so as evidence.

The argument that the recipient of the information was not a competitor is irrelevant as you never know when that might change or who they might then pass it onto. The further it gets from the source, the more readily it is passed on. Unfortunately the shining light in your portfolio is very likely innovative and current. Just pick examples that are released to the market.

Regards
Pat
See FAQ731-376 for tips on use of eng-tips by professional engineers &

http://eng-tips.com/market.cfm

for site rules

 

[MacGyverS2000]

It also depends upon the engineering... as a software designer, it's not like I can whip out a pamphlet of source code.

Also, I can't exactly show stuff created under a clearance to another employer, even if the new position was cleared.

Dan - Owner

http://www.Hi-TecDesigns.com