I would like to change teams before 1 year mark.

A good manager is rare, so my first instinct is to figure out if there's a way to make this situation work. A couple considerations on whether to switch projects or not:

• As a senior engineer on the team, are you able to craft a new project or initiative that you would actually enjoy working on?
• Is there something you can "take with you", e.g. a promotion or milestone that can help you get to E6? Switching teams means you'll have to rebuild context and relationships, so make sure you're aware of the time cost of that.

Given that you don't like the people on the project, that feels like a good reason to switch teams. Keep in mind that if you switch projects (and not teams), there's a decent chance you may still get stuck working with the same people. Staffing on projects is prone to change among team members.

In terms of bringing it up with your manager,

• You typically want to frame your request in terms of "I'm going toward something" rather than "I'm running away from something'. That means you should do some research before talking to your manager about an idea or pre-existing project that you're excited about.
• Timing should be when you've made the commitment to switch projects/teams. If you waffle on the decision, you'll cause confusion for yourself and the team, and you will likely lose trust with your manager. I wouldn't be too concerned about whether this is 9 months vs 11 months vs 1 year.

Here's another great discussion about changing teams within Meta: https://www.jointaro.com/question/dMNWpXZPWuqm4mPvkJl6/when-is-a-good-time-to-change-teams/

Should I move to a new project?

9 months is pretty close to a year, so moving teams within this time-span isn't too bad. If you were to switch within the next 1-2 months, you should have enough time to do well in PSC too (you want to avoid completing the switch in the summer as now you have a "half-baked" case with 2 teams).

That being said, I do have some questions for you:

1. How long is this new project? - If it's just 2-3 months, you could just complete it and move on.
2. How tied are you to the project? - E5 is the level where I start expecting ICs to have an opinion about what they're working on, and EMs will often allow high-performing E5s (i.e. those making progress towards E6) to have a say in what they're doing. Can you talk to your manager about switching to a different project?
3. Is this project fixable? - Can you build better relationships with the other stakeholders on the project? Sometimes people just don't naturally get along, and it takes time for the working relationship to improve. Patience is important.

As Rahul mentioned, having a good manager you get along with is very rare, even at a top company like Meta. Most engineers I know at Meta took several managers before landing one they really clicked with. Personally, I would lean much more towards repairing the current situation.

How to bring this up to my manager and when is the right time?

As mentioned before, you should bring this up ASAP to make the PSC math cleaner. Spend 1-2 weeks seriously thinking about your future on your current team, and if you have decided that you have to move, bring it up in the next 1 on 1 with your manager.

I recommend reading through these as well:

• "Guidance on changing teams?"
• "What's the best way to approach a team switching conversation with my manager?"
• "How do I know when it's time to leave a team/company?"