VII.Founding designer · July 2026
One designer, a room full of engineers, and a job description that rewrites itself weekly.
Being the only designer in an engineering-led startup is part product design, part marketing asset factory, part front-end bug hunt — and, on the good days, the fastest way for a company to grow a design eye.
By Gisella Famà · 5 min read · Founding designer
There is a specific kind of quiet you notice when you're the only designer in a company full of engineers. Not a bad quiet. Just an unfamiliar one. Nobody is arguing about spacing. Nobody is quoting a Dieter Rams principle in Slack. Nobody is going to notice that the modal has drifted four pixels to the left over the course of three sprints. That part is on you.
It is interesting. It is sometimes hard. And, on the weeks it clicks, it is one of the most rewarding jobs I've had.
"When you are the only designer, design isn't a department. It is a habit the company either picks up or doesn't — and you're the one holding the mirror."
The job description keeps rewriting itself
Monday I'm doing what most people would call classical product design. Flows, prototypes, a user testing session with people who very politely explain that our onboarding is confusing. Tuesday I'm making a set of marketing assets because the launch is on Thursday and "you're the designer" is, technically, true. Wednesday I'm in the codebase removing a visual bug that nobody else noticed, because I noticed, and because the fix is smaller than the Loom I would have to record to explain it.
None of this appears in a job spec. All of it is the job.
What being a generalist actually looks like
Product design and prototyping, yes — but often at the speed of "can you have something by end of day", not the speed of a case study.
User testing that you run, moderate, synthesise, and turn into a decision, sometimes in the same afternoon.
Marketing assets: a landing hero, a LinkedIn banner, a slide deck that has to look like it was made by a company three times our size.
Front-end tweaks: spacing, states, the tiny bits of polish that would sit in a backlog for six months if you filed a ticket instead of opening a PR.
The invisible work: naming things, killing bad ideas early, being the person who says "we don't need that yet" without turning it into a debate.
The hard part isn't the workload
The hard part is context switching without dropping the plot. You can be halfway through a research readout, get pulled into a marketing emergency, come back three hours later and try to remember what the insight was. Nobody is going to protect your calendar for you. You have to protect the through-line yourself — the reason all of this work is meant to connect back to a product that people can actually use.
The other hard part is that there is nobody to check your taste. No senior designer nodding or wincing at the right moments. You are the taste, for better or worse, and the company will absorb it either way. That is a strange kind of responsibility. It is also the whole point.
Why an engineering team is a good place for it
I used to think being the only designer in an engineering-led company would be lonely. It isn't, or at least not in the way I expected. Engineers who take design seriously are some of the sharpest collaborators you can have. They don't want a mood board. They want a decision, a reason, and a spec they can build against. The bar for craft is high, just measured differently — in how well the thing works, not how well it photographs.
The trade you're making is: you lose the design critique culture, and you gain a build culture. If you can bring your own critique with you, the trade is a good one.
"A founding designer isn't there to make the product pretty. They're there to make sure the company knows what it looks like — inside and out — before it forgets."
Why now is a good time to be a generalist
These are strange, generative times. Tooling has collapsed the distance between "I have an idea" and "there is a working version of it". A single designer with taste, opinions, and enough curiosity to open a PR can move a company's design maturity forward by a year in a few months. Not because they're doing more work, but because they're closing loops nobody else was closing.
The companies that figure this out early get compounding rewards. Good foundations. A house style that doesn't need a rebrand at Series A. A product that feels considered before it needs to be defensible. The companies that don't figure it out end up hiring three specialists eighteen months later to undo the drift.
What I'd tell the next founding designer
Say yes to the weird asks. The banner, the deck, the front-end fix, the naming exercise nobody wants to run. Each one is a chance to set a tiny piece of the standard while nobody is watching. Once enough of those tiny pieces exist, the company starts to have an eye — not because you gave a talk about design principles, but because the work looks a certain way and people started to expect it.
And accept that the job description is never going to sit still. That is not a bug. That is the reason the role exists. If you wanted a stable brief, you would have picked a different chair.
Disagree? That's the point. Tell me why.
← Back to all thoughts