What should I think about and focus my efforts on when I get a project and a role that's of (1) bigger scope and (2) tighter deadlines than I'm used to?
A reorg has suddenly thrust me into the TL role for a very high-profile project on a new team. This project is part of OKRs 4 levels up the chain and has the eyes of several director level people across different functions. From what I've heard, this project already suffered from "too many cooks in the kitchen" syndrome, and on top of that, this project has delivery date set in Q3, which is quite aggressive from our org's standards.
I've landed in this position because I was transitioning to this team prior to the reorg, AND the EM/TL/PM/2 L5s has been reorg'ed out, and they needed someone who had previously TL experience and was willing to do it.
I've previously TL'ed a team of 4 people, with important but "normal" priority projects. This is clearly a great opportunity for me, but I am afraid I'm not ready to handle it and I'm at a bit of loss as to what I should be focusing most of my effort on. With the tight deadlines I have, I feel like every day will be a battle so any advice on how to approach this will be appreciated.
I have one other L5 supporting me who I trust very much and a new EM who's rumored to be very good. We currently have 4 SWE including me and we'll be getting more at least 4 more engineers, with lots of adjacent teams helping out. I do also have good standing and connection in the org overall and I know how to get a "normal" project in our org over the line (I did an in-org transfer).
All great questions! I know this is easier said than done, but my main advice is around mentality: See this as an opportunity, not a chance for failure. Be excited, not scared.
There's a lot to unpack here, so I'll go through the questions one-by-one.
...so maybe I should focus on is to understand the work that's been done really well, and the design choices that's been made already?
Good instinct - You should definitely do this! When working at a massive company like Google, there's going to be sooooo much context and nuance underneath the hood. It's crucial that you get it all out there. Take ample notes and create a singular source of truth project doc.
Here's some good resources to help with this:
I feel like biggest personal risk is that I don't know how to show up in higher-stake meetings with directors. Is it any different?
Yes - They're going to be operating at a much higher altitude than you are. Learn to speak in high-level strokes and don't get bogged down in the details. They care about whether the project is going to ship on time and what teams need to brought in to support dependencies, not what library you are using to pass data between services.
A lot of the concepts behind skip-level 1 on 1s apply here. I recommend going through these:
Where do you all see the risk is?
Knowing how similar Google and Meta are in terms of engineering culture and company maturity, I'm 90% sure the biggest risks are non-technical. Think communication gaps with other teams, compliance/legal issues, and ambiguity around the product requirements.
Here's a great discussion around how you can derisk the project here: "How to sequence activities to reduce risk?"