---
title: "How to Hire a Founding Designer | Utkarsh Panwar"
description: "What a founding designer is and how to hire your first one: when to hire, which contract, interviews, equity and red flags. From a YC founding designer."
url: https://www.utkarshdesign.com/guides/hiring-your-founding-designer
author: Utkarsh Dhairya Panwar
updated: 2026-10-08
---

# What a founding designer is, and how to hire one

Guide · 8 min read · By [Utkarsh Dhairya Panwar](https://www.utkarshdesign.com/about) · Updated 8 Oct 2026

![The CodeAnt AI team, about 18 people in matching black hoodies, on a seaside terrace with palm trees](https://www.utkarshdesign.com/images/K3suPixRz4jMGM5qYBqQbdwYy8.webp)

**A founding designer is a startup's first designer, owning the product, website, brand and design system. Hire one when design is blocking a number you can measure, like activation or website conversion. Start freelance or fractional for one clear problem, and go full-time once that work runs every week.**

## What a founding designer is

I've been the founding designer at CodeAnt AI (YC W24) since June 2024. In practice that means designing the product, the Framer website, the brand and the design system, often in the same week. Nobody sets design priorities for you, so you set them with the founders, from what the numbers say.

"Founding" is about timing and scope. You arrive before there's a design process, and part of the job is building one the next designers can join. (A design co-founder is different: they start the company.)

- Product designer: designs features inside a defined product area. A founding designer also decides which area matters this quarter.
- Design lead or head of design: manages designers. A founding designer usually has no reports yet and does the work directly.

## When a startup needs its first designer

You need one when a design problem is costing you something you can count. The first problem I owned at CodeAnt had a clear number on it: developers dropped at the repo-connection step because they lacked GitHub admin rights (the full story is in how we doubled trial-to-paid).

A rough-looking product isn't enough on its own, since plenty of teams win their first customers with an engineer-built UI. I'd hire when one of these is true:

- Engineers make layout and flow decisions inside pull requests, and those decisions keep getting reversed.
- Signups are fine but activation is flat, and nobody can say which step loses people.
- Your website explains the product to people who already understand it, and to nobody else.
- Sales calls stall while someone narrates the product. At xPay, redesigning the checkout used in live demos cut sales walkthrough time by 30%.
- You're about to build a second product line and the first one has no shared components.

If none of these apply yet, keep shipping and look again next quarter. A designer with nothing measurable to own drifts towards polish.

## Freelance vs fractional vs full-time designer

Pick the contract by the shape of the work. A website rebuild is a project. Onboarding, pricing pages, dashboards and a brand that changes every month add up to a stream.

|  | Freelance | Fractional | Full-time founding designer |
| --- | --- | --- | --- |
| Best for | One scoped project: a Framer site, an audit, an MVP flow | Steady product and site work before you can justify a hire | Continuous work across product, site and brand |
| Commitment | Fixed scope, a few weeks | Agreed days or hours a week, billed monthly | Full-time, usually with equity |
| Owns outcomes | Only within the scope | Yes, for the areas you agree | Yes, for all of design |
| Main risk | Gaps once the project ends | Context lost between sessions | Hiring before there's enough to own |
| How to judge it | Did it ship and work | Do the agreed metrics move month to month | Is design still the bottleneck after six months |

Plenty of startups go freelance, then fractional, then full-time. That works if each designer leaves files, components and written decisions the next one can pick up.

## What to look for in a founding designer

A founding designer is the only designer, with no lead reviewing their work and no researcher handing them findings. So check these:

- Range across surfaces. Someone who has only worked on one surface will need help on the others.
- They can build the marketing site themselves. If they work in Framer or Webflow, the site stops competing with the product roadmap for engineering time.
- They talk about numbers they moved and are precise about their share of the result.
- They can describe a decision they got wrong and what they changed.
- They understand your users' tools. For a developer product that means knowing what a pull request, a CI check and an org admin are.

## How to interview your first designer

1. **Go deep on one project**: Ask them to pick one shipped project and explain the problem, the options they dropped and what changed after launch. Thirty minutes on one project tells you more than a slideshow of ten.
2. **Ask what they'd fix first**: Give them your signup flow or website beforehand. A strong candidate names one step and a hypothesis about it instead of a list of visual tweaks.
3. **Run a short paid trial**: One real problem, a few days, paid. You'll see how they ask questions and handle missing information, which matters more than the output.
4. **Call an engineer they worked with**: Founders give references about outcomes. Engineers tell you whether specs were buildable and whether the designer thought about edge cases.
5. **Write down the 90-day outcomes**: Two or three, agreed before the offer. For example: activation on a named step, a rebuilt site live, a component library the engineers use.

## Talking about equity, in general terms

Founding designers are usually offered equity on the same logic as early engineers: they join before the company can pay a market salary and shape things that are hard to redo. The structure normally mirrors what your early engineers got, including vesting.

I've sat on the other side of that table, and two things mattered to me. "Founding" should mean ownership: a seat in product planning and the final call on design, beyond an early start date. And the scope needs to be exact, because "product, website and brand" is a bigger job than "product UI". For numbers and tax treatment, ask your lawyer or accountant; this isn't legal or financial advice.

## Red flags when hiring a first designer

- Every case study ends at the Figma file. Nothing shipped, or they can't say what happened after.
- Process slides with no decisions in them: personas and diamond diagrams, but no moment where they chose one option over another.
- They want to start with a full rebrand before finding out where users drop.
- Only polished shots. A dashboard with no empty, loading or error states usually means they haven't designed one people used daily.
- On your side: a brief that says "make it look more premium" with no problem attached. That brief produces a reskin.

## What the first three months should produce

At seed or Series A, I'd expect a founding designer's first quarter to include one activation fix shipped and measured, a starter component set the engineers import, and a website a cold visitor can understand. At CodeAnt the repo-connection fix cut drop-off at the admin wall by 40%, and the component work started much smaller than the system it became.

If you'd like someone to own this part-time before you commit to a hire, that's what my fractional product designer service is for. If you're hiring for the full-time seat, I'm open to founding roles, and the open-to-roles page has the details.

## Questions people ask

### What does a founding designer do day to day?

Whatever design problem is costing the company most that week: an onboarding step, a landing page, a component the engineers keep rebuilding. Most of the job is choosing which one.

### What's the difference between a founding designer and a first design hire?

A founding designer owns design across the company and has a seat in product decisions, usually with equity. A first design hire can be narrower, for example product UI only.

### Can a founding designer work remotely?

Yes, if the team works from written context and keeps a short daily overlap. I'm based in India and work remotely with teams in other time zones.

## Sources

1. [Installing a GitHub App from a third party](https://docs.github.com/en/apps/using-github-apps/installing-a-github-app-from-a-third-party), GitHub Docs

## Working on this?

Tell me what you're building and where it's stuck: [book a 30-minute call](https://cal.com/utkarsh-design/30min), email [work@utkarshdesign.com](mailto:work@utkarshdesign.com) or [send a brief](https://www.utkarshdesign.com/contact).

## Related

- [Fractional product designer for early-stage startups](https://www.utkarshdesign.com/services/fractional-product-designer)
- [Founding product designer, open to new roles](https://www.utkarshdesign.com/open-to-roles)
- [Product designer vs UX designer vs UI designer](https://www.utkarshdesign.com/guides/product-designer-vs-ux-designer)
- [CodeAnt AI (YC W24)](https://www.utkarshdesign.com/work/codeant-ai)

---

Utkarsh Dhairya Panwar, Founding Product Designer and Design Engineer (IIT Roorkee; Founding Designer at CodeAnt AI, YC W24). Email: work@utkarshdesign.com · Book a call: https://cal.com/utkarsh-design/30min · Hire: https://www.utkarshdesign.com/hire · About: https://www.utkarshdesign.com/llms.txt