Hi all
Recently received an offer at meta as a principal engineer (E7) working on ig recsys. I am currently an L6 at google
It is an exciting opportunity with 2x TC increase.
But at the same time I always have a doubt to how I should prepare my onboarding since this is a high level of seniority to be in a new company and expectation of leading 30 engineers roadmaps.
Could I ask for your help?
Thank you in advance for your help:)
Oh wow, congrats on the offer! The vast majority of engineers never make it to Meta E7. I know that Google's pay bands aren't nearly as competitive compared to Meta's once you get to really high levels (L6+), so the 2x TC increase makes sense.
First, I recommend this thread: "What are the hidden and easy cherry picking to do for E7 promo?"
What are the mindset change I need to adopt to build impact?
Honestly, I think your mindset doesn't have to change much. From my experience, operating at E7 is largely an extension of the mindset shifts you made to get to E6.
If you haven't already, you should do some introspection and figure out what Staff+ engineer archetypes work for you. From there, figure out what Staff+ archetypes your team needs (you can even ask your manager about it as Meta has official archetypes). Here's the section of our L5 -> L6 course about the Meta archetypes: https://www.jointaro.com/course/grow-from-senior-to-staff-engineer-l5-to-l6/why-have-archetypes/
How do I build my reputation quickly to safeguard against layoff?
On top of delivering extremely high quality work, E6/E7 engineers are also judged heavily on how they're able to build deep relationships quickly across broad swaths of the organization. I made an entire course about that: Networking Guide: Build Deep Relationships Quickly In Tech
Hi Alex,
How do I figure out who to build relationship with? What would ideal E7 performance evaluation look like?
How do I figure out who to build relationship with?
I recommend these lessons:
An E7 will absolutely need to have good relationships with the following:
I assume "ig recsys" is "Instagram Recommendation Systems", which seems more like an infra team instead of a product team. So I imagine needing to know the non-technical people like product design, PM, marketing folks, etc aren't as necessary.
Hi Alex. I forgot to mention this. But due to personal matter, I will need to onboard and work remotely for at least 1 year before moving.
Do you have good tips and advice on building connections while you are remote? Thank you
Do you have good tips and advice on building connections while you are remote? Thank you
I recommend this: Networking Guide: Build Deep Relationships Quickly In Tech
This is another good resource: "How to build meaningful relationships with your co-workers if you work remotely?"
What are good expectations to have to achieve within 3, 6, 9, 12 months and any tips to achieve them?
This is tricky as it depends on your Staff+ Engineer archetype, what the needs of your team are, and the overall seniority of the team. If you are the only E7, the team will expect you to be the overall lead. If you aren't the only E7 and maybe your team even has an E8/E9, then it's possible you're functioning in more of an IC capacity (some crazy stacked infra teams are like this).
To understand Meta leveling, I would go through this: "What do career levels structure in big tech company look like? What are the responsibilities for each level?"
If I were to generalize E7 expectations, I would expect them to really "Wow!" the team within the first 1-2 months. I remember we hired a Google L6 as a Meta E7 into my org at Instagram Ads and in the first month, he discovered an ad optimization that added $10M+ in yearly revenue. That's what I would expect from an E7 (that's why you guys get paid the big bucks!).
After 6 months, E7s should be strong owners of multiple workstreams and leading multiple E6s.
Hi Alex,
Could you give a bit more detail about what the first 1-2 months be like on bootcamp and ramping up especially for E7 Meta? Is there any directions on ramping up "smartly" and not "hard"
I think that I will need to prepare more due to:
Could you give a bit more detail about what the first 1-2 months be like on bootcamp and ramping up especially for E7 Meta?
I understand that you're looking for more granularity here, but at E7, it's just really, really, really hard to give. E7s are so specialized and different, and the necessary behavior and impact for an E7 will vary wildly from team to team.
The first 1-2 months are also pretty unpredictable nowadays as bootcamp functionally doesn't exist at Meta anymore. Back in my day, bootcamp's primary purpose was team matching, and it was a relatively fun time with low expectations where you're doing general training and learning about the culture.
Now, every team wants their new hires to hit the ground running ASAP. Bootcamp exists in name only, and everything I described in the previous paragraph doesn't really exist. So your initial time at Meta will be dictated by whatever the situation of the team is, and it's hard to predict that. Meta moves incredibly fast, so the burning need on a team can easily change every month or even every week.
In a nutshell, you will need to do the following as an E7 within your first quarter (this should apply to any team):
If #2 can't be fully done, I would expect the E7 to at least be in experiment stage.
Instagram Recommendation Systems is a very mature team I imagine, so I would bet that the team goals are very clear and measurable.
My last bootcamp is when I was L3. So I am not sure if during the first 1 year, I should expect spending around 60 hours per week to have "wow" impact.
You should 100% expect long hours:
Of course, you will get rewarded for all of this with the 2x TC increase.
Zooming out from all this, a strategy you can take here is to simply not take the Meta E7 offer, especially if you still enjoy your life at Google as an L6. You are actually on the right side of the fence as Google does negotiate internally (Meta doesn't), especially to prevent Meta poaching. I know so many Google engineers who took a Meta offer to their director and got massive pay increases ($100k - $250k). One of them was a Google L4 who got their TC to $425k!
A Meta E7 offer is incredibly valuable, and I would be really surprised if you couldn't get Google to bump up your TC by minimum $250k.
How do I seek for mentor? I am afraid my old mindset of building things might be outdated for E7
There is a secret E7+ engineer group in Workplace at Meta. I would look there. However, I would also set expectations super low as E7+ engineers are super busy people, and there really aren't a lot of you.
On top of the networking course, here's a nice thread about finding a mentor: "How does one attract a sponsor who is invested in their growth?"
Any guides on using ai and vibe coding to help me build impact as E7?
Honestly, my guide is pretty much this: Don't.
Unless you are the code machine archetype (which is super rare), the expected amount of commits from you isn't super high. You'll need to go for more of a quality play where you're working on the hardest tasks and submitting the highest-quality code. In other words, you'll be working on problems where AI is effectively useless (even toxic), which is a big value prop for why engineers are E7+ to begin with (i.e. they solve the problems AI can't solve).
Hi Alex, what would be the ratio on coding and non coding expectation for Meta E7?
Can you give me a rough idea on a typical day of E7 and what would be the percentage time allocated for different work?
Hi Alex, what would be the ratio on coding and non coding expectation for Meta E7?
Again, it really depends. I worked in Instagram product, so the E7+ engineers were mostly product hybrid archetype. The most senior one (E3 -> E8 in <7 years) only had ~10 commits per half. They spent <5% of their time coding.
On the other hand, an E7 code machine will have 400-500 commits per half and probably spends 70%+ of their time coding.
Specialist and fixer archetypes will also spend more of their time coding, but their diff output will definitely be lower than code machine.
Can you give me a rough idea on a typical day of E7 and what would be the percentage time allocated for different work?
You run into the same dilemma as before - It entirely depends on your archetype. The archetype you will be also isn't set in stone as engineering leadership generally expect E7s to be flexible and able to switch archetypes depending on org need. Talk to your manager.