Therapy for Tech Founders and Engineers in Colorado

If you’re a founder or engineer somewhere in Colorado’s tech corridor, from Boulder to Denver to Fort Collins, and you’re privately struggling in a way your résumé would never suggest, there’s a specific reason to consider working with Bob Manthy. Bob was a software engineer at Google, with a master’s in computer science, before he trained as a Licensed Professional Counselor. That order matters. He learned how systems thinkers actually reason, and where that reasoning quietly fails them, from the inside, years before he ever sat in a counselor’s chair. So the things most therapists need explained, on-call weeks, a bad board meeting, a down round, the particular loneliness of being the person everyone else looks to, don’t need explaining. Bob is licensed as a professional counselor in Colorado only, which means you can do this work from anywhere in Colorado without a drive. What you get isn’t a watered-down, more comfortable version of therapy. It’s work that takes your analytical strength seriously and then goes where analysis alone can’t.

Key takeaways

• Bob was an engineer first. A Google software engineer with a CS master’s who then became a Licensed Professional Counselor, so the technical world you live in is already understood, not translated.
• Colorado’s density is real, and so is the pressure. Boulder and the Front Range hold one of the highest concentrations of startups and high-tech workers in the country, which means a lot of people carrying this specific weight in a fairly small area.
• The research is honest about founders. In one widely cited study, roughly 30 percent of entrepreneurs reported a history of depression, notably higher than a comparison group.
• Systems thinking has a blind spot. Engineers can describe an emotional pattern with real precision and still not change it, because understanding a system isn’t the same as repairing it.
• This is counseling, not coaching. A confidential clinical service, delivered by telehealth to eligible Colorado clients, and clearly distinct from non-clinical executive coaching.

Why Colorado’s tech corridor produces this exact strain

Colorado didn’t back into being a tech hub. Boulder in particular carries one of the densest startup ecosystems in the country relative to its size, fed by the University of Colorado, a deep aerospace base, and large employers like Google and IBM with a real presence along the Front Range. That density is part of why people move here. It’s also part of the pressure.

When you’re surrounded by other high performers, the ambient expectation is that you’re handling it. Everyone around you looks like they’re executing. The founder two doors down just raised. The staff engineer on your team ships without visible strain. In that environment, the honest admission, that you’re brilliant at the work and privately coming apart underneath it, gets harder to say out loud, not easier. The competence becomes a kind of armor, and the armor gets lonely.

None of that means something is wrong with you. It means you’re in an environment that rewards a very particular performance and rarely asks about the cost of holding it.

What the research actually says about founders

It helps to know the pattern you might be recognizing has been studied, because it can otherwise feel like a personal failing.

The psychiatrist and former entrepreneur Michael Freeman, working with colleagues at UC San Francisco and UC Berkeley, ran one of the more cited studies here. In Are Entrepreneurs Touched with Fire?, his team found that founders reported meaningfully higher lifetime rates of certain conditions than a comparison group did, with roughly 30 percent reporting a history of depression. The point isn’t that building a company makes you unwell. It’s that the people drawn to this work, and the conditions the work creates, deserve more honest attention than they usually get.

If you want the fuller picture of the isolation specifically, the piece on counseling for founders walks through the loneliness that comes with carrying context no one else on the team can hold. The short version: it’s structural, not a failure of communication, and most founders end up carrying it alone.

Why systems thinkers get stuck on emotional problems

If you’ve spent your career building and debugging systems, you’ve developed a genuinely powerful toolkit. Decompose the problem, trace causality, form a hypothesis, test it, revise. That works on software. It works far less well on the internal stuff.

Emotional patterns don’t behave like systems you can debug. They’re recursive, so the way you feel about the problem is part of the problem. They’re distributed, so the pattern in your marriage connects to the one in how you take feedback at work, which connects to something that formed long before either. And the more analytically capable you are, the more elaborate your model of the problem tends to get, which can quietly become a way of staying at a safe distance from actually feeling it. You can know exactly why you avoid conflict and keep avoiding it anyway.

There’s a clinical edge to this worth naming. Alexithymia, a term from the psychiatrist Peter Sifneos, describes real difficulty identifying and putting words to what you feel. Most engineers aren’t alexithymic in the clinical sense. But the milder shape of it, a rich internal life paired with a thin vocabulary for it, is common in people rewarded their whole lives for precision about the external world and rarely asked to describe the internal one. The feelings are there. The interface to them just hasn’t been built out. The deeper dive on this lives in therapy for engineers, including why standard therapy so often creates friction for technical minds.

What the work actually looks like with Bob

Working with someone who’s lived inside high-performance technical environments changes the texture of the sessions. You don’t burn time establishing context or simplifying your situation to make it legible. The conversation can run at a level of precision that feels right, and it can move faster because the translation layer is gone.

The analytical work still matters. Mapping the real pattern, noticing exactly when it fires and what the sequence looks like, is something engineers and founders are often unusually good at, and it’s genuinely useful. What that work can’t do on its own is generate the experience of something different. Change requires engaging with the thing you’ve been observing from a distance, which is the uncomfortable part analysis lets you defer. Bob’s whole approach is to hold both: the rigor you trust and the experiential dimension that rigor alone can’t reach.

This is counseling, a confidential clinical service, and it’s worth keeping it clearly separate from executive coaching, which is non-clinical and aimed at skills and performance. If what you’re carrying is closer to burnout, depression, anxiety, or relationship strain than to a business gap, counseling is usually the right door. The broader picture of that work is on the executive counseling page.

Bob Manthy is a Licensed Professional Counselor with a background as a Google software engineer, a nuclear engine operator on a U.S. Navy submarine, and an ultramarathon runner. He works with founders, engineers, and high achievers across Colorado, the people who’ve already tried the obvious fixes and know they’re dealing with something deeper. Bob Manthy is licensed as a professional counselor in Colorado only, so telehealth counseling is available for clients located in Colorado.

If this resonates, schedule a confidential free consultation.