How to Evaluate a New Team Before Joining

You did all the hard work. Passed the interviews, negotiated the offer, picked the company. Then you joined a team where three people quit in your first four months, the roadmap changed twice, and your manager was so buried in meetings that your 1:1s got canceled more often than they happened.

Six months later, you're building a case for promotion with no one to advocate for it and no project scoped large enough to justify it.

This happens constantly. Engineers spend weeks evaluating companies and almost no time evaluating the team they're about to join. The team determines your day-to-day experience, your access to meaningful work, and how fast you move up. A strong team at a mediocre company will do more for your career than a weak team at a top-five employer.

Whether you're transferring internally or accepting an external offer, here's how to figure out what you're walking into.

Why the team matters more than the company

The company gives you the brand and the compensation band. The team gives you everything else: the manager who will or won't fight for you in calibration, the projects that will or won't give you next-level scope, the peers who will or won't push you to grow.

Gallup's research found that managers account for at least 70% of the variance in employee engagement scores. That means if you know nothing about an employee except who their manager is, you can predict their engagement with surprising accuracy. The company name on your badge matters less than the person running your 1:1s.

This is also where promotion timelines diverge. Engineers on teams shipping small incremental features rarely get promoted above senior. The projects aren't scoped at the level calibration committees look for. The Pragmatic Engineer has written about this directly: greenfield teams and high-impact initiatives are where engineers build the scope that gets them to the next level. Keeping the lights on has never been rewarded the same way as building something new.

Pick the wrong team and you'll spend months compensating for structural disadvantages that better diligence would have caught.

Questions to ask in 1:1s with potential teammates

The manager will sell you the vision. Your future teammates will tell you the truth. Always ask to speak with at least two engineers on the team. If the team won't arrange this, that's a signal by itself.

"How many people have left the team in the last year, and why?" One departure for a great opportunity is normal. Three departures in twelve months means something is wrong. Listen for whether they're candid or evasive.

"When was the last time someone on this team got promoted?" If no one has been promoted in two years, either the scope isn't there or the manager isn't advocating effectively. Both are problems.

"What does the on-call rotation look like?" Operational burden is often hidden during evaluation. A team where engineers spend 30% of their time firefighting leaves less room for project work that builds a promotion case. Ask about pager frequency and what incidents look like.

"What's your manager's biggest strength and weakness?" Most people will soften the weakness, but the framing tells you a lot. "They're busy but supportive" is different from "They're hard to reach." "They give autonomy" might mean they're absent.

"Is the roadmap clear for the next six months?" You want defined ownership areas, not a team where priorities shift every sprint. A clear roadmap means you can identify a project, own it, and build a narrative around it.

Red flags that predict a bad experience

Not every problem is visible in a 30-minute chat. But some patterns are reliable.

High turnover with vague explanations. If multiple people have left recently and no one can explain why, the reasons are ones they don't want to share with a candidate. On Team Blind, engineers flag "always hiring" as a signal of churn, not growth.

The manager is always in meetings. A manager who can't protect their own calendar will not protect yours. A manager who's perpetually unavailable doesn't know your work well enough to represent it. When calibration comes around, they'll have vague praise instead of specific examples. Making your manager fight for your promotion requires that your manager actually knows what you've done.

Unclear ownership boundaries. If you ask "who owns what" and the answer is "everyone pitches in on everything," expect confusion about credit and accountability. Shared ownership sounds collaborative. In practice, it means no one gets credit for anything specific.

No one can describe what success looks like. If current team members can't tell you what a strong first six months looks like, the team doesn't have clear expectations. That ambiguity makes it hard to build a promotion case because no one agrees on what "great" means.

The position was just created with no clear charter. New roles can be opportunities, but they can also be catch-all positions that exist because leadership wanted headcount without defining the work. Ask what problem this role solves.

Green flags worth paying attention to

Clear roadmap with defined ownership. If the team can show you what they're building for the next two to three quarters and which engineer owns which area, you're looking at a well-run operation. You'll be able to pick up a project, lead it, and point to the outcome.

Recent promotion history. A team where multiple people have been promoted in the last 18 months tells you two things: the work has enough scope to justify promotions, and the manager knows how to get people through calibration.

A manager who talks about people, not just projects. When you ask the manager about the team, listen for whether they describe people's growth or just deliverables. A manager who says "I helped two engineers get to senior last year" is telling you they invest in careers. A manager who only talks about shipping velocity is telling you they manage output.

The team has an onboarding buddy system. Sounds minor, but it's a proxy for how much the team invests in new members succeeding. Teams with structured onboarding retain people longer and ramp them faster.

Low regret among current members. Ask teammates: "If you could go back, would you join this team again?" The hesitation or confidence in their answer tells you more than any pitch.

How to assess the manager before you commit

The manager decision is the most consequential part of choosing a team. A great manager on a mediocre team will still develop you and advocate for you. A weak manager on a great team will let your work speak for itself, which sounds fine until you realize that work doesn't speak in calibration rooms. People do.

Ask them to describe a recent hire who succeeded and what that person did. This reveals what the manager actually values. If their answer centers on output and hours, that's a different environment than one where the answer centers on ownership and growth.

Ask how often they have career development conversations. Some managers treat 1:1s as status updates. Others use them to discuss trajectory, gaps, and next-level criteria. The answer tells you which kind you're getting.

Ask what happened when someone didn't get the promotion they expected. Uncomfortable to ask, but revealing. A manager who says "we built a plan for the next cycle and they got it six months later" invests in recovery. A manager who deflects or blames the committee won't go to bat for you when it's hard.

Watch the 1:1 logistics. If your introductory meetings get rescheduled twice before they happen, you've learned something about their availability. Managers who cancel on candidates will cancel on reports.

How team choice affects your promotion timeline

The same engineer, with the same skills, will get promoted two years faster on the right team than the wrong one. Here's why:

Scope availability. Promotions above mid-level require demonstrating next-level scope. If the team's work is narrow or maintenance-heavy, that scope doesn't exist. You can be the best engineer on the team and still lack the evidence calibration committees need. When you're building a career path, team selection determines whether the path has room to grow.

Manager advocacy. Your manager argues your case in a room you're not in. A strong manager walks in with specific examples and quantified outcomes. A weak manager walks in with "strong contributor, good teammate" and folds at the first pushback.

Peer caliber. Working with engineers better than you accelerates your growth. Working with disengaged engineers slows it. The team sets the bar for what "normal output" looks like, and that bar is what you'll be measured against.

Organizational visibility. Some teams sit at the center of the business. Their launches get mentioned in all-hands, their impact is visible to leadership. Other teams are support functions that leadership rarely thinks about. Both matter. But one gives you more surface area for getting noticed in your first months and building the visibility that feeds promotion decisions.

The team you choose isn't just where you'll work. It's the ceiling on how fast you can move.

---

CareerClimb helps you build your promotion case from the day you join a new team. Log wins, track progress against your company's criteria, and make sure your manager has the evidence to fight for you when it counts. Download CareerClimb