Get comfortable with AI
The goal here is just exposure — enough hands-on comfort with AI that it stops feeling like a mystery, so it shows up naturally in how you talk about your work later.
The goal: you can describe how AI fits into your design process, in your own words, without reading off a script.
Free self-guided courses — AI in your design workflow
Article- and video-based, go at your own pace, no sign-up deadlines.
Design & prototype with AI
Once AI stops feeling foreign, this is where it actually earns a place in your process — as a way to move faster from idea to something clickable, without losing the judgment that makes it good.
The goal: you've tried at least one AI-assisted prototyping workflow on a real piece of your own work, not just a tutorial file.
Product sense & designing AI people trust
A technically impressive AI feature can still be a bad product. This is about keeping your product judgment sharp, and learning what makes people actually trust an AI feature instead of feeling unsettled by it.
The goal: you can explain, in a sentence or two, what would make you personally trust — or not trust — an AI feature you were designing.
Designing AI into your product
Different from the section above — that's AI as a tool in your own process. This is AI as a feature inside the product itself: what it should do, how much control to hand it vs. the user, and how people learn to trust it or don't.
The goal: you can point to a specific pattern or guideline you'd actually reach for next time you're asked to design an AI feature into a real product.
Free self-guided resources on designing AI into a product
Going deeper: UX for AI by Greg Nudelman & Daria Kempka (in the books list below) is the closest thing to a full framework for this exact area — paid, but worth it if this is where most of your work is heading.
Visual design & polish
AI can get you most of the way to a working screen. The last stretch — the part that makes something look considered instead of assembled — is still a craft skill, and it's worth keeping sharp on its own, separate from anything AI-related.
The goal: you can look at one of your own screens and name what's making it feel unfinished, then actually fix it.
Free self-guided resources on craft & polish
Collaborating with engineering, product & business
Good design work that never gets built, funded, or understood by the people around you doesn't help anyone. This is about the relationships and framing that get your work taken seriously by engineers, PMs, and leadership.
The goal: you can walk into a conversation with an engineer, a PM, or a VP and speak in terms that land for them, not just for other designers.
Free reading on working across functions
Learn just enough code to understand what engineers actually do
You don't need to become an engineer — but a little real fluency in how code works changes every conversation with the people who build what you design. You'll ask sharper questions in standup, scope feasibility yourself instead of guessing, spot when a "quick fix" isn't actually quick, and be taken more seriously in technical rooms — which matters most early on, when you're still building that credibility.
The goal: enough working knowledge of how a webpage or app is actually built that you can read a pull request description or a bug report and follow what's going on.
Position yourself as a leader, no matter your level
Leadership isn't gated behind a manager title — and if you're early in your career, you're the person this applies to most. Getting people to trust your judgment and follow your lead without any formal power to make them is exactly the skill that gets noticed, gets you staffed on the project that matters, and gets you promoted. It's called "leading without authority," and it's learnable.
The goal: you can name one concrete way you influenced a decision this month — without having the authority to just make the call yourself.
Proving your impact with metrics
Being able to say what you built matters less than being able to say why it mattered. This is about setting goals you can actually measure, checking whether your work moved them, and turning that into a story you can tell a team — or a hiring manager.
The goal: for one past project, you can state the goal, the metric that shows whether you hit it, and what actually happened — in three sentences.
Free reading on measuring design's impact
Reposition for the job you want
Once you're comfortable with AI, this is where it turns into an actual job search — pulling roles you genuinely want, finding what they have in common, and rebuilding your LinkedIn, resume, and portfolio around that pattern instead of a generic version of your career.
The goal: a LinkedIn, resume, and portfolio that all tell the same, specific story about the kind of designer you are.
Free resources on framing your story
1. Pull 5 job descriptions you genuinely love
Not five you're settling for — five that, if the offer landed tomorrow, you'd actually say yes to. This is the raw material for everything that follows, so it's worth being picky here.
The goal: a folder with the full text of 5 real postings, saved somewhere permanent — postings get taken down, so copy the whole thing, not just the link.
2. Run them through Claude or ChatGPT
Paste all five in and ask what they have in common: the problem the team is actually trying to solve, the industry or domain pattern, and — the part that matters most — what's implied but never said outright. Then ask how to frame your own background so those unspoken things are obvious at a glance.
The goal: a short, plain-language summary of the pattern across all 5 roles, and 3–5 phrases or framings you can reuse across your LinkedIn, resume, and portfolio.
Here are 5 job descriptions for roles I'd genuinely love to have. [paste all 5, full text] Look across all of them and tell me: 1. What do they have in common — responsibilities, tools, and phrasing that repeat? 2. What underlying problem is each team actually trying to solve by hiring for this role? 3. What industry or domain pattern connects them, if any? 4. What's implied but not stated outright — the "hidden" requirement or ideal candidate trait each one is really looking for? 5. Given all of that, how should I frame my own background so the things they're looking for are obvious within the first few seconds of reading about me?
3. Update your LinkedIn
Same positioning from Step 2, applied everywhere someone will actually look.
The goal: a profile where the header, photo, About section, and job entries all say the same thing about you.
- AHeader/banner — a simple, current visual that matches how you're now positioning yourself.
- BProfile picture — recent, professional, and warm; this is a trust signal before anyone reads a word.
- CAbout section — open with the framing from Step 2, not a list of job titles.
- DJob entries — rewrite bullet points to echo the language the job descriptions used, where it's honestly true of your work.
4. Rebuild your resume around it
Same framing as your LinkedIn — a hiring manager who looks at both should see one consistent story, not two different people.
The goal: a resume where the top third makes your fit for these 5 roles obvious, even to someone skimming for six seconds.
More on acing the interview itself
See it from their side: what interviewers are actually evaluating
A recruiter, a hiring manager, a fellow designer, and a VP are sitting in on the same loop for different reasons — a recruiter is checking basic fit and screening out risk, a hiring manager is picturing you doing the job day to day, a design peer is judging your craft and process, and a VP or C-level is usually looking for judgment and how you'll represent design in a room without other designers in it. These are written from the hiring side, so you can see what they're actually watching for.
How the big tech companies say they hire
Straight from the source — the official interview-prep pages the companies themselves publish, rather than a third party's guess at their process.
Practice out loud: free mock interviews, any level
Reading about interviews only gets you so far — at some point you need to say your answers out loud, to another person, and hear how they land. Both of these are free and work for junior through senior designers; you're matched with whoever's available rather than a level-specific track.
Standing out & getting hired
More free reading on standing out right now
Verified early-career & rotational design programs worth knowing about
Beyond one-off job postings, a handful of companies run structured programs built specifically for early-career and career-changing designers — often with a lower bar to entry than a standard hire (a bootcamp background, an apprenticeship model, no degree requirement at all).
Books worth buying
Everything else on this page is free. These aren't — they're the exceptions, included because they're genuinely worth the cost for this exact moment in a design career. If you already pay for Spotify Premium, check before you buy: Premium includes 15 hours of audiobook listening a month (US) at no extra cost, and 3 of these 7 are available as Spotify audiobooks — tagged below.
Prices below are gathered from Amazon and cheaper used-book sites (ThriftBooks, etc.) and rechecked weekly, but they're a snapshot, not a live price feed — always confirm on the retailer page before buying. Last checked Sep 18, 2026.
Build (or rebuild) your portfolio
Your portfolio is doing more work than your LinkedIn or resume — it's the only one of the three where someone actually watches you think. A wall of screens with no reasoning behind them, or a case study that makes someone read ten screens to find the point, loses a reviewer who's skimming dozens of these a week.
The goal: 3–5 case studies, each one answering two questions in order — what was the opportunity or gap you were handed, and what was the actual impact of what you solved. Everything else in a case study is in service of those two things.
Free reading on portfolio structure
Courses on Maven
How UXfolio & Framer think about structure
Two different vantage points on the same problem: UXfolio is built specifically around UX case studies, so their guidance is about what a hiring manager needs to see in one; Framer is a general site builder, so its framework is about the pages and content system underneath, whatever you put in it.
Get real feedback on it
Find your people
Learning AI and job-hunting are both easier with other humans around. These are free places to get unstuck, get feedback, or just not do this alone — a mix of online-only and in-person/local communities, for both design and product management.
The goal: at least one real conversation a week with someone outside your own head about this.
Design & UX communities
Product & product management communities
Format and region are based on how each community describes itself; where a group doesn't state it outright (like UX Chats' online-only format), that's noted as inferred rather than confirmed. UX Chats' exact Discord/join link is easiest to grab straight from theuxchats.co — the site's homepage didn't expose it to an automated check.
Upcoming hackathons & workshops
A hackathon is a fast, low-stakes way to get a brand-new, AI-touched project into your portfolio — something built in days, not months. A few free workshops and recurring feedback sessions are mixed in too. All free, all starting or running between now and the end of October 2026.
The goal: one small, finished, shippable project to add to your portfolio — not a masterpiece, just proof you can move fast with these tools.