Is a UX certification worth it, like the Google one?
Short answer: I have one. The Google UX Design certificate, and a master’s degree with a title on it. In all the years since, not one client, recruiter or hiring manager has asked to see either.
That's a stranger answer than “don't bother”, and I think it's a more useful one, because it comes from somebody who paid.
What the certificate actually did for me
I did it while I was moving into UX from building things with code and doing visual work. What I got from it wasn't really knowledge — most of the content is available free, and anybody who tells you otherwise is selling something. What I got was structure: a running order, deadlines, shared vocabulary, and a reason to finish things instead of leaving them at 70%. The master’s did the same job on a bigger scale.
I don't regret either. At that moment I needed scaffolding and scaffolding is worth paying for.
But I have to be honest about what happened next: the market never once checked. The portfolio checked, every single time.
What actually got me work
Three things, in the order they mattered.
Projects with a decision in them. Not screens. A decision: we could have done A or B, we did B, here is why, here is what happened. Most portfolios are a gallery. The ones that got attention were the ones where I could say why that screen and not another one.
Being able to describe a failure precisely. The most useful thing I own professionally is a set of specific, unflattering stories. Four months building something a landing page would have answered in nine days. Three weeks on a design system a four-person team never used. Those come up in almost every serious conversation, and they do more work than any credential, because they are evidence of judgement rather than a claim of it.
Talking to people already doing it. Unglamorous and effective. Most of the work I've had came from somebody I had once spent an hour talking to about something unrelated.
None of that came from the course. All of it came from having done something, and having paid attention while doing it.
So why do I still say it isn't necessary
Because a certificate is a way of learning, not a way of proving — and almost everybody sells it as the second thing.
If you buy it as a way of learning, you're buying structure, and structure is a legitimate purchase. If you buy it as proof, nobody's going to ask for it, because they'll ask about the work instead.
I used to think the certificate was what would open the door, and it wasn't. It was scaffolding, which is fine, but it's only worth the price if without it you'd never have built anything.
Where a certificate genuinely does help
This is the part the “just build a portfolio” crowd skips, and it's where I think they are wrong — “build a portfolio instead” is very easy advice to give once you already have a portfolio.
When an automated filter stands between you and a human. Larger companies and agencies do screen on keywords, and a recognisable credential can be the difference between a CV being read and not. That isn't a comment on the value of the knowledge. It's a comment on the pipeline, and pretending the pipeline doesn't exist helps nobody who is stuck in it.
When you're changing career and have no structure. If you're coming from teaching, or law, or hospitality, with no projects, no colleagues in the field and no deadlines, then what a good course sells isn't knowledge. It's structure, feedback, and a reason to finish things. I know, because that's exactly what I bought. The honest test is whether you would have built the same portfolio without the course. For some people the answer is obviously yes and the money is wasted. For plenty of others it's no, and that's worth paying for.
What I'd do with the money instead, if you have the choice
Find a real problem with a real person attached. A local business with a booking flow nobody completes. A charity with a form that loses people. A friend’s side project. Something where somebody notices whether it works.
Then do the whole thing, including the uncomfortable part: watch a person use it, in silence, without helping. That hour teaches you more about whether feedback is real or just polite than any module on research methods, because you'll watch somebody struggle and then tell you it was fine.
One project like that, described honestly, is worth more than any certificate — for the specific reason that it produces a story about a decision that had consequences, and a course can't manufacture consequences.
The honest summary
In the end a certificate says you did a course, not that you can do the job. I've got two and nobody has ever looked at them. What they've looked at, every single time, is the work.
So: if you need the structure, buy it and use it without apology. If what you really want is the title to show people, know that nobody's going to ask for it.
What nobody can sell you is the part that decides this job: having been wrong about something in a way that cost you, and being able to say what you took from the shape of it. That comes from doing the work, getting it wrong, and paying attention. It's free, it's slow, and it's the only route I know that reliably works.
If you're weighing one up right now
Genuinely, tell me your situation and I'll tell you what I think — whether you're a career changer with nothing on paper yet, or you already have projects and are wondering if the certificate closes some gap.
Email me at hello@sgualda.com, or send me a DM on Instagram if that's easier. I answer, and I have no course to sell you.
Questions people ask about this
01Do you need a certification to get a UX job?
No. I have one and it has never come up — not in a client conversation, not in a hiring process, not once. In every hiring conversation I've been part of, on either side, the portfolio decided it. What a certificate can do is get you past an automated filter or an HR screen when you have nothing else on paper, which is a real problem for some people and no problem at all for others.
02What do UX hiring managers actually look at?
Two or three projects where you can explain what you decided, why that and not the alternative, and what it cost when you were wrong. The third one separates candidates. Almost everybody can narrate a process; very few can name a decision that went badly and say what they learned from the particular shape of the failure.
03Is a UX certification worth it for a career changer?
It can be, and this is the part I can speak to directly. What my certificate and my master’s actually gave me was structure: deadlines, an order to learn things in, and a reason to finish. That's worth real money if you're starting from nothing. What they didn't give me was a credential anybody ever checked. Buy the structure if you need it; don't buy it expecting it to be the thing that gets you hired.
04What is the alternative to a UX certification?
Find a real problem with a real person attached: a small business, a charity, an open-source project, a friend’s side project. Then do the whole thing end to end, including the part where you watch somebody use it and it goes wrong. One of those beats any course, because it produces the one thing a course can't: a story about a decision that had consequences.