With a technical writing portfolio, you can show potential employers how well you can write, how you think, and what other skills you have that go well with writing. It could make or break your chances of getting an interview.

In job hunting or searching, submitting your technical writing portfolio is almost always required, regardless of whether you're looking for a full-time or freelance writing position. Your portfolio demonstrates your strengths as a writer, your ability to think critically, and other soft skills.

What is a technical writing portfolio?

A portfolio is the ideal way to highlight your technical writing skills, educational background, and showcase your professional experience, whether you're seeking a permanent position or freelance work.

For a technical writer with some experience, your technical writing portfolio is also a collection of your writing samples and information about you that may be of interest to prospective employers. A well-designed and professional-looking portfolio highlighting your best work is essential to impress potential employers or clients.

Why do you need a technical writing portfolio?

Here are a few reasons why you should have a technical writing portfolio:

• You can effectively advertise your skills if you present an archive of your work to the job market.

• Your portfolio demonstrates your versatility as a technical writer and proficiency in other genres. This means you are not picky about the industries you work with.

• Your writing portfolio shows your writing style and the structure of your technical documents.

• Looking at your work on a bad day and seeing how far you have come in your technical writing journey will motivate you.

Contents of a technical writing portfolio

Portfolios should follow a simple format that introduces you and showcases your projects. Here’s what you should include in your portfolio:

Introduction: This gives a brief bio about yourself and an understanding of your personality. Briefly describe your skills and how you will apply them to a technical writing position. This should be in an “About Me” section of the portfolio. Additionally, if you have technical writing skills and certifications that set you apart from others, be sure to include them.

Technical writing samples: This is the most important part of your portfolio. Include samples of your technical writing projects like; user guides, tutorials, other articles, etc. When displaying your projects, give a summary, a screenshot and a link to the project. To impress potential employers, select the best and most interesting pieces of work to include in your portfolio and not necessarily all your projects.

Contact information: Display your contact information like phone number, email and social media links in strategic places on your portfolio websites. This can help you build up your credibility and authority.

Clips of public speaking and presentation slide decks: If public speaking is one of your skills, adding clips or a link to the sessions and presentation slides could be a great fit for your portfolio.

Testimonials: Good feedback from Previous clients or employers can paint a good picture about you to your would-be employers. If you have evidence of your client feedback, you can display them on your portfolio website.

Common errors found in a technical writing portfolio

These are 5 mistakes that could cost you that job that you are applying for;

1. Grammatical error: You sell yourself as a technical writer. Even the slightest mistake can have a negative impact on your application. Proofread your work and then send it to your friends or family for review. Avoid using jargon and a negative tone in your portfolio.

2. Inaccurate details: Cross-check the details in your portfolio and update them if necessary. Make sure your portfolio contains your current information. Important information such as your mobile number and email address should be accurate. Try to narrow down your information to only the essentials.

3. Unprofessionalism: This ranges from your portfolio design to your content. Choose a professional design template (colour schemes, fonts, layouts, etc.) to create your portfolio or use a portfolio builder for technical writers like Contentre, Lintree, or Contently. Make your content and images professional.

4. Plagiarism: A recruiter can easily tell if the sample you provide is yours, because they come across many similar works in the industry, and you could lose your chances. Make sure your samples are original and authentic.

Sample of Technical Writing Portfolios

At this point, you are familiar with the basics of creating a great portfolio. One of the best ways to get hired is through your portfolio, which allows readers and clients to discover more about you and your work. Take a look at these great technical writers' portfolio samples for inspiration:

Zainab Daodu

Zainab is a technical writer with 3+ years of experience writing technical documentation to improve developer experience, and 4+ years of experience as a software engineer developing, testing, and maintaining enterprise software applications. . She is an advocate for gender diversity and inclusion in the open-source space and an eloquent speaker on technology, women's empowerment, and open-source contribution.

Linda Ikechukwu

Linda Ikechukwu is a Frontend Developer & Technical Writer. She loves to build interfaces and write about them. Curiosity drives her to figure out how things work.

For more ideas on creating your technical writing portfolio, here are some other portfolios of technical writers that can motivate you:

• Mario Garon

• Chelsea Moats

• Craig Wright

Conclusion

Writing portfolios is one of the most important marketing tools for generating new clients and can also cause you to lose them quickly if done incorrectly. Making a good first impression on your prospective employer is important, and a portfolio can do that for you. You can start working on a new portfolio or update the one you already have.

Feel free to contact me via Twitter if you need someone to review your portfolio or other technical writing-related issues.