Egor Krasnoperov · July 28, 2025 · 8 min read
What if I were just starting out in design today?

No job yet. No commercial experience. Just a bunch of curiosity and the drive to figure things out.

What if I was trying to land my very first UX/UI role in 2025, when the market is flooded, AI keeps evolving, and job posts keep asking for “3+ years of experience” like it’s no big deal?

Would it still be possible to break in?

Honestly, I think it would. But I’d have to approach it differently. Not through perfect credentials, but by being intentional, resourceful, and visible.

So here's what I might do if I were a junior designer with no experience, trying to get that first real job.

How to land your first UX/UI, Product Design job without experience (and not lose your mind along the way)

Portfolio. I’d focus on building a real website, not a Behance or Notion portfolio
Notion is convenient and easy to set up. But it won’t really help me stand out. It doesn’t show what I’m capable of as a designer, and it lacks the polish of a real product.

Behance feels outdated. It’s clunky to work with, hard to customize, and viewing case studies on mobile is a pain. Publishing there doesn’t reflect the kind of experience I want to deliver.

Instead, I’d go with something like Framer or Webflow. Even if I used a basic template, I’d treat it like a real product. A site that loads fast. Works well on mobile. Has clean typography and thoughtful layout.

I’d show 2-3 case studies, even if they’re made up, where I explain my thinking: what the problem was, how I approached it, what I tried, and what I learned.

And I’d add a section for visual or creative experiments. Shots, animations, micro-interactions, typography ideas, even AI-generated explorations.

Things I’d do:
  • Pick Framer or Webflow template and personalize it
  • Write short but clear case studies: problem → process → result
  • Add a section called “Playground” or “Visual Lab” with experiments
I’d aim to become an AI-native designer
Right now, nobody has a clear definition of what an “AI-native designer” actually is. That gives me an honest shot, even against more experienced folks.

I’d treat ChatGPT like a collaborator. Ask it to help with research, to critique my UX flows, to generate ideas I might not think of alone.

I’d try Lovable to build quick MVPs. I’d learn Make or n8n to automate small things and explore how workflows are part of product design too. I’d build a plugin for Figma or try to prototype something simple end to end, maybe a tiny web tool or onboarding flow.

The idea is not to wait until someone teaches me. It’s to explore, build, and learn as I go.

Things I’d do:
  • Build a simple Figma plugin or mini-product (ex: onboarding quiz)
  • Create something with Lovable from scratch
  • Set up one automation with n8n
  • Write a post: “What I learned building with AI as a junior designer”
I’d create case studies from real-life frustrations
No portfolio projects? No problem. I’d pick an app I use often that just… annoys me. I’d analyze what’s broken, then turn that frustration into a hypothesis.

I’d validate it by reading reviews, asking people, checking Reddit or App Store comments. If I saw a pattern, I’d treat that like a real brief.

Redesign not just for looks, but to solve a user pain. Build something, share it, improve it. Show before-and-after screens. Talk about the process.

That’s already a case study. And maybe even something people care about.

Things I’d do:
  • Pick a frustrating flow or app and write out what’s wrong
  • Search Reddit and reviews to find similar complaints
  • Create a redesign and share it on LinkedIn or UX forums
  • Collect feedback, iterate, and document improvements
I’d start being visible before I even apply
I wouldn’t wait until I “felt ready.” I’d start sharing what I was learning: a screenshot from my redesign, a quick insight from using a tool, a short reflection on what confused me and how I solved it.

One or two posts a week. LinkedIn, X, anywhere. Not to go viral, just to get noticed. Just to show I exist.

And I wouldn’t just post. I’d interact. Comment on posts that resonated. Ask questions. Add to the conversation. Slowly build real connections with designers I admire.

That visibility might open doors before they officially open.

Things I’d do:
  • Start a weekly post: “Design Diary – Week 1, Week 2…”
  • Document progress: from idea to redesign to feedback
  • Reshare learnings or cool things I discover about tools
  • Comment on 2–3 posts a week with genuine thoughts or questions
  • Follow and engage with designers I respect to grow my network
I’d look to startups as a real-world playground
Instead of waiting for a company to hire me, I’d look at Product Hunt, Indie Hackers, and early-stage YC startups. If I found a product I liked or an idea that made sense, I’d DM the founder.

“Hey, I’m a junior UX designer. I like what you’re building. I’ve got a few suggestions for onboarding or UI. Would love to help, even just as a volunteer.”

Founders care about progress. If they see value, they’ll likely say yes.

And if not? No big deal. I can always move on.

Things I’d do:
  • Check Product Hunt daily, find apps with poor UX
  • Reach out with specific offer (ex: “3 quick ideas to improve signup”)
  • Track and share the results if they take your ideas in
I’d treat asking for help as a skill, not a weakness
I’d reach out to other designers. On ADPlist. On LinkedIn. In communities. But I’d avoid vague asks like “Can you review my portfolio?”

Instead, I’d make it easy:
“Hey, could you take a look at this one case? I’d love quick feedback on structure or clarity.”

Respectful. Quick. Focused. That’s how you get replies.

Things I’d do:
  • Prepare a short message template to send to mentors
  • Choose one case study to ask for feedback on
  • Keep track of who replied and what they said
I’d practice talking like a designer
Designers don’t just design. They explain. They defend decisions. They guide teams. So I’d practice answering common questions out loud. Use the STAR method:
  • Situation
  • Task
  • Action
  • Result

I’d record myself. Or use Mockin to simulate interviews. Even if I stumble, I’d learn something every time.

Speaking clearly matters as much as designing clearly.

Things I’d do:
  • Write and rehearse answers to 5 common interview questions
  • Record myself explaining one case study using STAR
  • Practice mock interviews weekly (alone or via Mockin)
And if I felt behind?
I’d remind myself: I’m not late. I’m just early in the process.
I don’t have to be perfect. I just have to keep going.

A little progress every week. A new experiment. A better case. A stronger answer. That’s the whole game.

That’s how I’d approach it if I were starting from zero today.
And maybe, that’s exactly enough to land that first yes.
Don’t just dream — prepare!
Use Mockin today, succeed tomorrow