My First Three Months as a Junior Designer: Honest Reflections

Nobody prepares you for the gap between what you studied and what you are suddenly expected to produce. You close your laptop after your final exam, open a new project file, and realise that the version of yourself who felt confident in the classroom is nowhere to be found.

This is a piece I wish I had found during those first weeks. Not the highlight reel — the actual experience, month by month, with all the doubt and the small wins and the moments where things finally started making sense. Here it is.

"Growth in a new role doesn't happen in a straight line. It happens in waves — and the first wave is mostly just staying afloat."

The Three-Month Arc

Month One — Imposter Syndrome

Everything looks harder than it should

My first month was dominated by a single feeling: I shouldn't be here yet. I would open Figma and stare at a blank frame for longer than I'd like to admit. I was second-guessing every spacing decision, every typeface choice, every color palette. I kept thinking, "What would a real designer do here?" — and I didn't trust my own answer.

The turning point was a conversation with a senior colleague who reminded me that every designer starts with a blank frame. The difference between a junior and a senior isn't confidence — it's just reps. You get through the discomfort by shipping work, not by waiting until you feel ready.

Month Two — Finding My Voice

The work starts to look like mine

By month two, I stopped trying to copy what I thought a "professional" design looked like and started making decisions I could actually defend. I began asking "why" more — why this layout over that one, why this color creates more urgency, why this interaction pattern reduces cognitive load.

I also learned the most important skill no course teaches: how to present your thinking, not just your output. Sharing a design without context is just showing a picture. Sharing a design with rationale is making an argument. Month two was when I learned the difference.

Month Three — When Things Click

The process becomes instinct

Month three felt different. The blank frame was no longer threatening — it was a starting point. I had developed a personal workflow: research first, sketch rough ideas before touching software, build in components from the start, and test early even if it's just on myself.

I also stopped comparing my output to work I found online. The design community produces incredible work — but those projects have budgets, teams, and timelines that are incomparable to a junior with three months of experience. The only fair comparison is to your own work from last month.

What I Actually Learned (That School Didn't Teach)

🎓 Practical Lessons From the Field

Feedback is not criticism When someone marks up your design, they are improving the outcome — not judging you. The moment I separated my ego from my work, revisions became collaborative instead of demoralising.

Constraints are creative tools A tight deadline, a small budget, or a limited component library doesn't kill creativity. It channels it. Some of my best decisions came from having no other options.

Ship imperfect work, then iterate A design that ships and gets real user feedback is infinitely more valuable than a perfect design that stays in Figma. Version 1 is just the beginning of the conversation.

Ask questions early and often Spending three hours building the wrong thing because you didn't ask one clarifying question is a mistake every junior makes exactly once. Now I ask before I build.

Things I Wish I Had Known on Day One

⏱
Your speed will double in three months
Tasks that took me four hours in week one took me ninety minutes by month three. Don't be embarrassed by your current pace — it's temporary. Track your time so you can actually see the progress.
🗂
Document everything from day one
Every decision, every revision, every piece of feedback. Not for anyone else — for yourself. In three months, you'll want to see where you started, and you'll be glad you wrote it down.
🤝
Being junior means being curious, not being helpless
Ask questions, but also attempt answers first. "I've tried X and Y — which direction would you go?" gets a very different reception than "I don't know what to do here." Show your thinking, even when it's incomplete.
🎯
Focus on one tool deeply, not five tools broadly
The designers I admired most weren't impressive because they knew everything — they were impressive because they knew one thing extremely well and built outward from there. Depth beats breadth in the early stages.
🌱
The discomfort means you're in the right place
If you're comfortable, you're not growing. The anxiety of the first month isn't a warning sign — it's a signal that the work is actually challenging you. That's exactly where you want to be.

Conclusion

Three months is a short time and a long time simultaneously. Short enough that you're still figuring out the basics. Long enough that you can look back and see genuine growth in your work.

If you are in your first three months right now and it feels hard: it's supposed to. The discomfort is the curriculum. Every blank frame you push through, every piece of feedback you absorb, every design you ship before it feels ready — that is what builds a designer.

Not the courses. Not the tutorials. The reps.

Veeny Ree Mae Bautista

UI/UX Designer & Frontend Web Developer

Based in Bataan, Philippines. BSIT graduate of Bataan Peninsula State University. I design and build thoughtful digital experiences — and occasionally write about the lessons that come with growing up in tech.