Role-specific CVs

Freelance technical writer CV: show audience and documentation scope

Help a client understand what you documented, for whom, and how the work fit the project.

Name the audience and deliverable

Use O*NET’s technical writer profile as a prompt to research common tasks, then match the brief to documents you have actually produced. State whether your work covered user help, internal procedures, release notes or another deliverable.

Name the intended audience when that information is safe to disclose. A document for customers and an internal engineering guide may require different examples.

Explain how you worked with subject experts

Describe how you gathered and checked information, handled review comments or maintained a document set if those responsibilities were yours. Keep the distinction between writing, editing and technical approval clear.

Do not imply that you validated technical facts independently when a subject expert approved them. Explain your process without naming confidential systems or people.

Choose shareable writing samples

Link to public or approved examples and label the document type. If no sample can be shared, describe the scope and review process without reproducing client material.

Check that a sample does not expose private product plans, customer data or internal procedures before publishing it.

UK considerations

This is general CV guidance, not a rule for every employer. Follow the UK client or recruiter’s requested format and application instructions.

Sources and further reading

Keep your project history clear

Build a CV around the work you have done.

Start your CV
← All freelance CV articles