1

How should the management chain impact my team selection in bootcamp?

Profile picture
Senior Software Engineer [E5] at Meta2 years ago

I'm debating between two teams in bootcamp. All else assuming equal, the hiring manager (HM) of team A is higher up on the org chain (Team A HM reports to X, Team B HM reports to U who reports to W who reports to X).

Should this play a factor in deciding between teams?

54
1

Discussion

(1 comment)
  • 0
    Profile picture
    Meta, Pinterest, Kosei
    2 years ago

    In general I’d say Team B is better, as long as you don’t think it blocks your mobility (e.g. if you have immediate plans to transition into management, it’ll probably be harder in Team B).

    More details:

    Team A (where you have a more senior manager) gives you more access to senior leadership, but you’re also likely to have a busier manager.

    • Having a more senior manager is really only beneficial if you’re quite senior, E6+, where having that level of visibility is important. (For more junior folks, this could actually be a negative.)
    • Question to ask: how many reports does the HM for team A have, and how is that expected to change over time?
    • You want to avoid joining the team and then getting thrashed with some new manager taking over within a few months. Then you’d have to rebuild trust with someone new.

    Team B (where you have the manager lower in the chain) is going to have more time + energy for you, and can work more closely with you in things like project selection, team collaboration, and PSC. For most engineers, this is probably a good thing.

    • As long as you feel like there’s a sufficient amount of work to justify promo, I don’t see the long management chain as a huge issue.
    • The failure mode is if this manager is a noob and ineffective. It’s always better to have an experienced manager, esp if the person is also new to Meta.