Guide 10 min readUpdated by the Design Code Jobs editors

Design engineer portfolio examples and what to include

A design engineer portfolio proves you can design an interface and build it in production code. The strongest ones show live work you can click, the code behind it, and a short note on what you decided and why. Hiring teams read them for craft, ownership, and systems thinking, not for polished mockups alone.

This guide is based on 36 open design engineer, UX engineer, UI engineer, design systems, and creative technologist postings from 23 companies, pulled from public Greenhouse and Ashby job board APIs on 3 November 2026, plus eight public portfolios from working design engineers, checked the same day. It covers what to include, what hiring teams look for, real portfolio examples, which format to use, and how to start without a design engineer job. Mechanical design engineering portfolios are a different thing, and they are not covered here.

On this page:

Roles that ask for this kind of work are on design engineer jobs.

What should a design engineer portfolio include?

A design engineer portfolio should include three to six pieces of live, working work: shipped product UI, an interactive prototype, and a reusable component or design system contribution. Give each one a link a reviewer can open, the code or a write-up of how it was built, and a plain statement of what you personally designed and built.

The postings are specific about the kind of work they want to see. Ramp asks for craft “in live experiences or working prototypes.” Stripe’s Expansion team lists “design systems, engaging microsites, Figma plugins, webGL experiments, CSS art, or anything else—you tell us.” WRITER wants work “that includes systems-level work and not just feature work.” Put together, a solid set looks like this:

  1. One shipped product surface. Something real people used, with a link if it is public and a short account of the problem, the constraints, and the result.
  2. One interactive prototype. A working build of an idea, not a video of a Figma file, so a reviewer can feel the interaction.
  3. One component or system piece. A reusable component, a design token setup, or a contribution to a design system, with its states and accessibility handled.
  4. One piece of motion or interaction detail. A transition, gesture, or micro-interaction, built in code. The motion skill page lists roles that ask for this.
  5. Code a reviewer can read. A GitHub repo, a CodeSandbox, or annotated snippets in the write-up.

Keep each write-up short. Say what you owned, what you traded off, and what you would change. You can check your set against the design engineer portfolio checklist, which tracks the same proof points, including empty, loading, and error states.

What do hiring managers look for in a design engineer portfolio?

Hiring managers look for craft you can feel in a live build, clear personal ownership, and work beyond surface polish. Of the 36 postings checked on 3 November 2026, 11 asked for a portfolio by name. They wanted live experiences, working prototypes, systems-level work, and substantial personal contribution to shipped products, not marketing pages alone.

Here is what those postings say the portfolio has to show, in their own words.

PostingWhat the portfolio must show
Ramp, Design Engineer“high visual and interaction craft in live experiences or working prototypes”
tldraw, Design Engineer“exceptional product craft and substantial personal contribution to shipped products”
WRITER, Design engineer“a portfolio, side projects, GitHub, or production work that includes systems-level work and not just feature work”
Reddit, Principal UX Engineer, Ads“use cases, technical architecture, systems thinking, organizational complexity, and collaboration with engineering teams, not only polished UI outcomes”
Stripe, Design Engineer, Brand Studio“technically ambitious, highly crafted work such as experimental websites, interactive experiences, realtime graphics, games, installations, creative tools”
Stripe, Design Engineer, Expansion“design work and frontend code showcasing design systems, engaging microsites, Figma plugins, webGL experiments, CSS art”
Perplexity, Design Engineer, Growth & Marketing“A portfolio site that shows your previous work on marketing sites and design work.”
Granola, Design Engineer (Web & Brand)“work you can show us that demonstrates both visual judgement and technical ability”

Two patterns stand out. First, the bar is live, working work. Not one of these postings asks for static mockups. Second, ownership matters as much as polish. tldraw also asks for “experience working on sophisticated interactive software, not only marketing websites or static interfaces,” and Reddit says “not only polished UI outcomes.” Brand and marketing teams, like Stripe’s Brand Studio, Perplexity’s growth team, and Granola’s web team, are the exception, and they do want sites and experiments.

Some teams look at work live instead of reading a site. Ashby’s eight Design Engineer and Staff Design Engineer postings (one role per region) say the first call is a 30-minute introduction where you should “be prepared to screen-share examples of your work.” Have two or three pieces ready to walk through, including the code. For the full loop, take-homes and resume prep, read design engineer interview questions.

Which design engineer portfolio examples are worth studying?

The most useful design engineer portfolio examples are personal sites from people who do the job, because they show the work instead of describing it. Emil Kowalski, Rauno Freiberg, Paco Coursey, shadcn, Jhey Tompkins, Jonnie Hallman, Jakub Krehel, and Lochie Axon each lead with live projects, open-source code, or interaction experiments.

Each of the portfolios below was live on 3 November 2026. The descriptions come from the sites themselves.

  • Emil Kowalski describes himself as a design engineer who “worked at Linear and Vercel where I helped build the visual side of the product and marketing surfaces.” His projects include open-source React components such as Sonner, a toast component, and Vaul, a drawer. His write-up “Building a toast component” is a model project write-up: it walks through the animation, swipe gesture, and state code, with live demos. What to take from it: one deep write-up of a component, with code, beats ten screenshots.
  • Rauno Freiberg, an interaction designer working with Vercel, keeps a Craft page: a dated list of small interaction builds such as “Exclusion Tabs,” “Gooey Shader,” and “⌘K Breadcrumbs,” next to product work like “Next.js Dev Tools.” His essay “Invisible Details of Interaction Design” explains the thinking behind them. What to take from it: a steady stream of small, dated experiments shows craft and curiosity over time.
  • Paco Coursey says he is “Webmaster at Linear” and that “in the past I’ve developed the Vercel design system, website, and dashboard.” His projects include next-themes, dark mode for Next.js apps, and cmdk, a command menu component. What to take from it: naming the system you built and linking the libraries other teams use is strong proof of systems-level work.
  • shadcn writes “I’m a design engineer on the AI team at Vercel. I created shadcn/ui and shadcn/registry.” The shadcn/ui repository is public. What to take from it: a portfolio can be a short list of products, each one linking to the thing itself.
  • Jhey Tompkins, “Designer · Engineer · Tastemaker” at Shopify’s Brand Design Studio, describes his work as “crafting interfaces, prototypes, and experiments for the web.” What to take from it: for brand and creative roles, playful CSS and motion experiments are the portfolio.
  • Jonnie Hallman, an independent design engineer and formerly “a staff design engineer at Stripe, leading the design engineering team for stripe.com,” lists the landing pages and marketing sites he built and has written up how he built several of them, such as Building the Open Standard website with Stripe. What to take from it: process posts turn a finished site into evidence of how you work.
  • Jakub Krehel, a founding design engineer at Interfere, pairs small tools like a guide to OKLCH colors and a loader library for React with essays. In “The invisible side of design engineering” he points to “accessibility, responsiveness and performance” as work that rarely gets shared. What to take from it: say in writing what you fixed that nobody sees.
  • Lochie Axon lists sites under a “design engineer” heading, such as aave.com and family.co, then his own tools: easing.dev, “a collection of easing functions for web animations,” and npm packages like web-haptics. What to take from it: a one-page list of links can work if every link is real, working work.

For more names, Maggie Appleton keeps “A Collection of Design Engineers”. She adds a useful warning: “the work people put in public is not necessarily the work they do day-to-day,” and “some of the especially tedious and labourious work isn’t easily shareable, such as advocating for robust design systems and cleaning up legacy code.” Your portfolio should explain that work in words, even when you cannot show it.

Should a design engineer portfolio be a website, GitHub, or case studies?

Use a personal website as the front door, and link GitHub and short case studies from it. A built site is itself a code sample, so it shows craft that a PDF cannot. Add GitHub for readable code, and add case studies for team work you cannot open-source, explaining your role, decisions, and the result.

Most of the examples above follow this shape. The site is the index, each project links to a live build or a repo, and the longer pieces are written up as posts. WRITER explicitly accepts “a portfolio, side projects, GitHub, or production work,” so any of these can carry the proof as long as it is easy to find.

A few practical rules:

  • Make the site fast and accessible. Reviewers judge the portfolio as a product. Check it with a keyboard, a screen reader, and on a phone.
  • Put the best work first. Ashby’s first round is a 30-minute call. Lead with the two pieces you would screen-share.
  • Label private work clearly. For work under NDA, write a short case study with your role, the constraints, and what shipped, and offer to walk through it live.
  • Keep a CV that matches. The same projects should appear on your CV. Run it through the resume checker for design engineers before you apply.

How is a design engineer portfolio different from a UX or front-end portfolio?

A UX designer portfolio usually tells the story of research and design decisions through images. A front-end developer portfolio usually shows code and apps. A design engineer portfolio has to do both in each project: show the design reasoning and the working build, with your hands on both halves.

Ashby’s posting puts it bluntly: the role “isn’t just a Frontend Engineer with new branding, nor is it a Designer vibe coding prototypes.” So a design engineer project should show the Figma exploration or sketch next to the shipped component, and name the trade-offs between the two. If you are coming from UX design, add live builds and code. If you are coming from front-end, add the design thinking: why this layout, why this motion, what you tried first.

UX engineer and UI engineer portfolios sit close to this. Reddit’s Principal UX Engineer posting wants architecture and collaboration with engineering teams, which pushes the portfolio toward systems and process more than visuals. The UX engineer guide covers how that title differs, and what a design engineer is covers the broader role.

How do you build a design engineer portfolio without job experience?

Build and ship small, real projects that people use. Ashby’s posting says it expects “experience designing products and shipping code to hundreds of users (even if through side projects).” A small open-source component, a tool, or a site for a real client, each with a write-up, can stand in for job experience.

Some starting points, taken from the kind of work in the postings and examples above:

  1. Rebuild one interaction you admire, in code, and write up how you did it and what you changed.
  2. Publish one reusable component to npm or GitHub, with documentation, keyboard support, and its loading, empty, and error states.
  3. Design and build one small tool for a real group of users, then report what they did with it.
  4. Keep a dated experiments page, like Rauno Freiberg’s Craft page, and add to it every few weeks.

Ashby’s posting also describes what it wants at the junior end: “projects (personal or professional) with at least a couple of users that showcase great visual taste and burgeoning talent in both UI/UX and Engineering.” The how to become a design engineer guide covers the skills and routes into the role. Entry-level openings, when they appear, are listed on junior design engineer jobs.