For most product design roles, the hiring manager opens your portfolio link before they read your resume properly. The resume gets a quick scan to check level and where you've worked, and then the click. So the order of priority is: a portfolio link that works and loads fast, two or three case studies that show how you think, and a resume plain enough to get you through the form and the recruiter's filter.
Most designers invert this. They spend a week on a beautifully laid out resume and leave the portfolio with five thin case studies that are mostly final screens.
What actually gets opened, in order
Picture a design manager at a product company in Bengaluru with forty applications for one mid-level role and an hour on a Thursday to get through them. Roughly what happens:
- The recruiter or the system has already filtered on years of experience and the basics.
- The manager glances at the top of the resume: current title, company, years.
- They click the portfolio link.
- They open one case study, usually the first or the one closest to their own product.
- If that case study is good, they look at a second one and then read the resume properly.
Every step depends on the one before. A broken link, a password you forgot to include, or a portfolio that takes ages to load on office Wi-Fi ends things at step three.
The resume: plainer than you think
A designer's resume has two readers: the application system and a recruiter who may not be a designer. Both want the same thing. Clear titles, clear dates, clear companies, and some idea of what you worked on.
Two-column layouts with skill bars and icons look good as a Dribbble shot and parse badly in Workday or Greenhouse, where your experience ends up scrambled across fields. Use one column, a readable typeface, and let your restraint be the design statement. Our ATS-friendly format guide covers the layout; it applies to designers as much as engineers.
Put the portfolio link at the top, next to your email, as a full readable URL. If it needs a password, put the password right there too. Hiring managers will not email you to ask for it.
For each role, write bullets about outcomes and scope rather than deliverables. Compare:
Designed screens for the onboarding flow in Figma.
Redesigned onboarding for the lending app; cut the steps to first loan application from nine to five, and completion went up over the following quarter.
The second one tells a manager what you were trusted with and what changed. If you don't have a number, describe the change in scope or the decision you drove. Don't invent a percentage. Interviewers ask about numbers, and an invented one falls apart in about two questions. There's more on this in writing bullet points that get read.
Skills: list tools briefly (Figma, prototyping tools, whatever you genuinely use) and the practices you can speak to in an interview: usability testing, design systems, interaction design. Skip proficiency bars. Nobody knows what "Figma: 85%" means.
The portfolio: fewer, deeper case studies
Two or three strong case studies beat six shallow ones. A hiring manager rarely reads more than two, so the extra four only dilute the impression.
Pick projects that differ in the kind of problem they solved. Visual variety matters much less. One that involved hard trade-offs with engineering or business constraints. One where research changed your direction. One with a shipped outcome you can talk about.
What a case study needs
A case study that gets finished usually covers, in plain language:
- The problem, and who had it. One short paragraph.
- Your role, honestly. "I was the only designer" and "I owned the checkout redesign within a team of four" are both fine. Overclaiming a team project gets caught in the interview.
- The constraints: deadline, tech limits, a stakeholder who wanted something else.
- Two or three decisions, with what you considered and why you chose what you did.
- What shipped and what happened after, including what didn't work.
Notice what isn't on that list: a "process" diagram of Empathise, Define, Ideate, Prototype, Test copied onto every project. Managers have seen it hundreds of times. Show the actual messy route instead: the rejected version, the usability session that changed your mind.
Put the summary at the top
Start each case study with three or four lines a hurried reader can take in before scrolling: the product, your role, the problem, the outcome. Then the detail. Many managers decide in the first screen whether to keep going.
Under NDA? Still doable
A lot of designers in India work at service agencies or on client projects they can't show. You can still write a case study:
Describe the problem and your decisions in words, blur or redraw sensitive screens, change the brand and the data, and say plainly at the top that details have been altered for confidentiality. What managers are assessing is your reasoning, which you can almost always share without the client's logo on it.
If you truly can't show anything, a well-chosen self-initiated project (a redesign of a flow you use daily, with a written rationale and some real user feedback) is better than an empty portfolio. Label it as self-initiated.
Freshers and career switchers
If you're coming out of a design programme or switching from graphic design, development or another field, the resume will be thin and that's expected. The portfolio carries you.
Course projects are fine. Make them read like real work: who it was for, what you learned from testing it, what you'd change. One project where you tested with five actual people and changed the design because of it is worth more than three polished concept apps that nobody used.
On the resume, a switcher should keep the previous career, briefly. A frontend developer moving into design has a real advantage when working with engineers; say so in one line. If you're a fresher, our resume for freshers post covers the basics of a first resume.
What to cut
From the resume: a photo, date of birth, a "hobbies" section that says "sketching, travelling", a skills section with fifteen tools, and any objective statement.
From the portfolio: case studies older than four or five years unless they're your best work, every visual exploration you did in college, and the third case study that's mostly a duplicate of the first. Also cut any project you can't talk about for twenty minutes. If it's in your portfolio, an interviewer may ask you to walk through it.
Check the boring parts
Before you send anything, open your portfolio link on your phone, on mobile data, in a private window. That's closer to how a busy manager will first see it than your laptop is. Check the password, check every case study loads, and check the link in the resume PDF is clickable.
It takes five minutes and catches the problem that sinks more design applications than any layout choice does.