This is a leadership fable. The characters and companies are fictional, drawn as a composite from multiple experiences over two decades of technology leadership. This year’s slower pace, working from home and having more time for the advisory conversations I have with people navigating their careers, brought this pattern into sharp focus. The pattern is real.
I have watched smart, capable people choose jobs based on the company’s reputation, the title, or the compensation. They underweight the factor that matters most: the person they will report to. This is the story of what happens when someone gets that calculation wrong.
Part One: The Courtship
Marcus Chen had two job offers.
The first was from Lodestar, a media and technology company whose name appeared regularly in business press coverage. The kind of company where, at a dinner party, you say where you work and people nod with recognition. The role was Vice President of Product, reporting directly to the CEO, a man named Richard Calder. The team was forty people. The compensation was 30% above what Marcus was making.
The second was from a company called Fern Hill, a mid-size digital publishing firm that most people outside the industry had never heard of. The CEO was a woman named Grace Park. The title was the same, the pay was comparable, and the team was smaller.
Marcus flew to Lodestar’s headquarters for a final round of interviews on a Tuesday in March. The offices occupied three floors of a glass tower downtown. The lobby had a wall of awards. The conference rooms had names like “Velocity” and “Horizon.” Everything communicated ambition and momentum.
Richard Calder met Marcus for dinner that evening at a restaurant where the host knew Richard by name. Richard was magnetic. He leaned forward when he talked, made eye contact, and had a way of making you feel like his full attention was a gift he was choosing to give you. He described a vision for Lodestar’s digital transformation that was genuinely compelling. He talked about building a world-class product organization, about empowering technology leaders, about creating a culture where the best ideas win regardless of where they come from.
“I need someone who can own this,” Richard said, setting down his wine glass. “I mean truly own it. Not someone who waits for permission. I want you to come in, assess the landscape, build your strategy, and execute. I will give you the air cover.”
Marcus asked about decision-making authority. Richard waved a hand. “You will have full authority over the product roadmap. That is why I am hiring a VP. I do not want to be in the weeds.”
Marcus asked about the executive team dynamic. Richard smiled. “We are a collaborative group. Strong personalities, but everyone respects expertise. You will have a seat at the table from day one.”
They shook hands outside the restaurant. Richard clapped Marcus on the shoulder. “I have a good feeling about this, Marcus. I think you are going to do something special here.”
Grace Park’s interview process was different.
There was no expensive dinner. Grace met Marcus in a plain conference room at Fern Hill’s offices, which were in a converted warehouse with exposed ductwork and mismatched furniture. She had a cup of tea and a legal pad with notes. No awards wall. No room named “Velocity.”
Grace started with something Marcus did not expect. “Before we talk about the role, I want to tell you how I manage, because that matters more than anything else I could say about this company.”
She spoke for twenty minutes. She said she meets with her direct reports every week, on the same day at the same time, and she cancels only for genuine emergencies — not the kind of “emergencies” that are really just scheduling conflicts with someone more senior. She said she expects her VPs to own their domains fully: make decisions, communicate those decisions, and live with the consequences. But she wants to hear about problems early, not late. “If something is going sideways, tell me Tuesday, not Friday,” she said. “I can help on Tuesday. By Friday I can only do damage control.”
She said she is direct, sometimes uncomfortably so. She said people have told her that her feedback can feel blunt. She does not soften it with compliments to make it easier to hear, because she thinks that is manipulative. She expects the same directness in return. “If I am wrong, tell me I am wrong. Do not hint. Do not wait for me to figure it out.”
Then she said something that stopped Marcus for a moment.
“The last two people in this role did not work out. The first one was technically strong but could not handle ambiguity. He wanted me to tell him exactly what to do, and when I would not, he got frustrated and disengaged. The second was politically skilled but did not actually build anything. She spent more time managing perceptions than managing the product. I fired her after eight months.”
Grace paused and looked at Marcus directly. “I am telling you this because I want you to know what you are walking into. I am not an easy person to work for. I have high standards, I am impatient, and I do not always give people enough time to ramp up. Those are my weaknesses. You should factor them in.”
Marcus appreciated the candor. But when he left Fern Hill that afternoon, he was not thinking about Grace’s management philosophy. He was thinking about Lodestar’s glass tower, Richard Calder’s charisma, and the 30% raise.
He called his wife from the car. “I think Lodestar is the move,” he said.
“What about the other one? The woman who was so honest with you?”
“She was great. But the opportunity at Lodestar is just bigger.”
He took the Lodestar offer. Within eighteen months he was looking for a new job.
Part Two: The Reality
Marcus started at Lodestar on a Monday in April. His first day was a blur of onboarding paperwork, IT setup, and introductions. The chief of staff, a woman named Dana, walked him through the executive calendar. She handed him a printed schedule and pointed to a slot on Thursday afternoons.
“That is your one-on-one with Richard. Thirty minutes.”
Marcus looked at the schedule. “I had weekly one-on-ones with my last boss, but they were an hour.”
Dana gave him a diplomatic smile. “Richard has eleven direct reports. Thirty minutes is the standard. And I should mention — they do get moved sometimes. Richard’s schedule is unpredictable.”
His first one-on-one was rescheduled twice, then cut to fifteen minutes because Richard had to take a call. In those fifteen minutes, Richard was warm and encouraging. “How are you settling in? Getting the lay of the land? Great, great. Let me know if you need anything.” He did not ask about Marcus’s initial observations. He did not discuss priorities. He did not mention the digital transformation vision he had described so passionately at dinner.
Marcus told himself this was normal. The CEO was busy. Things would settle down.
The first real warning came three weeks in. Marcus had spent his initial weeks listening, reading, and interviewing stakeholders. He had identified three strategic priorities for the product organization and drafted a concise strategy document. He was proud of it. It was sharp, specific, and grounded in what he had learned.
He presented it at the weekly executive team meeting.
Richard sat at the head of the table. Around it were the CFO, the COO, the head of sales (a man named Victor Moran), the head of content, the general counsel, the head of marketing, and Marcus. Eleven people in a room designed for eight.
Marcus walked through the strategy. He recommended killing two underperforming products to free up engineering resources for a new subscriber platform. He showed user data, revenue projections, and a staffing plan.
When he finished, Victor Moran spoke first. “I have a problem with sunsetting those two products. My team sells bundles that include them. If we kill them, I lose leverage in negotiations.”
Marcus had anticipated this objection. He pulled up a slide showing that the two products generated less than 3% of total revenue but consumed 15% of engineering capacity. “The math is clear, Victor. These products are a net drain. We can build something for your sales team that actually —”
Richard raised a hand. “I hear both sides. This is a good discussion. Why don’t you two work this out offline and come back with a joint recommendation?”
Marcus waited for more. Something about priorities. Something about the strategic direction Richard had described at dinner. Some signal about whether the CEO supported his strategy or not.
Nothing came. Richard moved to the next agenda item.
After the meeting, Marcus caught up to Richard in the hallway. “Richard, quick question. The strategy I presented — are we directionally aligned? I want to make sure I am not going down a path that you —”
Richard put a hand on Marcus’s shoulder. “Marcus, I trust you. That is why I hired you. Work it out with Victor and bring me something you both agree on.” He smiled and turned the corner.
Marcus stood in the hallway for a moment, processing. He had just been told, very warmly, to get permission from the head of sales before executing a product strategy. The “full authority over the product roadmap” that Richard promised at dinner had a footnote he had not mentioned: as long as no one else objects.
“Work it out offline” became the phrase Marcus heard most often in the next six months. It was Richard’s response to any disagreement at the executive table.
The head of content wanted to redirect engineering resources to build a proprietary CMS. Marcus believed they should buy one and focus engineering on revenue-generating products. “Work it out offline.”
Victor Moran wanted the product team to build custom analytics dashboards for the sales team. Marcus believed this was not a product function. “Good points on both sides. Work it out offline.”
The CFO questioned Marcus’s headcount request, arguing that the engineering team was already large enough. Marcus had data showing they were understaffed relative to industry benchmarks. Richard nodded thoughtfully and said, “Let me think about it,” which Marcus learned was another version of the same thing: a decision deferred until it no longer needed to be made, because the status quo would win by default.
Marcus began to understand the operating system of Lodestar’s executive team. Richard Calder was not a leader who made hard calls. He was a leader who avoided them. He hired strong people and then let them fight for resources, attention, and authority in a system where no one had clear ownership because the CEO never drew the lines.
The result was an organization that ran on political capital. The executives who had the most influence were not the ones with the best ideas. They were the ones who had been there longest, who had personal relationships with Richard, who knew how to navigate the ambiguity. Victor Moran had been Richard’s second hire. He had been at Lodestar for twelve years. When Victor and Marcus disagreed, Marcus had the data. Victor had the relationship. Victor won every time.
One evening in September, five months in, Marcus stayed late to prepare for a board meeting. He was sitting in his office reviewing slides when his phone buzzed with a calendar notification: his Thursday one-on-one with Richard had been rescheduled to the following Tuesday. This was the fourth time in six weeks.
He pulled up his calendar and counted. In five months, he had had eleven one-on-ones with Richard. Seven of the scheduled twenty had been canceled or rescheduled and never rebooked. Of the eleven that happened, three were cut short. In total, he estimated he had spent about four hours alone with his boss in five months.
Four hours. With the person who determined his success, his reputation, his authority, his resources.
Marcus closed his laptop and stared at the Lodestar logo on the wall of his office. For the first time, he thought about Grace Park. He thought about her saying, “I meet with my direct reports every week, same day, same time.” He thought about her saying, “Tell me Tuesday, not Friday.” He wondered what it would feel like to work for someone who actually wanted to hear what he was thinking.
He pushed the thought away. He had made his decision.
Part Three: The Unraveling
The board meeting in October went badly for Marcus, though he did not realize it until later.
Richard presented the company’s digital strategy to the board. Marcus had prepared the slides, the data, and the narrative. But when a board member asked a pointed question about why the subscriber platform was behind schedule, Richard did not say what Marcus expected — that the project had been stalled because the CEO’s own indecisiveness on the product sunset had left Marcus without clear authority to reallocate resources.
Instead, Richard said: “We have had some execution challenges in the product organization. Marcus is working through them.”
Marcus was sitting three chairs away. He felt the blood drain from his face. He kept his expression neutral. He did not correct the record in front of the board. He told himself that would be inappropriate.
After the meeting, he went to Richard’s office. Dana told him Richard was booked for the rest of the day. Marcus asked to be squeezed in for five minutes. Dana said she would try.
Richard found Marcus at the end of the day. “Hey, what is on your mind?”
“The board meeting. You said we have had execution challenges in the product organization.”
“We have,” Richard said, as if stating something obvious.
“Richard, the subscriber platform is behind because we have not been able to sunset the legacy products. We discussed this in August. I need those engineering resources freed up, and that requires a decision on the sunset.”
Richard leaned back in his chair. “I hear you. But Victor has real concerns about the impact on sales. I cannot just override him.”
“You can. That is what CEOs do. You prioritize.”
Richard’s expression shifted. Not anger, exactly. Discomfort. The look of someone who is not used to being told directly what his job is. “Let me talk to Victor,” he said. “I will get back to you.”
He never got back to Marcus.
November and December were a slow erosion. The subscriber platform fell further behind. Marcus lost two senior engineers who left for competitors, citing frustration with the unclear product direction. The head of content, emboldened by what she perceived as Marcus’s weakened position, began going directly to engineers with feature requests, bypassing the product team entirely.
Marcus raised this with Richard during a rare one-on-one in December. Richard said, “I will talk to her about that.” He did not.
Marcus started sleeping badly. He would wake at 3 AM, his mind cycling through problems he could not solve because the solutions required authority he did not have. He had the title of VP of Product. He did not have the ability to make product decisions that any other executive disagreed with. He was an expensive project manager with a corner office.
His wife noticed. “You are not yourself,” she said one night after the kids were asleep. “You used to come home and tell me about things you were building. Now you come home and tell me about meetings that went nowhere.”
Marcus did not know what to say. She was right.
In January, a year into the job, Marcus had a lunch with an old colleague named Priya who had recently joined a company he had never heard of. She was four months in and already radiating the energy Marcus remembered having at the start of his career.
“My boss is incredible,” Priya said, without Marcus asking. “She is demanding. She pushes back on my ideas constantly. Last week she told me my product strategy had three blind spots and made me redo it. But she is there. She is present. She responds to my messages the same day. When I need a decision, I get one. When I need air cover with the sales team, she walks into the room with me.”
Marcus felt something tighten in his chest.
“What is that like?” he asked, and he meant it as a genuine question.
Priya looked at him. “It is like having a real partner. She is not my friend. She is my boss. But she takes the job of being my boss seriously, the way I take my job seriously. She sees it as her responsibility to make me successful.”
That night, driving home, Marcus replayed the conversation. He thought about all the things Richard Calder had said during the interview process. I need someone who can own this. Full authority over the product roadmap. I will give you the air cover. Every one of those promises had turned out to be aspirational at best, false at worst. Richard had described the boss he wanted to be, not the boss he was.
And Marcus had believed him because the company was impressive, the office was beautiful, the title was flattering, and the money was good. > He had evaluated the job the way you evaluate a restaurant: brand, reviews, and menu. He should have evaluated it the way you evaluate a partner: values, communication style, and how they handle conflict.
Part Four: The Departure
Marcus resigned in June, fourteen months after he started. Richard seemed surprised and a little wounded. “I am sorry to hear that. I thought things were going well.”
Marcus considered saying what he really thought. He considered explaining that things were not going well, had never been going well, and that Richard’s inability to see that was itself the problem. He considered describing the board meeting where Richard blamed execution challenges on the product organization instead of owning his own indecisiveness. He considered asking Richard whether he knew how many one-on-ones he had canceled in fourteen months.
He said none of this. What he said was: “I appreciate the opportunity, Richard. I have learned a lot.” Which was true, though not in the way Richard would interpret it.
Marcus took a role at a smaller company, a digital media firm run by a CEO named Jonathan Wu. Marcus had found Jonathan through his network. Three different people — independently, without being prompted — described Jonathan the same way: “He is direct, sometimes blunt, always available, and he will tell you when you are wrong.”
In his first week, Jonathan sat with Marcus for ninety minutes and walked through every major decision the company had made in the past year, what went right, what went wrong, and what he wished he had done differently. He told Marcus about a product launch that had failed and took full responsibility for it. “I pushed the team to ship before it was ready because I was impatient. That is on me.”
Marcus asked about decision-making authority. Jonathan said: “You own the product roadmap. When you and the head of sales disagree — and you will — come to me together. I will listen to both of you and then I will decide. You will not always like my decisions. But you will always get one.”
That single sentence — “you will always get one” — felt like water in a desert.
In his first month at the new company, Marcus had four one-on-ones with Jonathan. Each was an hour. None was canceled. Jonathan came prepared with notes. He pushed back on Marcus’s ideas, asked hard questions, and twice told Marcus directly that he disagreed with his approach. Both times, he explained why. Both times, Marcus left the conversation with a clearer sense of what to do.
Marcus has been there four years. He has no plans to leave.
Part Five: What Grace Built
There is a coda to this story.
Grace Park, the CEO Marcus did not choose, hired someone else for the VP of Product role. A woman named Elena Vargas, who had been passed over for a promotion at a larger company and was looking for a place where she could build something real.
Grace managed Elena the way she described in the interview: weekly one-on-ones that never moved, direct feedback that was sometimes hard to hear, full ownership over the product domain, and a promise that problems discussed early would be met with help, not blame.
Elena thrived. In her first year, she rebuilt the product team, launched two new revenue products, and reduced the engineering defect rate by 40%. In her second year, Grace promoted her to Chief Product Officer and gave her a seat on the company’s operating committee.
When an industry publication ran a profile on Fern Hill’s turnaround, Elena was quoted: “The best career decision I ever made was choosing a boss who told me her own weaknesses before I accepted the job.”
Marcus read that article on a Saturday morning. He set his phone down on the kitchen table and sat with it for a long time.
He was in a good place. Jonathan Wu was a good boss. The company was growing. Marcus was doing work he was proud of.
But he thought about that March afternoon in the plain conference room with the exposed ductwork. Grace Park sitting across from him with her legal pad and her cup of tea, telling him exactly who she was: demanding, impatient, direct, flawed, and honest about all of it. He thought about how he had walked out of that room and called his wife to say, “I think Lodestar is the move.”
He had chosen the glass tower over the warehouse. The charisma over the candor. The promise of air cover over the proof of presence.
He knew now what he did not know then: the job is not the company, the title, or the compensation. The job is the relationship with your direct manager, every day, for as long as you are there.
How to Evaluate a Potential Boss
Most people evaluate potential employers the same way they evaluate restaurants: brand, reviews, and menu. They should be evaluating them the way they evaluate potential partners: values, communication style, and how they handle conflict.
If you are considering a new role, here are the questions that matter most.
Ask how they manage. A good leader can articulate their management philosophy with specific examples. “I believe in empowerment” is a platitude. “I meet with each of my direct reports weekly, I expect them to make decisions in their domain without my approval, and when I disagree with a decision, I tell them directly and explain why” is a management philosophy. If a potential boss cannot describe how they manage in concrete terms, they either have not thought about it or they do not want to tell you. Both are problems.
Ask about conflict. “Tell me about a time one of your direct reports disagreed with you and how you handled it.” The answer reveals whether this person can engage with disagreement productively or whether they avoid it, escalate it, or punish it. If they say “we do not really have conflicts on my team,” that is not a sign of harmony. It is a sign that people have learned not to speak up.
Talk to people who have worked for them. Not the references they provide. Those are curated. Use your network to find people who actually reported to this person. Ask specific questions: When you had a problem, did they help you solve it or tell you to figure it out? When you made a mistake, how did they respond? Did you feel you had real authority or were you constantly seeking permission? Did they advocate for your growth, even when it meant losing you?
Watch how they communicate during the interview process. Are they responsive? Do they follow through on what they say they will do? Do they answer questions directly or deflect? The interview process is the best version of themselves. If communication is poor during the courtship, it will be worse after you accept.
Ask about their failures. Grace Park told Marcus about the two people who did not work out in the role, and she explained what she thought went wrong, including her own part in it. Richard Calder described a vision of perfection. One of those approaches requires self-awareness and courage. The other requires a good dinner reservation.
Assess whether they will grow you. Some managers see their direct reports as extensions of themselves, useful in their current position. Others see them as people with their own trajectories. The second type will push you into uncomfortable situations because growth requires discomfort. They will give you honest feedback, including the kind that stings. They will advocate for your promotion even when it means losing a strong performer from their team. The first type will keep you where you are useful to them and call it empowerment.
A strong boss at a company you have never heard of will do more for your career than a weak boss at the most admired company in your industry. This is not a close call. I have seen it play out enough times, in enough organizations, with enough capable people, to be certain.
Choose the boss, not the company.
Jeffrey Pfeffer’s research at Stanford on power and leadership effectiveness is relevant here. His book Leadership BS makes the case that what leaders say about their values during interviews often has little relationship to how they actually behave. I reviewed Pfeffer’s book and found his argument particularly useful for anyone trying to separate genuine leadership from polished performance.