Designers should be paid the same as engineers

👋 Hello, I’m Felix! This is an exclusive edition of AI-First Designer Newsletter, to help designers transition into successful AI-First builders. Members get access to proven strategies, frameworks, and playbooks.

Friends,

Let’s talk about something I’ve watched happen in offer letters for years, including my own, on both sides of the table.

Designers who build should be paid the same as engineers.

I know how that sounds. It sounds like a hot take. It sounds like something you’d scroll past on LinkedIn and assume was written for engagement. But I mean it in a quieter, more practical way. I mean it as someone who has seen what companies actually pay for, and what they only say they value.

Here’s how the gap got built. And why I don’t think it’s mysterious anymore.

How we ended up here

For a long time, a designer’s job ended at a file.

You made the thing look right. You cared about the details nobody else noticed. You handed it off. An engineer turned it into something real, something users could touch, break, complain about, love. Companies pay for what ships. So engineering owned shipping. And engineering owned the higher band.

That’s not a conspiracy. That was just true.

If you’ve been in this industry for more than a few years, you felt that structure in your bones. The late-night Figma comments. The handoff docs. The waiting. The sense that your work was “done” long before the product existed. You were essential, and somehow still adjacent to the moment of truth.

Adjacent is an expensive place to live.

What the numbers quietly say

I don’t want this to live only in feeling, because feelings are easy to dismiss in a negotiation.

According to Levels.fyi’s U.S. data, median total compensation for a product designer sits around $170,000. For a software engineer, it’s around $226,000. That’s not a rounding error. Thats a meaningful haircut — roughly a quarter less — attached to the folder your resume landed in.

And the climb isn’t even. Levels’ 2025 compensation report showed product designer median TC growing only about 1.8% year over year, while mid and senior engineering kept compounding harder. The market doesn’t just pay designers less once. It often keeps paying the “design” path slower.

When people say designers get paid less, I think what they’re really describing is a handoff-era job. The market still prices the label. It does not always price the work.

But look at what happens when companies stop pretending the work is only screens.

Roles called design engineer — people who design and ship — increasingly post compensation that looks more like engineering than classic product design. Ramp’s Design Engineer role, for example, has been listed in the $172k–$440k range. That isnt a “nice portfolio” band. That’s a “you make the product real” band.

The industry is already telling on itself. Just not always in the job title they offer you first.

The part that changed

It isn’t true anymore that design has to end at a file.

I know designers right now who take an idea from a blank canvas to a deployed product without ever opening a handoff doc. Same feature. Same outcome. Same user impact. Still, somehow, twenty to forty percent less money in too many offers — because a recruiter dropped their resume into a folder called design.

You were never paid less for being a designer.

You were paid less for handing off.

AI didn’t make taste optional. It made waiting optional.

The old pipeline asked you to design, document, wait for capacity, argue edge cases in tickets, and hope the thing still felt like your intention when it finally shipped. The new pipeline, for people willing to learn it, looks more like this: design the product, build a working version with AI on a real stack, put a live link in front of someone, and iterate on something that already exists.

Same craft. Same judgment. Different economics.

If you only deliver screens, you are still competing in the old market, the one built around handoff. If you deliver a link, you are competing in the market that pays for shipping. Those are not the same conversation, even when the company uses the same word for both of you.

What this does to us personally

There’s a quieter cost here that doesn’t show up in Levels charts.

When your work ends at a file for long enough, you start to internalize a smaller story about yourself. You become excellent at process. You become excellent at explaining. You become excellent at waiting politely. And then you walk into an interview with a case study about how you think, while someone else walks in with something the interviewer can open on their phone.

I’ve watched talented people shrink their ask because the system taught them that design is preparatory. Preparatory work gets preparatory pay. Even when the person in the room is no longer preparatory, even when they already shipped the thing.

That mismatch is exhausting. It’s also negotiable. But only if you stop arguing from the old story.

How to walk into the room differently

So if you build, stop pricing yourself like someone who doesn’t.

Don’t walk in with a case study about your process as the main event.

Walk in with the link. Let them use it. Let them click around. Let the product do the talking you used to do in slides. Then ask what the engineering band is for the person who would have built it, because that’s the job you just did!

The title on your offer is a filing decision. The number should follow what you actually shipped.

A simple way to say it out loud:

I designed it and shipped it. Here’s the live product. For this scope, what’s the engineering band for the IC who’d own the same outcome?

You’re not requesting charity; you simply won't let a folder name determine the worth of a shipped result.

If you haven’t started yet

This is the part a lot of designers avoid, and I understand why.

For a long time, “learn to ship” sounded like “become a junior engineer in disguise,” and it’s extremely scary. It sounded like abandoning the craft that made you good. It sounded like starting over in a room where you used to be competent.

It doesn’t have to mean that anymore.

That’s why we built AI First Designer School (https://adplist.org/vibe-code-designers/), a community for designers who want to go from mockup to live product with AI. Vibe Coding with Cursor and Claude Code. Figma MCP. The unglamorous full-stack pieces that make a link real: GitHub, Vercel, Supabase, auth, domains. Lifetime access is only $129 ($10/month). There are about 1.9K members in there now.

I’m not telling you to join because every essay needs a button at the bottom.

I’m telling you because the pay gap doesn’t close with better case-study storytelling. It closes when you can put something live in front of people and negotiate from what shipped.

Apply to join today

If that’s where you are, if you’ve felt the quiet unfairness of doing more and still being filed under less, this is one place to build the missing piece.

Designers who build get hired. Designers who build, and then price themselves like builders, get paid.

Thank you for reading, and come join us and become a designer who ships.

See you at the next read,

Felix