Skip to content
Gig History
Menu

Resume vs. Work Portfolio: What to Share With Recruiters

Keep your resume concise while giving hiring teams a way to explore the work behind it.

By Gig History

A resume provides a concise overview of your background. A work portfolio gives selected experiences room for context, decisions, and supporting details. They serve different reading needs and can work together.

A portfolio is not a reason to ignore an application's requirements. If an employer requests a resume, specific file format, or application questions, provide those. Use a portfolio link as additional context where it is welcome.

What belongs in the resume?

Keep the information a reader needs to understand your background quickly: roles, employers, dates, relevant skills, and a concise selection of contributions. Make the relationship between a claim and its role clear.

A resume should stand on its own. Do not replace the substance of an application with “see my portfolio” or require a reader to open a link to learn basic employment history. Check the rendered file before sending it; a polished editing view does not prove that an exported document is readable.

What belongs in the work portfolio?

Use the portfolio for details that lose meaning when compressed: the problem you encountered, constraints, choices, your individual contribution, and the result. Include supporting work only when you have permission to share it.

  • A software project: explain the user's problem, the part you built, and a technical choice, with a public repository or demonstration if available.
  • An operations improvement: explain the old workflow, the change you introduced, and what you observed afterward.
  • A research or analysis project: explain the question, the sources or method, and the limits of the conclusion.
  • A collaboration: explain the team's goal, your responsibilities, and how you handled a decision or dependency.

You do not need to include all of these. Select experiences that demonstrate different aspects of the work you want to discuss. The work portfolio guide includes a reusable structure and a fictional example.

Keep the short and long versions consistent

Imagine a resume says, “Introduced a checklist for support onboarding.” The portfolio can explain why the checklist was needed, how you gathered feedback, and what happened when it was used. It should not turn that contribution into “led a company-wide transformation” unless that is independently true.

Check role names, dates, ownership, and results across both documents. If you update one after discovering an error or learning a result, review the other. A longer format gives you space for nuance; it should not create a different history.

Share a link with a clear purpose

Where an application allows a portfolio or website link, use a stable public address and a descriptive label such as “Selected work and project context.” Keep essential facts in the application itself. For a conversation with a recruiter, point to the experience most relevant to the discussion and explain why it is relevant.

Before sharing, check the link in a signed-out browser. Confirm that it opens the intended public page, that you have published only the entries you meant to share, and that any contact methods work as expected. Review the mobile view too.

Know the difference between public, unlisted, and private

A public page can be viewed by other people. An unlisted page is not promoted through a directory, but anyone who receives its link may still open and forward it. A private draft should not be accessible through that public link.

Gig History profiles start unpublished. Publishing makes the selected content available to anyone with the link; candidate profiles remain unlisted, and the site instructs search engines not to index them. That instruction is not access control. Keep confidential material out of published content even when you only plan to send the link to one person.

What does an interactive work record add?

In Gig History, hiring teams can read your published record and ask questions about it without creating an account, within the profile's question allowance. Answers draw on what you published and are instructed to say when information is missing. They can still be imperfect and do not independently verify your claims.

That makes clear source material valuable. Use specific work experience descriptions so the record has something substantive to answer from. The profile supports a conversation with you; it does not replace one or promise an interview.

Start with one experience.

In Gig History, you can write an experience by hand, choose what to publish, and share a link where hiring teams can read and ask questions. Your profile starts unpublished. Published profiles are unlisted and accessible to anyone with the link.

See the current plans and allowances.