How to build a developer advocate portfolio

Roan Weigert editorial portrait for a developer advocate portfolio

Written by

in

A developer advocate portfolio should connect a capability to work someone can inspect. Include your contribution, an implementation or recording, and the context needed to interpret the result. My portfolio combines engineering projects, research, technical writing, speaking, video production, and community work because each demonstrates a different responsibility.

Let the visitor choose what they want to evaluate

A hiring manager looking for implementation depth should reach a repository quickly. An event organizer needs a speaking sample. A team planning developer education needs to see how I explain a technical subject. I organize a portfolio around those questions.

My selected work, community and speaking page, and press page give visitors different starting points. The link labels should explain what is behind the click. A project title alone often leaves the visitor to work out why it matters.

Connect each capability to an artifact, your contribution, and evidence the reader can inspect.
Connect each capability to an artifact, your contribution, and evidence the reader can inspect. My proposed working framework, illustrated for this article.

Show technical judgment with a build and an experiment

My academic-paper analysis project demonstrates a retrieval workflow, while my generative-video evaluation demonstrates an approach to comparing outputs and cost. They answer different questions. One shows how I assembled a system; the other shows how I examined behavior.

A useful project card explains the task first, then identifies my contribution and points to the implementation. For the research project, the paper, dataset, and code belong together. A reader should be able to separate the method from the conclusions and decide how relevant the sample is to their own work.

I keep collaboration visible. If a project includes another person’s work, the portfolio should name the role I owned and credit the team. That makes the evidence easier to discuss in an interview.

Separate authored work from coverage about the work

The GPU bill is the new AWS bill is an opinion article I authored for CIO. It demonstrates how I explain AI infrastructure decisions to a business audience. The byline matters because it identifies the contribution.

The AI Journal profile and the IntelligentHQ profile are coverage about my work and background. They provide another route into the portfolio. I label those as profiles so a visitor understands the difference between an article I wrote and an article about me.

My World Models book is a longer teaching artifact. A book invites a reader to follow a subject over several chapters. It can sit beside shorter technical articles because the formats answer different learning needs.

TV Tarobá coverage of my book. The broadcast linked from my press page provides context for the book project. The segment is in Portuguese. Watch on YouTube.

Let a speaking sample demonstrate the delivery

My speaking page links a keynote, a CANA panel, and a recording associated with LA Tech Week and the AI Builders Meetup at GitHub HQ. The recording lets an organizer evaluate how I explain a subject and engage an audience.

I also include smaller teaching settings. My session with the SJSU AI/ML Club covered inference concepts and practical API use. A university workshop, a panel, and a keynote each ask for a different delivery style. Showing the setting makes the experience legible.

Roan and SJSU AI/ML Club participants
A university teaching example alongside conference and panel recordings. Source and context.
My keynote at Digital Garage, linked from my speaking portfolio. Watch on YouTube.

Give production work its own evidence

My San Francisco studio build shows the work behind producing educational video and interviews. The article documents the layout and the two recording formats. My technical-storytelling article explains how that production background fits into developer relations.

A studio photograph demonstrates the environment. A finished lesson demonstrates how I use it. I want both in the portfolio so production skill connects to a learning outcome rather than becoming a list of equipment.

Make the next conversation specific

Before sharing a portfolio, I read it as someone who has five minutes. Can they identify the relevant work, understand my role, and open a useful artifact? I then read it as someone preparing a detailed interview. Can they find enough material to ask about an implementation decision or a teaching choice?

Start with one project and write four sentences: the task, your contribution, the result you observed, and what the linked artifact lets someone inspect. Add a photo or recording that supports those sentences. That is a strong portfolio entry you can keep improving.

Questions readers ask

Can I build a portfolio before my first DevRel job?

Yes. A personal integration, a clear tutorial, or a community contribution can demonstrate relevant work. Describe the context accurately and make the artifact easy to inspect.

Do I need a large audience?

An audience can provide useful context, while the work itself can demonstrate technical and teaching ability. Show who the resource serves and how it helps them complete a task.

What should I improve first?

Choose one project and make its purpose, your contribution, and its evidence clear. A detailed, understandable example gives the reader more to discuss.