TL;DR

After years of founding companies and surviving bad managers, I took a software engineering job at a Fortune 100 company — and met the best boss of my life. He remembered I was a human being, not a headcount. He challenged me without crushing me, noticed my weaknesses and paid for me to fix them, welcomed me back after a serious illness, and went home at 5 p.m. like work-life balance was a law of physics. This is what he taught me about what good leadership actually looks like.

Two Days, One Whiteboard, and a Week of W3Schools

I had spent most of my adult life as an entrepreneur, which is a polite way of saying I had spent most of my adult life exhausted. So when I decided to interview at a Fortune 100 company, it felt like stepping off a moving train onto solid ground. I wanted the structure. I wanted, for once, to be the person who didn't have to invent the entire world before lunch.

The interview process did not ease me in gently. It spanned two days. Two days of conference rooms with frosted glass, of whiteboards smudged gray from a hundred previous candidates, of the particular silence that falls when someone hands you a dry-erase marker and waits.

I had a problem, though. I knew how to build companies, but the specific syntax they wanted to grill me on had gone rusty. So in the week before the interview, I did what any reasonable, slightly panicked person does: I went to W3Schools and studied JavaScript and HTML like my life depended on it. Late nights at the kitchen table, the laptop glow turning everything blue, muttering for loops to myself like prayers. By the end of the week I could close my eyes and see angle brackets.

The first day, the hiring manager walked in and shook my hand. He was lean and weathered in a way that office work doesn't usually produce, and he asked me hard questions — the kind designed less to check a box than to watch how you think when you don't have the answer ready. He pushed. When I gave a clean solution, he asked why it would break at scale. When I stumbled, he waited, neither rescuing me nor enjoying the silence.

Somewhere in the middle of all that, almost as an aside, he mentioned that he loved mountain climbing. He said it the way people mention the thing that actually keeps them alive — quickly, a little embarrassed, then back to business. I filed it away.

The Mountain Question

The second day, I came back for the next round. The frosted glass, the marker, the same chair still slightly too low. Before we dove into another whiteboard problem, I asked him how the climbing was going. I asked whether he'd been up anything recently, what the conditions had been like.

He looked at me as if I'd said something in a language he hadn't heard in years.

"You remembered that?" he said.

"You mentioned it yesterday," I told him. "It sounded like it mattered to you."

He sat back. Something in the room changed temperature. It wasn't that I'd flattered him — I hadn't said his climbing was impressive or asked him to teach me. I'd just registered him as a person who existed before he walked into that conference room and would exist after. He seemed taken aback that I'd held onto something he thought was trivial, a throwaway line in a long day of interviewing strangers.

I think now that the moment told us both something. It told him I paid attention. And it told me, watching his face soften, that this was a person who noticed when he was noticed — which is its own quiet kind of test. The people who can't bear to be seen as human are usually the ones who can't see it in anyone else either.

I Interviewed Them Right Back

Here is the thing nobody tells you when you've survived bad workplaces: you stop being able to enjoy a job offer at face value. I had been burned. I'd worked for people who treated talent like a renewable resource — use it up, order more. So I went into those two days determined not to walk into another version of the same fire.

So I asked questions. A lot of them. I asked the engineers what they actually did all day. I asked what happened when a project went sideways and who got blamed. I asked the manager directly how he handled people who disagreed with him. I asked everyone I could corner in a hallway how long they'd been there.

That last question is the one that decided it.

Person after person told me the same thing: ten years. Fifteen. "Oh, I'm coming up on twenty-two in the spring." It kept happening. In an industry where eighteen months at a company counts as loyalty and people treat their résumés like bus schedules, this place had somehow convinced people to build entire careers under one roof.

You can fake a lot of things in an interview. You can fake a mission statement, a foosball table, a page of values stenciled on a wall. You cannot fake two decades of people choosing, year after year, not to leave. That number was the truest thing anyone said to me in two days. They kept their people. Which meant their people had a reason to stay.

I got the job.

The First Weeks Were Terrible (Because I Was Waiting for the Catch)

I would love to tell you I relaxed into it. I didn't.

The first stretch was stressful in a way that had nothing to do with the work and everything to do with me. I had dealt with horrible bosses before — the kind who praise you in public and gut you in private, the kind who treat a Tuesday emergency as your personal failing — and I kept waiting for this man to reveal himself as another one of them. Every time he called me into his office I braced. Every gentle correction, I scanned for the trap underneath it.

What if this one was the same? What if the climbing, the patience, the long-tenured team were all just a better-decorated version of the cage I'd been in before?

He never sprang the trap, because there wasn't one.

Slowly — and it was slow, because trust that's been broken doesn't reset on schedule — I started to understand that he was simply different. He cared about people. Not in the HR-poster sense, the laminated kind. In the ordinary, unglamorous, day-after-day sense. He treated the people who reported to him like human beings, which sounds like the lowest possible bar until you've spent years stepping over the bodies of managers who couldn't clear it.

I didn't feel like a number. I want to dwell on that for a second, because it's a phrase that gets worn so smooth it stops meaning anything. What it meant in practice was this: when he assigned me work, he had clearly thought about me — what I could already do, what would stretch me without breaking me. The tasks landed in that narrow, generous band between boredom and panic. He knew I could do them. He also made sure they cost me something. That is harder to calibrate than it sounds, and almost no one bothers to try.

"Go Take a Class on My Dime"

He was also, unnervingly, observant.

It didn't take him long to spot my weaknesses. I came in strong technically and strong on hustle — that's the entrepreneur's package. But communication, the patient corporate kind, the kind where you bring a room of skeptical stakeholders along with you rather than just being right at them? That was rougher. I could ship. I couldn't always persuade.

A worse manager would have used that against me, or just quietly capped how far I could go and never told me why. Instead he named it, plainly and without cruelty, and then he did something I'd never had a boss do. He encouraged me to go fix it. On the company's time and the company's dollar.

"You've got the ideas," he said. "I just want everyone else in the room to get them as fast as I do."

So I took communication classes at Stanford. I sat in rooms learning how to structure an argument, how to read a room that's drifting, how to say the hard thing without lighting the building on fire. I got better. And the entire time, I knew my manager wasn't doing it to squeeze more output out of me. He was doing it because he'd looked at my career as something longer than my usefulness to his quarter.

That's the difference between a manager who's investing in you and one who's depreciating you. One is planting. The other is mining.

He Welcomed Me Back

Then I got sick. Seriously enough that I had to take family leave — to step away entirely, with no clean date on the calendar for when, or whether, I'd be the same person coming back.

If you have ever been the employee on leave, you know the second sickness that comes with it: the fear that the world will simply close over the space where you used to stand. That you'll return diminished and be treated accordingly. I'd seen it happen to other people. The slow demotion nobody announces. The meetings that stop including you.

When I came back, he welcomed me with open arms. Not performatively — there was no all-hands, no awkward speech. He just made it unmistakably clear that my chair was still my chair, that the work was still mine, that nothing about my standing had quietly eroded while I was gone. He asked how I was, and then he listened to the answer, and then he let me ease back in at a pace that respected the fact that I was a person recovering rather than a resource being switched back on.

There are very few managers in this world who treat you like you are important — not important in the sense of indispensable to the org chart, but important in the older, simpler sense. That your wellbeing counts. That you'd be missed as a someone, not just as a function. He was one of them.

The Man Who Went Home at Five

Here is the detail that genuinely shocked me, more than the climbing, more than the Stanford classes.

He left work at 5 p.m. And he expected the people who worked for him to do the same.

I cannot overstate how foreign this was. As an entrepreneur I had worked hundred-hour weeks under conditions I now describe to people with a kind of stunned laughter. I wore the exhaustion like a medal. Late nights were proof of seriousness; weekends at the desk were a personality. The idea that a high-performing person at a Fortune 100 company would simply stand up at five o'clock and go live his life — and consider it a failure of management if his team didn't — rearranged something in my head.

He climbed mountains, after all. You don't get good at a thing like that by being chained to a desk past dark. He had built a life that the job served, rather than a life the job had eaten. And he extended that same dignity downward to all of us. Work-life balance, which had been a phrase I associated with people who weren't serious, turned out to be the discipline of someone who was deadly serious — about the work and about the living.

It mattered to me more than I can say. After years of grinding myself down, I had a boss whose entire example argued that I was allowed to put myself back together.

What He Left Me With

I spent a lot of years meeting and dealing with terrible people. People who confused fear for respect, who mistook your loyalty for leverage, who looked at a team and saw a cost center. By the time I walked into that two-day interview, I'd half-decided that good bosses were a thing people made up to feel better, like a workplace Santa Claus.

This man made me hopeful again. Not in a soft, sentimental way — in a hard, evidentiary way. He was proof, sitting right across the conference table asking me why my code would break at scale, that you could be excellent and humane at the same time. That you could push people and protect them. That you could go home at five and still climb mountains, literal and otherwise.

I carry him with me into every team I build and every person I manage now. When I'm tempted to treat someone like a number, I remember the look on his face when I asked about the climbing — the surprise of a person being seen. And I try to give that look back to the people who work for me, because somebody once decided I was worth more than my output, and it changed the entire trajectory of how I work.

The best boss I ever had taught me the lesson by living it: people will climb mountains for you, but only if you first treat them like they were never just a tool to get up the hill.