Current Issue

Chapter News
Features
Viewpoints
Student Views
From the Editor's Desk
Message from the President
Reviews
Society Notes & Community Announcements




 Article Archives 

Book Review
Career Development
Case Studies
Content Management
Contracting & Consulting
Core Competencies
Meeting Reviews
Usability
Networking
Online Help & Embedded Assistance
Technologies
Translation and Localization
Up and Coming Corner
Information Architecture


 Past Issues 

February, 2013
January, 2013
November, 2012
October, 2012
August, 2012
June, 2012
May, 2012
April, 2012
March, 2012
February, 2012
December, 2011
November, 2011
October, 2011
September, 2011
August, 2011
June, 2011
April, 2011
February, 2011
January, 2011
August, 2010
July, 2010
June, 2010
May, 2010
April, 2010
March, 2010
February, 2010
January, 2010
December, 2009
November, 2009
October, 2009
September, 2009
July, 2009
June, 2009
May, 2009
April, 2009
March, 2009
February, 2009
December, 2008
October, 2008
September, 2008
May, 2008
April, 2008
February, 2008
January, 2008
November, 2007
September, 2007
August, 2007
April, 2007
March, 2007
January, 2007

Assembling a winning portfolio

Share on Facebook :: Printer Friendly Version

—by Odile Morrison (with thanks to Tony Chung for his notes)

Published: January 2006 in Contracting & Consulting, Viewpoints

A resume summarizes your credentials to your potential employer. It chronicles where you’ve been and what you did while you were there.  Your portfolio showcases what you have achieved and how you did it. Your resume may get you an interview, but it’s your portfolio that will win you the job.

So, what do employers look for in a portfolio?  A panel of technical communicators who regularly hire contractors tackled that topic at the October Contractors Group meeting.

Your portfolio should consist of three to five pieces that demonstrate that you have the skills to carry out the range of tasks outlined in the job advertisement. Tailoring your portfolio also shows that you can define your audience and understand their needs. Interviewers are obviously looking for technical ability, so select examples that focus on your writing ability and information design skills, rather than the content.

Your portfolio also enables the interviewer to explore your soft skills.

For example, show the table of contents, glossary, and index of a manual, together with one or two pages of content, not the complete 400-page tome. Rahel Bailie, principal of Intentional Design, Inc., also recommended tucking away some oddball pieces showcasing your range, to use as backup ammunition. From her own portfolio, she showed samples of packaging her company designed and an information booklet printed in comic book form.

If you have not completed any commercial projects that address the interview’s criteria, the panelists recommended that you create a piece solely for your portfolio. You might take a poorly written installation guide and rewrite it, write a white paper, or start a blog.

Annotate each piece, briefly outlining the business case, why you have included it, and what it shows about you. “The pieces in your portfolio trigger the discussion,” said Heather Sommerville, documentation manager at Sage Software. Our panelists also pointed out the importance of being honest about your role in the project and giving credit to other team members.

Your portfolio also enables the interviewer to explore your soft skills. “I expect you to be able to write,” said Liessi Haussler, principal of Cyberscribe Solutions, Inc. “What I’m looking for is someone who can complete project-based work effectively.” If you are interviewing for a contract position, use your portfolio pieces to demonstrate your time-management and organizational skills, as well as your ability to work under pressure and deal with difficult people.

Panelists were divided in their opinions about leaving portfolio pieces behind after the interview, but they did agree on protecting your work and the interests of your clients. If you decide to leave pieces behind, never leave originals, and for electronic versions supply only secure PDF files. One way to showcase work covered by a non-disclosure agreement is to ask the client’s permission to show a version of the piece that has been “sanitized” by changing the product name, omitting pages that include proprietary code, and showing content pages out of sequence.

If you decide to leave pieces behind, never leave originals, and for electronic versions supply only secure PDF files.

Thanks to our three panelists for a lively, informative, and very useful session.

Heather Sommerville has been a technical writer, editor, and manager since 1986. She currently manages a documentation department at Sage Software, formerly ACCPAC International.

Liessi Haussler incorporated Cyberscribe Solutions in 1999 in response to a growing demand for more, and better, information.

Rahel Bailie is the principal of Intentional Design, a boutique consultancy that provides content management consulting and related services such as information architecture, usability consulting, and content development services.

Odile Morrison is a freelance technical writer. You can reach her at .(JavaScript must be enabled to view this email address).

Previous: Implications of Accessibility on Technical Communication

Next: The Business of Blogging


 Subscribe via RSS

Visit the main STC website.

STC advances the theory and practice of technical communication across all user abilities and all media.


STC-related links

Note: You may need to be logged into these services to view the pages.

©2013 STC CWC | Home | .(JavaScript must be enabled to view this email address)