Career Change to Product Manager at 40

Sixteen years in restaurants. Why leave?

The hours. That's the short answer. I managed restaurants in Denver for 16 years. Started as a server at 22, became a shift lead at 24, assistant manager at 26, general manager at 28. I ran three different restaurants. The last one was a 180-seat upscale casual place in LoHi. I managed a staff of 42, handled a $3.2 million annual revenue, and worked 55 to 65 hours a week including every Friday and Saturday night. I missed my nephew's high school graduation because it was a Saturday. I missed my best friend Carla's 40th birthday because it was a Friday. I missed a lot of Fridays and Saturdays.

When I turned 40, Marco and I had a conversation. He's a project manager at a construction company. He works Monday through Friday, 7 to 4. We barely saw each other. I'd get home at midnight, he'd be asleep. He'd leave at 6:30, I'd still be asleep. On Sundays, my one day off, I'd spend half of it recovering. He said "I love you, but I want to see you." That's when I started thinking about what else I could do with the skills I had.

How did you land a PM job with no tech experience?

I got lucky, and I was strategic. The lucky part: a recruiter reached out to me on LinkedIn because she saw "restaurant management" on my profile and her client was a hospitality SaaS company that specifically wanted PMs who understood the restaurant industry. The strategic part: I'd spent six months before that redoing my LinkedIn, taking a free Product Management course through Coursera, and reading every PM blog I could find. I did a mock case study with a friend of Marco's who works in tech. I rewrote my resume three times. I positioned my restaurant experience as product-adjacent, which it is if you know how to frame it.

In the interview, they gave me a case study: "Our reservation system has a 22% no-show rate. How would you approach reducing it?" I lit up. I spent 16 years dealing with no-shows. I knew the psychology. I knew why people no-show (they double-book, they forget, the reservation was aspirational). I knew what works (confirmation texts at 4 PM, credit card holds for parties of 6+, flexible cancellation policies that make canceling easier than no-showing). I didn't approach it like a PM case study. I approached it like a restaurant manager solving a restaurant problem. The VP of Product, a woman named Jill, told me later that my answer was the best she'd heard because everyone else gave generic PM frameworks and I gave her the actual answer.

$112,000. You were making $74,000 as a restaurant GM?

Yeah. So the pay actually went up, which is unusual for career changers, I know. But restaurant GM pay is terrible relative to the hours and responsibility. I managed 42 people, handled vendor negotiations, dealt with health inspections, managed a P&L, resolved customer complaints, and once had to fire a line cook who threw a sauté pan at the dishwasher. For $74,000 a year with no bonus. My total comp now is $112,000 base plus a 5% bonus target. Even if the bonus comes in low, I'm making significantly more money to work significantly fewer hours in a job that doesn't require me to talk a drunk customer out of a bad Yelp review at 11 PM on a Saturday.

How does restaurant management show up in your PM work?

Every day, and in ways I didn't expect. The biggest one is triage. In a restaurant, Friday night at 7:30 PM, you have nine things happening simultaneously: a table complaint, two servers who need to leave early, a delivery that's late, a reservation that overbooked, and four tables waiting for a busser. You can't do all nine things. You have to decide, in real time, which three things need to happen right now and which six can wait five minutes. And you have to be right, because if you pick wrong, the customer who was already annoyed gets furious and the busser falls further behind and the whole system degrades.

PM is the same thing at a slower speed. I have 12 tickets in the sprint, 3 customer escalations, a feature request from sales, and a bug that's affecting 8% of users. I can't do all of it. I triage. And I'm good at it because I've been doing it under much worse conditions for 16 years. My engineering manager, a guy named Arthur, told me last month that I'm the calmest PM he's ever worked with. I said "Arthur, I once had a kitchen fire during a 300-cover Saturday. Jira is not stressful."

What's the hardest part of the transition?

The technical language. Not the concepts, the vocabulary. I understand databases conceptually. I understand APIs conceptually. I know what a sprint is. But when Arthur talks about "refactoring the GraphQL schema to handle polymorphic reservation types," I need about three seconds to translate that into English. And in those three seconds, the conversation has moved on. I've gotten better. Fourteen months in, I'd say I'm at 85% comprehension in technical meetings. But there are still moments where I smile and nod and then Slack Arthur afterward to ask what something meant. He's patient about it. He says my domain knowledge is worth the vocabulary gap. I hope he still thinks that in a year.

The other hard part is the pace. In a restaurant, the feedback loop is immediate. You make a decision at 7:30 and by 8:00 you know if it was right. Did the table complaint get resolved? Did the delivery arrive? Is the floor caught up? In PM, I make a decision in March and I find out if it was right in July. That delay is disorienting for someone who spent 16 years in real-time feedback environments. I'm getting used to it. But there are days when I miss the kitchen energy, the controlled chaos, the feeling of surviving a Friday night and sitting at the bar at midnight with the staff drinking a beer and knowing you all made it through together. PM doesn't have that. PM has a Slack message that says "feature shipped" and a thumbs-up emoji. It's not the same.

What's yours?

The identity thing. For 16 years, I knew who I was. I was a restaurant person. I knew the language, the rhythms, the hierarchy. I could walk into any restaurant in Denver and within five minutes I'd know if it was well run. That identity was bone-deep. When someone asked what I did, I said "I run a restaurant" and they immediately understood. They could picture it.

Now I say "I'm a product manager" and I get the same blank look that everyone in PM gets. But it's worse for me because I'm not just learning a new role. I'm letting go of an old one. I'm 42 and I'm a beginner. My manager Jill is 34. Some of the engineers on my team are 26. They've been doing this longer than I have. I'm not the expert in the room anymore. In the restaurant, I was the authority. Here I'm the person who asks good questions from a domain I understand but needs help with the domain everyone else takes for granted.

Marco says I should be proud. I am proud. But proud and comfortable are different things. I'm proud of the leap. I'm not yet comfortable with the landing. Every meeting I walk into, there's a small part of my brain that says "you don't belong here." And every meeting I walk out of, there's a slightly larger part that says "actually, you do." The second part is winning. But the first part hasn't left yet.

You taught for 17 years. That's a career, not a stepping stone.

It was my career. I never planned to leave. I taught AP US History and AP Government at a high school in Durham, North Carolina. I loved teaching. I loved the kids. I loved that moment when a student, and you can see it, when a 16-year-old suddenly understands why the Commerce Clause matters, or why Marbury v. Madison is a big deal. That moment is electric. It's why people teach.

But the system around the teaching got harder every year. I spent 17 years watching class sizes go up, budgets go down, and administrative demands multiply. My last year, I had 162 students across five sections, I was required to submit lesson plans two weeks in advance for administrative review, I was on two committees, and I was coaching the mock trial team. My base salary was $62,000 after 17 years. My wife Tracy, she's an occupational therapist, she makes about the same. Between the two of us, $124,000 for a family with two kids in Durham. It's livable but there's no margin. The college fund had $8,400 in it and our oldest, Ellie, was 14.

How did you go from teaching to PM?

Tracy's brother Chris works at a tech company. One Thanksgiving, I was complaining about the learning management system my school used. It was called Pinnacle. It was terrible. The interface looked like it was designed in 2006, which it was. I said "I could design a better system than this" and Chris said "you should talk to my friend who works at an edtech company." I thought he was being polite. He wasn't. He connected me with a woman named Rosa who ran product at a small edtech company. I had coffee with Rosa and told her everything that was wrong with Pinnacle. She said "you just did a user research interview on yourself."

Rosa didn't have a PM opening at the time, but she connected me with three other edtech companies. I applied to all three. Two of them rejected me immediately, the automated "your background doesn't match our requirements" email. The third one, the company I'm at now, invited me for an interview because their VP of Product, a man named Stuart, had a rule: at least one PM on the team has to have worked in education. He believed that building software for teachers without having a teacher on the product team was like building kitchen software without anyone who's cooked. I got the interview because of that rule. I got the job because I knew the user better than anyone else in the room.

$105,000. That's almost $43,000 more than teaching.

Yeah. It's weird. I spent 17 years building a career I was proud of, and then I switched to a career I'm less experienced in and immediately made 69% more money. That math says something about how we value teachers in this country that I'm not going to editorialize about because I'll get upset. But yes. $105,000 base, 8% bonus target. Last year the bonus was 7.2%, so about $7,500 before tax. Total comp is roughly $112,500 to $113,000. Tracy and I went from $124,000 combined to about $175,000 combined. We put the difference into Ellie's college fund and our younger one's, Jake, he's 10. The fund is at $42,000 now. That number represents two years of PM salary. It would have taken me eight more years of teaching to save that.

How does teaching show up in PM?

Constantly. And not in the ways the career-change articles suggest. They say "teaching gives you communication skills." That's true but it's surface-level. What teaching actually gives you is sequencing. When I planned a unit on the Civil War, I had to think about what the student needs to know before they can understand the next thing. You can't teach Reconstruction if they don't understand the economic structure of the antebellum South. You can't teach the antebellum South if they don't understand the Three-Fifths Compromise. Everything builds on everything else. The sequence matters as much as the content.

PM roadmapping is the same thing. You can't build the advanced reporting feature if you haven't built the data pipeline. You can't build the data pipeline if you haven't migrated the database. The sequence matters. And I'm good at sequencing because I spent 17 years figuring out which thing has to come before which other thing in a room full of 32 teenagers who will tell you immediately, with no filter, if the sequence doesn't make sense. Engineers are more polite about it, but the underlying skill is the same.

What about the technical side? That must have been a gap.

It was, and it still is, partially. When I started, I didn't know what an API was. I didn't know what "deploy" meant in a software context. I thought a database was, like, a fancy spreadsheet. My first week, my engineering lead, a woman named Kenji, used the phrase "REST endpoint" in standup and I wrote it down on a Post-it and Googled it under my desk. I had about 40 Post-its by the end of my first month.

Two years in, I'm functional. I can read a basic SQL query. I understand our tech stack (Rails backend, React frontend, PostgreSQL database, hosted on AWS). I know what a migration is, what an integration test is, what "the build is broken" means. I'm not technical. I will never be technical. But I'm literate enough to participate in technical conversations without slowing them down. Kenji said recently that my questions are "better than most PMs she's worked with" because I ask why something is hard, not whether it can be done. Teachers learn early that asking "can you do this?" gets a different answer than asking "what makes this hard?" The first one is yes or no. The second one is where the real information is.

Do you miss teaching?

Yes. Honestly, yes. I miss the students. I miss the moment when a kid gets it. I miss the mock trial team. I miss being known as "Mr. Patterson" in a building where everyone knew me. I don't miss the 162-student workload, the committee meetings, the administrative review of my lesson plans, or the salary. But the core of it, the teaching, standing in front of 30 kids and making the Federalist Papers feel relevant to their lives, that was the best version of me. I haven't found the PM equivalent of that yet. I might not. The work is interesting and the pay is dramatically better, but it doesn't have that feeling. Not yet. Maybe not ever. I'm OK with that trade. Most days.

What's yours?

How much I think about the teachers who are still there. My friend Val, she teaches English at the same school. She's been there 19 years. She makes $64,000. She texted me last week about a parent complaint and I thought, I used to spend an hour every week dealing with parent complaints and now I spend that hour reviewing Figma mockups for $43,000 more a year. The guilt isn't constant. But it surfaces. Because I didn't leave teaching for a better career. I left teaching for a better-paying career. Those are different things. The career I had was better in many of the ways that matter, the human connection, the sense of purpose, the daily evidence that your work changed someone's understanding. PM has its satisfactions but they're quieter and more abstract. I helped ship a feature last month that saves teachers 20 minutes a week on grade entry. That's real. But I'll never see their faces when they use it. In teaching, I saw the face. Every day. Thirty-two of them.