Next Chapter: Landing the Dream Job

Next Chapter: Landing the Dream Job

I got the offer on a Thursday afternoon. I remember sitting there reading the missed voicemail transcript (from someone who I thought was spam calling) before it actually registered. After two years of wondering if I'd made a mistake, if the path I'd chosen even had a destination. It did.

But that Tuesday doesn't mean much without everything that came before it.

The Two Years Nobody Talks About

Fresh out of undergrad with a portfolio I was proud of and a CS degree in my back pocket, I thought I was ready. The reality of breaking into UX hit differently than I expected. Applications went out. Some came back with rejections. Most didn't come back at all.

The entry-level paradox is real: every junior role seemed to want two to three years of experience, and nobody seemed interested in handing that experience out. So I did what made sense at the time, I said yes to everything I could find. Contract work. Freelance gigs. Volunteer projects. If someone needed a designer and I could learn something from it, I showed up.

There were weeks where I questioned all of it. The work wasn't glamorous. Some projects were small, some clients were difficult, and the pay on certain contracts barely covered the time I put in. It would have been easy to read that season of my life as a failure, as proof that I wasn't good enough or that I'd miscalculated somewhere.

But I don't see it that way.

The Hidden Gift in the Detour

Here's what those two years actually gave me: real client experience. And I don't mean that lightly.

There's a version of design school where feedback comes from professors and peers who are rooting for you, where the stakes are a grade and the timeline is a semester. That environment teaches you a lot, but it doesn't quite prepare you for a client who changes the brief halfway through, or a stakeholder who can't articulate what they want but knows immediately when something is wrong. That's not a criticism of school, it's just a different kind of education, and the freelance years filled in the gaps.

I learned how to run a kickoff meeting when there's no project manager guiding it. I learned how to ask the right questions upfront so I wasn't redesigning the same screen four times. I learned how to present work to someone who doesn't speak design, how to separate personal attachment from professional feedback, and how to advocate for a decision while staying genuinely open to being wrong.

Those are soft skills that look invisible on a resume but are completely obvious in an interview room. When I got to the final rounds for this role and they asked how I handle ambiguity or pushback from stakeholders, I wasn't performing an answer. I was recalling actual experiences. That's a different energy, and I think it came through.

Bringing the CS Brain Into the Design Work

One thing I leaned into heavily and I believe it set me apart was the way my computer science background shaped how I approached design problems.

A CS degree doesn't just teach you to code. It teaches you to think in systems. It teaches you to ask what happens at the edge cases, to consider how one change ripples through everything connected to it, and to break a complex problem into smaller, manageable pieces. When I brought that mindset into UX, it changed how I designed.

Iterating on designs, for example, came naturally. I wasn't precious about early concepts because I understood them as drafts in a process, not finished products. I could move quickly from low-fidelity to high-fidelity, test an idea, get signal, and adjust without losing the thread of what I was trying to solve. That rhythm of building, testing, and refining felt familiar because it mirrors how software development actually works, and understanding that cycle made me a faster, more decisive designer.

But the place where it showed up most concretely was in how I organized my files.

Anyone who has worked in a cross-functional team knows the quiet chaos of opening a design file and having no idea what anything is called, where components live, or which version is the one actually handed off to engineering. I've been on the receiving end of that confusion, and I made a commitment early on that my files would never be the source of it.

Layers named. Components structured logically. Frames organized the way a developer would expect to navigate them. Handoff notes clear enough that a question never had to be asked twice. This isn't just tidiness, it's respect for the people you're working with. And because I understood what developers actually need from a design file, I could deliver it in a way that saved everyone time and reduced the back-and-forth that slows teams down.

In interviews, this came up more than once. Teams want designers who can collaborate without friction. Showing that I'd thought about the engineering side of the handoff, and that I had a system for it, signaled something beyond design skill, it signaled that I understood the full picture of how a product actually gets built.

What I Know Now

The two years between graduation and this offer were not wasted time. They were, looking back, the most formative stretch of my career so far. Not because they were easy, but because they asked something of me that a full-time job with structure and mentorship might not have: they asked me to figure it out.

I figured out how to find work when no one was offering it. I figured out how to build relationships with clients from scratch. I figured out how to apply a technical foundation to a creative discipline in a way that felt natural rather than forced. And somewhere in all of that figuring out, I became the designer who eventually got the offer on a Tuesday afternoon.

If you're in the middle of your own version of those two years, I want you to know that the detour is doing something. The freelance project that feels beneath you is teaching you client management. The volunteer work that doesn't pay is building your portfolio and your patience in equal measure.

The dream job doesn't always appear right after graduation. Sometimes it appears after you've done the work to actually deserve it.

And when it does, you'll know exactly how you got there.