How to write a portfolio headline and tagline that say what you do

Your headline is the first line most visitors read on your portfolio, and for many it's the only one before they decide whether to scroll. A good headline tells a stranger what you do and where you fit in a single glance. A weak one makes them work it out, and most won't.

This guide covers what makes a headline clear, a few formulas to start from, and many examples you can adapt.

Headline vs. tagline

The two terms get used loosely, so here's how this guide uses them.

• Headline: the main line under your name. It says what you do. "UX researcher for financial services apps."
• Tagline: an optional second line that adds focus, approach or a hint of personality. "I find out why people abandon forms, and help teams fix it."

Your headline must work on its own. The tagline is a supporting act. If you only write one, write the headline.

What a good headline does

A strong headline does three things:

1. Names what you do in words your target reader would use. "Front-end developer," not "digital experience craftsperson."
2. Narrows it down with an audience, industry, specialty or type of problem.
3. Stays short, usually under about ten words, so it reads in one glance and fits on a phone screen.

What it doesn't need to do is impress. Clever wordplay or grand statements tend to hide the information the reader came for.

The test for any headline: if someone read only that line and then had to describe you to a colleague, could they? If not, it isn't specific enough yet.

Four formulas to start from

Role + specialty

"[Role] specializing in [area]."

• "Copywriter specializing in B2B software"
• "Accountant specializing in small creative businesses"
• "Backend developer specializing in payments"

Simple and reliable. Good for job seekers in established fields.

Role + audience

"[Role] for [type of client or organization]."

• "Brand designer for independent restaurants"
• "Bookkeeper for freelancers and sole traders"
• "Content strategist for healthcare nonprofits"

Works especially well for freelancers, because it tells a potential client immediately whether you work with people like them.

Role + outcome

"[Role] who [helps someone achieve something]."

• "Product designer who makes complex tools easier to learn"
• "Data analyst who turns sales data into decisions"
• "Recruiter who helps engineering teams hire their first ten people"

Good when your value is easier to describe as a result than as a specialty. Be careful not to drift into vague promises like "who helps businesses grow."

Role + context

"[Role] with a background in [field]."

• "UX designer with a background in nursing"
• "Software developer with a background in accounting"
• "Marketing coordinator with a background in journalism"

Useful for career changers, because it turns your previous field into an asset instead of a gap. See the career change portfolio guide for more.

Examples by field

Here are headlines for a range of hypothetical people. None of them are perfect for everyone; use them as patterns.

Technology

• "Full-stack developer building tools for small teams"
• "iOS developer focused on accessibility"
• "DevOps engineer who keeps deployments boring"
• "QA engineer for mobile banking apps"

Design and creative

• "Illustrator for children's books and educational apps"
• "Product designer for internal business tools"
• "Wedding and event photographer in the Lake District"
• "Motion designer for explainer videos"

Writing and communication

• "Technical writer for developer documentation"
• "Grant writer for arts and community organizations"
• "Editor for nonfiction books and long-form reports"

Business, data and operations

• "Operations manager for growing e-commerce brands"
• "Financial analyst focused on retail forecasting"
• "Project manager for hospital construction projects"
• "Customer success lead for B2B software"

Education and public service

• "Primary school teacher specializing in early literacy"
• "Instructional designer for corporate onboarding"
• "Policy researcher focused on housing"

Notice that each one names a role and then narrows it. That narrowing is what makes them memorable. More field-specific advice is in guides like the software developer portfolio and designer portfolio.

Weak-to-strong rewrites

Most weak headlines fall into a few familiar traps. Here's how to fix each.

Too vague

Weak: "Creative professional" Stronger: "Graphic designer for packaging and food brands"

"Creative professional" could mean a hundred different jobs. Name the one you do.

Too many things

Weak: "Designer | Developer | Photographer | Writer | Strategist" Stronger: "Web designer who also builds the sites"

A list of five roles makes the reader wonder which one you're actually good at. Pick the one you want to be hired for, and mention a second only if the combination is the point.

All adjectives, no information

Weak: "Passionate, innovative problem-solver" Stronger: "Operations analyst who fixes slow, manual processes"

Adjectives describe how you'd like to be seen. The stronger version shows it.

Jargon or inside language

Weak: "Driving synergistic value across omnichannel touchpoints" Stronger: "Marketing manager for retail brands, online and in store"

Write in the words a hiring manager or client would type into a search box.

Too modest

Weak: "Aspiring web developer" Stronger: "Junior web developer building accessible sites"

"Aspiring" tells the reader you don't consider yourself ready. If you've built things, you're a developer. Describe what you do, not what you hope to become. For more on this, see building a portfolio with no experience.

Writing a tagline

Once your headline is clear, a tagline can add something the headline can't hold. Good taglines usually do one of these:

• Explain your approach: "I start every project by talking to the people who'll use it."
• Add a proof point: "Currently building scheduling tools at a healthcare startup."
• State what you want: "Open to senior design roles in London or remote."
• Show a little personality: "I like tidy data, clear charts and a good spreadsheet formula."

Keep it to one sentence. Avoid repeating the headline in different words. And if a tagline isn't adding anything, leave it out; a clean headline alone is better than a filler line.

Matching your headline to your goal

Your headline should point toward the work you want next, not just describe the job you have now. If you're a support engineer aiming for a developer role, "Developer with three years in technical support" will serve you better than "Technical support engineer."

That said, stay honest. Your headline should be something your projects and experience can back up. If a reader sees "Senior data scientist" at the top and then finds only beginner projects below it, the mismatch hurts more than a modest headline would.

Quick checklist

Before you settle on a headline, check:

• Does it name a recognizable role?
• Does it narrow that role by audience, industry, specialty or outcome?
• Is it under about ten words?
• Would my target reader use these words themselves?
• Do my projects back it up?
• Does it point toward the work I want next?

Write five or six versions, put them side by side and ask someone outside your field which one tells them most clearly what you do.

Putting it together

A clear headline is a role plus something that narrows it: an audience, a specialty, an outcome or a background. Keep it short, use plain words and make sure your portfolio backs it up. Add a tagline only if it brings something new, such as your approach, a proof point or what you're looking for.

Once your headline is set, write a professional bio that expands on it, so the top of your page reads as one clear introduction. If you're starting from a resume, Folitox AI can suggest a headline from it that you can then sharpen using the formulas here.