UI/UX designMay 22, 2026

5 Skills That Turned Me From Junior Into an AI-Proof Senior

UIUX

built by @louyi.ux — receipts on remote design career building Original link


💡 💡 How to use this page: Duplicate it to your own Notion (top right → Duplicate). Then work through one skill at a time, check the boxes as you go, log your progress, come back when you need a kick. This is a tracker, not a TED talk.


Before You Scroll

I'm a self-taught senior product designer. No degree. Fully remote. I figured out the hard way that the thing keeping juniors stuck isn't their Figma skills, it's everything around the design work.

These 5 skills are what got me hired senior and what's keeping me there in 2026 while AI is eating half the junior pipeline. They're not glamorous. They're not "10 Figma plugins you need." They're the actual leverage.

Work through them in order if you're starting from zero. Skip ahead if you already know what your weak spot is.

Ready? Check the box. Let's go.

  • I'm in. I'll actually do this, not just read it.

📊 Your Progress

Tick these off as you complete each skill. Don't lie to yourself, half-doing it doesn't count.

  • Skill 1 — Prompting (the one everyone fakes)
  • Skill 2 — Working without a babysitter
  • Skill 3 — Owning the product, not the screen
  • Skill 4 — Documenting everything (yes, everything)
  • Skill 5 — Copywriting (the one designers hate)

Skill 1 — Prompting (The One Everyone Fakes)

⚠️ 🎯 The brutal truth: AI isn't replacing designers. It's replacing designers who can't prompt. There's a difference.

📖 What this actually means

Most designers type "make it better" into AI and wonder why the output is garbage. That's not using AI. That's gambling.

Learning to prompt properly means being specific about what you want, who it's for, what constraints matter, and what good looks like. It's a skill. It has rules. And right now, almost nobody in design is taking it seriously, which is exactly why you should.

This isn't about replacing your thinking. It's about making your thinking 5x faster.

💼 Why it matters in 2026

Every junior designer has access to the same AI tools you do. The ones who get hired senior are the ones who can direct the tool with precision. That's the gap. That's the entire job.

✅ What "done" looks like - [ ] You can take a vague request and break it into a structured prompt without thinking - [ ] You've stopped saying "make it better" out loud and in your head - [ ] You've picked ONE tool (Claude, ChatGPT, Midjourney, whatever) and gone deep instead of dabbling in five - [ ] You can prompt for: research, copy, ideation, critique, edge cases, not just generation
⚡ Action items - [ ] Pick your one tool this week. Commit to it for 30 days. - [ ] Write 10 prompts a day for 7 days. Save the ones that worked. - [ ] Reverse-engineer a great output: ask the AI to tell you the prompt structure that would have produced it. - [ ] Join one community where people share prompts (Reddit, Discord, X, pick one)
📚 Where to learn - [**Anthropic Prompt Engineering Docs**](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/overview) — free, no fluff - [**Lenny's Newsletter**](https://www.lennysnewsletter.com/) — search "prompt engineering for product" - [**Wes Roth on YouTube**](https://www.youtube.com/@WesRoth) — practical, no hype

Skill 2 — Working Without a Babysitter

⚠️ 🎯 The brutal truth: Remote teams don't hire people who need to be managed. They hire people who manage themselves.

📖 What this actually means

If your manager has to check on you, you're a junior. If your manager forgets you exist because you're just shipping clean work and communicating it well, you're senior.

Async collaboration is the skill of operating without real-time hand-holding. It means writing clearly. It means asking the right questions before you start, not halfway through. It means leaving a paper trail so the next person doesn't have to ask you what you were thinking.

This is the #1 thing remote-first companies screen for. And most designers fail it.

💼 Why it matters in 2026

The design job market split. There are local in-office jobs where you can get away with being chatty. And there are remote senior jobs that pay 2-3x more and require you to operate like an adult. You don't get the second category without this skill.

✅ What "done" looks like - [ ] You write daily updates (or at least weekly) without being asked - [ ] Your Slack messages are scannable, not paragraphs - [ ] You record Loom walkthroughs instead of asking for meetings - [ ] You can take a brief, ship work, and explain the why, all in writing, without anyone checking in
⚡ Action items - [ ] Start a daily "what I worked on" log in Notion, even if no one reads it - [ ] Next time you'd schedule a meeting, send a Loom instead and see what happens - [ ] Read one async-work resource per week for a month - [ ] Watch how senior people on your team communicate. Copy their structure.
📚 Where to learn - [**"The Art of Async" by Doist**](https://doist.com/blog/asynchronous-communication/) — free - [**Loom's Async Workshop**](https://www.youtube.com/watch?v=9dEz4JjkCIg) — on YouTube - [**Notion Async Standup Templates**](https://www.notion.com/templates/team-standup-feed-ai-ready-async-updates-daily-standup?srsltid=AfmBOoq8PBaXv5SYoA6FZ0FGGsPuB5XyE5I8NFMW__ueXtmSLff05ucw)(https://www.notion.com/templates/team-standup-feed-ai-ready-async-updates-daily-standup?srsltid=AfmBOoq8PBaXv5SYoA6FZ0FGGsPuB5XyE5I8NFMW__ueXtmSLff05ucw)— plug and play

Skill 3 — Owning the Product, Not the Screen

⚠️ 🎯 The brutal truth: Juniors design screens. Seniors own outcomes. The title doesn't change until your scope does.

📖 What this actually means

Product ownership means you don't just take a brief and design what's asked. You understand the problem before you open Figma. You talk to engineers about feasibility before pixels exist. You ship with the team, then track what happened, opens, retention, conversion, whatever metric the feature was supposed to move. Then you iterate based on what you learned.

Screens are 20% of the job. The other 80% is owning the outcome. Most designers never make that shift, which is exactly why most designers stay junior forever.

💼 Why it matters in 2026

AI can generate screens. AI cannot understand your business, talk to your users, or own the result. That's the part of the job that's actually safe, if you do it. Designers who stay screen-only are getting compressed first.

✅ What "done" looks like - [ ] You can name the metric every project you've worked on was trying to move - [ ] You talk to users (or PMs who talk to users) before you start designing - [ ] You follow up after launch instead of disappearing onto the next thing - [ ] You can answer "what happened?" with numbers, not vibes
⚡ Action items - [ ] For your current project, write down the business metric it's supposed to impact. If you don't know, ask. That's already step one. - [ ] Schedule a 15-min call with a PM or engineer this week. Ask them what they wish designers understood better. - [ ] Read one product-thinking book or newsletter per month - [ ] For one project, run the full loop: define problem → ship → track → iterate. Even if it's small.
📚 Where to learn - [**Inspired by Marty Cagan**](https://www.svpg.com/inspired-how-to-create-products-customers-love/) — the bible (book) - [**Lenny's Newsletter**](https://www.lennysnewsletter.com/) — essential reading - [**Continuous Discovery Habits by Teresa Torres**](https://www.producttalk.org/2021/05/continuous-discovery-habits/) — book

Skill 4 — Documenting Everything (Yes, Everything)

⚠️ 🎯 The brutal truth: Undocumented work doesn't exist. And one day you'll need every piece of it.

📖 What this actually means

Every design challenge you take on. Every 30-day commit. Every small win at your job. Every freelance project, every personal project, every weird side thing. Document all of it.

Write down what you did, why you did it, what worked, what didn't, what you learned. Take screenshots. Save your process. Keep a folder.

I cannot tell you how many times the things I documented when I was a junior, random side projects, design challenges I almost didn't post, became case studies that got me interviews years later. Promotion conversations. Salary negotiations. Freelance pitches. All of it.

The work disappears if you don't write it down. And you will never remember the details when you need them most.

💼 Why it matters in 2026

The job market is competitive. AI is making it more competitive. The people who win are the ones with receipts, visible, dated, documented evidence of how they think and what they've shipped. You can't fake this. You can only start now.

✅ What "done" looks like - [ ] You have a "brag doc" or working journal that you actually update - [ ] Every project, no matter how small, has a one-paragraph writeup somewhere - [ ] You have a folder of screenshots, links, and process notes you can pull from - [ ] When someone asks "what have you been working on?" you have an answer ready
⚡ Action items - [ ] Start a Notion page TODAY called "wins log" or whatever you want to call it - [ ] Document the last 3 projects you worked on, even briefly. Just to break the seal. - [ ] Set a 15-min recurring calendar block every Friday: "log this week" - [ ] Commit to one public post a month about something you built or learned (Twitter, LinkedIn, Threads, anywhere)
📚 Where to learn - [**"Show Your Work!" by Austin Kleon**](https://austinkleon.com/show-your-work/) — short, life-changing (book) - [**"Get your work recognized: write a brag document" by Julia Evans**](https://jvns.ca/blog/brag-documents/) — free article - [**#buildinpublic on X / LinkedIn**](https://twitter.com/search?q=%23buildinpublic) — copy what works

Skill 5 — Copywriting (The One Designers Hate)

⚠️ 🎯 The brutal truth: Great design with weak copy doesn't convert. Words are part of the design. Accept it or stay junior.

📖 What this actually means

Most designers treat copy as placeholder. "Lorem ipsum" mentality. Then they wonder why their portfolio doesn't land interviews, why their case studies don't get read, why their outreach gets ignored, why their products don't convert.

Copywriting is design. The words on a button matter. The headline on your portfolio matters. The first line of your cold email matters. Learning to write, clearly, persuasively, in your own voice, multiplies every other skill on this list.

This is the skill that took me the longest to take seriously. It's also the one that changed the most for me when I finally did.

💼 Why it matters in 2026

AI can generate copy. It cannot generate your voice or judgment on what to say. The designers who can write, about their work, about their thinking, about why their decisions matter, are the ones building audiences, landing roles, and getting paid more. It's not a soft skill. It's a multiplier.

✅ What "done" looks like - [ ] Your portfolio reads like a person, not a template - [ ] You can explain any design decision in one clear sentence - [ ] Your outreach gets replies (because the first line is actually good) - [ ] You've written at least one piece of public content about your work in the last month
⚡ Action items - [ ] Rewrite your portfolio About section this weekend. Cut all "passionate," "dedicated," "innovative." Replace with specifics. - [ ] Write one Threads post or LinkedIn post about something you designed. Just one. - [ ] Read one marketing/copy resource per week for a month. It's not hard. Just stop avoiding it. - [ ] For one project case study, write it like you're texting a smart friend, not submitting to a corporate review
📚 Where to learn - [**Everybody Writes by Ann Handley**](https://annhandley.com/everybodywrites/) — book - [**Marketing Examples**](https://marketingexamples.com/) — free, brilliant, one-page lessons - [**Harry Dry on LinkedIn / X**](https://twitter.com/harrydry) — best in the game right now - [**Building a StoryBrand by Donald Miller**](https://buildingastorybrand.com/) — book

🎉 You Finished. Now What?

If you actually worked through this, not just read it, you're already ahead of 90% of designers.

The trap from here is treating this as a list you completed once. These are skills you compound over years. Come back to this page every quarter. Recheck the boxes. Notice what slipped.


Want More?

I post receipts on remote design career building 4-5x a week. Real numbers, real strategies, no fluff. If this guide helped, that's where the rest of it lives.


If This Guide Helped You

  • I duplicated this page so I'll actually use it
  • I followed @louyi.ux for more receipts
  • I'm sending this to one designer friend who needs it

Made with care by Louyi. Don't repost without credit, but DO share the link with anyone who needs it.