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.

 

[EngineerErrant]

I was in a similar situation. I attribute getting my current job to bringing some prototypes I'd worked on to the interview, and describing my contribution to the project (as well as being absolutely clear what I did not contribute).

"Engineers like to solve problems. If there are no problems handily available, they will create their own problems." -Scott Adams

 

[red92s]

Brought a couple samples of commercially available work and described my contributions during various project phases. I think the impact was good and the audience was appropriate. Seems to have been well received as I've been asked to come back.