Designers face a particular version of the overqualification trap: the portfolio is the proof, but the resume is the gate. If the resume reads “lead designer,” the portfolio rarely gets opened — and the IC role never happens.
Why design titles trip the filter especially hard
Designer titles compress like engineering titles, but with an extra wrinkle: design leadership reads as “process and team,” and IC design reads as “craft and shipping.” The shapes are very different.
A Lead Designer’s resume usually says:
- “Set the design vision for the product.”
- “Aligned 4 designers and 12 engineers on the new system.”
- “Owned the design system roadmap.”
An IC Senior Designer’s resume should say:
- “Designed and shipped the v2 onboarding flow; cut signup drop-off 38%.”
- “Owned the checkout redesign end-to-end (research → ship).”
- “Built the component library and shipped 22 production components.”
Same person can do both. The resume must pick a shape.
The three filter signals (designer-specific)
1. Title
“Lead,” “Principal,” “Director of Design,” “Head of Design” — leadership-coded. On an IC application these trip the filter even when the work matched. Retitle honestly if the work was 50%+ hands-on (e.g., “Senior Designer / Design Lead”).
2. Scope language in the first bullet
“Set the vision for…” “Owned the design strategy across…” “Aligned X designers on…” — leader-shape language. Replace with shipped work.
3. Process-vs-craft balance
A bullet that describes the process (“ran 3 design critique sessions; aligned PM, eng, and design”) reads leadership. A bullet that describes the craft (“designed the new home screen; A/B tested 3 variants; shipped the winner with a 17% CTR lift”) reads IC.
The IC role wants 70%+ craft bullets. The lead role tolerates 50/50.
Six surgical edits for designer downshift
Same shape as the applying-down-a-level playbook, with design-specific tuning:
- Retitle if accurate. “Senior Designer / Design Lead” if you spent 50%+ on the craft.
- Lead with shipped work. “Designed and shipped X (metric)” before any process or team bullet.
- Drop scope language. “Aligned the design org on…” → out. Replace with a shipped artifact.
- Show craft. Mention specific design decisions: “moved the CTA from drawer to inline modal; conversion from 12% to 19%.”
- Drop the team-size mentions. “Mentored 4 designers” reads leadership; replace or move to the bottom of the role.
- Curate the portfolio for IC craft. Lead with shipped work and metrics. Save the design-system-roadmap and team-vision case studies for lead applications.
The “I built the design system” trap
Design system work is high-leverage but reads as platform/leadership work. On an IC role, lead with product-shipping work instead. Move the design system bullet to position 3–4 of the role, not position 1.
If the IC role specifically wants design system experience, that bullet can move up — but mirror the JD’s framing. If the JD says “ship components,” your bullet should say “shipped 22 production components,” not “owned the design system.”
Run the design altitude check
The diagnostic reads your resume’s verb shape and scope language, then compares to the JD’s expected altitude. If you’re tripping the leadership filter on an IC application, the verdict tells you which bullets to rewrite first.
Check my designer altitude — free →
When the portfolio matters
Once the resume clears the gate, the portfolio carries the rest. But you need to clear the gate first. A great portfolio with an overqualified resume gets the same callback rate as no portfolio at all — because the portfolio link doesn’t get clicked.
The order: fix the resume, then optimize the portfolio for the role altitude.
Related reading
- Applying down a level — resume tips — the deliberate-downshift framework.
- How to fix an overqualified resume — the canonical edit list.
- Is this job below my level? — the pre-application check.
- Manager to IC resume step-down — adjacent transition pattern.