How to Choose a Career Coach for Tech Professionals

Search “career coach” and you’ll get thousands of results, most of them generalists working from the same handful of frameworks: values exercises, strengths assessments, five-year vision boards. None of that is wrong exactly. It’s just not built for the specific shape of the problem tech professionals actually bring into a coaching conversation.

If you’re an engineer, product manager, or engineering leader trying to figure out your next move, the coach you need to evaluate differently than you’d evaluate a generic life coach or executive coach. Here’s what actually matters when you’re choosing one.

Why tech professionals need something more specific than a generalist

Three things show up in tech careers more consistently than in most other fields, and a coach who hasn’t worked inside them will miss the real problem every time.

Equity and comp complexity. Unvested RSUs, refresh cycles, total comp packages that make any alternative look like a pay cut on paper even when it isn’t one over a longer horizon. A coach who doesn’t understand how this actually works will either dismiss it (bad) or let it become the whole conversation (also bad). Weighing it accurately, taking it seriously without letting it take over, is part of the job.

Identity fused with title. Title and company carry unusual social weight in tech. “Senior Engineer at [recognizable company]” becomes part of how someone introduces themselves, thinks about their own competence, and measures whether they’re doing okay. A coach who treats this as incidental will miss why a career decision feels like an identity threat instead of a logistics problem.

Risk-averse cultures around real risk-takers. Plenty of tech professionals took a real risk once (a startup, a bet on an unproven technology, a jump between disciplines) and then spent the next decade in an environment that quietly rewards not rocking the boat. The mismatch between who they were and who their environment has trained them to be is a specific pattern, and naming it directly is most of the work.

A coach who hasn’t seen these patterns up close will spend the first several sessions rediscovering things a tech-specific coach already knows walking in.

What to look for

Someone who asks about the specifics before offering a framework. A good first conversation surfaces details before it reaches for a model. If a coach jumps straight to “let’s do a values exercise” before understanding your actual situation, that’s a sign the framework is doing the thinking instead of the coach.

No stake in a particular outcome. The person you’re talking to should not benefit from you staying or leaving. That’s part of what makes coaching different from advice from a manager, a mentor, or a friend: everyone else in your life has some interest in what you decide. A coach shouldn’t.

Directness, alongside the support. Support without directness produces a nice conversation and no clarity. Look for someone who will name a pattern out loud even when it’s uncomfortable, rather than only reflecting your own words back to you.

Transparent pricing and structure. You should know exactly what a session costs and how long it runs before you book it. Vague pricing or pressure toward a long-term package before a first conversation has happened is a signal to keep looking.

Red flags

• Promises a specific outcome (“you’ll have total clarity in 3 sessions”) instead of describing a process
• Pushes a multi-month package before you’ve had a single real conversation
• Talks more than they ask questions in the initial call
• Has no direct experience in tech or adjacent high-comp, high-identity fields
• Can’t clearly explain what a session actually looks like when you ask

Questions to ask before booking

1. “What does a session actually look like?” A specific, concrete answer beats a vague description of “a supportive space.” If they can’t describe the mechanics, you don’t know what you’re buying.
2. “Have you worked with people in a similar role or situation?” Not proof by itself, but relevant pattern recognition speeds up every conversation that follows.
3. “What happens if I don’t know what I want yet?” The right answer is some version of “that’s normal, and that’s often the actual work.” If the answer implies you need to arrive with a plan already, that’s a mismatch.
4. “What’s the pricing and how does it work?” Should be immediate and specific. $X per session, no surprise upsell.
5. “How do you handle it when I’m avoiding the real issue?” You want someone who will name it directly, rather than let a comfortable tangent run for 45 minutes.

How to actually evaluate fit

The best way to know if a coach is right for you is not a testimonial or a bio. It’s a single real conversation. Most coaches worth working with offer some version of a short introductory call specifically so you can feel the difference between a generic conversation and one where the coach is actually tracking your specific situation.

Pay attention to what happens in that first call: does the coach ask questions that get more specific as you answer, or do they stay at the surface? Do they name something you hadn’t quite said out loud yourself? That moment, being told something true about your own situation that you hadn’t fully articulated, is a reasonable signal that the fit is real.

Takeaway

A generalist coach isn’t wrong, but tech careers carry specific patterns: complex comp, identity tied to title, a mismatch between past risk tolerance and current caution, that a generalist framework tends to miss or flatten. Evaluate a coach the same way you’d evaluate any specialist: ask about their actual process, watch how they handle your specifics rather than a template, and judge the fit through a real conversation instead of a bio page. How I coach walks through the specific approach used here, and a free 15-minute call is the fastest way to find out if it’s the right fit for you.

FAQ

Common questions