Explain Like I’m 5: Demystifying Meta’s GenAI Infrastructure

Session led by: [Malik (Mike) Alnakhaleh](https://www.linkedin.com/in/malik-mike-a-32b63818b/)

**Event description**

Dive into the fascinating world of Meta's next-generation artificial intelligence with an event crafted for simplicity and clarity!\
\
Whether you're a software developer, a tech professional, or a bit AI-curious, join us for an illuminating session where complex concepts are made accessible. No PhD required!

### **What You Will Learn:**

- The Backbone of Meta’s GenAI: Unpack the core components and architecture powering Meta's cutting-edge AI, from robust data center hardware to innovative computing networks.
- Scaling AI for Tomorrow: Explore how Meta scales its AI infrastructure to support complex models and vast datasets, ensuring efficiency and sustainability.
- Innovations in AI Deployment: Discover the cutting-edge tools and practices Meta employs to deploy AI applications, from development to production.

### **Who Should Attend:**

- Software developers and engineers seeking to understand the infrastructural demands of AI.
- Professionals interested in AI, machine learning, and data center engineering.
- Anyone curious about how large-scale AI systems are built and used.

Ready to peel back the layers of Meta’s AI infrastructure with the curiosity of a five-year-old?\
\
Secure your spot today and step into the world of tomorrow's AI, exploring the future, one simple explanation at a time.

Meet The Team

Software Engineering is a team sport, and therefore building strong relationships with your team is a prerequisite for your success. Book 1 on 1s with teammates proactively, and for key people, look into recurring meetings for the first month or two.

One useful thought exercise: think about **who can throw you under the bus?** By doing this pre-mortem (analysis *before* an issue has happened), you can take steps to make them like you and prevent an issue to begin with.

The other key component to building strong relationships with your team is to prioritize in-person interaction. 

- Trust is much, much easier built when you're in person compared to remote
- If you’re hybrid, try to come in as much as you can. Align on days when other people are in the office.

Working With Your Manager

Your manager is the most important person for your career progression. If they don't support you, you will not get promoted. This means you should allocate sufficient time and attention to this relationship when you first join.

Rahul's suggestion for the bare minimum interaction during the first few months at the company:

- Weekly (or biweekly) recurring 1:1 meeting
- 30+ minutes

Two tips to ensure you get sufficient value out of the manager relationship:

- Let them know you’re eager for feedback
- Add structure to the interaction by writing things down and following a template for each meeting

If your manager frequently cancels 1:1s with you, use the running 1:1 doc with an agenda as a defense mechanism. People will think twice about canceling something if they know it's important to you.

Why Most Companies Suck At Onboarding

You should not expect a good onboarding process at your company. Helping new employees ramp up is a good example of something that is *important but not urgent*. Tenured employees likely don't remember what it's like to be new.

While many companies will have insufficient or non-existent onboarding, the other end of the spectrum is also unfortunate: larger bureaucratic companies will have excessive onboarding, with months of training before you can do anything productive.

Even if the company has good intentions, building a solid onboarding plan is a hard problem: the tech industry's rate of change is very high, with people, tools, and technologies changing every year. Naturally, documentation and processes around onboarding become outdated.

Despite the difficulties, poor onboarding can be seen as an opportunity for new employees to have an immediate impact.

Level Up Your Code Quality As A Software Engineer [Part 15] - Make It A  Little Better Each Time

We all want to make big, fast strides, but this is often hard to actually achieve. When it comes to leveling up your code quality, a lot of the battle is incremental. This lesson will teach you:

- A framework you can apply to your code repeatedly to make it better and strengthen your coding skills
- How small improvements here and there can really add up over time to increase the quality of a codebase and build up your respect among the team
- An organic trick that Alex and all his mentees used at Meta to strongly succeed on the technical axis and get promoted fast

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

Do This To Get Maximum Value From Your Manager 1 on 1s

The manager 1 on 1 meeting is arguably the most sacred and high-leverage time you have in your career. Make sure you don't waste it by stumbling in with 0 preparation.

Here are the core points from the video:
- **Come in with a plan** - In your running meeting notes doc, write down the agenda beforehand with discussion points ordered by priority. Not only does this make your meeting more effective, it improves the perception of you from your manager's eyes as it shows that you're being more respectful of their time and you're more serious about your own growth and productivity.
- **Alert your manager of the plan 24+ hours beforehand** - This allows them to "pre-compute" the best responses to your meeting topics, so they don't get caught like a deer in the headlights with the trickier ones. It also makes it harder for your manager to cancel, especially when you have deeper, more important topics on the agenda.

Related resources:
- [[Taro Top 10] Software Engineer To Engineering Manager (IC -> M Track)](https://www.jointaro.com/playlist/oz0mnJvHHgM8NfVF7rgp/)
- [[Masterclass] What Software Engineers Should Look For In Their Engineering Manager](https://www.jointaro.com/lesson/oeY7ncZhzJ5NO6dij5e7/masterclass-what-software-engineers-should-look-for-in-their-engineering-manager/)

What Advice Do You Have For Women (And Allies) In Tech?

There are not enough women software engineers. Rachel talks about the importance of sponsorship for career advancement, being ok with discomfort, and using employee resource groups (ERGs) to find community + support.

For allies (those in positions of privilege), acknowledge contributions from women and call out their good work if it's not getting noticed. 

Rachel also discusses how to evaluate a company's priorities around diversity and inclusion.

For more wisdom from Rachel, [here's her Taro playlist](https://link.jointaro.com/Cm5rJk4RJTkWhhnq7).

The Key To Avoiding The Performance Improvement Plan (PIP)

Getting hit with a performance improvement plan (otherwise known as a "PIP") is one of the worst things that can happen to you as a software engineer. This makes avoiding a performance improvement plan one of the most important things for you to do, especially in the currently layoff-rich economy.

Here's the core points from the video.

- Your performance review rating should never be a surprise: Regularly check in with your manager to figure out how you're trending to avoid the dreaded PIP.
- On top of asking for constructive feedback regularly, you shouldn't be afraid to ask every 2-3 months if you're on track to get the rating you want once the formal performance review happens. The clearest way this manifests is a hypothetical rating: *"Would you give me at least a \[Meets Expectations\] for my performance so far?"* This is the most powerful way you can stay in sync with your manager.
- Make it clear with your manager that you'll take any hypothetical rating with a grain of salt, so they're more comfortable giving it to you. If you're brave enough, you can even ask them to err towards the lower-end so you don't overset expectations.
- Keep your eye on the ball: Keep referencing the expectations plan you made at the beginning of the cycle and evolving it as necessary.
- Turn it up at the later end of the cycle. Humans have bad memory: It's unfair, but recency bias is huge. Try to land your bigger wins just a few weeks or months before the formal performance review process starts.

Related resources:

- ["What's the difference between a low performer software engineer and a high performer?"](https://link.jointaro.com/QHkWNXoJV5Y9VYvH9)
- ["How do I help my manager (who is also my mentor) be a better manager and mentor?"](https://link.jointaro.com/eG5c6usaJNY9wopP8)

What People Get Wrong About The Manager To Software Engineer Relationship

In this lesson, we discuss the common mistake that senior engineers commit, which is that they continue to assume that the manager is an authority figure.

This is often the case, but doesn't have to be. David talks about a case in his past job where an IC on the team was more senior than him as the manager. And the IC engineer was objectively more important to the team, indicating the value of this senior-level person not only to getting work done, but also setting direction and giving feedback to others.

Senior engineers should view the relationship with the manager as a partnership rather than a person for whom they must *follow orders*. **The tech lead and manager have different but overlapping responsibilities in helping the team succeed**. Realizing this unlocks a more fruitful collaboration.

Remember, managers will frequently have blind spots that a tech lead can point out. These insights and observations may manifest in actually pushing back on the manager's plans or strategy. This is a role that senior engineers should embrace.

- More from David: <https://www.jointaro.com/topic/david-pan/>
- [Onboarding as a Tech Lead at Robinhood in 1 Month](https://www.jointaro.com/lesson/X8vpfJooDpsX915ouC00/case-study-becoming-a-tech-lead-again-in-just-1-month-after-joining-robinhood-from-meta/)
- [The EM "Partner In Crime": The Tech Lead](https://www.jointaro.com/lesson/uZQZlS6tdXbztajM0tqa/the-em-partner-in-crime-the-tech-lead/)

An Often Forgotten Part Of Tech Pay - Don’t Mess Up Your Taxes!

This video segment offers **critical tax advice for high-earning employees in big tech**, particularly in the U.S. It emphasizes the importance of understanding how taxes work with equity compensation to avoid severe financial consequences.

- **Set your withholding percentage close to your actual effective tax rate**, which for many tech workers is around 30%. This helps avoid massive surprise tax bills—sometimes exceeding $100K—during tax season.
- **RSUs (Restricted Stock Units) are taxed as income when they vest**, not when they’re sold. If the stock value drops after vesting, you’re still taxed at the higher initial value, creating a potential mismatch between tax owed and actual value retained.
- **Default withholding settings are often too low**, especially on platforms like E\*TRADE (commonly set at 22%). If not adjusted, this can lead to underpayment and steep penalties later.
- **If RSUs lose value and you’ve under-withheld**, you may be forced to sell more shares than expected just to cover your tax liability.
- **Some intentionally under-withhold to invest the difference**, but this is risky and should only be done with a clear financial strategy in mind.

How To Build A Strong Manager Relationship (From An Ex-Amazon VP)

The relationship you have with your manager is the most important one in your professional life. So why do so many tech workers **make obvious mistakes** when dealing with their manager?

In this session, Ethan will share strategies and tips to:

1. Build trust with your manager, even if you've had challenges in the past
2. Drive your professional development and earn investment
3. Navigate difficult conversations and manage up effectively.

[**Ethan Evans**](https://www.linkedin.com/in/ethanevansvp/) managed teams of 800+ while a Vice President (VP) at Amazon. Across 15 years, he grew from manager to Vice President, providing executive leadership for multiple $500M+ businesses. In that process, he's managed hundreds of people directly across dozens of changes in his own management chain.

Ethan is now a career development expert and teacher. Watch his course about layoffs on Taro: [**Make The Most Of A Layoff: Maximize Your Severance Package**](https://www.jointaro.com/course/maximizing-a-severance-package/)

Learn more:

- Watch the [**interview series with Ethan about eng management on YouTube**](https://www.youtube.com/watch?v=V8McoEVUiYQ&list=PLMrAfqhZjqfIkD-0p0tJ_zqvPnBdYsixT&index=4).
- Ethan's live cohort-based course "Stuck at Senior Manager" is open for enrollment now: [**https://maven.com/ethan-evans/break-through-to-executive**](https://maven.com/ethan-evans/break-through-to-executive)
- Taro members get a discount to join [**Ethan's Level Up community**](https://levelupwithethanevans.substack.com/taro25)

Come Up With 500k+ User Project Ideas [Part 18] - Go Deeper: Follow Through

Join Alex for Group Office Hours (check the bottom right): <https://www.jointaro.com/p/alex-chiou/>

Share your side project idea in the Taro forum: <https://www.jointaro.com/questions/create/>

Community member made summary of the course: [Side Project Ideas - Summary Doc](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/courses%2Fgeneral_resources%2F%5BSUMMARY%5D%20Side%20Projects%20-%20Coming%20Up%20With%20An%20Idea.pdf?alt=media&token=d7a9aa4e-c02d-4663-ac91-a09547428fe2)

Related courses:

- [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- [Get More Interviews: Write A Stellar Resume As A Software Engineer](https://www.jointaro.com/course/get-more-interviews-write-a-stellar-resume-as-a-software-engineer/)

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

Break Into Tech And Become A Software Engineer [Part 1] - Intro

In this lesson, we explore how anyone can transition into a tech career, regardless of their background.

This lesson covers:

- Brian's journey from a troubled past to becoming an engineering manager and business owner
- How his late start in tech, at age 30, began with small interactions while driving for Uber
- The decision to attend a coding bootcamp, where his passion for coding took off
- The importance of support from friends and community in learning to code and landing a first job
- The idea that people from all kinds of backgrounds, including those with difficult pasts, can break into the tech industry

If you need extra help breaking into tech, join Brian's exclusive, cohort-based bootcamp (just 10 students per batch). Use this link for Taro users for $800 off: <https://www.parsity.io/taro>

Connect with Brian on LinkedIn: <https://www.linkedin.com/in/brianjenney/>

21 Ways to Make Yourself a Better Engineer (From a Senior Engineer at Pinterest)

Join Taro and [**Jordan Cutler**](https://www.linkedin.com/in/jordancutler1/), a Senior Engineer at Pinterest and [**High Growth Engineer**](https://read.highgrowthengineer.com/) author to learn 21 rapid-fire ways to become a better engineer. You'll learn the top underused tips and skills to grow in your career.

We'll cover:

- Career growth
- Influence
- Communication
- Managing up
- Leading projects
- Technical skills
- Productivity

Be ready for practical and actionable advice. No BS included.

Helpful links: 

- [Slides](https://drive.google.com/file/d/1PEgnDJEa4wRw3bjxe22obyfP2qSm9lBB/view?usp=sharing)
- [Jordan on LinkedIn](https://www.linkedin.com/in/jordancutler1/)
- Jordan's newsletter with 68K+ subscribers: [High Growth Engineer](https://read.highgrowthengineer.com/)
- Jordan's course on Taro: [Become The Go-To Expert As A Software Engineer](https://www.jointaro.com/course/become-the-go-to-expert-as-a-software-engineer/)

Maximize Your Productivity As A Software Engineer [Part 8] - Touch Grass

Let's be real: Most software engineers are out of shape. While this isn't too bad early on, things quickly get worse. This lesson teaches you:

- How to get into exercising as easily as possible
- The many benefits of regular exercise
- A way to hack your brain to make yourself more likely to exercise

Write A Stellar Resume As A Software Engineer [Part 2] - Why You NEED A Killer Resume

As a software engineer, there are a million different things you can do. Choosing the right things to work on from engineer to engineer, but the good news is that having a great resume is one of those right things for every engineer. This lesson teaches you:

- Why optimizing your resume is one of the highest return on investments you can possibly do
- Understanding the overall job search funnel and how a good resume fits within it

Master The Behavioral Interview [Part 23] - Just Be A Human

Behavioral interviews are really just an exercise in communication (a skill many software engineers struggle with). This lesson teaches you:

- The difference between being an introvert (this is fine) and shy (this is really bad for your career in tech)
- The right mindset to have when it comes to building relationships and the underlying skills necessary to ace behavioral interviews
- The secret behind getting extremely good at communication

To get better at communication, check out our course: [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)

Master The Behavioral Interview [Part 8] - Timing

Behavioral interviews are intense, containing more questions than every other interview type. This greatly affects how you need to talk to pass these rounds as a software engineer. This lesson teaches you:

- Why behavioral interviews are a marathon
- How long you should take per behavioral interview answer
- Tactics you can use to communicate more efficiently

For more advice on communicating concisely: ["How to make communication succinct and more impactful?"](https://www.jointaro.com/question/QDLV5owweJveRLlspOdc/how-to-make-communication-succinct-and-more-impactful/)

Tech Career Growth Videos

Our instructional videos provide software engineers with insights needed for career growth. Masterclasses go incredibly in-depth on a specific tech topic while case studies are real examples from established engineering leaders.