I am in the very fortunate position to be choosing among some great offers. My question is how to properly choose between

1. A company with an industry-leading reputation (eg Citadel, Two Sigma, DeepMind)
2. A “lower tier” company with less brand recognition/lower quality bar but is able and willing to outbid company (1) on comp.

If comp were equal going to company (1) would be a no-brainer, but how much of a premium should I place on the brand of a company? Put another way, how can I place a number on things like exit option value, social/engineering prestige and so on.

How do I assess the “brand premium” when choosing a company?

Session #2 - Building A Meta Internal Tool To Empower An Entire Org: Staff Promotion Story

- Debugging was a huge pain point for the Facebook Portal org.
- To fix this, Rahul built a tool that made it far easier to debug tricky Android issues (Portal runs a fork of Android). It took all the crazy dump files from Android bugs and extracted the insights.
- Rahul started off the tool with an *extremely* simple interface: Upload the massive dump file and it would extract insights. He would improve it later by making it so the user only needed the bug ID.
- The tool started off with around 100 engineers using it and then grew to 250+! This massive scope was enough to get Rahul AE (additional equity) and a promotion to E6 (Staff at Meta).
- How you can incorporate these learnings into your work:
  - Look internally for opportunity. There are ways to have impact besides shipping flashy products, and in Big Tech in particular, improving engineering efficiency can be a *huge* win given how many engineers there are!
  - Understand the pain of your peers. Not only is this just a kind, empathetic thing to do that builds relationships, pain often comes with opportunity.
  - Think outside your stack. Instead of working forward from your stack of choice and what you can do with that, zoom out and holistically look at problems across your org in general. It's cheap to learn other stacks to build solutions - The main thing to do is identify problems.
- Here's [a link to the slides](https://docs.google.com/presentation/d/1Scxll_pApdPLXk42jSHcrZ4LaTE8_7BUjvB14z9-SgU/edit?usp=sharing).

Related resources:
- [In-depth breakdown on why this project was Staff-level behavior](https://link.jointaro.com/uLUXinMbCNkUFj9H7)
- [What's the Difference Between A Senior And Staff Engineer?](https://link.jointaro.com/BEM2RAjPFe8Pv7826)

Got feedback from manager that my rating is just MA and on the border. I was given the context that my project complexity was not that much and it was a lower level project. I worked really hard and was expecting good ratings. What can I do to make sure that I exceeds the expectations next time?

Feeling discouraged that my rating is lower.

Performance Review Ratings Example: Meta & Google

- Meta:
  - Meets Some Expectations (MS)
  - Meets Most Expectations (MM)
  - Meets All Expectations (MA): Need this or above to be doing okay.
  - Exceeds Expectations (EE)
  - Greatly Exceeds Expectations (GE)
  - Redefines Expectations (RE)
- Google:
  - Needs Improvement (NI)
  - Consistently Meets Expectations (CME): Need this or above to be doing okay.
  - Exceeds Expectations (EE)
  - Strongly Exceeds Expectations (SEE)
  - Superb
- Other companies will use a 1 to 5 system which roughly maps to the above, Google in particular

If you fall below MA at Meta or CME at Google, you will either immediately be put on a [performance improvement plan (PIP) or be at huge risk for one](https://www.jointaro.com/lesson/7SsdpweHE4sbyTtz2kxQ/the-key-to-avoiding-the-performance-improvement-plan-how-to-figure-out-where-youre-trending/).

Related resources:
- [[Masterclass] How To Navigate Your Performance Review In Tech](https://www.jointaro.com/lesson/b0B8uqIAUnBLE10jJHJG/how-to-navigate-your-performance-review-in-tech-7232022/) - This is the full video this clip was taken from
- ["What's the difference between a low performer software engineer and a high performer?"](https://www.jointaro.com/question/nMxx2EMVIlJbl1oK4SGu/whats-the-difference-between-a-low-performer-software-engineer-and-a-high-performer/)
- ["How do I help my manager (who is also my mentor) be a better manager and mentor?"](https://www.jointaro.com/question/LbHgSEtXcb5QR5nVu8xt/how-do-i-help-my-manager-who-is-also-my-mentor-be-a-better-manager-and-mentor/)

Entry-Level Software Engineer [E3] at Meta

I'm currently in bootcamp and deciding between back-end and iOS/Android. I'm pretty neutral about these stacks, but I do have a slight preference for back-end as it seems similar to topics I learned in school.

Are there any differences in growth potential in any of these focus areas?

Which team and stack should I choose in bootcamp?

Session #9 - How To Become A Data Guru As An Engineer (w/ Senior Director of DS Mo Shahangian)

Mo has had a successful career at the intersection of data science and engineering at companies like Pinterest, Meta, and Epic Games.

Mo talked about the biggest data mistakes and how the job changes as you navigate seniority levels. He also shared his contrarian approach to promotion that has worked so well in his career. 

## Data knowledge for engineers:
- Data science is an overloaded term. The high-level goal for anyone working with data is to surface insights that will inform decisions. 
- Being insightful isn’t enough -- you need to surface **actionable** and **causal** relationships.

Everyone needs a reminder correlation != causation. Have some tools to remind yourself.
- Which way does the causal arrow go?
- Remember [Goodhart’s Law](https://en.wikipedia.org/wiki/Goodhart%27s_law)

## Career growth
- At the most senior levels, leaders are business owners/product leaders, not functional leaders.
- At more junior levels, it’s the opposite, there needs to be order and a separation of responsibility. The best people learn how to work, not only within their lane, but across.

Career success comes from being deliberate:
- A career is a series of decisions
- These decisions come with tradeoffs
- Those best at navigating tradeoffs emerge as leaders
- "Deliberate" means that you are both intentional and calculated

Mo started out building data systems at UCLA, joined Pinterest during hypergrowth, and eventually became a Senior Director of Data Science at Meta, and recently joined Epic Games at the leadership level. Connect with Mo: https://www.linkedin.com/in/mohammad-shahangian-b040188/

[Connect with Mo](https://www.linkedin.com/in/mohammad-shahangian-b040188/)

More resources: 
- Another Taro Premium Session about [junior --> senior eng promos at Meta](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/session-5-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/)
- [Why chasing promo could hurt you](https://www.jointaro.com/lesson/qj2kX94TfFPgBLlQZBtb/why-chasing-promotion-could-hurt-you/)

For this upcoming half, I'm working in four different areas: reliability, sourcing,  delivery, and datastore table. It just seems like it's too much and I'm not building any depth? Feels like I won't be able to build expertise in anything and be unable to contribute as a good team member if I'm working on everything? \
\
My TL has also informed me they are struggling to scope out work due to a lack of senior engineers. This has resulted in me getting menial tasks such as better engineering work and refactoring in some of these projects (i.e. delivery,  sourcing, and reliability). It's great for my diff stats, but I want larger scope and less narrow work to be considered for E4. I'm discussing with EM, but the EM and TL seem like they are on different pages. I'm most interested in sourcing, but seniors are struggling to scope out work.\
\
Any suggestions on what to do here? I feel a bit lost overall and I'm struggling to understand how to get scoped and larger non-menial project work. Should I involve my skip manager here? A couple of questions in this one question but appreciate all the help in advance.

My ideal plan was to reach E5 (Senior Engineer) on my current team and then leave. But I am nowhere near promo currently. I’ve been on my current team for about 1.5 years now. I have to get promoted in about a year from now, or else I’ll be fired. 

I need help deciding whether I should roll the dice and switch to another team. I’ve built some strong relationships on my current team, worked with my manager for over a year now and am fully ramped up to my current team’s stack. I’m not sure how to make the decision of whether to leave or to stay.

An XFN stakeholder came up with a last minute requirement for a big project I'm working on, which will probably slow down the launch by at least a couple days. I already made promises to other XFN about the launch date.

What's the best way to mitigate the heat on failing to launch on time and zooming out, how do I deal with last minute launch blockers in general?

Got hit with a last minute requirement on my project - How do I minimize the thrashy impact it has?

Hi Taro community,

Seeking your help in evaluating two offers that I received from two start-up companies.

- (1) In general, in such situations how do you suggest researching about the companies and determining which company and offer is better.
- (2) I am also concerned how my future job potential will be affected and so I want to take the decision accordingly.\
  (3) In this particular case, my offers are as follows,
- company A
  - Unicorn (post money valuation: $1B-$10B), Industry: Ad Tech (ML and cloud infra based), Last funding type: Series C, Total funding amount: $190M, Estimated revenue range: $1M - $10M, Founded in 2013 by ex-googler,
  - I have seen several folks joined from FAANG companies (eg, Google)
  - Offer: base $160K, bonus: 24K, Equity: $88K (not sellable now, but the company is expecting to go for IPO in one year)
- company B
  - Emerging Unicorn (post money valuation: $500M-$1B), Industry: Healthcare/AI, Last funding type: Series B, Total funding amount: $120M, Estimated revenue range: $1M - $10M, Founded in 2017
  - Among big techs, I have found just one person from AWS who joined this company
  - offer: base $190K, no bonus, Equity: 114K (not sellable now, the company is expecting to go for IPO in 2-4 years). I may be able to negotiate this offer.

Thanks in advance for any kind of suggestions/comments.

Need help evaluating start-up offers (Series C Unicorn vs. Series B)

This quarter, my skip requested/ gave me an opportunity to lead an org wide efficiency initiative as we are at risk of hitting quotas for some internal services (he mentioned potential IC6 scope) and it’s quite urgent to act on it. My role is to start and lead a large team of engineers on this initiative which involves tons of direction to ensure our org isn’t over quota. I would look my role as a hybrid of TL+ TPM with following responsibilities: analyzing data to find opportunities, creating roadmaps for the program, supporting engineers for execution to reduce usage, project management, understanding and enforcing processes, building knowledge on internal services, coaching engineers, setting Eng excellence culture within the org. All that to say, given limited time and a need for someone to lead, I will be focusing on direction and delegate all of the execution work to the squad.

1. How risky is it to have low code output as an IC5? Given the year is just starting, does it make sense to explicitly discuss this with my manager and skip that my code output will be close to zero in Q1?

I did read some accounts (anon post on WP) where EM and skip aligning on low code out out but the IC5 still got MM at the end because they had only 10 diffs for a half. I don’t want to be in that position.

1. Should I deprioritize some direction work and allocate some time for coding on my timeline through P2 projects? This will increase diff count but that just seems not a great usage of my time. TIA!

[Part 4] Software Engineer Onboarding: Understand Strategic Decisions

Learn the business to make good strategic decisions.

By the time you're a month or more into your job, you should start execution on your projects, but you should continue gathering context about your team and company. You should document key decision points in your work, and reflect on who is involved, how long various steps take, and the level of detail various stakeholders ask for.

------

This is part 4 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go back to part 1 of the masterclass here](https://www.jointaro.com/lesson/IYZRmwp33E3TBeFQFr9c/part-1-software-engineer-onboarding-embrace-your-lack-of-knowledge/)
- Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Check out the [Formation.dev discount](https://www.jointaro.com/perks/) for Taro Premium members
- [How To Figure Out If A Team Is Important To A Company](https://www.jointaro.com/lesson/9OwPRwFFSMvEoVj6Zt5Q/how-to-figure-out-if-a-team-is-important-to-a-company/)
- [How To Find A Good Team With Career Growth Opportunities](https://www.jointaro.com/lesson/UGIUC9zaGccK0tOarBri/how-to-find-a-good-team-with-career-growth-opportunities/)
- [This Is How You Get Feedback - Making The Process Smooth](https://www.jointaro.com/lesson/aGuxjGbFjYb34ofhRxjs/this-is-how-you-get-feedback-making-the-process-smooth/)

Hi everyone, I'm looking to optimize my resume ([link here](https://drive.google.com/file/d/1gN-V7aRcZjZ4xDbRAE1TM1WwBrJDnw_7/view)) and would love some feedback on it. I also have two specific questions about it.

1. **Should I even include my personal projects in my resume?** Neither have any active users, so all they do is show that I can build something, not necessarily something of value. I've seen advice online about not including personal projects unless they have some sort of tangible value and/or active user-base, but I wanted to hear this community's thoughts about this.
2. **Is my resume too short? Can a resume even be too short?** This partially ties into my first question because without those two projects, the resume would only fill up half of the page. My resume used to have a lot more points describing what I did during my professional experience, but most of it was fluff, so I decided to cut them out. I feel like I am stuck between a rock and a hard place here because if I want to fill up my page with more information, it feels like I would need to add fluff-like material. However, I don't want the few seconds a recruiter will spend looking at my resume to be spent looking at the unimportant fluff material I used to fill up the page, so I added the projects as a way to hopefully avoid the whole issue. I'm wondering if this is even something I should worry about.

Of course, if there's another issue with my resume that I didn't mention in these two questions, please feel free to point it out, even if it's a nitpick. Also, if it helps, for context, I am currently looking to pivot from data engineering to backend development, so I am aiming for more junior level roles.

Thanks in advance!

Resume feedback and questions for a pivot into junior back-end roles?

[Part 8] Meta Intern Success Series - Rahul's Internship + Current Economy

I interned at Meta in the summer of 2013 (it was called Facebook in my day…). I barely got the return offer at the end of the summer. My reflections on what I could have done better: 
- Too much back and forth on my code. I made the same types of mistakes in the code I wrote, and I occasionally tried to pushback if a reviewer requested changes. 
- Not communicating with enough with teammates. In addition to my intern manager, I should have had a regular 1:1 with the person who was primarily reviewing all my code. 

What I did well: 
- I was responsive. I replied to messages + comments quickly, and I tried to share my insights (from my project) where possible.. 
- I was a good culture fit: I built a substantial hackathon project which garnered some attention.

Advice for the current economic condition: 
- Focus on cultivating relationships with people on your team, so they are able to refer you. 
- Leverage the work you did in Meta to more easily land interviews at competitive companies.

[Go back to part 1 of the Meta intern series](https://www.jointaro.com/lesson/DPcsvbf5IKk57xcqyiAC/part-1-meta-intern-success-series-internship-program-overview/)

After this past half (I joined mid-August), my manager is saying I'm working at a meets all (MA) level. Granted, I only joined in the middle of the half, but when I ask him how can I take the next level to be promoted or have an EE or above rating, I get very vague answers with not much detailed support (he's also a new manager and this will be his first PSC).

This past half, we had an expectations doc where it listed each project and the impact it should have. I hit all those expectations, but with his vague advice, I'm not able to create actionable steps for myself for this half to get the promo or higher ratings.

From Taro, I'm learning code quality, velocity, and impact are the most important at my level - which from my feedback, I'm doing well in. What are some ways to take it to the next level? Finish my projects earlier and take on more projects in the half?  Feeling a little bit lost so any advice is greatly appreciated!

How do I prove to my manager I deserve a promotion to E4? Or above a meets all rating?

Hey folks,

I don't know how to contribute to our team's monthly planning. How should I come up with ideas for things that the team should work on and contribute to our team's road-mapping meaningfully?

How to start contributing to team roadmapping/monthly plans?

I joined about 6 months ago and my manager is absolutely great. I don’t have anything where I think they can be better at at this stage. At the current stage, I feel like I have a lot of self improvement to do before expecting anything more from them. What do I say in the critical feedback section for my manager?

How to write PSC Feedback for stellar manager?

Hey folks,

 I’ve been on my current team for almost 1.5 years now. My hope is to get a promotion sometime this year which might require a higher performance review (Exceeds Expectations). But if I get an average performance review (Meets All), does it make sense for me to roll the dice and switch to a different team in the hopes of faster growth there?

I know there are significant costs to switching teams, and I want to make a well-informed decision if I do decide to switch teams internally.

When is the right time to switch to a different team?

Currently, I'm on a 10 person team, but we only have 3 senior engineers and the remaining 7 are E4s (5 people) and E3s (me and one other new grad). For our upcoming half, they want E4s leading some of the projects for their development. However, I would like guidance, mentorship, and feedback from an E5 or above ideally since they are more experienced. Also, from one of the Taro videos on feedback, one of the points made was to find a way to get feedback from senior engineers at the end of the half who will bolster your PSC packet versus a mid-level engineer who might not hold as much weight (Correct me if I'm wrong)? 

Anyway to navigate this the right way? Should I avoid certain projects that are led by E4s? Does this even matter?

How can I position myself best for success given a shortage of senior engineers on our team?

Some background about my experience. I have overall 10 years of experience out of which first 3 years was in Service based company in India and then 6 years at Amazon/AWS and around 9 months at Meta. I got promoted to Sr. position almost 3 years ago and have been working as Sr. Engineer since then.

Since few months before my promotion I am feeling bit burnt out. Promotion came after lot of hard work and honestly the compensation increment was totally underwhelming. So I interviewed and switched and comp increase was really good but I am not liking work culture now. This made me sort of realize few things:

1. Promotion and level don’t actually mean much. I feel like I am part of a rat race and trying to prove my worth to someone who can whimsically just say yay or nay. This is extremely demotivating.
2. Early days of my career were great, I was making good money and learning ton of new stuff. However, now I realized that most of the stuff I learned is not useful outside and I saved enough money to not feel the need to do job just because of money.
3. It is not worth being loyal to one employer. Even though I changed companies for comp, my new employer (Meta) recently let go of lot of people. Some of them have been there for at least a decade. Plus the remaining of us are now in constant fear of layoff based on performance.

Now I want to get out of this job→money→stress→new job→money→stress cycle but don’t know how. I am planning to move back to India after few months and was hoping to start may be freelancing or some consulting work where I can control my time. I am more than happy to take a pay cut. So I started doing some research:

1. **Freelancing**: Most of the jobs in freelancing are web development. I have lot of experience with backend and some experience with web development but I am nowhere close to the people on youtube/udemy. I can most certainly build stuff but have no experience to show for and I am not sure if I’ll be able to find any work whatsoever 😟.
2. **Consulting**: Everybody suggests to build a network and then you can find work through them. My network is mostly SDEs in FAANG who I’ve already talked to. Most of them told me, dude if we know about such work we’ll jump ship as well, but they have nothing. One of my jobs was to build cloud services so I know how to build them at scale. But I have less experience in how to use them, so even if I do certifications I am not sure I’ll be able to find work on this area.

Now last option for me is to find a job which pays less and have less stress which will be okay. I can most certainly say screw it and not worry about getting promoted. But then I don’t know if that’ll be satisfactory, it’ll be more like I accepted defeat and ducked out of rat race but I still have no direction to go on.

Sorry if this all sounds like a rant, but I would love to have some guidance from people who have been in similar situation. What did you guys do and do you have any suggestions for me?

Hi Taro folks,

I’d like to create a doc to track my deliverables across engineering axes to make my work easier to see for my manager. This should also help with arguing for promotions down the road… does anyone have a good format for such a doc? FYI: engineering axes include project impact, people, direction, engineering excellence, etc.

What’s a good example of a 1:1 document to help your manager keep track of your accomplishments?

Why Chasing Promotion Could Hurt You

Daniel has never gunned for a promotion when choosing teams or projects. In fact, he's actively turned down promotions he was offered at Microsoft and Meta (Philip Su famously down-leveled himself at Meta so he was no longer a Director). 

Here's why chasing a promotion could end up causing more stress and end up hurting your career in the long run. 

- Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Videos from [Philip Su](https://www.jointaro.com/tagname/Philip%20Su/)

Related video: 
- [Taro Premium Session: Mentoring Meta Engineers From E3 -> E5](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/session-5-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/)
- [Rockstar Software Engineer Story: SW2 -> Principal In Just 4 Years](https://www.jointaro.com/lesson/Lvf1TDKt1R4ZJSCr9BVv/rockstar-software-engineer-story-sw2-greater-principal-in-just-4-years/)
- ["Is there something as growing too quickly?"](https://www.jointaro.com/question/o9oyCcIjWT4Xa6w1Eau5/is-there-something-as-growing-too-quickly/)

When Should You Switch Teams Or Companies? - Daniel Tomko's Perspective

Daniel Tomko spent much longer at the companies in his career compared to most engineers: 11 years at Microsoft and 8 years at Meta. Within these companies, Daniel did various team changes.

- Switching companies has a higher "transaction cost" compared to switching teams.
- At a large enough company, you have tons of interesting technical challenges and people to work with.

Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)

Other relevant resources: 
- [How to approach a team switch conversation with my manager?](https://www.jointaro.com/question/XFQqRINGf9JvW3xmnVHa/whats-the-best-way-to-approach-a-team-switching-conversation-with-my-manager/)
- [How To Figure Out If A Team Is Important To A Company](https://www.jointaro.com/lesson/9OwPRwFFSMvEoVj6Zt5Q/how-to-figure-out-if-a-team-is-important-to-a-company/)
- [How To Find A Good Team With Career Growth Opportunities](https://www.jointaro.com/lesson/UGIUC9zaGccK0tOarBri/how-to-find-a-good-team-with-career-growth-opportunities/)
- [What's it like working on an ads team?](https://www.jointaro.com/question/GCCIkaBVUpPxGCF4MjRL/what-is-it-like-working-on-ads-teams/)

Hi all, recently during Q1 roadmapping I chose to move on to a new workstream from a growth/independence point of view as part of working my way up to E4. (My earlier effort was a 1-&gt;100, this one is 0-&gt;1 and was decided by me, my TL and EM together), and I had a couple of questions about this move. 

1. I have spent the past 6 months gaining context on a set of technologies and tools (internal to Meta) that perhaps only 2 other engineers on the team have context on. 
   1. Should I do a knowledge transfer session or write up a doc to ensure all the context I have doesn't get lost? 
   2. Should I allocate some time to supporting the team until I'm here on areas I gained context on? 
2. There is some possibility of scope thrash since I'm also long-term supporting one of the projects part of the earlier workstream (I delivered the v0 and have been making iterative but small changes since then). Should I talk to my manager about this? 
3. This is a very n00bish question: from a growth perspective, is it better to go 110% on the new workstream and all its nuances/open problems or go 80 and 20? As far as allocations go, I'm slated to be 100% on the new workstream as part of the roadmap. 
4. Bonus question: should I do a year-in-review/look-back post in tandem with my self review? (This is a very Meta-specific question in a way, but would love to hear other views too!)

Use Code Review Feedback For Hypergrowth - Meta Prodigy Engineer Story

As a junior software engineer, one of the main ways you're going to grow is through feedback on your code review. Because of this, it's vital that you get the maximum value from code review feedback.

Here are the core points from the video:
- **Respect quickly and with appreciation** - Be thankful of good code review feedback, and try to respond to code review comments within 1 to 4 hours. Don't be defensive when it comes to code review feedback.
- **Don't make the same mistake twice** - Take the time to really understand and absorb the feedback: Don't just make the suggested change. If you don't understand the principles behind some feedback on your code, just ask! [Here's our in-depth advice on how to really not forget code review feedback](https://link.jointaro.com/7wjo6DcDcJmxDVYB9).
- **Alex's mentee prodigy story** - Alex had a Meta mentee who was able to grow from junior [E3] to senior [E5] in just 2 years. A big part of this was their incredible code velocity:
  - This mentee really nailed learning from code review feedback. Their initial commits were a bit messy, but they quickly got to a point where they stopped making mistakes.
  - They were also very meticulous about their pull request quality. They always had very thorough summaries alongside very complete test plans. For more complicated commits, they would have up to 5 videos walking through every case.
  - After 1 half, this engineer was writing almost 500 commits a half, making them the #1 code committer in the entire organization. This was largely because their stellar code quality and code review learning allowed them to land their pull requests on the very first try 90%+ of the time.

This highlight is from our masterclass on "How To Write Better Code Faster As A Software Engineer". [Click here to watch it.](https://link.jointaro.com/v6zEgUfQTxoSj33Z7)

Related resources:
- [Quick Tips To Get Higher Quality Code Reviews Faster](https://link.jointaro.com/dE4U41RAVtZKLhxJ7)
- [Avoid These Junior Engineer Mistakes With Code Review](https://link.jointaro.com/agkYrLH8uuCv4UcPA)
- [Code Review MUST Be Fast, Otherwise The Team Is Unhealthy](https://link.jointaro.com/oxK55E1bkX8nMeNGA)

As an E5, I'm switching to more of a tech lead role, and one of the engineers I'm leading has had consistently poor code quality despite being at Meta for a few years now.

I've asked my manager for feedback about this, and they say that we should come up with a plan to improve the situation. I've already invested time in this, and I'm not seeing results. How can I get the code quality feedback to fully land and improve this engineer's code?

I'm having trouble getting code quality feedback to land with an engineer I'm leading - What can I do here?

I've grown to be more of a "tech lead"-style E5, which leads to a lot of time spent roadmapping and talking to people instead of actually executing on the project and being more hands-on. My team is heavier on the E3/E4 side, so I'm able to delegate a lot of the coding work away. I was wondering if this was normal for Meta and whether this is an okay way to operate as an E5?

How normal is it to be mostly hands-off as a senior engineer?

The setup on my team is pretty standard: There's an E6 tech lead that has broken up a big project into multiple pieces, and I own one of those pieces (and the rest of the pieces are owned by other E5s). I'm leading a couple engineers (<5), and I think they're E3/E4.

Zooming out, this seems like decent E5 scope, but I'm sure there's some gaps to turn it into E6 scope. The tricky part is that my org is pretty XFN heavy, so it's hard to get things added to the roadmap, and with the hiring freeze, it's hard to get more engineers onto my team to lead.

All that being said, what are some ways I can find staff scope in this situation?

Session #3 - Becoming A Tech Lead Again In Just 1 Month After Joining Robinhood From Meta

[Here's the presentation slides](https://docs.google.com/presentation/d/1j5Lj_IGrtCRUpobj0f8k9egrBAej9apzikGp_V_iTCk/edit?usp=sharing).

- The expectations for an L5+ (senior+ at a FAANG or similar company) engineer are high. You won't get 12 months or even 6 months to fully onboard: You need to start having huge impact and showing your depth within 1-2 months.
- After starting, Alex told his managers that he was happy to offload any responsibilities they had so they could focus on higher-level issues and expand their scope. As a tech lead, you need to view your manager as a partner, not just a boss. "Treat me as a resource."
- The project that Alex was first put on was to make settings more server-driven within Robinhood
- The most impactful thing to do was to add color to the project:
  - Stabilize and then drive the workstream meetings
  - Create a thorough tech spec
  - Align XFN to figure out how to treat each settings section properly, especially in places where there were inconsistencies
- How Alex added his depth:
  - Wrote a 5+ page Android spec for his portion
  - Manually audited all of settings and compiled a detailed spreadsheet of inconsistencies to fully capture impact
  - Thorough data analysis spec, doing complicated SQL queries himself
  - Mentored an L4 engineer in the process, giving them L5 scope
- Recap (how you can incorporate the learnings here into your work):
  - Earn trust quickly: Be "aggressively" nice. Find out how you can add value to others and be very sincere and upfront about it.
  - Fill in the gaps: View your projects holistically and figure out what's missing to move the project forward. This will often times be "less flashy" non-coding work.
  - Bring people together: Don't be paralyzed by your lack of knowledge. Especially if you're new to a company, you will be clueless in a lot of scenarios. If you're in a cutting edge company like Meta/Robinhood, there will be a smart person(s) somewhere out there with the answer: You just need to bring them together in a healthy way.
  - Go deep: There's far more to a senior engineer than their ability to code. If you're a new L5+ engineer, even the tenured L3/L4s at the company will code circles around you in the beginning. If you're an L5+ engineer, figure out what behaviors and fundamentals you have that more junior engineers don't and show those as much as you can. This generally involves shipping software in a much more holistic way.

Hi everyone, I have about 0 experience with machine learning and I'm thinking of ways to significantly increase my value in the future. My ideal plan is to get promoted to E5 in &lt; 1 year and then change domains to ML (or ML Infra and work closely with ML engineers). I have almost 0 experience with ML directly, but I think they make much more money in the long run? I'm currently a backend software engineer.

   Basically I want to know if it's worth investing my time & effort this or if it would be better to just eventually go for engineering management in the domain that I am already familiar with.

Is it worth transitioning to become a Machine Learning Engineer?

Session #7 - Building XFN Alignment Across Multiple Orgs (w/ Staff Engineer Cat Chen)

[Cat Chen](https://catchen.me/) talked about his success building alignment across multiple orgs. 

Cat was working at Facebook as a Staff Engineer on the growth team. His charter to get the Android apps on app stores beyond the Play Store. (There were 10+ non-Google stores where Android apps get downloaded with some level of traffic.

Getting an app listed on a 3rd-party platform is simple – sign up as a developer on that platform; upload the Android app for review; wait for approval and launch it. Just as simple as publishing to Google Play.

**BUT it's not that simple at a company like Facebook.** Facebook lawyers wouldn’t allow Cat to accept the Terms of Service on behalf of Facebook the company. Cat didn’t have the privilege to bind Facebook into this contract and even if he did, the lawyers would certainly advise against that.

Instead of simply handing this problem to another person or org, Cat met with a director-level lawyer. Given he was on a different time zone, and in a different job function altogether, this took some legwork. The director explained the risk profile (Facebook could have unlimited downside by blindly accepting an agreement). Eventually Cat discovered a workable solution by using a contracting company to sign the legal agreement, which limits the damages that Facebook may face.

Impact of this work: 
- Successful launch of the existing Android apps
- Ability to launch other apps in the future
- Deep and positive relationship with the legal team, and Cat owned that relationship (which made him indispensable)
- **Almost zero lines of code written!**

[Connect with Cat](https://www.linkedin.com/in/catchen/)

For more resources on how to communicate, build alignment, and operate as a Staff Engineer:
- ["How do I sell the vision behind a large, org-level project?"](https://link.jointaro.com/NGCrB2ifkkpDaDe69)
- ["What's the Difference Between A Senior And Staff Engineer?"](https://link.jointaro.com/BEM2RAjPFe8Pv7826)
- [Guide to Effective Communication](https://link.jointaro.com/mP3WEd4zt5ecnupX6)

I recently got moved to a new manager, and I've been having some trouble building back up the more fluid and quite positive relationship I had with my prior manager. In particular, I'm trying to get more signal into my feedback and how I can improve. When I go over this kind of content with my new manager, they'll say something more quick and high-level like "That makes sense", but they won't give me something more specific and concrete. How can I go deeper with these kinds of conversations while keeping our relationship healthy? I want to make sure I respect their boundaries.

How can I get my manager to dig more into the "awkward" stuff in 1 on 1s?

Hi,

With tons of layoffs already happening and rumors about impending layoffs, is there something one can do to protect themselves? Logically, performing above expectations and being a critical part of the team would make sense. However, recently looking at LinkedIn and other career news, seems like no one can be sure that they’re safe. So, do you have any tips on how to approach this? Does it make sense to stay put within a team where you have great relationship with your manager and skip etc or find a new company to get ahead of this risk? Thanks!

Are layoffs random or can I do something to prevent getting laid off?

My manager changed in H2, and my previous manager became my skip. While my current manager has a decent idea on the current projects I am working on and their importance, sometimes I see them mixing up specifics, which could be because they’re still ramping up. With that context, how do I make sure my manager represents my year long performance in upcoming calibrations well? Should I give them context on all my work in our 1:1s, especially my H1 work as they weren’t in my team?

Managing up my performance review with my new manager?

I'm a new MLE at Meta, so I'm in bootcamp. I'm trying to go for a team that’s super in-depth with regards to ML and neural architectures vs. a team that would give me more breadth. How can I find such a team and what questions can I ask to identify it?

How to find a team with specialized technical depth?

I'm a new engineer at Meta, and my goal is to find a team with a real product future. Because of that, I'm wondering if there's ways to evaluate if a certain project is going to pick up traction. How can I figure out during the team selection process if a team is doing its due diligence on gathering context and proving out business value before building features or if its just building them for the sake of building them?

I'm new to Meta, so I'm currently in team selection. My goal is to choose a team that maintains more critical pieces and are more stable with respect to layoffs/reorganizations vs. (slightly) more moonshotty teams with higher risk/reward. An example of the latter would be a team working on maintaining an ads pipeline while one for the former would be a team experimenting with new UI features.

How can I find a team that meets that bill, and what questions can I ask to help identify this?

How can I find a team that's more on the stable side?

I've been on my current team for around a half, working primarily on the back-end. Unfortunately, I discovered *after* I joined the team that Android work is very interesting to me, so in order to pursue this, I would need to switch teams. There is actually a team fairly close to mine in my org where there's compelling Android work.

Right now, I'm heads down on a big project, so my immediate instinct is to wait until that's done to bring up this conversation with my manager, who I have a very good relationship with. Is this the right thing to do or should I have this conversation sooner rather than later?

What's the best way to approach a team switching conversation with my manager?

I'm considering a team switch, but I'm wary of the effect that it will have on my E3 -> E4 promotion timeline, which I know we have to do within 2 years. I've been at Meta for around a half - Does the timing for a switch work out here and what other factors should I consider?

How should I factor team switching into the E3 -> E4 promotion timeline?

I've been on ~5 teams during my ~4 years at Meta, and I'm wondering if I need a mindset shift when it comes to choosing a team and staying there. Is it more on Meta that teams don't fit or should I make a bigger effort to stay on teams longer and establish myself there? I'm also looking to get to E6 someday, so the team switching makes things tricky.

I've been on a lot of teams and wondering if I'm thinking about teams correctly.

I joined Meta very recently, so I'm in bootcamp. However, the company just announced a mass hiring freeze, so teams aren't taking in bootcampers at all effectively (there are very few exceptions). It's not clear when this freeze will end. Teams are still giving bootcampers tasks as they understand that we're pretty much "free" labor.

This is such a weird situation, and I feel like I'm spinning my wheels. I like Meta as a company a lot, but I'm unsure how to make the best of this situation. Any advice?

Some additional questions:
1. What do you look for in the team?
2. Do you tell your manager?

What's the best way to think about a team switch?

[Part 1] Meta Intern Success Series - Internship Program Overview

- The Meta SWE internship program is very legit. It resembles the experience of working as a full-time Meta engineer as closely as possible, complete with calibrations and a formal manager.
- The program is also hard. The pass rates that got mentioned around the company were 50 to 75%. It's one of the harder internships to get a return offer from as the goal is to perform at E3 MA. If this is your 1st internship or you have only interned at companies weaker than Meta prior, the high bar can be overwhelming.
- However, the reward is tremendous. Meta is an incredible company to work at and amazing as a career starter. Meta is also one of the highest paying companies for the entry-level band (E3), and the signing bonus for return offer interns is sky-high (60k to 100k).
- 4 outcomes for Meta SWE interns:
  - No offer: As mentioned before, many interns will unfortunately be here. The numbers after this correspond to the percentage of the "surviving" pool.
  - MA (70%): "Meets All Expectations", which is a regular return offer. The vast majority of successful interns get this. 
  - EE (25%): "Exceeds Expectations", which is given to very strong interns.
  - Rockstar (5%): For interns that completely crush it and are very close to functioning as a mid-level engineer (E4).
- Internship schedule (assuming standard 12 week length):
  - Weeks 1-3: Onboarding
  - Weeks 5-6: Mid-cycle review
  - Weeks 10-11: Final calibrations (return offer is decided here)
  - Weeks 11-12: Relax and have fun. Only your performance from Weeks 1 - 10 is counted towards your final review
- As an intern, you formally report to an intern manager (IM), which is shown on the org chart. On top of the IM, you will have 1-3 other peers who will review your diffs and help you. During calibrations, feedback from your IM and these peers will determine your final rating.

For more expert internship advice: [Full SWE Intern Advice Playlist](https://www.jointaro.com/tagname/Software%20Engineering%20Intern/)

The product I support breaks often and I've been the go to individual to resolve internal fires. Addressing them takes time away from tackling more impactful tasks, and it's beginning to affect my output. My team doesn't find such infra issues as priorities so fixing them gets little visibility and I'm concerned this will have a negative impact on my PSC. How do I balance this properly?

How do I balance addressing fires and working on p0's?

One thing I'd love to ask about is effective pressure management. Coming from small cos to a big company like Meta; despite startups having a reputation for chaos, I personally find there's  a larger number of failure modes at big companies - a review taking too long, lack of good logging, misalignment, which can lead to either a project being derailed or just flat out failing. I've personally gotten better myself at pressure management (trial by fire); but would love to have thoughts from folks on how they work on this skill!

How does one effectively handle pressure especially when the stakes are high?

I work overtime a lot, and it's pretty stressful. I'm also worried that amidst all this effort working for Meta, I'll lose track of who I am overall and what I can do for other companies. What can I do to strike a better balance here?

How can I have less burnout and better work-life balance?

I'm in bootcamp right now, and many teams are telling me that they have all 3 of these things. My bootcamp mentor says that's not really feasible - There are trade-offs. Am I gullible if I believe these teams at face value?

Is it possible for a team to have great WLB, availability of scope, and impact?

Session #5 - Mentoring Junior SWEs [E3] to Senior [E5] In Just 2.5 Years At Meta

For the key points, you can find them in the slides (linked below), so the summary will be framed more as action items.

**If You're Pushing For Senior/Are Senior+ Already**
- Mentorship is a core part of healthy senior engineer behavior, so invest in it if you aren't already.
- Now you need to find good mentees. *The main thing to look for is their coachability, which largely depends on how smoothly they process feedback*.
- How can you tell if someone is coachable?
  - They go the extra mile making sure their code is clean.
  - They respond to code review comments (particularly yours) with enthusiasm and speed. They're hungry to learn more and go deeper into feedback on their code.
  - They go out of their way to help others as opposed to many people who just help reactively (or not at all).
  - They have a good cadence with you when you spend time with them (e.g. it's easy to have a fun conversation with them over lunch).

**If You're Mentoring Other Engineers**
- *If the extent of your mentorship is that you answer a lot of your mentee's question, you're not truly a mentor.*
  - True mentorship is being proactive and having a clear vision for what your mentee will become. Create a growth plan for them to get to the next level and outline deltas to make it clear.
- If you haven't already make sure that your manager and the manager of your mentee (if they're on a separate team) are aware of your involvement. This is vital for getting proper credit and not growing them incorrectly.
- Your mentality should be that you serve your mentee, not the other way around.
- To build a ton of trust quickly, tell your mentee this: *"No matter what happens, I'll do whatever extra work is necessary to make sure that you're okay."* You are majorly responsible for your mentee's well-being.
- Always call out when your mentee does good work, even if it's something small like a well-written commit. Do it in your 1:1 where it has more gravity. Showing appreciation as a trust/morale building technique is *severely* underutilized.

**If You're A Mentee Looking For A Mentor**
- Show strong gratitude for code review comments on your commits. Don't just give them a thumbs up or worse, silently make the change. For deeper feedback (often times coming from senior engineers who you want to mentor you), go the extra mile giving thanks.
- Put yourself out there: Don't be a hermit. Go to team lunch, offsites, coworking - Become known as a friendly face within your team. Strike up conversations with engineers more senior than you just to get to know them.
- Strive to write good code. It can scary as a junior engineer in particular and default to churning out tickets as fast as possible with bare minimum quality; avoid that instinct and try to spend an extra 30 minutes to 1 hour trying to build things out properly (and then talk about your thought process on your pull requests). You want to show senior+ engineers that your hunger to be an actually good software engineer instead of a commodity coder is there.

Related Resources:
- [Presentation Slides](https://docs.google.com/presentation/d/12OelIHF08oBZwe-TzVlz8fqp4WiOTem_e9KsGe7X8XA/edit?usp=sharing)
- [Meta E4 To E5 Growth Plan (Pretty Applicable To Any Large Company)](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/articles%2Fmeta_e4_to_e5_growth_plan.pdf?alt=media&token=e13d88fd-9356-4c20-a229-cf0cad78a9af)
- [How To Get The Most Out Of Mentorship](https://link.jointaro.com/sobZVTxh3nvUFTnb9)

I'm trying to get promoted to E5, and my progress so far has been decent. I'm doing well on all 4 axes, but I currently have a gap on the people axis (it's not Exceeds Expectations yet). I know that people/direction are very important for E5s, so I really want to get better here. I do things like give tech talks and mentor some rotational engineers, but it doesn't seem to be enough for an E5-level people contribution. What can I do to shore up this aspect of my performance?

How can I strengthen my people axis to push for E5?

I am a little worried about the potential of layoffs at Meta. I am not sure if I will get a needs support. I have been working on doing a design doc for the past month, and my manager has generally been very positive towards me. But I feel like I might get a NS due to my not submitting as many diffs and accepting as many diffs. I joined my team less than three months ago, and still technically ramping up. I would be sad if I got a NS or a pip, but it wouldn't destroy me.I guess my question would be how can I best buffer myself during these next few months, and how can I avoid situations like this in the future? What should I do if I do get put on PIP/NS?

Hi,

I got promoted last half to IC5 and have been leading impactful work streams within our team. I am enjoying my new role and work. In our last 1:1, my manager asked if I wanted to lead a very high priority org level initiative that has impact across multiple teams and suggested this could be a potential staff level project. While this is a great and unique opportunity for promotion, I am also nervous about taking this up because:

1. I am scared this might be more challenging than I am ready for and failing this would put our Org's key launches in risk.
2. I just got promoted and didn't want to actively pursue promotion as I wanted some time to settle in and become a solid IC5 first.

Wanted to get your thoughts on this and what you would do in my position? And if I say no, should I be worried about my manager passing me up for potential opportunities in the future? Thanks!

Is there something as growing too quickly?

My team got split up recently, and I got put onto a sub-team I'm less familiar with (I have more context and experience with the other sub-teams formed in this re-org). Any thoughts on how I can make a case to be on one of the teams I feel like is a better fit for me, and if I'm not able to do that, how do I make the most of this new situation?

Ended up on a less preferred team after a small re-org - How to navigate this?

Like a lot of E5s, I'm working on a piece of my team's overall project roadmap, which is set by an E6 TL. The piece I own is less technically complex than other parts, but it is quite XFN heavy (great for people/direction contribution). I was wondering if this is still enough to get to E6 or do I need the higher technical complexity as well?

Is it okay to have less technical complexity when growing to staff?

I'm a product generalist at Meta and I've been offered to opportunity to ramp up to Android and possibly specialize in Android dev. What are the considerations I should be thinking about when 'switching tracks' like this. E.g. will this reset my progress towards promotion as a prodgen or will it enhance my skillset for future opportunities?

I've been working mostly as a Backend Engineer. 
I'm growing interest in ML. I have a few questions:

- Will my SWE knowledge help me, or will it complement with ML? Or being MLE is a totally different/separate field?
- Is there overlapping between ML and SW?
- Would be recommended to do a Masters or Practice/Courses?

Software Engineer interested in ML - How would a transition work?

I joined my team in June this year right after bootcamp. When I joined this team, we set the goals for the half, and then got reorg-ed to a different domain (think ML for ads vs ML for recommendations).

Our models had only shown limited success in the previous domain before the reorg, we spent around 2 months (July and August) just building new versions of these models for the new domain. 

It's October already, the model hasn't shown any significant success in any of our projects with XFN. We are getting closer and closer as we understand the problems better. However with code freeze in November, December - it is unlikely it will reach production or even online experiments by then.

Does that mean I would have "no impact" at my first PSC? This would be the case for all of my teammates which seems bonkers.

I thought about writing a long note with all of the progress we've made in understanding the problem (which will result in a model that's cheaper than the current one and easier to understand), what are some results we have seen already, and hypothesis on where to go next. 

Still to be honest I'm scared the results I got won't be good enough to get to production by PSC-time, and thus I'll be marked as no impact. In retrospective I should have studied the problem more when I joined but I was so new to Meta. 

How can I mitigate this? Looking for a side-project now I can fully own (as E5, I don't think attaching myself to a teammate's project is good enough) is unlikely to get any results with the current model we have.

For example, knowing that we got EE- in people axis meaning that it's on lower end of EE.

In PSC, will we know ratings for each axis?

I joined Meta as an E4. I'm coming from a company which doesn’t have as much structure around performance review. 

I feel good about my coding ability and project impact, but I’m not entirely sure what are the ways to think about the people dimension as someone relatively new.

I just joined Meta as an E4 engineer. What are the ways I can succeed in the people axis?

I joined Meta as an E5, and now I'm looking to get to E6. I want to stay on the IC track, so my goal is concretely to get to E6 and stay there, not become an M1. I know that leadership is crucial for EMs, but is it the same for staff engineers at Meta? I'm currently leading <5 engineers who are probably E3/E4, and I'm wondering if I need to expand my leadership scope there.

Is the amount of engineers you lead relevant to get to E6?

Meta is my first large tech company, so I don't know much about the other big players (Amazon, Google, etc). I was curious as to what makes Meta unique compared to other giant tech companies, so I could get a better understanding of the industry overall.

How does Meta's culture differ from that of other Big Tech companies?

As a self-taught developer, I don't have a systematic knowledge base as those who were trained by college degrees or bootcamps. How can I built up a knowledge system as a Software Engineer over work?

For example, after I get a bird-eye understand of the industry, I can fit the pieces that I'm dealing with at work into this system and build up my knowledge with a more systematical way. Can I get some suggestions/approaches for this, or get to know your experience building your own knowledge system?

For self-taught developers - How to build my own knowledge system during work?

Hey all, as you know there’s high probability of cost cutting and lay offs by increasing bar at meta.
I joined the company 2 months ago and plan to travel to another country(12 hour time difference) and work remotely for about 20 days! (Whole month of December)

In lieu of new information, should I be trying to stay in the same time zone and be seen around meetings(my team is fully remote)? It will probably also help my productivity.

I’ve already booked tickets and I’m not sure what to do.

I'm relatively new to the company, so I would love to understand more about this. Here's more specific questions I had:
1. How is the first one evaluated? Is it different because you're new?
2. Is it evaluated from the day you joined the company or the day you joined a team out of bootcamp?
3. How is delayed impact factored in? Since I'm new, I'll have some small wins by PSC time but am not likely to have big ones as they're waiting to launch/realize impact.

5 Offers w/ FAANG Companies As A New Grad: Details + Lessons

In 2014, Rahul graduated from Stanford with a BS and MS in Computer Science. He received new grad Software Engineer offers from 5 companies: 
1. Facebook
2. Twitter
3. Microsoft
4. Google
5. Square

This video outlines the exact details of the offers, and models out the increase (or decrease) in value of those offers 8 years later, in 2022. The total compensation of the offers range from $174K/year to $262K/year, and those numbers go a lot higher if you factor in stock appreciation.

If you want to better understand how compensation works in top tech companies, first watch [this video](https://link.jointaro.com/819tdsqwJj4VnaEC6).

I'm looking to get promoted to E4 in the next cycle, but I'm worried as my impact contribution isn't very clear. I've done a lot of work, but due to churn within my org (which includes a recent re-org), a good amount of my code isn't truly in production yet. I've documented my work in Quips and tasks to show that I did it, but I'm wondering if a lack of shipped impact will hold back my PSC.

How does a lack of impact due to org churn affect impact axis in PSC?

I'm pushing for the E4 promotion in the next PSC cycle, and I've gotten some feedback that I could shore up my people axis contribution. Given that, I was wondering how important people is for this promo and how I can get points on this axis as a growing E3. People axis contribution seems harder given the hiring freezes (e.g. it's harder to be a bootcamp mentor) and the fact that the main intern season is over.

How important is people axis for E3 -> E4 promo?

As we all know, Big Tech hiring is drastically slowing down, which includes Meta. However, this means people axis sources like interviewing and being a bootcamp mentor become harder to get.

I'm also fairly new to the company, so it's harder for me to do things like mentor and onboard others for people axis credit.

All that being said, how does people axis work for me and how can I get a good rating there?

How does people axis work with a hiring freeze and being new?

I'm a new E4, so I obviously have promotion on my mind. I have a good amount of experience coming into Meta (~5 YOE), so I want to move more aggressively with this promotion. If I work 40-45 hours per work with very good work ethic, what's a reasonable target to hit for the E5 promo?

What's a good trajectory to go from E4 to E5?

I work on a pretty planning intensive team. Sometimes we'll spend several weeks planning out our next project, but since planning takes so long, not much time is left for execution after we're done planning. This leads to us having to sprint to deliver, and after we go that, we go back to planning and the cycle starts all over again. This is all pretty hectic, so I was wondering if anybody had any ideas on how to improve this process?

How to deal with weird development cycles?

When I started in bootcamp, my bootcamp mentor assigned me a couple tasks to do. How important are these tasks? Do I need to get them done with a certain speed and quality? Are you judged on them in any way?

How much do the initial tasks you get in bootcamp matter?

I'm a new E3, and I know that there's the up-or-out promotion timeline to E4. I was wondering how much of a challenge this level-up generally is and what are the main things to keep in mind with this promo?

In my effort to grow my scope as an engineer (and get promoted), I’ve constantly hit the same weak spot - not “working through others” enough.

I’m always happy to identify problems and solve them, but as a relatively inexperienced engineer compared to the rest of my team, I feel uncomfortable pushing work onto others, as I often am not sure my ideas will even be fruitful.

This issue is exacerbated by the fact that my team skews very senior and I don’t feel comfortable/qualified working through them.

How should I approach this problem?

I'm a senior engineer on a team that's mostly E5+. How can I work through others?

I just started at Meta in the business engineering org (formerly solutions eng). We have a lot of XFN work with sales and SWE teams, so lots of opportunity to coordinate projects and be customer-focused. I was a SWE at my past company but I'm hoping to eventually transition to PM as I believe it is better for upward mobility within a company?

How can an engineer transition to product manager and do you think there is higher potential to reach VP level at PM?

It seems to me that Meta has SWEs drive a lot of product decisions but I've always heard Product is better for high growth and the famous examples of Sundar and Satya

Is Meta more engineering driven or product driven and how does this affect internal mobility for EM vs PM?

I was curious if anyone had tips on writing a decent one page resume - especially in how to pick apart what's most "important" from my previous work experiences and fit it into one page.

Hi guys, I’ve recently joined a new team and learning a new coding language. The first task given to me by my team was a refactoring task to ramp up. They said to take your time as there’s no rush to finish it right now. However, it seems to be a very complicated refactor as there’s multiple lambda functions each referencing variables from all over the place. How do I communicate this with the team and not look incompetent?

Struggling with an underscoped refactoring task - What to do?

I have worked at Meta my entire career (~5 years). I know that Meta is pretty "startup-ey" among the Big Tech companies, but I imagine that it can't mimic startups entirely and there's unique learning value startups can offer. Does switching to startups give big value to career development?

What's the difference between Big Tech and startups in terms of learning and growth?

Comparing Meta to other companies, splitting between a PM and an engineer is very awkward. PMs end up doing a lot of strategy work, but when it comes to what tactics you pick, it seems like engineers have to pick there.

My PM is very senior at PM6 and their guidance is extremely high-level to the point where the concrete projects we need to work on aren't entirely clear. How do I fill in these details, so I know what to work on?

How can I fill in for concrete product strategy when the direction coming from my very senior PM is more high-level?

I'm pushing for E6, and I'm having trouble doing this in my current org. I'm considering an org switch, and I want to make sure I don't end up in a similar situation - How can I properly evaluate an org for availability of scope and mentorship?

How do I determine whether finding scope and working through others is easier on my team or on another?

At my old company, where I worked for many, many years, I wasn’t learning anything new. On my new team, I feel like a junior engineer since everything is new. Because of this, I don’t feel like I’m being taken seriously, even my engineers more junior than me.

I'm trying to stay positive throughout this learning process but would obviously like to build up respect among my team as quickly as possible to start feeling like a heavily valued voice in the room. Any advice on how to do that?

How can I quickly gain respect among my team as a senior engineer?

I'm in the initial stages of a job hunt right now and recruiters seem to have the perception that I'm more qualified than I actually am (especially at non-FAANG companies). I'm E4 at Meta (mid-level) and not performing exceptionally well at this level, but recruiters are trying to push me for 'Senior' roles. Should I just go along or push back?

I know this is a bit of an unorthodox question since most people have problems with downleveling, not the other way around. I'm somewhat confident of passing the coding/systems design rounds for Senior/E5 positions at these companies, but I really want to avoid a situation where I join and immediately start getting overwhelmed by the actual job responsibilities.

Context: ~2.5 YoE

Recruiters keep trying to up-level me. Should I push back?

For my current project, I have 2 broad options for the infra/platform to support the feature:
1. Using a proven technology that has existing use cases within Meta but a somewhat limited API
2. Using a new technology that's not completely done yet and has uncertainty, but should have better APIs and performance

There's also the option of trying to do both, benchmarking them against one another, and then choosing the better one. However, I don't think we'll have the time to do that.

All this being said, any thoughts on which technology to go with?

How do I choose between 2 technical approaches for my project?

I'm a new staff engineer at Meta, and I know that the bar is high for E6. In particular, an E6 needs to be able to have a large influence on the roadmap and team charter, leading and creating very substantial projects.

All that being said, I want to start crafting and executing that vision as soon as I can to hit the ground running, but I'm unsure on exactly how to do that with Meta's more bottoms-up culture. At my previous job, things were more top-down (i.e. leading *with* authority, where software engineers work on things because their manager/leadership tells them to). How do I lead the team with this almost opposite engineering culture?

I've heard from my peers at Meta that you should post a lot on Workplace, otherwise it can reflect badly on your PSC. Is this true or more of a myth?

Is posting on Workplace required for good performance?

In particular, is the number of "comments" on the question correct after creating a question?

**this is cool**

## this is a header to really emphasize the point

I'd love to understand the backend of Taro

Before I was at Meta, I worked at a networking company for 10+ years. It was very different from Meta as a massive consumer web company. On top of the domain differences, the culture is also very different between these 2 companies.

I'm working on ML at Meta, which is something I'm pretty new to. As a senior engineer who wants to make an impact quickly and make a push for staff, how can I effectively make this domain switch to hit the ground running fast?

What’s the most effective way to switch domains in tech?

I had a feedback session with my manager, and they gave me feedback that I was doing well overall but they would like to see me become more familiar with Meta's experimentation tools. They mentioned that this wasn't bad feedback as this unfamiliarity is expected with relatively new Meta engineers like myself. That being said, I'm unsure how to process it: Should I process it urgently and if so, how do I become familiar with Meta's gigantic experimentation infrastructure?

I got feedback about experimenting, and I'm unsure how to process it.

I'm relatively new to Meta, so I'm having trouble processing things in meetings as they happen, making them a substantial waste of time for me overall. I don't want to seem dumb, so I would to avoid asking a bunch of questions during meetings to make people explain what they just said. What can I do to make meetings more productive for me?

It's hard processing what happens in meetings - How can I be more effective?

I'm a mid-level engineer who's struggling with some performance issues at work. A staff engineer on my team has taken notice and has been very generous with offering help and advice, to the extent of basically handholding me through my projects. While I truly appreciate the help, I'm wondering if this will be seen as a negative signal during performance evaluation since I'm supposed to be operating 'independently' at this level.

Is excessive help from senior engineers good?

I've been at Meta for a while and have thought about outside opportunities. I feel like it can be frustrating getting things done at Meta a lot of the time - Too many processes and people to align to ship projects. I want to work somewhere where I can just write code and ship cool products. Any thoughts on next steps for someone who's been at Big Tech for a while?

I recently joined Meta, and I'm aware of "up-or-out". However, I would like to more deeply understand how it works and have a better mental map of the entire thing in general.

How long do Meta SWEs overall take to go from E3 to E4 and then E4 to E5?

How does up-or-out work and what's the transition generally like for E3 -> E4 -> E5?

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?

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

There's so many teams to choose from - It can be overwhelming. However, in a company as large as Meta, I'm sure there's huge variance among teams. How can I find one that works for me, particularly when it comes to find E5 scope for promotion?

In bootcamp right now - Any thoughts on good orgs to join?

In particular, I'm having trouble figuring out really complex bugs. For example, on my current project, we're auditing a lot of the existing feature set to see what issues they have so we can fix them as we revamp them. I'm happy to find lots of issues, but I have no idea how to fix them, even after finding a code pointer.

I talked with a senior engineer on my team for help, and they were able to get more color on the situation. However, they mainly were able to do this as they have been in the org for a while and knew who to go to for what: I can't replicate that deep knowledge they have as I'm fairly new to the company. How can I create a systemic process I can follow to figure out these situations?

How can I become more independent and better at unblocking myself with tricky technical issues?

How Alex Got Into Meta With 0 Prior Leetcode Experience

It's hard to figure out what's going on right now; there's just a lot being said like that some Meta employees "don't belong here", it's time to "turn up the heat", and "low performers" need to be weeded out (I would have thought this was already the case at Meta?).

At the end of the day, I just want to figure out what this means when it comes to employee performance and PSC in particular. I've heard from some managers and engineers that the ratings will be upshifted (e.g. you need old EE to get MA), but I've talked to my manager and they said that this won't happen. But if that's the case, how will the performance review system change?

Any tips on what concretely could be happening and what we can do here to adjust to these changes?

Related articles:
- [Zuck "turns up the heat"](https://fortune.com/2022/07/01/facebook-warns-staff-not-expect-big-budgets-new-hires-be-prepared-to-work-harder/)
- [EMs instructed to push out low performers](https://www.wsj.com/articles/meta-managers-are-urged-to-identify-push-out-low-performers-11657576630)

Zuck is "turning up the heat" for employee performance. Unsure what this means and what I should do.

I was working with a team during bootcamp, and they mentioned that they intentionally have very low test coverage (both unit and integration). This team is more on the back-end side. Is this a bad sign or is there something specific about Meta's culture that I'm missing here?

Is it a red flag if a team doesn't have tests?

I work on the privacy side, so our core projects are often held up by XFN. This leads to me having to find something to do in the meantime, which often means smaller, ad-hoc efforts. However, I've been told that working on larger projects across a lengthier time horizon is better for promotion. What can I do during these blocked times that also shows good execution signal for promotion?

What can I do if my projects are blocked?

I've shared feedback before with engineers more junior than me, and they didn't seem to take it well. They started avoiding our meetings afterwards - I feel like they thought their PSC was at risk. How can I prevent this situation from happening in the future when sharing feedback with E3s/E4s?

As an E5, I will have 1:1 meetings with E4s on the team to lead/mentor them. However, I find myself running out of time in the meetings sometimes - What can I do to make effective use of all the time?

How to make effective use of 1 on 1s with E4s?

Meta Platforms, Inc. is an American multinational technology conglomerate based in Menlo Park, California. The company owns Facebook, Instagram, and WhatsApp, among other products and services.

Mid-Level Software Engineer [E4]

First, I recommend [this discussion from another Meta SWE interested in transitioning to ML](https://link.jointaro.com/jzRN3atwUXWUr3uE8).

While it's true that MLEs tend to get paid more than other SWEs (I recently found out that Google pays 25%+ more for MLEs compared to SWEs), my advice largely remains the same for these switching scenarios: **Take it up if you're genuinely passionate about it**.

To me, it seems like your primary motivation is compensation. While money is important, I feel like most engineers I know who hyper-optimized for compensation had slower career growth than those who treated it as more of a secondary motivation/lagging indicator, which I talk about more [in this video here](https://link.jointaro.com/b2NF1H1AkWmFQaAh8).

If money is the main reason you want to do ML, I wouldn't switch into it, even if you have some interest for it (not super relevant if it's the secondary motivation). There's 2 other factors in play:

- **If you like back-end dev** - If this is true, I definitely think you shouldn't switch.
- **If you're planning to stay at Meta/Big Tech** - Given the scale of these companies, they tend to reward depth, so it's usually better to double down on something you already like and are good at (one of the E6 archetypes is literally "Specialist"). While MLE will pay more in a vacuum, the gains will probably be cancelled out by the hard pivot, especially if you're not genuinely super interested in ML.

Robinhood, Meta, Course Hero, PayPal

Alex Chiou

This link was super helpful, thanks Alex! (<https://www.jointaro.com/question/6ZaGA1FUTL1OaPlQOkan/software-engineer-interested-in-ml-how-would-a-transition-work/>)

I'm honestly not sure whether I would enjoy ML, does anyone have any recommendations on how to start on machine learning side projects?

I found [this article about machine learning side projects](https://www.simplilearn.com/machine-learning-projects-for-beginners-article), which seems decent.

To make the side project more sharable, I'm thinking you could make some sort of API or utility tool that uses ML underneath.

In terms of what to build with side projects, I highly recommend looking for inspiration among your interests and day-to-day life: That's when the most effective side projects arise. When it comes to ML/AI for me, a good example is [Deep Leffen Bot](https://twitter.com/deepleffen). For context, I'm a big follower of competitive Smash Brothers Melee. These engineers trained a bot on the thousands of tweets of a prominent Melee pro and has its auto-generated tweets shared to that Twitter account (which is absolutely hilarious).

[Here's the masterclass I gave around coming up with a great side project idea](https://link.jointaro.com/zGVSSuo3u7K3Apzx9) where you will actually follow through.

If you're fairly close to getting the E5 promo, I like your plan to first secure the E5 promo. That effectively becomes a *floor* for future roles, effectively guaranteeing your seniority.

I wonder if you could de-risk some of the move to MLE by: 

- doing a coffee chat with existing MLEs at Meta to understand their day to day (and also ask them about opportunities at other companies)
- do some sort of side project in MLE. This is harder since a side project will likely not be representative of the work you'd do at a large company like Meta. 

I broadly agree that ML in general will become more and more lucrative, and there will be more opportunities in the coming years. However, you want to ensure that you'll have staying power. You can likely get a short term comp bump by switching into it at Meta, and then leveraging the "Meta AI engineer" brand for a great offer elsewhere. 

But the massive comp bumps will come from understanding the AI landscape, upcoming trends/companies, and having opinions about them. Could you develop that now as a way to ensure you'd be happy with the transition?

Meta, Pinterest, Kosei

Rahul Pandey

In addition to the other answers, I'd add the following notes:

Every team is different. Being an MLE in a research oriented/R&D team will involve implementing and productionizing algorithms, often directly from papers. Being an MLE in an AI inference or edge team will involve a lot of low level code and optimization. Being an MLE in a core ads team might involve a lot of testing, experimentation, and statistics to help evolve a complex system. (In fact, testing/experimentation is probably the most useful skill you can pick up if you're trying to go into an ML role at Meta!) As Rahul mentioned, sitting with an MLE is a great way to find out what their day-to-day life is like. I would also poke around their diffs, public posts, authored docs etc. to see even more specifics about what individuals are doing.

But I wouldn't let that discourage you from *learning* ML or trying side projects for fun. Give it some sort of time box window - like a month - to hack on something you find meaningful. Afterwards, identify the parts of it you enjoyed doing, and the parts you didn't. (For me, the parts I enjoyed were always designing the model architecture + seeing the optimization process happen in my notebook. The parts I hated were always data cleaning :) If there's enough of it that you *did* enjoy, then it's probably a good bet.

Also, it's worth mentioning that being in eng management for both an ML team and an SWE team will become more and more similar the higher you go - less about the specific technical decisions, and more and more about people, process, and culture management overall. I don't know about compensation at higher levels, but I don't think it's so different that it should really be a huge decision factor in the long term. However, MLE at Meta is good in that you are potentially more layoff proof, and can work on some high priority projects like ranking/recommendation.

Senior Software Engineer [E5]

- You can think about roles on a spectrum -\
  ML Researcher -&gt; Applied Scientist -&gt; ML Engineer -&gt; ML Infrastructure Engineer\
  You go in decreasing of ML knowledge and increasing order of software skills. So one consideration would be thinking about where you want to land ultimately.
- Most ML infrastructure overlaps a lot with a typical backend role. So you would face the same set of challenges more often than not. At the same time, there will be a lot of new ML design patterns - distillation, multi-stage models, etc. But you can easily pick them up with basic ML background. So I would say the transition is possible if you are interested, as Alex said before.
- It would be a good idea to start as an ML Infrastructure engineer and if you like the modeling parts of it, look to contribute towards that in a project working with MLEs. First, consider the problems that interest you - recommendation, ads ranking/auctions, graphs, natural language processing, computer vision, etc. Then talk with teams in those areas and see if there is a match.

I hope this helps :)

PayPal

Mid-Level Software Engineer

Being a good manager is hard enough already - It's even tougher for engineering. Learn more about this complex craft and how you can land a stellar engineering manager yourself.

Mid-level engineers have very strong technical proficiency, able to execute on small to medium-sized projects with minimal hand-holding, leveling up from junior engineers.

The clearest way a company can acknowledge your growth. At the end of the day, you can't solely interview your way to a principal engineer; promotion is the true foundation of your pay and career.

Is it worth transitioning to become a Machine Learning Engineer?

Meta

Discussion

Meta