Efficiency Tips for Engineers (From An AI Researcher/Stanford PhD/Ex-Meta Engineer)

[**Mo Tiwari**](https://www.linkedin.com/in/motiwari/) is an AI researcher, Stanford PhD, Facebook Software Engineer, DRW finance quant, and Caltech Math + Physics major 😳 🤯

The secret to his prodigious career: **ruthless efficiency**. Mo is able to achieve more per unit time than most of his peers.

This talk covers both behaviors and tactics to improve your ability to get things done. Sample topics:

- How and when to process email to minimize disruption.
- Best practices for calendar invites and scheduling
- Keyboard shortcuts that Mo uses dozens of times/day to save time

Download the slides here: <https://drive.google.com/file/d/1HET2AgDGeXA7Guhfq0IjaU53wY5AlsOE/view?usp=sharing>

Connect with Mo on LinkedIn: <https://www.linkedin.com/in/motiwari/>

Take the productivity course: [\[Course\] Maximize Your Productivity As A Software Engineer](https://www.jointaro.com/course/maximize-your-productivity-as-a-software-engineer/)

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?

[Case Study] 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:
- [[Case Study] Effective Communication: Leading A Multi-Org Re-architecture At Meta](https://www.jointaro.com/lesson/Rovw6IfITXGr55NdftFw/case-study-effective-communication-leading-a-multi-org-re-architecture-at-meta/)
- [What's the Difference Between A Senior And Staff Engineer?](https://www.jointaro.com/lesson/FzvHLUprcYonudsxnJc2/whats-the-difference-between-a-senior-and-staff-engineer/)
- ["I would like to get more clarity on what a Staff-level project and execution look like."](https://www.jointaro.com/question/RQa5tsnXnZr6Xg1ziv0X/i-would-like-to-get-more-clarity-on-what-a-staff-level-project-and-execution-look-like/)

Mid-Level Software Engineer at Taro Community

Is sprint planning and agile not a thing at meta? I’m doing a lot of research since I’m trying to see how it’s like as I’m spending time leetcoding and if the vibes there are it’s on you to plan your projects and set a timeline then sprint planning would actually make the engineers not excel in independent planning?

And it seems like it’s against good e4 performance to be prompted to set your deliverables at the end of the sprint? Just not sure how agile is used cuz if it’s on everyone to figure out how to project manage on their own then what’s the point of agile?

Is sprint planning and agile not a thing at Meta?

Become An Open Source Master [Part 1] - Course + James Intro

This course is a methodical guide to get you involved in open source. The course is led by James Pearce, a former engineering director at Meta. While mastery might be a lifelong journey, we'll cover the basics to get started.

- Gain insights from James's experience running one of the world's largest open source programs.
- The course will focus on individual involvement in open source (not running a program).
- Meta/Facebook has a strong open-source culture, using and creating software like React, Cassandra, and PyTorch. Here's the talk James gave at OSCON 2015: <https://www.youtube.com/watch?v=vBbDAk5WYEo>
- James has built his own open-source project called [tinybase](https://github.com/tinyplex/tinybase), a data store for local-first apps. Watch this course so you can contribute!

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

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 (these are the old PERF ratings):
  - 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/). Learn how to [avoid or manage a PIP from our course](https://www.jointaro.com/course/the-ultimate-performance-improvement-plan-pip-guide/).

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/)

Nail Your Promotion As A Software Engineer [Part 1] - How This Course Works

Switching jobs is great, but it can only get you so far. *The true foundation of any ultra-successful tech career is promotion.* However, promotion gets a bad reputation as it's sorely misunderstood, both by individual engineers and entire tech companies. This course is here to demystify promotion and teach you how to go through it as efficiently as possible. Here are the core parts of the lesson:

- Your instructor [Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) walks you through his extensive 10+ year Silicon Valley background with rapid career advancement, ending up as a high-performing tech lead making $750k at Robinhood. More importantly, he goes through how he was able to grow his mentees to lightning fast promotions, particularly at Meta where he grew new-grads (E3) to high-performing senior engineers (E5) with \~$500k TC by their mid-20s (far faster than Alex himself!).
- You'll understand why promotion is underrated and critically important to a successful tech career with serious longevity. You'll also understand why constantly going on the interview grind is way worse than pursuing organic promotions when possible.
- We walk you through the course objectives. By the end of the course, you will understand:
  - 💡 How promotion **actually works**, particularly at top companies
  - 🧠 The framework to understand the **senior engineering career ladder**
  - 📃 How to define a **clear plan** to get to the next level
  - ✅ What it takes to get **maximum credit** for every project
  - 🚀 What it means to master your performance review and produce the **best promo packet**

If you want to learn how Alex was able to grow his mentee engineers ⚡ fast (more than 2x quicker than industry average), check out his deep-dive here: [\[Case Study\] Mentoring Junior SWEs \[E3\] to Senior \[E5\] In Just 2.5 Years At Meta](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/case-study-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/)

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?

The Journey to Staff Engineer In Big Tech (Panel Discussion) - Sep 2023

The journey to Staff Engineer is unique for everybody. In this session, we talk about all the ways we got there! Senior Engineer is a terminal level at most tech companies.

Staff Engineer is the next level up. This is referred to as Staff at Meta/Google, or Principal Engineer at Amazon/Microsoft.

Themes discussed in the video:

- Staff Engineers need to have multiplicative impact and influence across multiple teams. There are several ways to achieve this (occasionally referred to as archetypes): code machine, architect, product thinking, fixer, and more.
- Communication, and right-sizing it to the level and discipline of your audience, is critically important.
- Being able to speak to real, quantifiable numbers when it comes to the impact you have is essential.
- Staff engineers are typically known as the experts in certain domains or situations. Becoming well-known in an area is a skill and does require some amount of marketing.

See discussions about Staff Engineers on Taro: <https://www.jointaro.com/topic/staff-engineer/>

Publicly available promotion stories:

- [Ryan's Instagram video processing improvements](https://engineering.fb.com/2022/11/04/video-engineering/instagram-video-processing-encoding-reduction/)
- [Rahul's internal tool for debugging](https://www.jointaro.com/lesson/qvp2quodqAEWSkN7sayt/case-study-building-a-meta-internal-tool-to-empower-an-entire-org-staff-promotion-story/)

Panelists:

- [Zach Wilson](https://www.linkedin.com/in/eczachly/)
- [Rahul Pandey](https://www.linkedin.com/in/rpandey1234/)
- [Carly Taylor](https://www.linkedin.com/in/carly-taylor-data/)
- [Lee McKeeman](https://www.linkedin.com/in/lmckeeman/)
- [Ryan Peterman](https://www.linkedin.com/in/ryanlpeterman/)

Watch the [Q&A portion of the panel here.](https://www.jointaro.com/lesson/P7bEwvDaCuYRfEtmfcaL/the-journey-to-staff-engineer-in-big-tech-qanda/)

Watch the full [Senior to Staff course on Taro](https://www.jointaro.com/lesson/NE3J4vWP7BoWlNgbRtCw/becoming-a-staff-engineer-in-big-tech-panel-discussion/).

Entry-Level Software Engineer [E3] at Meta

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?

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?

[Case Study] Becoming A Tech Lead Again In Just 1 Month After Joining Robinhood From Meta

- 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.

Related resources:
- [Presentation slides](https://docs.google.com/presentation/d/1j5Lj_IGrtCRUpobj0f8k9egrBAej9apzikGp_V_iTCk/edit?usp=sharing)

Nail Your Promotion As A Software Engineer [Part 3] - The Key To Understanding Promotion

We're told our entire lives that the key to success is to work hard. While this is admittedly true for most professions, it's very much not the case when it comes to software where you need to work *smart* in order to get anything done, especially for promotion. This lesson teaches you:

- The key insight behind understanding what promotion truly means, especially at top companies
- Why you can't get promoted by just working longer hours and writing more code, especially at very senior levels
- A framework to understand what separates incredibly senior (L6+) engineers from the more junior ones
- What it means to think multiplicatively instead of individually, including an in-depth example

Excited about developing better product intuition after watching this lesson? Check this out: ["How to develop product sense as an engineer?"](https://www.jointaro.com/question/w84sxyM805YOCokfvuQ8/how-to-develop-product-sense-as-an-engineer/)

Engineer Your Ideal Tech Career [Part 11] - Michael Novati: Becoming A High-Level IC

Next, [Michael Novati](https://www.linkedin.com/in/michaelnovati) chats about his impressive career advancement and passion for high-level IC work. Michael progressed from a new grad engineer to Staff engineer at Facebook within 3 years, and then Senior Staff after.

He reflects on the key steps he took to progress quickly, common misconceptions people have about being a high-level IC, and the types of people who may love this work longer-term.

Looking for mentorship from tech’s top engineers + personalized job hunt assistance and interview prep? [Formation.dev](http://Formation.dev) can provide you unlimited career coaching, technical mentorship, personalized practice, and mock interviews. Join us here: <https://formation.dev/partners/taro>

Worksheet: [Formation - Coding Your Career](https://tinyurl.com/formationworksheet)

Senior Software Engineer at Taro Community

I've had 5+ friends leave Meta or quit software engineering altogether after E6. Either the responsibilities and stress were too much or what they were being asked to work on wasn't really aligned with their core interests. Business needs are always changing, so it can be a common occurrence to take a lot of ownership over a project you don't have personal interest in.

It's important to be adaptable, but I think intrinsic motivation can be hard to sustain if the people, project, or priorities are in flux.

For the older crowd, what really typifies career longevity in a software engineering?

[Case Study] 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)

Growing To Meta Tech Lead And Then Entrepreneurship - By Jocelin Ho

If you use WhatsApp web, level up your experience with the Cooby (the company Jocelin is cofounder and CTO of) plug-in: [Cooby: Best WhatsApp Extension for Work](https://chrome.google.com/webstore/detail/cooby-best-whatsapp-exten/hcikfoejbgdmajlbhadhfchoekcoablm)

To level up your software engineering knowledge, follow Jocelin on LinkedIn: [Jocelin Ho - LinkedIn](https://www.linkedin.com/in/jocelinho/)

Jocelin's presentation is **filled** with gems (including a fun video by Mark Zuckerberg), so we're just going to share her core learnings here:
1. **You need to be versatile to survive** - One of the biggest misconceptions about software engineering is that it's mostly about writing code: This couldn't be further from the truth. In order to be a genuinely stellar engineer, you need to have a vast array of skills on top of coding like communication, the ability to smoothly process feedback, multi-tasking, and much more. Jocelin excelled at developing these skills, which is why she was able to get promoted from E3 -> E4 at Meta (junior -> mid-level) in just 6 months, faster than 95% of FAANG engineers.
2. **Don't get emotionally attached to what you built** - Tech is always fast-moving and chaotic, and this is accentuated when you work at a top company like Meta. Organizational priorities change all the time, and this can mean that your hard work gets thrown out. Don't take it personally and continue striving to deliver impact and grow.
3. **Don't be afraid to take the leap** - You will literally never be ready for that big career or life change, whether it's taking your first FAANG interview, switching to management, or starting your own company. Once you have conviction in knowing what you want to do, make that jump and focus on growing and adapting as fast as possible. It's not about where you are now but rather where you can go in the future.
4. **Live up to your own expectations instead of others'** - While we should always try to add value to other people's lives and help one another, this doesn't mean we should derive our happiness from what they believe we should be. You own your own happiness - Set goals that are both feasible and exciting for you and ignore all the noise. This is especially relevant in tech where there's so many brilliant people, and it's tempting to compare yourself to others.

Related resources:
- ["What's the core insight behind quick growth?"](https://www.jointaro.com/question/nJ762p255cGyuth36H6w/whats-the-core-insight-behind-quick-growth/)
- [[Taro Top 10] Junior Engineer To Mid-Level Engineer (L3 To L4)](https://www.jointaro.com/playlist/iBKHYpkjd0BRWWLKQG2j/)
- [Presentation slides](https://docs.google.com/presentation/d/1BkaaiKQXXx6eUi5heaNiNmPgBriK9rr5UdTfHfd2K5k/edit?usp=sharing)

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 have a recruiter screening with Meta next week for a full-stack software engineer role. What can I expect in the recruiter screening?

This is my first interview after a very long time, I need to brush up my skills. what is latest acceptable time frame to schedule the technical interviews without being considered late?

Become An Open Source Master [Part 2] - How This Course Works

We'll explore the benefits of open source and how to contribute to existing projects in this course.

- Understand the benefits of open source and the mindset needed to work effectively in the open source ecosystem
- Learn how to get involved in someone else's project, understand their codebase, and make meaningful contributions
- Explore how contributing to open source can benefit your career by showcasing your skills and building your professional profile.
- This course won't cover how to create your own open source project or what it's like to work on one from within a company.

Connect with James: 

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

An Autistic Journey To Google Staff Engineer [L6] From Software Analyst - By Lee McKeeman

[Lee McKeeman](https://www.linkedin.com/in/lmckeeman/) is an autistic software engineer with quite an incredible journey: Across a whopping ~20 years of experience, Lee has worked at Amazon (where he was an engineering manager and bar raiser), Meta, and now Google.

Lee's career story is super long (watch the video to get the full picture), so instead, we're sharing some of the great learnings from Lee here:
- **School doesn't actually teach you software** - University is generally rooted in theory and overly abstract exercises, leaving you with a very basic raw coding foundation. While that certainly has value, it's not enough to make you capable of doing actual software engineering, especially in a team environment.
- **Debugging is a critical skill** - Lee started off as a software analyst, which was a role that was much more focused on diving deep and fixing issues as opposed to churning out new features. The experience Lee got here was extremely valuable and continued paying dividends across his career, even after he transitioned to SWE.
- **Help others and keep an open mind** - Everyone works in different ways and will be comfortable/uncomfortable in situations that don't match that of others. This includes the neurodivergent population like autistic people, those with ADHD, and more. Be a true teammate by being understanding and accepting of these differences. Assume good intent, and if you aren't sure how you can best support a teammate, just ask them!

To learn more from Lee, you should 100% connect with him on LinkedIn where he writes some of the best posts (and comments) on the entire platform: [Lee's LinkedIn](https://www.linkedin.com/in/lmckeeman/)

Here's some of the incredible wisdom Lee has shared on Taro:
- ["What does it mean to not require handholding anymore?"](https://www.jointaro.com/question/5vEWajcZlSi7nlohTGtJ/what-does-it-mean-to-not-require-handholding-anymore/)
- ["How to Balance Responsibilities: Prioritizing Personal Work vs. 'Glue Work' in a New Team Environment."](https://www.jointaro.com/question/9NL4LP40xHy5sgGMvsmB/how-to-balance-responsibilities-prioritizing-personal-work-vs-glue-work-in-a-new-team-environment/)
- ["Can someone elaborate on "always treating feedback as a gift"?"](https://www.jointaro.com/question/4DoEnMIq2ISadfAJuwp9/can-someone-elaborate-on-always-treating-feedback-as-a-gift/)
- ["What do career levels structure in big tech company look like? What are the responsibilities for each level?"](https://www.jointaro.com/question/qV5oikdcgs4GWmGeousX/what-do-career-levels-structure-in-big-tech-company-look-like-what-are-the-responsibilities-for-each-level/)

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?

I have been in the team matching process with Meta for the last 3 weeks. I have talked to 4 teams and 2 of them did not proceed futher. The other 2 teams are something I would rank in the top of the 4 but I am not completely satisfied with the role at these teams. How long do you think is it good to slow down the team matching for so as to explore other team matching calls? Or would it be a bad move as I can miss out the current available opportunities?

If I go ahead with any of the teams that don't completely align with my interests, how easy is it to switch internally after I join a team?

How to navigate through team matching with Meta?

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:
- **Respond 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)

Negotiation Course: Rahul's History And Success With Negotiation

Rahul's compensation went from $110K at the beginning of his career to $830K in his peak earning year, 2021, as a Tech Lead and Manager at Meta (Facebook). That's more than 7x! A lot of his Total Compensation (TC) growth can be attributed to his ability to negotiate. There were 2 main segments of negotiation in Rahul's career: 

- 2013: 5 offers at Facebook, Google, Twitter, Microsoft, and Square
- 2017: 6 offers at Facebook, Google, Snapchat, Stripe, Uber, and Airbnb

This gave Rahul the leverage he needed to see dramatic increases in compensation. Some examples: 

- The Snapchat stock grant went from $600K --&gt; $1.0MM and the signing bonus went from $10K --&gt; $100K
- The Facebook stock grant went from $325K --&gt; $600K and the signing bonus went from $30K --&gt; $45K

The numbers here are due primarily to timing, information, and options, all things you can learn. The results can be life-changing, and you don't need to be a genius programmer to discover your own version of this.

These data points show how negotiation is extremely high leverage. A few hours of extra work can lead to a change of 6 figures or more in compensation.

- Rahul's YouTube video about 5 offers he received as a new grad: <https://youtu.be/rceUVaiXQgU> 
- Rahul's YouTube video about how compensation in tech works: <https://youtu.be/wqdpzu4Oa2I>

I've received a verbal offer from Meta for the Android role and I'm in a team matching phase right now. I've a couple questions:

- My recruiter mentioned that team matching is taking a lot of time these days and suggested me to take a team that's available and later could think of changing the team. What should I do here wait for the right team or take a team that's hiring right now?
- Does anyone have any recommendations for teams at Meta which are layoff proof, has interesting and promising projects coming up and a good mobile engineering foundation?

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

- The Meta software engineer 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 software engineer internships to get a return offer from as the goal is to perform at E3 MA. If this is your first software engineer 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 software engineer 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 software engineer 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 a software engineer 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/topic/software-engineering-intern/)

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?

Mid-Level Software Engineer at Series A Startup

I'm moving forward to team matching at Meta for E4 and wanted to ask the community if they had any suggestions for teams with the strongest potential for growth, especially for the New York office.

The recruiter gave me the following survey. I stated I'd be more of a "Product - Generalist" role. Would also be curious to learn more about "Systems - Generalist" as I did the System Design interview as well. \
\
In general from what I've seen, there's a decent amount of opportunity in Instagram, Whatsapp, and Reality Labs (from product announcements and earnings calls). I've also been told to avoid monetization as it's difficult to make an impact there.\
\
Would appreciate any advice or suggestions! Also would appreciate tips on what questions to ask Hiring Managers to assess how they grow E4s.

**What is your role? (select the one that applies)**

- Systems - Generalist
- Product - Generalist

**What type of work motivates you the most? (select all that apply)**

- **Infra**: Scaling challenges
- **UX**: Building user experiences
- **Growth**: Top of line impact
- **Integrity**: Ensuring platform safety
- **Social Impact**: Progressing positive change on key social issues

**Who do you want to build products for? (select all that apply)**

- **Consumers:** External, individual users of the Meta family of apps
- **Businesses:** External business account users of Meta family of products
- **Meta Employees:** Users of internal tools
- **Developers:** Internal and external engineers using Meta developer products and APIs

**Please select which Meta Pillar(s) you’d be interested in joining? (select all that apply)**

- **Family of Apps:** Enable optimized enforcement and support of account integrity to foster safe and meaningful communities.
- **Monetization:** Empower people and businesses to succeed in the global economy
- **Gen AI:** bring the transformative potential of generative AI to people and businesses
- **Reality Labs:** build tools that help people feel connected anytime, anywhere

**How would you rank your preference in terms of products?** **(feel free to use numbers)**

- Facebook App
- Monetization
- Privacy
- Messenger
- Instagram
- WhatsApp
- Reality Labs (AR/VR)

Meta / Facebook Team Matching - How to find the best team? (E4)

I'm learning it's important not just to do good work but also to make your work visible to your team and sometimes wider circle. This is common feedback given to junior engineers at Meta. What are some ways to get more visibility on my work and what are some rules of thumb (e.g. structure of posts, cadence of posts, when to share progress in team meetings)?

[Case Study] Revamping Oncall For 20 Instagram Engineers - Senior to Staff Project

Oncall is a critical process for any good engineering team, especially larger ones. However, a lot of software engineers aren't truly exposed to oncall until several years into their career. This detailed case study covers what a healthy oncall looks like and how ex-Instagram tech lead Alex led his organization towards that.

This session covered a *lot* of ground, so we'll focus more on the learnings instead of the historical story:
- **Good oncall ingredients**
  - Very strong sense of ownership expected from the current oncall - The buck should stop with them
  - A detailed runbook and thorough documentation in general around SLAs, SEV criteria, and ownership
  - 7 to 12 engineers on the rotation so you're only oncall <15% of the time
  - A retrospective process that brings together the team to share knowledge and figure out how to improve their systems as a whole
- **Pain = Opportunity** - Never say *"That's just the way it is"*: Every problem is solvable. If you want to level up fast, strive to alleviate pain at scale for your team instead of running away from it. Here's a great discussion covering this concept in more detail: ["Ways to add value when asked “What do you think would be biggest challenges for next quarter?"](https://www.jointaro.com/question/zYbkS5Bn00H9RGKiiL4F/ways-to-add-value-when-asked-what-do-you-think-would-be-biggest-challenges-for-next-quarter/)
- **It's All About Relationships** - This is especially important at senior and staff engineering levels. In order to change process and push big projects, you need to get many people to agree with you. Understand that these relationships take time to grow and you need to start as early as possible. Check out this masterclass to deep-dive into this: [[Masterclass] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)
- **Understand Everyone's Incentives** - They will be very different for people who aren't on your team or aren't engineers. As a tech lead, you are expected to work across XFN boundaries regularly, and succeeding at this requires understanding what drives everyone and finding mutual interests.
- **Lead By Example** - Put yourself on the line and practice what you preach. A disconnect between what you're recommending and your own actions is one of the easiest ways to sabotage your own influence.
- **Stand On The Shoulders Of Giants** - At Big Tech companies in particular, there will always be hundreds of other engineers in the company who have already solved the problem you are currently working on. There is no need to reinvent the wheel - Seek out those people and learn from them.

Related resources:
- ["How to form a healthy on-call rotation?"](https://www.jointaro.com/question/8OuTidxuVaeuQCV28IhD/how-to-form-a-healthy-on-call-rotation/)
- ["How can I improve the unstructured, chaotic oncall rotation I'm on?"](https://www.jointaro.com/question/ScxFpybXXC90qmnLEU7A/how-can-i-improve-the-unstructured-chaotic-oncall-rotation-im-on/)
- ["How can I maintain work-life balance with a hectic oncall?"](https://www.jointaro.com/question/WLqDVZQa8rAEmFEl15oA/how-can-i-maintain-work-life-balance-with-a-hectic-oncall/)
- [Presentation slides](https://docs.google.com/presentation/d/19PpKY5VoRAP8OMhu2shwhLthKiodw5cUruk6Lycelho/edit?usp=sharing)

Hi All, 

Would love to get some advice on how to ask ***highly pointed*** questions during a 30 minute conversation with a hiring manager to get the maximum info out of him regarding the team culture and the product.

Regarding my preferences...

I would love to stick fully on the Backend stack. I have experience working with Python, NodeJS, Typescript and a bit of Java, I have experience working with Infra and databases as well. I get excited working with data at scale but do not have stellar industry experience with it such that I can start being impactful on day 1. 

Since this will be my first time at a big tech, I want to optimize for a decent to moderate enough ramp up time, good wlb and not being super heavy with oncall at least for my first team. 

Once I get used to the pace, I'll jump around to start optimizing for impact, visibility and scope. 

Here is what I have in mind for my Hiring Manager meetings but feel free to add/subtract from this.

1. Basics, what is the product/org
2. What is the team size and team structure (how many E5s, E4s etc) and tech stack.
3. What is the code velocity like on average for an E5.
4. Give me a brief idea about what the first project you have in mind for me, if not tell me about a project an E5 is currently working on.

[E5] What questions can I ask hiring managers at Meta during the team matching phase?

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 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?

How Alex Got Into Meta With 0 Prior LeetCode Experience

[Case Study] How To Land 18 FAANG+ Offers With Steven Zhang (Airtable, USDR, Tableau)

While on the job hunt in 2019, Steven Zhang received 18 offers (out of 22 onsites), including from companies such as Airbnb, Apple, Facebook, Palantir Technologies, Pinterest, Stripe, Uber.

In the process, he became an expert in software engineering interviews and job searching. Steven shared his thought process and methodology:

- When you have many interviews, **operationalize it, and treat it like a multi-week/month project**. Some days will feel like a slog, but that's ok and part of the process. (Steven used Airtable to coordinate all his conversations.)
- **Doing an interview prep course is completely worth it for DSA**. It may cost a few thousand dollars, but being able to land the ideal job is definitely worth it (and likely worth tens of thousands of $$). Steven used InterviewKickstart (his referral: https://bit.ly/swe-tips-ik).
- **For behavioral interviews**, Steven recommends:
  - Writing all questions you received in a Google doc
  - Recording yourself doing mock interviews with a friend and then listening to it.
- **Steven received offers at various levels through the bands**, from L3 (junior) to L5 (senior). Your level has huge implications for your compensation.
- Negotiation tips:
  - Negotiation should not be adversarial- think of it as doing price discovery
  - If you ask nicely, no one will rescind your offer for asking for more money.
  - Negotiation/post team matching is a way to get signal on the company itself

Relevant resources:

- [\[Masterclass\] How To Ace Your Big Tech Interview - Data Structures And Algorithms](https://www.jointaro.com/lesson/V4sTACzfOh22nMVcUV3w/masterclass-how-to-ace-your-big-tech-interview-data-structures-and-algorithms/)
- [\[Masterclass\] How To Ace Your Big Tech Interview - System Design](https://www.jointaro.com/lesson/J3I9fTW9ulr6T9KjxpqY/masterclass-how-to-ace-your-big-tech-interview-system-design/)
- [How Alex Got Into Meta With 0 Prior LeetCode Experience](https://www.jointaro.com/lesson/ZYiTbN21FsqFxFdpwt5a/how-alex-got-into-meta-with-0-prior-leetcode-experience/)
- Steven's [viral Medium article about this experience](https://medium.com/@stevenzhang/how-i-landed-18-faang-software-engineer-offers-after-not-interviewing-for-5-years-fc0dfc957a5d).
- Connect with [Steven on LinkedIn](https://www.linkedin.com/in/stevenqzhang/)

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?

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?

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?

Meta announced that they won’t be giving return offers to interns this summer amidst economic headwinds, which is really demoralizing. 

Other companies are also putting a hold on hiring junior engineers – what should I do?

Meta is rescinding intern offers. How can I succeed now that I can't convert to full-time?

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?

Hi community,

I am a recently joined M/L engineer at Meta and working in ads domain. I am stuck for last few weeks in verifying a change. Essentially, it involves multiple systems built, request routing and looking for the expected changes. Tried reaching out to T/Ls and internal users. Even politely asked team / outside to ramp me up in the domain but nobody responded positively. They all give me pointers to some internal documentation or workplace group to ask questions. I feel I am really stuck. I have regular updates meeting on Monday.

Here's 2 things about how the updates work:

1. I am making some progress everyday but things are moving very slow which is making me frustrated.
2. When sharing updates, everybody shares the impact and good followups where I only share one incremental step like looked at the logging, traffic is low so can't determine the magnitude of the change.

Anyone willing to share their experiences?

What to do if you get stuck in understanding the existing codebase?

Level Up Your Code Quality As A Software Engineer [Part 8] - Case Study: Instagram vs. Robinhood

Trying to nail down what good code looks like is equivalent to trying to staple jello to a wall. Almost every software engineer looks up to FAANG and FAANG-adjacent companies, and that's what this lesson will cover in-depth with an example. This lesson will teach you:

- The engineering philosophy behind Instagram's Android codebase, its unique attributes, and its priorities
- The engineering philosophy behind Robinhood's Android codebase, its unique attributes, and its priorities
- Why taking Instagram Android code and pasting it into Robinhood would have been terrible despite it being industry-leading in its own context (and vice-versa)

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 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?

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?

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?

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?

Staff Engineer (Head of AI/ML) at Pre-Series-A No-Code AI

Hi! I got a call from a Meta recruiter a few weeks ago, and I scheduled my phone screen for this coming week. However, my Practice Screening Interview did not go very well and uncovered certain gaps in my preparation.

Should I tell my Meta recruiter that I am not prepared enough for my actual screening interview next week and ask for a postponement? Or should I just go ahead with my interview and potentially squander a good opportunity?

In hindsight, I think I should have only scheduled the interview after (a) having done a decent amount of preparation, and (b) having assessed myself through some mock interviews. That's certainly a learning for the future, but I am not sure how I should navigate the current situation I am in.

Any advice, suggestions are most welcome. Thanks!

Senior Staff Engineer (L7) Describes Most Important Skill - Rahul Malik

Rahul is a Senior Staff Engineer at Meta.

- **Most important skill**: dealing with ambiguity and working through others. Senior Staff Engineers operate in a broad space, so they have to be independent enough to make impact without a specific problem.
- **Advice**: figure out how decisions are made. Who makes the decisions, and what is the underlying value system?

Here's the full playlist asking engineers what the most important skill is for their level: [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/J9Io5lDGaYUpI8vGrUyI/)

Helpful links:
- [SWE2 --> Principal Eng in 4 years](https://www.jointaro.com/lesson/Lvf1TDKt1R4ZJSCr9BVv/rockstar-software-engineer-story-sw2-greater-principal-in-just-4-years/)
- Taro's top 10 to get promoted from [senior to staff engineer](https://www.jointaro.com/playlist/YD8LMCSlE71VUGUbNAWM/)
- [David Pan on what makes a great tech lead](https://www.jointaro.com/lesson/uHqZZ15SK19MatEvLSO6/what-makes-a-truly-great-tech-lead-a-vp-of-engineerings-perspective/)
- [Rahul on LinkedIn](https://www.linkedin.com/in/rahulbmalik/)

Meta Case Study - Debugging A Massive Production Issue

Here we go through an example bug at Meta. Given the information, we need to figure out what kind of root cause is behind the issue. This case study shows:
- Why it's important to understand the blast radius of a bug
- How knowing the context behind a bug can help you locate the problem area
- The value of having robust analytics

This video is a clip from our debugging masterclass. You can watch it here: [[Masterclass] How To Become A Debugging Master And Fix Issues Faster](https://www.jointaro.com/lesson/ioR6WzamAIUTpySLAr7o/masterclass-how-to-become-a-debugging-master-and-fix-issues-faster/)

Related resources:
- [[Case Study] Solving A Multi-Million $$ Instagram Bug](https://www.jointaro.com/lesson/WYk4J05iBqOuPtD0CYKX/case-study-solving-a-multi-million-dollardollar-instagram-bug/)
- ["How can I become more independent and better at unblocking myself with tricky technical issues?"](https://www.jointaro.com/question/QhqQQGrDgFjZbqohpKe0/how-can-i-become-more-independent-and-better-at-unblocking-myself-with-tricky-technical-issues/)
- ["What is the effective way to understand new repository in order to make the required changes in that repo?"](https://www.jointaro.com/question/KoxB3UU2zWC9pdYU6Rx0/what-is-the-effective-way-to-understand-new-repository-in-order-to-make-the-required-changes-in-that-repo/)

[Case Study] Building An App With 1,000,000+ Users To Get Into Facebook

If you want to hear an in-depth \~30 minute breakdown of Alex's entire journey getting the Facebook offer, watch our video here: [How Alex Got Into Meta With 0 Prior LeetCode Experience](https://www.jointaro.com/lesson/ZYiTbN21FsqFxFdpwt5a/how-alex-got-into-meta-with-0-prior-leetcode-experience/)

To learn more about how to build effective side projects, check out these resources:
- [[Masterclass] How To Come Up With 100k+ Users App Ideas You Can Build For Free](https://www.jointaro.com/lesson/AI4zi759PSGn6RwIFT6f/masterclass-how-to-come-up-with-100k-users-app-ideas-you-can-build-for-free/)
- [[Masterclass] How To Build And Grow Tech Products To 500k+ Users For Free](https://www.jointaro.com/lesson/OEuX0KMhcnNSTJ50Voee/masterclass-how-to-build-and-grow-tech-products-to-500k-users-for-free/)
- ["How Long to Crank Out a Decent Side Project?"](https://www.jointaro.com/question/QA6lCGdPpwAd3xRrpjZ7/how-long-to-crank-out-a-decent-side-project/)
- [How Alex Made An App That Got 80k+ Users In 1 Month](https://www.jointaro.com/lesson/GlSjjLhuUdHt5drq3l5F/how-alex-made-an-app-that-got-80k-users-in-1-month/)
- [Presentation slides](https://docs.google.com/presentation/d/1MJU_LPnfc_QEu7386eSFvIbopG2VVUE3lTzkA458bYU/edit?usp=sharing)

If you want to dive deeper into the Random Name Picker app:
- [Download it on Google Play](https://play.google.com/store/apps/details?id=com.randomappsinc.studentpicker)
- [GitHub Source Code](https://github.com/Gear61/Random-Name-Picker)

The Journey to Staff Engineer In Big Tech - Q&A

This is the Q&A portion of the Staff Engineer Panel discussion. Watch the [main content here](https://www.jointaro.com/lesson/SaYyJGLYvrAy4XGrDhy7/the-journey-to-staff-engineer-in-big-tech-panel-discussion/).

The journey to Staff Engineer is unique for everybody. In this session, we talk about all the ways we got there! Senior Engineer is a terminal level at most tech companies. 

Staff Engineer is the next level up. This is referred to as Staff at Meta/Google, or Principal Engineer at Amazon/Microsoft. 

Questions answered in the video: 
- I'm making a career change into Software Engineering -- what advice would you have? I want to get into Augmented/Virtual Reality.
- I'm already a Staff Engineer, but I'm struggling with performance management. What advice would you have to exceed expectations?
- What resources would you recommend to improve at communication? What is an effective way to find a mentor?
- I'd like to first become a Tech Lead (TL) and then transition into a Staff Engineer role. What advice would you have for me?
- I'm a Data Engineer (DE) and big fan of Zach! How do I show the impact of my work to a manager who may be unfamiliar, especially since I don't do frontend?

See discussions about Staff Engineers on Taro: [https://www.jointaro.com/topic/staff-engineer/](https://www.jointaro.com/topic/staff-engineer/)

Publicly available promotion stories:
- [Ryan's Instagram video processing improvements](https://engineering.fb.com/2022/11/04/video-engineering/instagram-video-processing-encoding-reduction/)
- [Rahul's internal tool for debugging](https://www.jointaro.com/lesson/qvp2quodqAEWSkN7sayt/case-study-building-a-meta-internal-tool-to-empower-an-entire-org-staff-promotion-story/)

Panelists:
- [Zach Wilson](https://www.linkedin.com/in/eczachly/)
- [Rahul Pandey](https://www.linkedin.com/in/rpandey1234/)
- [Carly Taylor](https://www.linkedin.com/in/carly-taylor-data/)
- [Lee McKeeman](https://www.linkedin.com/in/lmckeeman/)
- [Ryan Peterman](https://www.linkedin.com/in/ryanlpeterman/)

Hey everyone, I tried searching online about this but couldn't find much info. I did virtual onsites with Meta this week and the recruiter called me asking if I knew anyone at Meta that could be used as an internal reference.

Is this generally a good sign and does this mean I'm going to the HC?

Meta recruiter asking for internal references - What does this mean?

Mid-Level Software Engineer [SDE 2] at Amazon

Hey everyone! \
\
I just passed all my Meta interviews for E4 in infra! and now I am onto team matching!\
However, my recruiter wants me to try out for the monetization/ads org, but I've heard a lot of bad rumors about that org, notably that work life balance is awful and stress is really high. (Blind seems to especially dislike it haha)\
\
Does anyone have real experience with that org here? Are the rumors true?\
\
I don't mind a little bit of extra stress and doing some overtime from time to time as long as it's not overtaking my personal life. \
For instance at Amazon (Gen AI) there were months where I was doing 80h+ per week non stop and that's the number one reason why I would like to leave tbh.\
\
This is only the fast track option that my recruiter is offering me tho, I might still be able to get into the normal team matching pipeline afterwards too.\
\
Anyways, thanks in advance! :) 

Just got into Meta as E4 but need some guidance on team matching

Ilya Reznik (Guiding ML Engineers through their career journey. ex-Head of ML, ex-Meta Staff SWE, ex-Adobe)

This post is part AMA and part request for your insights.

I’m currently developing a Taro course for Q1 of 2025, focused on navigating the transition to a career in machine learning. If this topic resonates with you, I’d love to hear your thoughts:

1\. What are the most pressing questions or concerns you have about making this transition?

2\. What is your current role or background (e.g., Software Engineer, Data Engineer, SRE/PE, Data Scientist, etc.)?

**About Me:**

I’ve transitioned from Software Engineer to Data Scientist to Machine Learning Engineer over the course of my 14 year career. I’ve been an MLE for 10 years, with experience at Adobe, Twitter, Meta, and as Head of MLOps at a Series B startup.

Thank you!

Update: Thank you for all the questions, keep them coming. I put together a [YouTube](https://youtu.be/t7tOGXZjhHM?si=tmeO0iIvPPT85Z90) video with a quick outline of the process as I generally recommend it, this is a high level overview and more practical things are coming in a Taro course early next year.

Looking to transition to ML Engineer? What do you want to know?

Ritendra Datta (Head of Applied AI at Databricks)

I just did [a live Ask-Me-Anything (AMA)](https://www.jointaro.com/lesson/j788E0O0w7vWWzLOWAre/ask-me-anything-ama-with-a-meta-and-databricks-eng-director-ritendra-datta/) but we can also collect questions here that I'll answer afterward.

### Work history

I recently joined Databricks as a Senior Director of Engineering. Most of my career has involved Machine Learning, and I've managed teams ranging from 2 to 200 engineers/research scientists.

Previously, I was the Head of FB Reels and Video Recommendations (Director of Engineering) at Meta, from 2019 - 2023. Before that, I was a Senior Staff Software Engineer and Tech Lead working at Google in Mountain View. I hold a PhD in Computer Science from Penn State, and my publications during that time have accumulated almost 9K academic citations.

Some questions I've heard:

- How Fair is Performance Evaluation for Tech ICs vs Managers?
- Can you give some examples of effective communication? What channels are used, level of abstraction, tone, etc?
- Any advice for a new grad to progress faster in their career?
- What are interviews even like for Director+?

### Other

I've started writing detailed notes in blogs titled TLDR0. Slightly cheesy, but it stands for Tech Leadership - Direct, Respectful, Zero Ego. See the full details on my [LinkedIn profile](https://www.linkedin.com/in/ritendradatta/).

- Substack: <https://tldr0.substack.com/>
- Medium: <https://tldr0.medium.com/>

I'm Ritendra, Ex-Meta/Google current Senior Director at Databricks. AMA!

Hi, I have my first team match call with a hiring manager this week. I am E4 level. I have compiled a list of questions to ask to try and demonstrate that I am willing to come in and work hard to contribute to the team's success. Would love some feedback:\
\
1\. What are some past projects that E4 engineers have worked on?\
2\. What is the team distribution, everyone's level, and how do people interact with each other?\
3\. What are the top 3 traits you look for in a candidate to join and be successful to contribute to your team?\
4\. What do you think I specifically would be working on at the start?\
5\. What are the specific expectations for my role/level during onboarding / ramp up? How long is ramp up? What are the expectations after ramp up?\
6\. How does the team celebrate success?\
\
And please feel free to add any questions you think would be helpful to ask!\
\
Thanks in advance!

Questions to ask managers during Meta Team Matching

Entry-Level Software Engineer [SDE 1] at Amazon

**Preparation**: Standard top 100 LC problems + Infra System Design Problems + Behavioral problems (STAR)

### Interviews

**Meta phone screen:** Asked two questions directly from the top 50 LC tagged (**Array Sum** and **Tree BFS** categories). Aced both questions and was notified the next day that I had moved on to onsite.

**Onsite prep**: This would be my first system design interview and I didn't want to mess it up. I booked multiple [**Hello Interview**](https://www.jointaro.com/perks/) mocks and though they weren't cheap, I was satisfied with the overall quality, feedback, and accurate grading.

**Meta onsite 1 (coding)**: This round tripped me up and I was disappointed given how much I had prepared 🙁

- First question: [**Tree BFS**](https://www.geeksforgeeks.org/level-order-tree-traversal/) (got optimal runtime, but not optimal space)
- Second question: **Multiple binary searches** on an array (did not get the optimal solution, couldn't find a question to tag)
- Immediately after the round, I realized my mistakes on both questions but couldn't go back and change it 🙁

**Meta onsite 2 (behavioral)**: No surprise questions and I answered them to the best of my capacity stressing my ability to work with other people specifically

**Meta onsite 3 (system design)**: The question is similar to [Post Search](https://www.hellointerview.com/learn/system-design/problem-breakdowns/fb-post-search)

- I had trouble understanding the interviewer and threw all my system design knowledge out there. There wasn't much discussion but I did mention concepts such as inverted index, sharding, replication, hot partitions, cache invalidations

**Meta onsite 4 (coding)**

- This was my strongest performance and I was proud of myself after this round. I solved both questions optimally
  - Question 1: [**Number Verification**](https://leetcode.com/problems/valid-number/description/) **(LC Hard)**
  - Question 2: [**Tree BFS**](https://www.geeksforgeeks.org/level-order-tree-traversal/)
- Surprisingly (given my other rounds) I received a call the next day saying that they wanted to give me a **follow-up** coding round

**Meta onsite 5 (follow-up coding)**

- I fumbled this round, which was especially heartbreaking. The questions were related to **Palindrome (LC Hard)** and **Grid DFS**
- Same day I was notified that I was rejected 🙁

Eye-opening experience overall and I know I have much more work to pass next time around. Total time: \~1.5 months

My Meta Interview Experience (Mid-Level [E4] | USA | Reject After Follow Up)

[Case Study] 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)

Meta recruiters request references of people you have worked with before who are current employees of Meta before submitting feedback file to review committee. 

My question is what & how much impact does providing these references have on your application, candidacy and the ultimate outcome of the interview process.

Does it hurt your chances to not be able to provide these one or more of these references? 

[Meta Hiring Process] Meta recruiters request references before submitting feedback file to review committee 

Ultimately, there is no shortcut to a promotion at this level—it requires significant, consistent contributions that demonstrate your readiness to operate at a higher level of responsibility and impact. And I understand that it might not be easy on those levels, but most of the things described in the official documentation are pretty intense. Is there an easier path to get to the top by doing things smarter and not harder? For instance, there are things that people could do in other companies for bonus points like organizing hike for the team, building Movember type of volunteering event or soccer tournament for the org? 

How about the following examples?

### **Mentorship and Team Development:**

Actively mentor junior engineers and contribute to team development. This can include leading internal workshops, contributing to onboarding processes, or providing regular, constructive feedback to peers.

### **Community and Culture Contribution:**

Contribute to the company's engineering culture and community. This can involve contributing to open-source projects, improving internal tools, writing engineering blogs, or participating in company-sponsored volunteer events.

What are the hidden and easy cherry picking to do for E7 promo?

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?

Failure Mode: Fake Learning

*Fake learning* is when an engineer wants feels good by consuming an endless barrage of:

- Tutorials
- Books
- Blogs

These resources (crutches) are addicting because it's easy to monitor progress (40% done with the book!), but they turn out to be terrible for you to retain anything.

Software engineering is about action, not theory. Your goal is to reduce the amount of time from reading about a concept to putting it into practice in front of the computer. This is usually best done within the company, not on a greenfield project or external book you found. Get your hands on the keyboard, and realize that growth comes from discomfort.

Entry-Level Software Engineer at Taro Community

I recently interviewed with Meta for a E4 level SDE role and was given a hire decision but for E3 level instead. However since my recruiter is unaware of any E3 roles currently, they are unable to move forward with my application. I reached out to other recruiters but with no response. What could I do in this situation? Kindly advise.

Interviewed for Meta and got rejected for E4, but there's no open E3 roles - What to do?

I have around 6.5 years experience in Android development. I joined Meta as a new grad in 2017 and never gave an interview after that. I plan to give interviews in about 6 months from now.

I see lot of resources available online for Backend System design interviews but very little information about Mobile System design interview.

Any pointers on what the interview process looks like/ how to prepare for interviews at this level?

Thanks

How to Prepare for Android/Mobile Senior Software Interviews?

I received a verbal offer from Meta for the Android role and I'm in a team matching phase. Recently team matching has been a lot of struggle and could take weeks or maybe months. Last year a lot of hiring managers posted on LinkedIn about hiring for roles and I did exchange a conversation with them. Is it wise to ask the hiring manager on LinkedIn about open roles in their org and then telling my recruiter about it or I should go with a team that the recruiter helps me to connect with?

I'm in Meta team matching - Is it okay to reach out to managers on my own or should I only go through the recruiter?

Started at Meta London as a mid-level engineer back in 2020. Put in everything I had, but stayed stuck at the same level despite trying for promotion every cycle. Made it through several re-orgs and manager changes, always thinking "next time will be different."

Never quite found my groove there. I know I'm a solid engineer, but between team circumstances and a poor fit with the product side, I couldn't land those "exceeds expectations" ratings needed for promotion. Now they're laying me off with a "below expectations" rating, which might block me from ever working at Meta again.

This hits hard. Really hard. I poured years of my life into this job, burned through my health both mentally and physically. Now I'm watching everyone talk about this massive AI revolution coming for tech jobs, while London tech salaries are already pretty rough, and I've just lost my position at one of the few companies that paid well here.

I've landed another job to keep the lights on (again, I can code), but it's clearly not somewhere I'll grow much. Being in my 30s and having to rebuild from scratch is scary enough - add in the AI uncertainty and it feels even worse. That "below expectations" rating from Meta feels like a brand I can't shake off.

How do you bounce back when you've had a shot at the big leagues and it didn't work out? When you have to start over but you're not fresh out of college anymore? Some days it feels like everyone's judging me for not making it.

Looking for any advice from folks who've been through something similar or found their way and succeeded even better after a major career setback.

Dealing with career setback at Meta & fears about AI future - need advice

I've seen advices here in Taro that seniors should make themselves very much replaceable so that when this senior is away, someone is able to cover for them and the team could do well, which makes sense.

I thought the fact that people found the advice to be helpful, shows that making yourself replaceable isn't something that's very intuitive the first time. Like if someone didn't read the advice, they probably wouldn't have optimized for that.

I'm not quite senior yet but just curious to understand the situation (and people) better - was this thinking assumes that the amount of scope is in hyper-growth phase? Are there cases where it isn't really applicable / optimal for them to do so (and so they don't make themselves replaceable, and still do well) - then wouldn't they just continue doing it and we can't really blame them? I feel it's rare that people would change their behavior unless they really understand why.

Why would a senior make themselves replaceable?

Master The DSA Interview [Part 6] - Why Does FAANG Do This?

If data structures and algorithms aren't actually used on the job, why do Big Tech companies use these problems as a cornerstone of their interview process? This lesson teaches you:

- Why Big Tech isn't just being evil and stupid when they use data structures and algorithms problems on their interviews
- How data structures and algorithms problems can have a surprising amount of depth
- What most engineers don't understand when it comes to how FAANG rejects candidates
- How Google and Meta in particular differ from almost all other companies when it comes to hiring, which affects how their interview processes work

If you're interested in working at early-stage startups that don't ask LeetCode problems: ["How to find and connect with scrappy startups?"](https://www.jointaro.com/question/9jFuRj3UymeHsaKIzXia/how-to-find-and-connect-with-scrappy-startups/)

Master The Behavioral Interview [Part 19] - Cultural Values

Culture fit is real. A lot of tech companies have toxic culture and don't vet for it properly, but that doesn't change the fact that culture fit is extremely important to running a healthy engineering organization. This lesson teaches you:

- Why cultural values are important
- What you should do to effectively study and internalize the cultural values of a company you are interviewing with
- How to weave a company's cultural values into your behavioral interview answers through an example with Alex for his Meta interview

If you're curious as to how Meta's engineering culture works: ["Is sprint planning and agile not a thing at Meta?"](https://www.jointaro.com/question/tB7borE2AWb1KcuFEcon/is-sprint-planning-and-agile-not-a-thing-at-meta/)

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?

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?

I have been working less than a year at Meta and am just unable to understand and jell with the culture. There are a few main things contributing to me feeling burnt out. 

### Endless number of things to do...

There is equal emphasis on contributions to all axis and there is barely any overlap in the work that I need to do in order to meet expectations on all of them (except maybe Impact and Direction)

Better engineering projects that my team has scoped out are very separate from Impact projects

For people axis, I have to drive org level impact which is a thing of its own and adds on to the BE projects and impact projects. 

Our oncall is extremely tough since we have a huge number of products with code dating back to 10 years ago. 

Due to all this it feels like I'm having to do 4 jobs at once.

### Process is bloated...

Especially for impact projects that result in changes to the product, there are a huge number of people involved, UX, DS, DE, 2 major orgs who are our customers and their representatives, Content, PM and business leaders. I get pinged for dates and status updates by 5 different people for either the same or different things every day. It is hard to keep up with and as someone who has some ADHD traits (unofficial diagnosis) and an introverted personality, just getting pinged and keeping up with responses feels exhausting let alone the coding aspect. Meta lives by its bottom up culture but in our org it just doesn't seem like its working. In my previous job, process was barely something I had to think of, and mind you we did weekly releases to 3 environments. 

### Laser focussed PSC conversations...

From having performance conversations 2 times per year to now having them 2 times a month seems like an extreme overkill and adds to the stress at all times. It isn't just the frequency. PSC self reports are so heavily dissected for every single word, every single metric that doing PSC right feels like a project in itself. so now it's 4 + 1 = 5 jobs.

What should I do? PSC season is again around the corner. Practically speaking I have a few options I want to get some thoughts on.

1. Change teams (requires an exception since it hasn't been a year)
2. Leave meta (and payback some comp components and say good bye to crazy TC)
3. Take a medical leave (still risk getting dinged at PSC)
4. Stick it out until the 1 year mark and revisit above options.

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?

Rahul's Compensation Journey To $800K (and behind-the-scenes)

In 2021, the last full year Rahul worked at Meta, he made $823K. When he joined Facebook (Meta) in 2017, his total compensation was $390K. See the full details [in the YouTube video](https://youtu.be/inydj1VZ0y0).

In this session, Rahul documents how his yearly compensation more than doubled over the 4.5 years he was employed at the company. This talk will cover details that didn't fit into the YouTube video while exploring angles of it more in-depth.

Topics:

- What components of compensation matter the most in a typical tech company
- Parts of a company's compensation philosophy which have large consquences, but are not often understood or discussed
- How to think about level and negotiation when job hopping
- The psychology around pay changes, and how people change their spending when hitting certain compensation milestones

Related content:

- [How To Earn Respect Fast - Senior Engineer Onboarding Story](https://www.jointaro.com/lesson/FaD8tVGXP6SiRQfee4SD/how-to-earn-respect-fast-senior-engineer-onboarding-story/)
- ["How can I think like a staff engineer?"](https://www.jointaro.com/question/RU3Mof8NeEYQP30l6giW/how-can-i-think-like-a-staff-engineer/)
- [This Is Why FAANG Engineers Make So Much Money - Tech Compensation Breakdown](https://www.jointaro.com/lesson/1aKjiSKcHDttnyTAYXy4/this-is-why-faang-engineers-make-so-much-money-tech-compensation-breakdown/)
- [\[Masterclass\] Understanding And Optimizing Your Pay In Tech](https://www.jointaro.com/lesson/gk408yBIV2fa5RjVR213/masterclass-understanding-and-optimizing-your-pay-in-tech/)

Staff Software Engineer at Taro Community

I’ll be starting as an E6 at Meta, working on internal tools. Currently, the headcount is really low, and people only have 60 days to match, so I decided to go with the first team I matched with, even though it’s not the most exciting option.

I’m committed to doing a great job in this role, but I’m a bit concerned about the potential impact I can have and how that might affect my performance reviews (or get me PIPd). Is this something I should be worried about? Any advice on how I can maximize my impact on a team that might not be seen as highly impactful? 

Impact Expectations as E6 Staff Engineer at Meta

I'm trying to figure out the proper level of fidelity here: Should I have very granular estimates or something that's not super structured - Just a high-level idea of projects with some buffer built in.

I'm curious to know how to structure this plan to ensure that one doesn't take on too much and get overwhelmed, but is also full enough so that in case of blockers on core projects, there's a pipeline of projects to switch into. Would love to hear everyone's thoughts!

Should I do a lot of upfront planning around the work I will take on across the half?

I was promoted to E5 in July 2022, and I’ve been working on a challenging and highly ambiguous project since then, where my TL and another UberTL have limited ideas on how to make it a successful project and what direction the project should go. I’ve been getting little XFN support since the beginning of the project but still was able to implement and ship the MVP design I did on my own, but I still got MA rating for this. Starting Q2, things got a little better and the direction is somehow clear for H1 with specific high-level components to implement. My questions are:

1. Given this setup, since my TL has already defined the design and different components to implement, how can I still have high impact as a senior eng on the project? Previously, my EM suggested I look at myself as the CEO of the project and my TL as a consultant, but this has already changed when he got very involved in the project. I already do regular project updates on the project and have been getting positive feedback from all stakeholders that I usually get everyone on board with my positive communication with all of them. 
2. My EM and TL have been giving me feedback that I need to move faster and target small wins, as opposed to working on a large goal that takes months of implementing, as was done for the MVP solution. The problem is: my whole team work past working hours up to 12-14 hours/day and sometimes on weekends too, which is not feasible for me, so I’m seeing this issue more as a relative issue compared to my teammates as opposed to being slow in execution. How can I resolve this issue? Can I talk to my EM about this?

Thanks!

Software Engineer Intern at Taro Community

I would first like to thank Taro for helping me land internship offers at two amazing tech companies. I could not have done it without Taro's amazing courses.

I am trying to decide between the two offers for my last internship. The offers are as follows (both are for software engineering position):

- Meta (Menlo Park)
- Microsoft (Redmond)

I am currently leaning towards Meta due to resume value and opportunity to work on interesting projects. It is also a lot closer to where I live. The pay for Meta internship is also higher by around $10,000.

However, based on initial research, it appears Microsoft's return offer rate is slightly higher. According to what I have heard, Microsoft's FTE conversion rate is generally around 75-80 percent.\
\
Would it still be wise to choose Meta in my case, or would Microsoft be a better choice? I would greatly appreciate any insights.

Internship offer selection - Meta vs. Microsoft

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/)

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?

Senior Software Engineer at Washington State Labor & Industry

I got an interview call from Meta for SDE position. They asked to send over any names of references I have at Meta. Can you please suggest me any names from Meta to put as references?

Thank you.

Can you please suggest me any names from Meta to put as references?

[Part 5] Meta Intern Success Series - Writing The Code

- Keep your diffs focused and atomic. Aim for 25-250 lines of code per diff.
- Use stacked diffs: They are core to Meta's code culture. If you're unsure how to break up your work into a diff stack, work with your intern manager to come up with how things should be broken down.
- Make sure that all your diffs have a really good context section. You can have a "Context" section at the top explaining the overall goal of the diff stack (i.e. usually what your intern project is meant to do) and then a "In This Diff" section which explains the specific problem your diff tackles.
- Attach a test plan to show that your code works and to turn the diff review into a high-value artifact. Record a video of you stepping through the flow if possible (this should be easy as many interns work on internal tools) and make sure to cover those edge cases!
- Keep a very close eye on your Phabricator notifications. Your goal is to respond to code review comments quickly (within 30 minutes) and gracefully. **Code review feedback is the main way you grow as a software engineer intern** as the internship's goal is to develop your raw coding ability.
- Land diffs ASAP, so you don't need to deal with rebase hell.

Related resources:
- [One Diff, One Thesis - What Every Code Review Should Be Like](https://link.jointaro.com/Wnp45zAysqyaidSF7)
- [The Most Common Mistake Made When Authoring Code Reviews](https://link.jointaro.com/bCaB7gh2u5budm2V6)
- [What A Test Plan Is And Why Every Code Review Needs One](https://link.jointaro.com/62fq4369rxjXuDju5)
- [This Is What A Good Code Review Test Plan Looks Like](https://link.jointaro.com/ieDhChExstEpD8sw9)
- [Full In-Depth 1 Hour Masterclass On Effective Code Review](https://link.jointaro.com/Vn7YSzTL61i9shwM8)

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?

Negotiation Course: Recruiter Case Study: Insights From An Ex-Meta Recruiter

This was a conversation with a recruiter who spent several years as a recruiter at Facebook (Meta) and Pinterest. 

- The tactic of *"I will sign the offer if you meet me here"* is **effective if it's sincere**. You should be prepared to explore/defend various options around other ways the company could compel you to sign the offer.
- Exploding offers are almost always fake. Recruiters know that "**time kills all deals**" so they want to close candidates quickly. However, as a candidate, you can and should push back on an arbitrary deadline. Ask why the timing constraint exists and share why you need more time.
- Be graceful when you turn down a company's job offer. This recruiter would frequently be able to hire candidates several years later who had received an offer if they kept the relationship alive.

[Part 2] Meta Intern Success Series - High-level Expectations

You can find the full playlist here: [Meta Intern Success Series](https://www.jointaro.com/playlist/D4fbBZdkNhIZCyOUofBx/)

- As mentioned before, your goal is to be operating as an E3 MA (Meets All Expectations) by the end of your internship. Assuming the standard 12 week internship, you have 10 weeks to do this.
- You will be working on production code, dealing with Meta's gigantic codebase. The exception is FBU (FB University, a "pre-intern" program) where you build an app/website from scratch in isolation.
- **Every week is crucial**. A great/terrible week can make or break your internship.
- Raw coding ability is the main thing you're judged on as a SWE intern (literally ~90% of your packet). The 2 main components here are velocity and quality, which means that your goal as a SWE intern is effectively just to write a lot of very high-quality code fast.
- In a vacuum, target landing 3-4 diffs per week. Of course, this will vary based on org, stack, etc - Work with your intern manager (IM) to get a more accurate range. You can look at previously successful interns in the org to generate a baseline as well.
- Write 1-2 Workplace posts as technical writing is super important at Meta. The easiest thing to do is write about your intern project as you hit major milestones, especially when you launch it.
- You need a cast of people to vouch for you during calibrations. Target having 2+ peers on top of your IM (i.e. so 3+ people total).
- You will likely work on an internal tool as it's free from XFN thrash and dependencies. Meta has a lot of respect for quality internal tools as well.

Nail Your Promotion As A Software Engineer [Part 13] - Create An Expectations Plan

Don't leave your promotion to chance - Getting promoted as a software engineer should be as close to a contract as possible. This lesson teaches you:

- Why you need an expectations plan to get promoted efficiently
- The right mentality to have when it comes to crafting an expectations plan
- How to organize your expectations plan, particularly at bigger tech companies
- What a top-tier expectations plan looks like with a real, in-depth example from Meta

If you're interested in the growth plan mentioned in the video, here it is: [Meta E4 -&gt; E5 Growth Plan](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)

Meta Manager Case Study: The Ultimate Guide To Navigating A PIP

This was an Engineering Manager at Meta who has put 20+ employees on PIPs throughout their career.

- PIPs come from a mismatch of a “square peg, round hole”

- PIPs should never be a surprise. PIPs get discussed with the skip manager and HR

- Designed to be achievable with effort

- Across 20+ PIPs, has never had anyone continue employment

- **Advice**: “Clarity is more important than agreement”

Ace Your Tech Interview As A Software Engineer [Part 33] - Understanding Big Tech Interviews

For many software engineers on the interview grind, FAANG is **the** pinnacle, the dream destination. However, Big Tech interviews are so frustrating and notorious for their difficulty. Why is that? This lesson teaches you:

- The general perspective of Big Tech when it comes to hiring software engineers
- What centralized hiring is, why it's unique, and how it affects the interview process (particularly for 2 certain FAANG companies)
- Which interview types are more common for Big Tech and why
- Which interview types are less common for Big Tech and why

To dive deeper into cracking the FAANG interview: [\[Taro Top 10\] Breaking Into FAANG](https://www.jointaro.com/playlist/roKqDHgxu4C5CioEFpJY/)

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?

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.

Meta Case Study: The Ultimate Guide To Navigating A PIP

This was a veteran engineer with more than 15 years of experience at other large tech companies before joining Meta.

- **Before**: Hired in as Staff Engineer \[**E6**\], brought in as a domain expert. Worked for almost 2 years before the PIP

- **During**: Not surprised based on rating trends. Main issue was code productivity, inability to use tooling such as version control

- **After**: Struggled with the PIP for a few months, then negotiated a severance package

Joining a company at too high a level is not good

If an employee's performance is subpar, it's better to act on that early, both for the employee and the team.

At a high level, your job is to lead the team and teach others. It’s ok if you don’t know the tooling, but you should not let that get in the way of landing code. Code output was poor.

[Case Study] 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/)

I'm primarily on the back-end, but I've been put on a lot of other stacks. I've worked with www and Bloks and now I need to pick up native Android to debug a deep link issue.

I'm having a hard time with the Android issue. I took a long time just setting up the environment, choosing between VSCode, Android Studio, and OnDemand. I'm now working with adb, which I don't really understand as it's completely new to me. There's not a lot of documentation for my problem area, and it's been rough.

More broadly speaking, how can I do better in these situations and pick up new stacks faster?

How can I pick up other tech stacks more quickly at Meta?

Last weekend, I got some surprising news from my EM after our team's Pulse review submission was done. \
Turns out, I'm getting a 'Meet Most' rating. I've been at Meta for two years now, and my EM thinks it's a good idea for me to start looking outside the company since a promotion seems tough in the next six months.

I'm not really sure what to think about this. Has anyone else been in this boat? I'd love to hear your experiences. Also, Is switching teams within Meta a viable option ?

Pls Advice : On the risk of getting Meet Most, EM suggest to start looking for Job

Senior Engineer (L5) Describes Most Important Skill - Richard Chen

Richard is a Senior Engineer (E5) at Meta.

- **Most important skill**: correct project selection. This requires balancing outcomes, priorities, and risks.
- **Advice**: bring people along with you. Careers are built over the long-term, so it's important to treat partners and work colleagues well.

Here's the full playlist asking engineers what the most important skill is for their level: [Asking 7 Levels Of Engineers The Most Important Skill](https://www.jointaro.com/playlist/J9Io5lDGaYUpI8vGrUyI/)

Helpful links:
- Taro's top 10 to get promoted from [entry-level to mid-level engineer](https://www.jointaro.com/playlist/iBKHYpkjd0BRWWLKQG2j/)
- Taro's top 10 to get promoted from [mid-level to senior engineer](https://www.jointaro.com/playlist/AUMiBTvYUv0gcOzuu26V/)
- Taro's top 10 to get promoted from [senior to staff engineer](https://www.jointaro.com/playlist/YD8LMCSlE71VUGUbNAWM/)
- [Richard on LinkedIn](https://www.linkedin.com/in/r-x-c/)

What sort of documentations should we have for our 1 on 1s? Is there a video on having a 1 on 1 doc?

My previous manager at Workday told me to discuss \
Wins, What I am focusing on, Blockers, Personal Development, Action steps

and created a shared google doc for us, but it seemed kind of status-reporty. Is there another recommended format for our 1 on 1?

What should be in our 1 on 1 doc (for manager 1 on 1s)?

Does my manager see how much time I’m actually working? I work offline sometimes and am worried if this may look like I’m coasting

Do managers know how long you use your system?

[Part 3] Meta Intern Success Series - Onboarding Efficiently

- Onboarding is arguably the most important part of your internship as it sets the foundation and tone for your entire software engineer internship.
- Set up a 30 to 45 minute meeting with your intern manager (IM) ASAP, so they can explain the codebase to you at a high-level (i.e. a component level).
- Make sure you have a recurring 1:1 meeting with your IM, which should be a weekly 30 minutes. Your IM should set this up for you, but in case they don't, you can work with them to set it up.
- You will get 2-5 onboarding tasks to work on across the first ~2 weeks. The purpose of these is to familiarize yourself with the codebase.
- Aim to put out your 1st diff by the end of Week 1. If you're doing this around the end of Week 2, you're really behind.
- Ask a ton of questions and learn to ask high-quality questions. Don't be afraid of "over-asking" questions: If you're polite while asking questions and attaching great context to them, you will be fine no matter how many questions you ask.
- Use Work Chat DMs to ask for help aggressively during this period as it's vital for you to become productive within the codebase very quickly

Related resources:
- [Asking Effective Questions That Get Great Answers Quickly](https://link.jointaro.com/E8eaKmMpZcKWNGkbA)
- ["How can I learn a large codebase fast as an intern?"](https://link.jointaro.com/L8tXjWah6ycdNpNf7)
- [There Is No Such Thing As A Stupid Question](https://link.jointaro.com/F4p3fL4eHqp5GXti7)

How can I figure out how long is a reasonable time to take on a task (especially with Meta' s move fast culture)?

Other Great Discussions