All notes
2 min read

The Eternal Reinvention Tax

Why Designers Keep Rewriting Case Studies, Engineers Don't

TL;DR

Product designers must document their thinking, prove impact, and master tools that launched last week, while the engineer's LinkedIn has said the same two words since 2019 and they are doing fine.

Product designers arrive at job interviews with case studies bound like dissertations. We have documented our thinking in Figma frames that could wallpaper a small apartment. We have optimized our LinkedIn headlines to within an inch of their lives, and A/B tested our portfolios.

Meanwhile, the engineer’s LinkedIn says “software engineer” in lowercase. It has said this since 2019. Their last post was a conference photo. They are doing fine.

The product manager walks into the same interview with a smile and three good stories about stakeholder alignment. No portfolio. No pixel-perfect mockups of their “strategic” thinking. They will talk about frameworks they have used, challenges they have navigated, teams they have guided toward better outcomes. Somehow this is enough. More than enough, often. Never mind that some cannot navigate a spreadsheet without help, or that learning a new tool seems optional for them while designers are expected to master the latest prototyping software by Tuesday.

Now there is AI to contend with. Job descriptions want five years of experience with tools that launched eighteen months ago. They want designers who have worked in fintech, healthcare, and enterprise SaaS simultaneously. They want documentation of your design process that reads like a peer-reviewed journal, even though actual design happens in fits and starts when you finally understand what the problem actually is.

It might be that design is cursed by being visible. Our work can be screenshotted, posted, critiqued by strangers who have opinions about rounded corners. We are asked to prove our thinking made the numbers go up, even when seventeen other variables changed that same quarter. The case study is not really documentation. It is a defensive perimeter.

Engineers have their own gauntlet of whiteboard problems and code reviews, certainly. But there is something about simply being an engineer that carries weight. Product managers exist in some other realm entirely, measured by outcomes that require no demonstrated facility with the tools that produce those outcomes.

Request an AI summary

Learn more about the ideas and references behind this note.

FAQ

Why do designers face higher proof-of-work demands than other roles?
Design is visible. It can be screenshotted, posted, and critiqued by strangers. Designers are asked to prove their thinking moved the numbers, even when seventeen other variables changed that quarter. The case study is less documentation than a defensive perimeter.
How has AI changed expectations for product designers?
Job descriptions now ask for five years of experience with tools that launched eighteen months ago, plus simultaneous expertise across multiple industries. The reinvention cycle has accelerated while engineers and PMs face comparatively stable expectations.
What are some related topics to explore?
product design hiringdesign portfolioUX careercase study fatigueAI and design jobsdesigner vs engineer expectations

Defined Terms

Case study
In product design hiring, a long-form portfolio artifact documenting a single project's research, reasoning, and outcomes.
Portfolio culture
A hiring norm in design that places disproportionate weight on self-produced documentation of prior work.

Foundations

UX Portfolios: What Hiring Managers Look For
Nielsen Norman Group
The Peter Principle: Evidence from a Natural Experiment
Digital Enterprise

Related Reading

Related Notes

The Metric That Ruins Everything
Software teams track everything: time on page, clicks, conversions, engagement. Then someone picks the metric that matters. That's when things start breaking.
The Performance of Not Performing
Creators build audiences by showing the same jacket twice and mending jeans. The algorithm now rewards its opposite. Not selling is the new pitch.
The Part Nobody Designed For
Haptics shift how buttons feel. Colour and scent shape decisions. The emotional layer of interfaces was never in the spec but always in the experience.