Building an IT portfolio that gets you interviews, even without experience

When you apply for your first networking, cloud or security job, almost everyone has the same CV: a degree or diploma, a certification or two, and a list of skills. A portfolio is how you stand out. It is a small collection of projects that show what you can actually do, written up so that a busy hiring manager can understand them quickly.

What counts as a portfolio project?

Anything you built, configured, investigated or fixed, and then documented. It doesn't need to be impressive in size. It needs to be clear, honest and finished. Good examples:

• A small office network in a simulator with separate VLANs for staff, guests and printers, inter-VLAN routing and a simple ACL.
• A site-to-site VPN between two virtual firewalls, with a diagram and the verification commands.
• An addressing plan for a growing company, worked out by hand and checked with the VLSM planner.
• A Linux server hardened step by step, with notes on each change and why you made it.
• A short Python script that backs up switch configurations, with a README explaining how to run it safely.
• A write-up of a practice security investigation: the alert, the logs you checked and your conclusion.

Choose projects that match the job

Look at three or four job adverts for the role you want and underline the skills that appear in all of them. If every network job mentions VLANs, routing, firewalls and troubleshooting, build projects around those. If cloud roles mention identity, virtual networks and logging, build those instead. Five well-chosen projects beat twenty random ones.

A simple structure for every write-up

Use the same headings each time so readers know where to look:

1. Goal: one or two sentences on the problem you set out to solve.
2. Diagram: a clear topology or architecture drawing. Hiring managers look at this first.
3. What I built: the main steps and key configuration, not every line.
4. How I tested it: the commands or checks that prove it works.
5. What went wrong: the problems you hit and how you fixed them.
6. What I would do next: improvements for a real environment.

The "what went wrong" section is the most valuable part. It shows you can troubleshoot, which is most of the job. The troubleshooting methodology note gives you a good structure for explaining how you found a fault.

Where to put it

Keep it simple. A free code-hosting profile with one repository per project works well for scripts and configurations. A plain personal web page or a well-organised shared document works for write-ups with diagrams. Whatever you choose, make sure the link opens without a login and looks tidy on a phone, because many managers will first glance at it between meetings.

Protect what you publish

Never include real passwords, keys, public IP addresses from work, customer names or screenshots of your employer's systems. Use private address ranges from your lab and change any names. Showing that you think about this is itself a good sign to a security-minded employer. If you are unsure, read IT risks and the law first.

Present it well

• Add a short line near the top of your CV: "Portfolio of lab projects: networking, VPNs and automation" with the link.
• Mention one project in each cover letter, chosen to match that job.
• In interviews, be ready to talk through one project for five minutes: the goal, a problem you hit and what you learnt.

Keep it growing

Add a project every month or two. As your skills grow, go back and improve older write-ups rather than deleting them; the progression itself tells a story. After a year, you will have something much more convincing than a list of skills: evidence.

Tip: pair your portfolio with a strong CV. Our guide to writing a CV for your first network or security job shows how to link the two, and the career paths show which skills each level expects.