Signs Your New Manager Will Be an Advocate vs. an Obstacle

It took me a year to realize my manager was never going to advocate for me. The signs were there from month one. The vague feedback that never sharpened. The way my project wins showed up in their updates without my name attached. The promotion conversation I kept trying to start that they kept deflecting.

Within your first few weeks under a new manager, there are concrete signals that tell you whether this person will help your career or hold it back. Most engineers miss these signals until it's too late. They assume good intentions, give it time, and then look up 18 months later wondering why nothing has changed.

You don't need 18 months. You need to know what to watch for.

Why the first few weeks matter so much

The first month with a new manager sets the pattern for everything that follows. Not because people are incapable of change, but because the behaviors your manager shows early are their defaults. Those defaults reveal their management priorities, their communication style, and how they think about the people who report to them.

A manager who asks about your career goals in your first one-on-one will likely keep asking. A manager who spends that first meeting talking exclusively about project status will likely keep doing that too. Neither is a permanent sentence. But one pattern leads to advocacy, and the other leads to you being treated as a delivery resource rather than a person with a career.

The sooner you read the signals, the sooner you can adjust your strategy. That's what this is about. Not labeling your manager as good or bad. Figuring out what you're working with so you can act accordingly.

Advocate signals: what to watch for

These are the behaviors that indicate your manager is invested in your career, not just your output.

They ask about your goals early

An advocate manager asks some version of this question in your first or second one-on-one: "Where do you want to be in a year? What are you working toward?"

This matters because the question itself is optional. No one requires managers to ask it. The ones who do are the ones who think about their reports as people with trajectories, not just engineers with task lists.

Pay attention to what happens after you answer. A manager who asks and then does nothing with the information was performing a checkbox exercise. A manager who references your goals in future conversations, connects project assignments to your growth areas, or brings up your development unprompted is using the answer as a working input.

They give specific, actionable feedback

"That design doc was well-structured, but the section on trade-offs needs more depth. The committee will want to see you considered at least three alternatives."

Compare that with: "Good job on the design doc."

The first version tells you exactly what to improve and why. The second tells you nothing. Advocates give directional feedback because they're thinking about where you need to go, not just evaluating where you are.

Watch the specificity of feedback in your first few interactions. Vague praise and vague criticism are both red flags. Specific feedback, even when it's tough to hear, is evidence that your manager is paying attention and investing energy in your development.

They mention you in rooms you're not in

This is harder to detect early, but the signals show up. You hear from a peer: "Your manager brought up your work in the team lead meeting." You get invited to a cross-team project and learn your manager recommended you. Someone in leadership mentions something about your project that they could only know if your manager talked about it.

Advocates actively narrate your work to people who matter. This is the single most valuable thing a manager can do for your promotion case, because promotion decisions happen in rooms you're not in. A manager who carries your name into those rooms is building your case before you even ask them to.

They connect your work to the bigger picture

"The reliability project you're leading ties directly into the VP's OKR around reducing customer-facing incidents. I want to make sure that connection is visible."

An advocate manager doesn't just assign you work. They help you see how your work maps to organizational priorities and, critically, they make sure the people who own those priorities know you're contributing. This framing is what separates "I worked on reliability" from "I drove the reliability initiative that reduced customer-facing incidents by 30%, directly supporting the VP's top quarterly goal." The second version is a promotion case. The first is a task summary.

They share context from leadership

"In the directors' meeting yesterday, they talked about shifting investment toward platform work next quarter. I think that's relevant to what you're working on."

Advocates share organizational context because they see you as someone who benefits from having it. They're treating you as a professional who can use information strategically, not as someone who only needs to know their next task.

This also signals trust. A manager who shares leadership context is signaling that they view you as part of the team's inner circle, not its labor force.

Obstacle signals: what to watch for

These are the behaviors that suggest your manager will not actively support your career growth. Some are intentional. Most are not. The impact is the same either way.

Their feedback stays vague across multiple conversations

"You're doing fine." "Keep doing what you're doing." "Things are going well."

One or two vague answers early on might just mean your manager is getting up to speed. But if you're three or four one-on-ones in and you still can't articulate what your manager thinks you should improve or what "great" looks like in their eyes, you have a problem.

Vague feedback is a signal of one of three things: your manager hasn't thought about your development, they're avoiding a hard conversation, or they genuinely don't know what growth looks like at the next level. None of these lead to advocacy in calibration. A manager who can't tell you what you need to work on will not be able to tell a committee why you're ready.

They take credit or fail to attribute your work

Your manager presents your analysis to the leadership team without mentioning your name. The project update email references "the team's" work on something you individually drove. Your skip-level doesn't seem to know you were the lead on a project you spent three months building.

This can happen through carelessness rather than malice. Busy managers sometimes forget to name names. But the pattern matters more than the intent. If your work consistently gets absorbed into your manager's narrative without attribution, your contributions are invisible to the people who decide promotions.

If you see this early, it's a signal to start building visibility independently rather than relying on your manager to carry your story.

They don't know your projects

You mention a project in your one-on-one and your manager looks confused. They ask questions that reveal they haven't read your status update. They mix up what you're working on with what your teammate is doing.

This isn't always a character flaw. Some managers are stretched across too many reports or too many responsibilities. But the effect is the same: a manager who doesn't know what you're working on cannot advocate for you effectively. They can't tell the calibration room about impact they've never registered.

They avoid or deflect promotion conversations

You say: "I'd like to talk about what it would take for me to get to the next level." They say: "Let's focus on the current quarter first." Or: "It's too early to be thinking about that." Or they simply redirect the conversation to project work every time.

The deflection itself is the data point. An advocate might say "I don't think you're ready yet" and then tell you why. That's hard to hear, but it's useful. A manager who won't engage with the topic at all is either uncomfortable with the conversation, doesn't think about your development, or has already decided they're not going to support you and doesn't want to say it.

If promotion conversations get deflected more than twice, stop trying to bring it up casually. Ask directly: "I want to understand what it would take for you to support my promotion. Can we set aside time to discuss this specifically?" Their response tells you whether this is avoidance or a conversation they're willing to have on the right terms.

They add responsibilities without context or recognition

You keep getting pulled onto new projects, extra on-call shifts, or cleanup work that nobody else wants. Your workload grows, but nobody frames these additions as growth opportunities. They're framed as needs. "We need someone on this." "Can you pick this up?"

There's a difference between a manager who stretches you toward the next level and a manager who stretches you because you're reliable and they need the work done. The first comes with context: "This cross-team coordination project will give you the visibility you need for your promotion case." The second comes with nothing. Just more work.

Signals that could go either way

Not every early behavior is clearly good or bad. Some require more time to interpret.

A quiet, reserved manager. Some of the best advocates are not energetic cheerleaders. They're quiet operators who fight hard behind closed doors but don't perform support in your one-on-ones. Give a reserved manager a few months before drawing conclusions. Watch what happens when your name comes up in broader forums.

A manager who challenges your work frequently. This can feel combative, but some managers push back because they're trying to strengthen your case. The test is whether the challenge comes with direction. "This won't hold up in front of the committee; here's what they'll ask" is advocacy disguised as pushback. "This isn't good enough" with no further explanation is not.

A manager who is new to management. First-time managers often don't know the promotion system, don't realize they need to advocate in calibration, and don't know what good career conversations look like. This doesn't make them an obstacle. It makes them inexperienced. The question is whether they're willing to learn and whether they're open to you helping them understand what you need.

How to test which type you have

If the signals are mixed, run these two tests deliberately. They'll give you clearer data.

The promotion question test

Ask your manager directly: "What would I need to demonstrate for you to support my promotion to [next level]?"

• Advocate response: Specific gaps, a rough timeline, and willingness to work on a plan. "You'd need to show cross-team impact at the scope we talked about. Let's map out what that looks like this quarter."
• Obstacle response: Vague deflection. "Just keep doing great work." Or: "We'll talk about it when the time comes." Or worse: silence, followed by a topic change.

The credit test

After completing a significant piece of work, notice what happens. Does your manager mention your name when discussing the project with their peers or leadership? Does your skip-level know you were the one who drove it?

If you want to test this proactively, send your manager a summary of a recent win with specific impact numbers. Then pay attention to whether that framing shows up anywhere beyond your one-on-one. An advocate uses the material you give them. An obstacle lets it disappear.

What to do if you spot obstacle signals

The worst response is to panic. The second worst response is to do nothing and hope it changes.

Don't assume malice. Most managers who display obstacle behaviors are not trying to sabotage you. They're overwhelmed. They're new to management. They have different priorities. They might not even realize they're failing at this part of the job. Understanding the reason helps you choose the right response. A busy manager who forgets to attribute your work is a different problem than a manager who deliberately takes credit.

Have a direct conversation. Before escalating or planning an exit, give your manager a chance. Be specific about what you need: "I want to make sure my contributions are visible beyond our team. Can we talk about how to make that happen?" Some managers will respond well to directness. They didn't know you needed this, and now they do.

Build alternative advocates. If your manager can't or won't advocate for you, your manager isn't the only path to promotion. Build relationships with your skip-level, peer managers, and senior engineers who sit on committees. Cross-team work, presentations, and written artifacts all create evidence that exists independently of your manager's voice.

Document your evidence. Regardless of your manager's behavior, keep a running log of your wins, framed in terms of impact and scope. If your manager eventually becomes an advocate, you'll have the material ready to hand them. If they don't, you'll have the documentation you need to build your case through other channels.

Set a timeline for yourself. Give the situation two to three months of deliberate effort. If, after direct conversations and visible wins, your manager's behavior hasn't shifted, the data is in. Start exploring internal transfers, alternative advocates, or other options. Waiting indefinitely for a manager to change is how engineers lose entire cycles.

The difference between a bad manager and a bad fit

One more thing worth naming. Some managers are genuine obstacles. They take credit, block visibility, and avoid growth conversations because it serves them.

But many managers who look like obstacles are just bad fits for what you need right now. A technically brilliant manager who's terrible at organizational politics might be great for your learning but terrible for your promotion. A manager who's excellent at advocacy but doesn't give meaningful technical feedback might accelerate your title but not your skills.

The question isn't whether your manager is a good person. The question is whether their default behaviors align with what you need to move forward. If the answer is no, and the conversation about what you need doesn't change anything, adjust your strategy rather than waiting for them to become a different manager.

The signals are there from week one. Your job is to read them early enough to act.

---

CareerClimb helps you build a promotion case that doesn't depend on one person's advocacy. Document your evidence, track your progress, and stay in control of your career. Download CareerClimb and start building your case today.