Mentoring Someone Into the Craft

Most people think mentoring someone into tech is a funnel. Pour in a motivated career-changer at the top, run them through some courses and coaching, and a job offer falls out the bottom. If the offer comes, the mentorship worked. If it doesn't, it failed.

That framing is wrong, and it quietly hurts the people it's supposed to help. It makes the mentee feel like a conversion metric, it makes the mentor optimize for the wrong thing, and it treats "got hired in the exact field we studied" as the only acceptable ending. The most valuable thing coaching actually produces is a person who can finally see the work clearly enough to choose well.

I've coached more than 150 product managers in classrooms, inside a giant healthcare portfolio, at defense software factories, and one-on-one with career-changers. The environments are wildly different. The patterns aren't. Here's the practice I run every time.

Start with the map, not the task

Before you give someone a single assignment, give them the terrain. When I coached a new mom into UX research over the course of a year, the first thing I built wasn't a task list, it was a deep-dive doc: what the field actually is, the difference between research and design, the field guides worth reading, real practitioner portfolios to study, and where to get paid to be a usability-test participant so she could feel the work from the other side.

Then I laid out the whole arc so she could see where we were headed: learn the craft, build real proof, fix how you show up online, then go get the job. People can walk a path they can see. They stall on a path that's just "trust me."

Strip out every excuse that isn't the work

My wife Zoe and I set up what we called the "Kate and Zoe scholarship," which is a fancy way of saying we covered any course the mentee wanted to take. The point wasn't generosity for its own sake. It was to remove every obstacle that wasn't actually about the work, so that what remained was the real question: do you like doing this?

Money, access, and logistics are the excuses people hide behind when they're scared. Take them off the table and the conversation gets honest fast.

Meet people exactly where they are

For one mentee, that looked like an Instagram DM. For another, a new mom, it looked like a standing slot after her baby went down for the night, every week, for about a year. The logistics of someone's real life are not an obstacle to the coaching. They're the container for it. If the only window someone has is 9pm after bedtime, then 9pm after bedtime is when class is in session.

Build real proof, not flashcards

Nobody breaks in on theory. They break in on an artifact they can put in front of a hiring manager and defend. So start with something concrete and personal. I had my UX mentee tear down an app she already used every day, learning real terminology on a product she already had feelings about. Then she built her own case study from scratch: interviews, three personas that were anything but cardboard, a journey map, two rounds of usability testing, and a high-fidelity prototype.

Make the thing, get feedback on the thing, make it again. The proof is the point, and the proof is also where the learning actually happens.

Watch for the moment they kill their own idea

There's one moment that separates someone who's learning the steps from someone who actually gets it: when they cut a feature they loved because the evidence told them to. My UX mentee built a rate-your-workout survey she was excited about, tested it, and heard "I never take surveys, I just check the boxes without reading them." So she killed it. A product mentee wireframed a feature she loved, realized it was far more complex than it looked, and dropped it.

You can't teach that directly. You can only set up the conditions, real users and real feedback, and then get out of the way so it can happen to them.

Make the work legible

Good work is only half of a career change. The other half is making it findable. Rewrite the resume so it leads with the new craft and reframes the old jobs as the transferable skills they always were. Rebuild the LinkedIn around a real headline. Stand up a portfolio site. The goal is that a stranger can find the proof and understand it in thirty seconds.

Coach the decision, not just the skills

Here's the part people leave off the stage. One of my mentees earned her UX certificate, built two strong case studies, and then took a job in a completely different field. That's not a failed mentorship. She got a real look at the work, the skills to do it, and enough self-knowledge to make a clear-eyed choice. The only real failure would have been two more years of "what if."

The highest-value thing you can give a career-changer isn't a portfolio. It's the clarity to know whether they actually want the field they've been romanticizing. Sometimes that clarity says go. Sometimes it says go somewhere else. Both are the job working.

If you measure mentoring by job offers, you'll miss most of what it does. Mentoring's real job is to hand people the work and the truth, so they can choose with their eyes open.

---

The full stories behind this practice: a year of coaching Megan into UX and what mentoring someone into tech actually takes.