Career Change to UX Designer at 40

Fourteen years teaching art. Why leave?

The money, first. I was making $54,000 after fourteen years at a public high school in Lakewood, which is a suburb of Denver. My husband, Ben, is an electrician. He makes about $72,000. We have a daughter, Cora, who's nine. We were fine, but the kind of fine where you check the bank account before saying yes to a birthday party invitation because the gift is $25 and that matters. I loved teaching. Genuinely. But at $54,000 after fourteen years, with a ceiling of maybe $62,000 if I got a master's and waited another decade, the math was never going to work.

The second reason is harder to explain. I was teaching visual communication every day. Composition, color theory, hierarchy, how to guide someone's eye across a page. And I kept thinking, there's a job where people get paid real money to do this exact thing, except the canvas is a screen instead of paper. I'd been aware of UX design for years. I followed a few designers on Instagram. Julie Zhuo's blog. Some Figma tutorials on YouTube. I just never let myself take it seriously because I was a teacher and teachers don't become tech workers. That's what I told myself.

What actually pushed me was a parent-teacher conference in November 2024. A dad came in for his son, Malik, who was in my AP Studio Art class. Good kid, talented. The dad worked at a software company and we got to talking after the formal part. I mentioned that I was interested in UX design and he said, "You'd be good at it. You already think in systems." And then he said, "My company just hired a junior UX designer. She was a pastry chef six months ago." A pastry chef. If a pastry chef can do it, a visual arts teacher who's been teaching composition for fourteen years can definitely do it. That conversation is the reason I'm here.

How did you make the switch?

Google UX Design Certificate first. Seven courses on Coursera, $39 a month. Took me five months doing it at night after Cora went to bed. The certificate teaches you the basics: user research, wireframing, prototyping in Figma, usability testing. Honestly, a lot of the research stuff felt intuitive because teaching is research. Every day in a classroom you're observing how people interact with material you designed. You're watching their faces to see if the lesson is landing. You're iterating in real time. UX research formalized something I'd been doing informally for fourteen years.

Figma was new but I picked it up fast. I'd been using Adobe Illustrator and Photoshop for years to make classroom materials. Figma is simpler than both. The auto-layout stuff took a minute to click but once it did, it felt like a superpower. I built my first wireframe kit in a weekend and Ben looked over my shoulder and said, "That looks like an app." It wasn't an app. It was a wireframe for a fictional dog walking service. But it felt like something real.

After the Google cert I did a bootcamp. Springboard UX Design, six months, $9,900. That one was painful financially. We used savings. Ben was supportive but nervous. I could tell because he stopped asking about it, which is how Ben shows anxiety. The bootcamp gave me a mentor, a woman named Priya who works at Intuit. Priya was the most useful part of the entire experience. Not the curriculum. Priya. She reviewed my portfolio projects and said things like, "Your visual design is strong but your case study doesn't show your process. Hiring managers want to see how you think, not just what you made." That reframe changed everything. I'd been treating my portfolio like an art show. Priya taught me to treat it like an argument.

How was the job search?

Seven months. I applied to 83 positions. Got 11 first-round screens. Got 5 portfolio presentations. Got 2 offers. The first offer was at a digital marketing agency in Boulder, $68,000. The second was at the healthcare SaaS company, $76,000. I took the healthcare company because the work seemed more interesting and $76,000 was life-changing. That's $22,000 more than I made teaching. After fourteen years of teaching, my first year in UX paid me more than I'd ever made.

The portfolio presentations were the hardest part of the process. You sit in a Zoom call with three to five people and walk through two case studies in forty-five minutes. They ask questions. They push on your rationale. At one interview, a senior designer named Garrett asked me, "Why did you choose a bottom navigation pattern instead of a hamburger menu?" I had a reason but I fumbled explaining it because I wasn't used to defending design decisions to other designers. In a classroom, I'm the authority on visual decisions. In a design interview, I'm the least experienced person in the room. That shift was brutal.

The interview that got me the job, my manager Trish asked me to walk through a design decision I'd made that didn't work. I talked about a usability test in my bootcamp project where users couldn't find the search function because I'd used an icon without a label. I showed the before and after. Trish later told me she hired me because I was the only candidate who showed a failure honestly instead of spinning it as a "learning opportunity." She said, "You showed me you can be wrong and fix it. That's the job."

What transferred from teaching?

More than I expected. The biggest one is presenting to hostile audiences. I taught art to teenagers for fourteen years. Teenagers who didn't want to be there. Teenagers who'd rather be on their phones. If you can explain the rule of thirds to a room of thirty 16-year-olds on a Friday afternoon, you can present a wireframe to stakeholders. The skill is the same: make complex visual concepts accessible to people who don't share your vocabulary.

Last month I presented a redesign of our patient intake form to a room that included the VP of product, two engineers, and a compliance officer. The compliance officer, Howard, kept interrupting with regulatory concerns. In another life, Howard is the kid in the back of the classroom who raises his hand every two minutes. I know how to handle that kid. You acknowledge the concern, park it visibly, and come back to it after you've finished your point. I did that with Howard. After the meeting, Trish said, "You handled Howard really well." I didn't tell her I'd been handling Howards since 2010.

What is it?

I miss the kids. I didn't expect that. I expected to miss the creative freedom, the summers, the routine. But what I actually miss is Malik asking me why negative space matters, and watching his face when it clicks. I miss the moment a student sees composition for the first time. Really sees it. That moment doesn't exist in UX. When I design a form that tests well, nobody's face lights up. The usability score goes from 3.2 to 4.1 and Trish says "nice improvement" in Slack and that's the feedback. It's efficient. It's professional. It's emotionally nothing.

Ben says I'm romanticizing. He says by year twelve I was coming home exhausted and complaining about lesson planning every Sunday night. He's right. But exhaustion and meaning can coexist. I was exhausted and I knew why I was doing it. Now I'm less exhausted and less sure.

Project management to UX design. That's an unusual pivot.

Not as unusual as people think. I was an IT PM for eleven years. The last five were at a financial services company in Charlotte, managing software projects. Agile, sprints, the whole thing. And in every sprint, I was in meetings with UX designers. I watched them present wireframes. I watched them run usability tests. I sat in design reviews. For five years, I was adjacent to design without doing any of it. And every meeting, this little voice in my head said, "You have opinions about this. You have good opinions. Why aren't you the one making the decisions?"

The trigger was a project in early 2025. We were redesigning the client onboarding flow for our wealth management platform. The designer on the project, a woman named Simone, presented her wireframes and they were, I'll be honest, not great. She'd put the account selection step before the personal information step, which meant users were choosing products before the system knew anything about them. I raised it in the review. I said, "If we flip the order, we can use the personal information to pre-filter the account options." Simone looked at me and said, "That's a good idea. Why don't you ever say anything in these reviews?" And I realized I'd been sitting on design opinions for five years because I thought it wasn't my lane.

That week I signed up for the Google UX Design Certificate. Three months later I started the Designlab UX Academy. Six months, $5,500. My wife, Keisha, thought I was having a midlife crisis. She wasn't entirely wrong.

What was the learning curve like?

The UX process stuff was easy. Research, synthesis, ideation, prototyping, testing. That's basically project management with different deliverables. I already knew how to structure a discovery phase. I already knew how to synthesize stakeholder input. I already knew how to present to executives. The process wasn't new. The tool was new.

Figma. That was the wall. I'd managed projects with designers who used Figma every day and I'd approved their work and I had literally no idea how hard it was to make a pixel-perfect screen. My first attempt at designing a login page took me four hours. Four hours for a login page. An email field, a password field, a button. The alignment was off. The spacing was inconsistent. The button looked like it was from 2008. I showed it to my Designlab mentor, a guy named Kai, and he said very diplomatically, "Let's talk about spacing systems."

The visual design skill took longer than anything else. I have adequate taste. I can look at a design and tell you if it's good or bad. But making a good design from scratch is a completely different skill than evaluating one. It's the difference between being a food critic and being a chef. I was a food critic for five years in those design review meetings. Becoming a chef took six months of practice and a lot of ugly login pages.

How did the job search go?

Faster than I expected. Three months, 34 applications, 6 interviews, 2 offers. My PM background was actually a huge advantage because I could speak both languages. In portfolio presentations, I didn't just show the design. I showed the business context, the constraints, the tradeoffs. Most junior UX designers present their work like it exists in a vacuum. "Here's my research. Here's my design. Here's my testing." They don't talk about why the business wanted this, what engineering couldn't do, or how the timeline shaped the solution. I did, because as a PM I lived in that world. Hiring managers noticed.

My current manager, Nia, told me she hired me partly because of the PM background. She said, "I have designers who can't write a Jira ticket. You wrote Jira tickets for eleven years. You understand the production pipeline. That's rare for a junior designer." Which is flattering but also a little depressing because it means part of my value as a designer is that I can do project management. The thing I left.

Ten months in. What surprised you?

How much of the job is not design. When I was a PM watching designers, I thought their job was: research, design, present. That's the visible part. The invisible part is the Slack threads. The Figma comments. The documentation. The component library maintenance. The design system governance meetings. The stakeholder pre-alignment before the meeting where you present. The thirty-minute call with an engineer to explain why the border radius should be 8 pixels instead of 4. Last week I spent an entire afternoon writing annotation notes in Figma so the engineering team in Hyderabad could implement a tooltip without a synchronous meeting. That's not design. That's communication. And it's probably 40% of the job.

The other surprise is how much taste matters and how long it takes to develop. I can do the process. Research, synthesize, ideate, test. That's structured. I can follow a structure. But when I sit down to design a screen, there's a moment where I have to make an aesthetic decision that isn't in any process. How much whitespace. What shade of gray for the secondary text. Whether the card should have a shadow or a border. These decisions accumulate and they're the difference between a screen that feels professional and a screen that feels like a bootcamp project. I'm still on the bootcamp side of that line. I can feel it. Nia can probably feel it too, though she's never said it.

What is it?

The pay cut. I was making $112,000 as a senior IT PM. I took the UX job at $78,000. That's a $34,000 annual cut. Keisha and I planned for it. We saved for eight months before I started the career change. We cut discretionary spending. We didn't take a vacation last year. We moved the kids from private swimming lessons to the community pool program, which saves $200 a month but my son Jaylen noticed and asked why.

The plan was: take the cut, get two years of experience, then move to a mid-level role at $95,000 to $110,000. On paper that makes sense. But living through it is different than planning for it. Every time I look at my pay stub I think about the $34,000 difference. Every time I see a PM job posting at $120,000 I think about whether I made a mistake. I don't think I did. But the doubt is there every two weeks when the direct deposit hits and it's less than what I used to bring home.

Keisha doesn't bring it up. She supported the switch. But last month she said, "When do you think you'll be back to where you were?" And I said, "Two years, maybe three." And she nodded in a way that was supportive but also, you could see her doing the math. Three years of the gap is over $100,000 in lost earnings. That's a real number. That's a room addition we talked about. That's Jaylen's college fund contribution we paused. It's not abstract. The career change cost us something concrete and we're both aware of it even when we don't say it.