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

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

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

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

[Case Study] Solving A Multi-Million $$ Instagram Bug

- A big part of moving from L4 (mid-level) to L5 (senior level) is being able to create your own scope. You can't just expect a perfect suite of projects to come from your manager.
- Like in this session's case study, bugs are a great source of finding your own scope!
- The bug was very slight: Instagram story ads started off on the wrong part when they were resurfaced to a user. As an Android engineer, Alex discovered this in IG Android initially. This bug had been in production *for over a year* at this point.
- How Alex expanded the scope after finding this bug:
  - Worked with iOS to see if the bug was there (it was)
  - Worked with PMMs to confirm that this violated the advertiser contract and merited a refund. This made the bug an immediate SEV.
  - Worked with a data scientist to figure out exactly how many times this bug occurred and calculate the exactly refund to advertisers ($2M+)
  - Put the fix behind an A/B test to measure impact and make sure it was working
- How you can incorporate the learnings from this case study:
  - Be detail-oriented. At Big Tech in particular, seemingly small issues can have massive impact.
  - Don't just silently fix bugs. Take the time to figure out its entire scope - It could be a SEV!
  - Understand the world outside of yours. Look for opportunities to bring in others (especially those of different roles) into what you're working on to expand scope for everyone!

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

For more resources around creating scope:
- ["How do I come up with innovative, impactful ideas and bring them to my team?"](https://link.jointaro.com/uBcb5LjZiD5DasfB9)
- ["How can I come up with big initiatives, especially those at a Staff level?"](https://link.jointaro.com/6MWig3VSr3nVo81w9)

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

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

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

[Case Study] Effective Communication: Leading A Multi-Org Re-architecture At Meta

Here are [the presentation slides](https://docs.google.com/presentation/d/184dP9pi41lO5TlME4cn4fRblCPtKFdet7d5WmrpnbGc/edit?usp=sharing) and the [polished chat log](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/tps_chats%2Ftaro_premium_session_4_chat_notes.txt?alt=media&token=ca1a199d-fe36-42bc-8d2e-fc91371e691f) from the session.

As an IC, you don't have authority over engineers in the way a manager might. So your impact is defined by your ability to have **influence without authority**. Influence comes from consensus + collaboration, which comes down to communication. Said another way: Communication is the foundation for trust. 

Rahul talked about 3 parts to effective communication in this presentation: 
- **Start with the audience**
  - Understand how much context your audience has, and connect the dots for them.
  - Your communication should be as short as possible.
  - Bad news should never be a surprise.
- **Choose the right medium**
  - Do some reflection on what your objective is: build relationships or efficiently communicating some info? Be clear the difference between verbal and written communication.
  - Evaluate the current processes for communication in your org: standups, team meetings, email updates, cross-org communication. 
- **Be consistent**
  - You should have a regular drumbeat of posts for your projects. If you feel like nothing happened, you should explain why nothing happened.
  - For long-running processes like brainstorms or architecture reviews, you should consistently message the timeline and milestones.

Related resources:
- ["How can I come up with big initiatives, especially those at a Staff level?"](https://link.jointaro.com/sm57uikgXJ3RRpTv8)
- [Writing is thinking](https://medium.learningbyshipping.com/writing-is-thinking-an-annotated-twitter-thread-2a75fe07fade) - by Steven Sinofsky (Former President @ Microsoft)
- [Be plainspoken](https://boz.com/articles/be-plainspoken) - by Andrew Bosworth (VP of Eng @ Meta)

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

[Case Study] Hypercharging Your Growth At Early Startups (w/ Staff Engineer Seed Zeng)

[Click here for the presentation slides](https://docs.google.com/presentation/d/1ZocNUZJL-feWAKoucVLUcaVxix2Xa1udEL4KpgQRBTo/edit?usp=sharing).

There are a *ton* of great points covered in this session, so we'll only share our Top 5:
- **Startups have massive scope** - In an early-stage startup, there is always an infinite supply of hard, technically deep problems. This allows you to have a lot of freedom choosing an opportunity that works well for you and build up a wide breadth of important skills. This is almost always *not* the case in Big Tech - [Check out this expert career advice on the difference between Big Tech and startups when it comes to learning](https://link.jointaro.com/n57gbTWERveGTQuM9).
- **Don't say "I'm not qualified to work on this"** - The best software engineers are able to adapt to any situation their team faces and add value regardless of what framework or tech stack is needed. In order to do that, you must first flip this fearful mentality. [Here's our masterclass on how to learn quickly in tech](https://link.jointaro.com/S2h95sJvRU8Utjj6A).
- **Don't be afraid to make mistakes** - Recovering from a mistake is one of the most powerful ways to learn, and startups will generally have more tolerance for mistakes as stakes are lower compared to a more mature, massive public company where product issues can make the news. [Here's our advice on how to maximize your growth from mistakes](https://link.jointaro.com/THof1u97Z5t1ovCr9).
- **80% of the journey is just showing up** - Seek out important, complex situations and run towards them instead of away from them, especially with production issues. If you're earlier-in-career, you can learn a lot simply by being a participant in fixing these fires; from there, you can make yourself a core driver more and more. [Here's our advice on how you can be more independent debugging tricky technical problems](https://link.jointaro.com/xE8oMpCaDYjuMhCg7).
- **It's all about the people** - Your career growth is largely a product of the people you surround yourself with, and this is especially true in a startup where the team is small, bonds are deep, and everybody knows each other. [Here's our advice on how to network effectively within a company](https://link.jointaro.com/Hr1nr53D7sfQAEv3A).

To see (and hear) more from Seed:
- [Connect with him on LinkedIn](https://www.linkedin.com/in/seedzeng/)
- [Check out his podcast "Superposition"](https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkLnBvZGJlYW4uY29tL3N1cGVycG9zaXRpb25zaG93L2ZlZWQueG1s?sa=X&ved=0CAMQ4aUDahcKEwjot6up4Zf7AhUAAAAAHQAAAAAQAQ&hl=en)

Related resources:
- [Session #6 - Maximizing SWE Growth: Ownership and Specialization At Startups](https://link.jointaro.com/2ZevbN54MPZPTocH8)
- ["What's the difference between Big Tech and startups in terms of learning and growth?"](https://link.jointaro.com/n57gbTWERveGTQuM9)

[Case Study] How Engineers Unlock Huge Impact With Artificial Intelligence (AI)

This was a joint presentation from engineers who have been using Artificial Intelligence (AI) to become significantly more productive. The result is fewer repetitive tasks, fewer bugs, and more impact. The AI transformation is not some future technology that we are anticipating -- **it's happening now**. ChatGPT is the fastest application ever to reach 100M monthly active users.

We can broadly categorize AI tools into 2 buckets (generative vs analysis). Think about what is most helpful for your job and dig into other tools in that domain.

We focus primarily on productivity benefits from conversational agents like ChatGPT, Bard, and Anthropic. **The first response is usually generic and unhelpful, but simple tricks can make the output significantly more valuable**. Sample prompts: *"How can I send a text message in a Rails app with Twilio?"* and *"How can I show a div in the screen after 15 seconds of inactivity on a webpage?"*

Top 5 prompt engineering tips for Software Engineers: 
1. Ask ChatGPT to list its steps, work, or sources
2. Split your prompt into clear sections
3. Use “unique”, “unconventional”, and “creative” to get better responses
4. Make ChatGPT roleplay
5. Give ChatGPT examples of correct inputs and outputs

Some sample prompts from Jordan's [summary doc](https://www.notion.so/jordancutler/GPT-prompts-90179f5fc49440c6bffaeb94e5cfcb4c?pvs=4): 
- **[Feedback]** "Tell me 5 reasons this feature won’t work as intended"
- **[Engineering]** "Given the following code, write a comprehensive test suite in X testing library"
- **[Learning]** "Explain { topic } as if I am a principal software engineer with 10+ years of experience. Go into deep technical detail and explain how it works under the hood"
- **[Meetings]** "I’m a junior software engineer at a Series A tech company. Can you come up with 10 topics for me to talk with my manager about in our 1-1?"

Here are the top paid tools that the speakers use: 
- [Github Copilot](https://github.com/features/copilot) - $10/month
- [ChatGPT Plus](https://openai.com/blog/chatgpt-plus) - $20/month
- [Notion AI](https://www.notion.so/product/ai) - $10/month

Speakers:
- [Donn Felker](https://twitter.com/donnfelker)
- [Jordan Cutler](https://www.linkedin.com/in/jordancutler1/)
- [Mike Alnakhaleh](https://www.linkedin.com/in/malik-mike-a-32b63818b/)

Related resources on Taro:
- ["How to AI proof your career?"](https://www.jointaro.com/question/3xg5SvXnyTQ0mhNLfbK1/how-to-ai-proof-your-career/)
- ["Using Artificial Intelligence (AI) in side projects?"](https://www.jointaro.com/question/20UiCYH3QwkWkvGTrFsY/using-artificial-intelligence-ai-in-side-projects/)
- ["ChatGPT plugins to your IDE - How to prepare?"](https://www.jointaro.com/question/ZqQiiaPjpzYQ8XKPOQZK/chatgpt-plugins-to-your-ide-how-to-prepare/)
- [The slides for this presentation](https://docs.google.com/presentation/d/1lfMP8qlSix6IDNAUbyraamLgtIHwkxbbQgbpgcBqr2c/edit?usp=sharing)

[Case Study] How I Get 500,000+ LinkedIn Post Views Per Week

[Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) is one of the cofounders behind Taro, and he owes a lot of his success building up Taro to his LinkedIn profile. As of September 2023, he:

- Has 66,000+ followers
- Gets 500k - 1M post views per week
- Spends just 10-15 minutes writing each post

Alex covers a lot of ground in this presentation, so here are just the Top 5 core points:

- **LinkedIn is extremely underrated** - When it comes to return on investment for your time, LinkedIn is easily one of the most effective content creation platforms if not *the* most effective. Unlike TikTok, Instagram, and YouTube which are media-based and require lots more effort, you can regularly go viral on LinkedIn with relatively short snippets of text.
- **Consistency is key** - LinkedIn is pretty generous at allowing you to post many times a week without your posts cannibalizing each other. Try to post at least 3-4 times a week with the upper bound being 2 times a day. If you post too frequently, you are leaving views on the table. Also, you are naturally going to have some posts that do terribly and some that do well: By taking more shots on goal, you are evening out your returns. *Variance can be conquered with volume.*
- **Keep it short, don't be too smart** - This is *by far* the most common mistake Alex has seen aspiring LinkedIn creators make. Engineers tend to be very smart people who love to cover all the nuance, which leads to overly long posts that are neither concise nor dense. This type of content does horribly on social media. Alex's style is to have 5-9 sections (each separated by a line break) with each section being just 1-3 lines for a 30-75 second read. Keep it snappy.
- **Write first sentences, not posts** - The entire purpose of the 1st sentence is to convince the reader to read the 2nd. LinkedIn by default hides the vast majority of your post's text behind the "See more..." button. Purely focus on writing a compelling first sentence, and the rest of the post should flow from there.
- **Never forget: It's just social media** - LinkedIn, like every social media platform with 100M+ users, is full of dumb stuff. *Don't let that get to you*. Don't be afraid to disengage from the platform and not read notifications and comments. And never ever couple your emotional state to how well your social media posts are doing.

Related resources:

- ["Why should I bother building a brand or becoming famous on LinkedIn?"](https://www.jointaro.com/question/s1NVrO0VlvIufReDKCSl/why-should-i-bother-building-a-brand-or-becoming-famous-on-linkedin/)
- ["How to be brave and post publicly on LinkedIn?"](https://www.jointaro.com/question/xUJSnOXQOmJyisZCB0Qa/how-to-be-brave-and-post-publicly-on-linkedin/)
- [\[Case Study\] Building An Engineering Brand - Why And How (LinkedIn, YouTube, Twitter, Substack)](https://www.jointaro.com/lesson/t06NajpS2kSCk98IEmQm/case-study-building-an-engineering-brand-why-and-how-linkedin-youtube-twitter-substack/)
- [How Rigid Should You Be With Your Coding / Content Schedule?](https://www.jointaro.com/lesson/GaOB5qFLoTbGilp7UokF/how-rigid-should-you-be-with-your-coding-content-schedule/)
- [Presentation slides](https://docs.google.com/presentation/d/1-_it2buJQ764fQAf5MgXtIKRrYJPI_ayUv5WdU5cslw/edit?usp=sharing)

[Case Study] Maximizing SWE Growth: Ownership and Specialization At Startups

**Huge** thanks to [Henry Prior](https://www.linkedin.com/in/henryprior/) for joining us and sharing his perspective and insights!

This was a *massive* session, so here are just some of the highlights:
- **Henry's core learning**: Bias towards action. You aren't really going to truly understand what is and what isn't fruitful to you until you just start trying things.
- **Story #1** - At his first startup job, Henry found a project to upgrade from Tensorflow 1 to 2. This ended up moving the metric he cared about, but he found out later that the business impact wasn't great. The company's clients were non-technical and didn't really care about the company's model being ultra-accurate.
- **Story #2** - Found a reinforcement learning project at his next company where he did all the modeling on his own and worked closely with an infra engineer to ship. The work was very complex and had huge impact, saving ~25 hours per week in Data Scientist cycles. He got massive recognition from the company, and this project was a big part of his move to senior.
- You have a lot of autonomy in early stage startups. Take advantage of this and actively look for large problems to solve, doing so as early as the interview process. It's not like Big Tech where you are generally given a good amount of direction on what to do (at least until you get to staff).
- *It's in your best interest to be completely authentic when interviewing with a startup.* It's not like Big Tech where you're putting on a facade to meet their interview requirements. A startup might not be the right for you due to a lack of work in your interest area: Big Tech in contrast has a little bit of everything.
- *If you're going to get into machine learning, you should understand the underlying math first.* This puts you in a much better position to work on the modeling part of ML vs. the more tertiary tasks like data wrangling. The math is a combination of probability/statistics, linear algebra, and calculus.
- **You can't study your way to being good at system design.** Resources like books and blog posts help, but system design is something you very much have to get good at by doing. Instead of just leaping into the code, start planning out your tasks and doing technical writing. From there, share your material with your team and get feedback.

Related resources:
- ["What's the difference between Big Tech and startups in terms of learning and growth?"](https://link.jointaro.com/yzWgzTF4WFzfXjS29)
- ["Does it make sense for me to choose a specialization like ML? If so, what's the impact?"](https://link.jointaro.com/jV34Jz7cJqQv2MpD8)

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

[Case Study] Building An Engineering Brand - Why And How (LinkedIn, YouTube, Twitter, Substack)

Most of Taro's success has come from the social presence of Rahul and Alex. For Rahul, his follower counts as of April 2023 are **75K on YouTube, 61K on LinkedIn, and 13K on Twitter**. Followers are an imperfect measurement of influence, but they are generally correlated. 

### Why invest in brand building?

- Be helpful for others
- Helps you learn more
- Increase your luck surface area
  - Inbound instead of outbound
  - Connect with other creators
  - Compounding value over time

Brand building is definitely *NOT* required to be a good engineer, but it will become more valuable over time.

### Which platform should I invest in?

The options I recommend are **LinkedIn** and **YouTube**. You should pick a platform with built-in distribution. That means a blog is almost always a bad idea (Substack is a bit different since it does have some distribution methods). 

Another dimension to think about is the competition on that platform -- how hard is it to get noticed? 
- Which audience are you trying to reach? (B2B vs B2C, students or professionals)
- How much effort is required to produce content? Videos are much more work than essays, which are much more work than tweets.

You can also take a bet here on a growing platform like TikTok, but there are risks around what kind of content is valued, and the longevity of the platform.

### Getting started as a creator

- Keep in mind the **spotlight effect**: "The psychological phenomenon by which people tend to believe they are being noticed more than they really are"
- Since no one really cares about you when you start out, you should focus on quantity over quality. Just make a lot of content, get feedback, and keep improving. 
- Focus on having your content actually add value. Just reposting articles, or making a list of 20 news articles is not that interesting. (It may get engagement, but you're not actually building a brand.)

### Aim for virality

A significant amount of my growth on LinkedIn came from 3 viral posts: [1](https://www.linkedin.com/posts/rpandey1234_learntocode-softwareengineer-activity-7052287566544306177-sn9R/), [2](https://www.linkedin.com/posts/rpandey1234_softwareengineering-compensation-licreatoraccelerator-activity-6989278004149465088-V-IF/), [3](https://www.linkedin.com/feed/update/urn:li:activity:6917123048710000640/) 

Some of your content will be "conversion" content, designed to get people to take action such as signing up for an email newsletter. These posts won't do as well, but you should also focus on having "distribution" content, which is the type of thing that can go viral. 

Once you have a viral hit, you can also repurpose the content on other platforms in order to maximize the value from it. That's what Rahul did with the "Learn To Code" video that he initially published on YouTube: 
- [YouTube](https://www.youtube.com/watch?v=awB99NJ2G38)
- [LinkedIn](https://www.linkedin.com/posts/rpandey1234_learntocode-softwareengineer-activity-7052287566544306177-sn9R/)
- [Twitter](https://twitter.com/rpandey1234/status/1646060396082790400)

### Practical tips
- Post content deliberately about one domain, e.g. engineering growth. Don't jump between topics. 
   - This is how you build a brand. 
   - Make it clear what value you provide, “e.g. the Car Dealership Guy” or “The No-Code Lady”
- Use content scheduling features to be consistent with posting
- Look up resources on copywriting
   - Start with a number
   - Nail the hook, e.g. *"Let me be clear."*
   - Tell a story: Instead of "A happened and then B happened", say "A happened, but X, so then B happened"

-------------

This is a recording of a Taro Premium session from April 20, 2023. See other discussions about [content creation on Taro.](https://www.jointaro.com/topic/content-creation/)

[What to be careful about when starting a blog or LinkedIn audience.](https://www.jointaro.com/question/O5qwwCqT6SAsWSNqlD2V/making-content-as-a-software-engineer-what-to-look-out-for/)

Supercharging Relationships - Building Bridges With Bosses, Teammates, Mentors, And Tech Leads

Discover the secrets to thriving in complex work environments by mastering the art of navigating workplace politics and dealing with difficult people! Jai explains the pioneering concepts in "Connect" by Dr. Carole Robin and Dr. David Bradford, as well as their acclaimed work at Stanford's Graduate School of Business on Interpersonal Dynamics.

Tailored specifically for engineers targeting senior levels, this masterclass will equip you with the skills and strategies to expertly handle challenging situations and personalities in the workplace. By attending, you will learn how to:
- Recognize and navigate the subtle complexities of workplace politics
- Understand and manage difficult people by identifying their motivations and triggers
- Build trust and create psychological safety with colleagues and superiors
- Effectively giving and receiving feedback
- Managing conflicts and promoting cooperation

Our expert-led session will provide actionable insights and practical tools that you can apply immediately to your professional life. Unlock your full potential by overcoming common obstacles and building strong, effective relationships with your colleagues.

Don't let workplace politics or challenging personalities hold you back. This session will let you take control of your professional success by mastering interpersonal dynamics!

This session was by HashiCorp full-stack engineer Jai Bhagat: [Connect With Jai On LinkedIn](https://www.linkedin.com/in/jaybhagat/)

To go deeper on the subject, here's more great resources around relationship building:
- ["How do you network effectively within a company?"](https://www.jointaro.com/question/DwT9GtdYK9nwFV3a7jrU/how-do-you-network-effectively-within-a-company/)
- ["Working with a micromanager"](https://www.jointaro.com/question/50HJtR05yMOB97LrkiCX/working-with-a-micromanager/)
- [[Masterclass] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

[Case Study] How to Quit Your Job The Right Way (w/ ex-Netflix TL Michael Lin)

[Michael](https://www.jointaro.com/profile/Ab2xedZA7RhROW0wo9wBHIJbAsX2/) famously [quit his $450,000 job at Netflix](https://www.jointaro.com/blog/why-i-quit-a-450k-engineering-job-at-netflix/), and asked for (and received) a severance package in the process! If you're thinking about quitting your job, consider these points **before** leaving: 

### Timing is important
- It’s better to leave on the 1st of the month than the 31st because employee benefits renew on a monthly basis.
- If you leave on the 1st, it’s like getting a full extra month of benefits. 
- But if you leave on the 31st, your benefits may end the next day.

### Quitting is a trade-off
- You’re weighing that the negatives of staying outweigh the negatives of losing out on income.
- If you have to cut vacations, move away from loved ones, and say no to social events, then those negatives may outweigh the negatives of your job.

### Act with urgency
- If your career is not going the right way, take action quickly.
- If you stay an extra two years at a job you wanted to leave and did this over five jobs in your lifetime, that’s ten years of your life spent doing work you never wanted to do.

---------
- Connect with Michael on [LinkedIn](https://www.linkedin.com/in/michael-lin-tech/)
- Subscribe to [Michael's newsletter](https://michaellin.substack.com/)

Related questions: 
- ["Should I request a voluntary layoff to my manager?"](https://www.jointaro.com/question/FnInc1bJ3AUJBz0grFyj/should-i-request-a-voluntary-layoff-to-my-manager/)
- ["Should I quit to prep for interviews?"](https://www.jointaro.com/question/Cno3oaZkvUu7BPLhHB7g/should-i-quit-to-prep-for-interviews/) from a Data Engineer

How To Land 18 FAANG+ Offers With Steven Zhang (Airtable, USDR, Tableau) [October 2023 Version]

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. If you're interested in learning from Steven as part of a cohort-based course about job searching, sign up here: [https://bit.ly/18offers-course](https://bit.ly/18offers-course)

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 original talk on Taro about receiving 18 offers](https://www.jointaro.com/lesson/gGkO4pLeFq1ctRM9tSBF/case-study-how-to-land-18-faang-offers-with-steven-zhang-airtable-usdr-tableau/)
- 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/)

Autism Allyship and Identity in Tech - By Lee McKeeman & Jaswir Raghoe

[Lee McKeeman](https://www.linkedin.com/in/lmckeeman/) and [Jaswir Raghoe](https://www.linkedin.com/in/jaswir-raghoe/) give an insightful talk on Autism Allyship in the tech industry, and how one can discover the power of creating inclusive workplaces for autistic individuals while gaining valuable tips on how to be an effective ally to autistic colleagues.

Lee and Jaswir talk about how autism is a spectrum with individuals having a wide range of abilities and needs. They give a deeper understanding of general biases and assumptions about autism, and learn why it's crucial to challenge them. They expound on the importance of asking autistic individuals about their preferences and needs, while understanding the significance of respecting their boundaries. Jaswir and Lee uncover the value of patience and understanding, as well as the importance of not expecting autistic individuals to always conform to social norms.

Join us in celebrating the diversity of autistic individuals and learn how you can become an advocate for their inclusion in the workplace.

Don't miss this enlightening talk that will empower you to create a more inclusive and supportive environment for all.

Incase you missed it, also check out Lee McKeeman's previous talk about his career journey: [An Autistic Journey To Google Staff Engineer [L6] From Software Analyst](https://www.jointaro.com/lesson/nujUVma6boGJxGAQzoiX/an-autistic-journey-to-google-staff-engineer-l6-from-software-analyst-by-lee-mckeeman/)

Taro Book Club: The Pragmatic Programmer - Session 4

Session led by: [Bikram Kashyap](https://www.linkedin.com/in/kashyapbikram/)

In this #taro-bookclub discussion, we'll further go over [**"The Pragmatic Programmer"**](https://www.amazon.com/Pragmatic-Programmer-Journeyman-Master/dp/020161622X) by Andrew Hund & David Thomas.

Here's the agenda:

- Power of Plain Text
- Shell Games
- Power Editing
- Version Control
- Debugging
- Text Manipulation
- Engineering Daybooks

Please send your questions ahead of time to [**Bikram Kashyap**](https://www.linkedin.com/in/kashyapbikram/) in the [**Taro Premium**](https://www.jointaro.com/membership/) Slack, so that they can be included in the discussion. [***If you don't have the book***](https://taropremium.slack.com/archives/C05CKBHPNTU/p1723491587867879) *or want more details on how this all works, check out the #taro-bookclub channel in the Taro Premium Slack as well!*

Get ready for another engaging and informative session!

Taro Premium Sessions Q&A and Videos

About Taro Premium Sessions