Creating A Portfolio That Makes Recruiters Come To You

Building a personal portfolio looks nice and feels good, but it *rarely* helps engineers find jobs. In this video, we cover how you can truly stand out as a software engineer and make the jobs come to you (instead of the other way around).

Here are the core points:
- Building a portfolio website can be a nice exercise, but don't spend too much time on it. *Don't expect to get any inbound recruiter reach outs due to your portfolio site*. There is no real central repository of them that recruiters browse.
- In terms of what recruiters do browse, it's primarily LinkedIn. If you have this portfolio energy, it's much better spent polishing your LinkedIn profile instead.
- At the end of the day, a portfolio website is resume++. This means that your foundation is still your resume: Make sure your resume is *extremely* sharp before you even consider building a portfolio website.
- Alex found a lot of success having his Google Play developer page be a portfolio as it hosted real, verifiable products on it. Since his side projects got millions of installs combined, he's gotten reach outs from top companies like Uber, Square, and Instacart through his Google Play developer email.

Related resources:
- ["What technologies or stacks should I create a project to add in my resume for entry level software jobs?"](https://www.jointaro.com/question/c0DiG5ureLbkZ1mKD9Rf/what-technologies-or-stacks-should-i-create-a-project-to-add-in-my-resume-for-entry-level-software-jobs/)
- ["I want to land a job in a big tech as a SWE - How to do it?"](https://www.jointaro.com/question/MWJfUBnnUr8CKYFCO8bp/i-want-to-land-a-job-in-a-big-tech-as-a-swe-how-to-do-it/)
- ["Can Github stars grab big tech recruiters' attention?"](https://www.jointaro.com/question/XaUn4XuIBMSmrr5fcHIT/can-github-stars-grab-big-tech-recruiters-attention/)

Junior Engineers, Avoid This Fake Growth Trap

What's the main change in expectations when growing into senior engineering levels?

True or false: Hustling (i.e. working extremely hard) is a common, healthy way to get promoted.

Why is it bad if you are able to get promoted to senior levels through sheer ultra-hard work and very high raw productivity?

- A lot of earlier-in-career engineers believe that being a better software engineer is all about coding: If you can write more good code faster, then you are growing.
- This is generally mostly true in the beginning, but then it quickly becomes a toxic way of perceiving growth.
- You will hit walls. There are only so many hours in a day, and you can only type so many lines of code per hour.
- As a senior engineer, you need to focus on multiplicative and deeper behaviors.
- If you are able to have the impact of a senior engineer but are working extremely long hours, you are essentially "faking" the appearance of a senior engineer. This working model is not sustainable, and once you burn out, it's a terrible situation for everyone.

How To Earn Respect Fast - Senior Engineer Onboarding Story

Even if you're onboarding, you can earn respect amongst your team. In fact, you should feel empowered to earn this respect despite being new, especially if you're a senior software engineer.

Here are the core points from the video:
- **Help junior engineers** - This is one of the most effective ways to earn respect on a team as a more experienced engineer. The junior engineers may be more fluent in the code than you are, but if you're a senior+ engineer, there is a reason you have this level: You have certain fundamentals and instincts that are applicable everywhere that junior engineers don't really have.
- **Show your depth** - You won't win with velocity and output when you're new. However, you can win with depth and quality as that's largely a function of your effort and time. If you're a more experienced engineer, think about how you can go deeper into something than everyone else on the team.
- **Alex's senior engineer onboarding story** - Here's how a senior Android engineer quickly made a splash after joining Alex's team back at Instagram.
  - They saw a junior engineer struggling with a very complex text layout bug with the Instagram Android app.
  - They volunteered to help with this bug, even though they didn't have to.
  - After many failed debugging attempts, *they slowly extracted the relevant code line by line into an entirely separate Android app to identify the breaking line*. This was a brilliant tactic that nobody else on the team even remotely considered.
  - This combination of goodwill and extreme software engineering depth earned them a mountain of respect pretty much immediately.

This clip is from our masterclass on how to succeed at a new team or company as a software engineer. [Click here to watch the full thing.](https://link.jointaro.com/9sJzfDeH3JdWzZRg9)

Related resources:
- ["How can I quickly gain respect among my team as a senior engineer?"](https://link.jointaro.com/i9j4dtohx2bXc2Sq8)
- ["How do you network effectively within a company?"](https://link.jointaro.com/Hr1nr53D7sfQAEv3A)

How To Get FAANG Interviews

Getting into FAANG is the dream of most software engineers in the world. However, it's much easier said than done, and there's a lot of misinformation about what Big Tech companies look for in interview candidates.

Here are the main points from the video:
- **It's near impossible to break in as a junior dev** - The demand (i.e. the number of junior engineers looking to break into FAANG) far outstrips the supply (the number of L3 and SDE 1 level FAANG openings). If you don't have a warm lead like a strong referral, a DEI program you qualified for, a Big Tech internship to covert, or a career fair at your prestigious university, you can easily spend hours applying into a black hole. *If you've already tried many times and you can't get in, just stop.* 
- **You don't need to get into FAANG right now** - Your career is a marathon, not a sprint. You can get into FAANG later in your career; don't compare yourself to others who made it in early and become obsessed with Big Tech. Focus on growing yourself as a software engineer, and you will eventually make it in.
- **Get past 2 YOE** - If you live in a relevant geography (e.g. SF Bay Area, London) and have more than 2 years of experience, Big Tech companies will generally start reaching out to you. This is because hiring junior engineers is very risky, and Big Tech generally likes to rely on converting interns to fill out that pool. Once you cross 2 YOE, you are considered mid-level and a more worthwhile hire.
- **Build massive side projects** - There is one "nuclear" level you can pull if you really want to get into FAANG ASAP, and that's making a side project with 10k+ users. Alex was able to do this, and he knew a few college dropouts who got into FAANG early doing the same. [Here's our masterclass on how Alex built side projects with 500k+ users](https://link.jointaro.com/fGuprKS4HT7VpVBL9).
- **Make major open-source contributions** - Big Tech has very strong open-source culture, so they have a lot of public libraries you can contribute to on GitHub. They monitor the pull requests into these libraries for potential talent, and many engineers get in that way. However, this is much easier said than done, and side projects are generally more approachable for junior software engineers.

Related resources:
- [The Pros And Cons Of Working At FAANG And Big Tech](https://link.jointaro.com/bw1bEKRxmZPXKiQP9)
- ["What technologies or stacks should I create a project to add in my resume for entry level software jobs?"](https://link.jointaro.com/A9Vugp1jcNQEsvaMA)
- [How To Ace Your Big Tech Interview [Data Structures & Algorithms]](https://link.jointaro.com/iTNxPCvkdGite4wT9)

The #1 Thing To Remember With Meetings

Which is the core principle you have to remember with meetings?

True or false: It is safer to just keep attending a meeting series, even if you are not clear exactly what value you are getting from it.

You have a meeting series where there is always action, but there is usually an awkward portion at the end where people run out of topics. What should you do?

True or false: When in doubt of a meeting's value prop, just delete it. You can always bring it back later.

You have a 1 on 1 meeting series, and by the time of the meeting, you feel like there are a lot of issues that you two are getting to too late. What should you do?

Software engineering is a inherently collaborative exercise, so every tech company is going to have meetings. The tricky part as a engineer is figuring out how to use them effectively: Navigating meetings incorrectly leads to mountains of wasted time.

Here are the key points from the video:

- Meetings are *extremely* expensive as it's the most valuable resource people have: Time.
  - This is why you need to be very aware of how productive meetings are for you. Don't just go to them blindly because you are on the meeting invite - This is a common failure mode for earlier-in-career engineers.
- If a meeting has value but isn't fully efficient, consider lowering the frequency or length of the meeting.
- Reflect on the value of every meeting, especially team meetings since they suck up the most time.
- *Lean towards deleting meetings or not attending them* - If you're unsure what value you got from a meeting, there's a good chance the meeting isn't actually helping you.
  - You can always run an "experiment" here. Remove the meeting from your calendar for a week and see if anything breaks - If the lack of alignment gets bad, you can put the meeting back.

Related resources:

- [\[Course\] Effective Communication For Engineers](https://www.jointaro.com/course/effective-communication-for-engineers/)
- ["How can I be more active in meetings and earn the respect of senior engineers?"](https://www.jointaro.com/question/RtISfsqipLWBhZxvyl69/how-can-i-be-more-active-in-meetings-and-earn-the-respect-of-senior-engineers/)
- ["I have anxiety when speaking up in meetings - how do I overcome this?"](https://www.jointaro.com/question/T1eEbbVZo1fuvbhCDXST/i-have-anxiety-when-speaking-up-in-meetings-how-do-i-overcome-this/)

DSA Prep Is One Of The Highest ROI Activities On Earth

If you do a good job studying for your data structures and algorithms interview, you can set yourself up financially for the next few years.

Related resources:
- [[Taro Top 10] Effective Interview Prep](https://www.jointaro.com/playlist/HLBYxJI7D1j8STolrwum/)
- [[Taro Top 10] Finding A Tech Job](https://www.jointaro.com/playlist/E6R0wVJ5EyCfVnVrlfno/)

Acing Tech Interviews In A Bad Job Market

Here are the core points from the session:

- **Organize and track your job search** - Every successful job search is split up into the 2 overall steps of *"Get interviews"* and *"Pass interviews"*. It's crucial to figure out which step you're struggling with as the solutions for each phase are wildly different. If your conversion rate from application -&gt; interview opportunity is less than 5%, that's a sign that you need to improve at the *"Get interviews"* step. Use a spreadsheet to keep track of how all your opportunities go, so you can construct a funnel and figure out which stage of the offer journey needs shoring up.
- **Have the right mentality** - *Do not view interviews as a "make or break" opportunity, even if they are!* When you put that much pressure on yourself during an interview, you become extremely high-strung and your performance tanks, particularly when you get a problem that you have never seen before (which is guaranteed to happen for any good tech company). Instead, go into every interview relaxed and view it as a fun learning opportunity where you get to hang out with very talented engineers. Having the wrong mentality is one of the most common reasons engineers fail FAANG interviews: Alex interviewed tons of candidates back at Meta where they had the skills and knowledge but they completely fell apart during the interview.
- **Learn how to cold message** - Too many engineers send generic cold messages to Big Tech recruiters, which is a complete waste of time. Cold messages really only work when you're doing it with a smaller company (&lt;250 employees) and putting actual effort into the message. Spend 10-15 minutes actually trying out that company's product and show that you've done that homework in your cold message.

Check out the full 4.5+ hour course diving even deeper into this session's concepts: [\[Course\] Ace Your Tech Interview And Get A Job As A Software Engineer](https://www.jointaro.com/course/ace-your-tech-interview-and-get-a-job-as-a-software-engineer/)

Get Taro Premium at a discount with our special link here: <https://www.jointaro.com/r/achiou15/>

For more job searching resources:

- ["How to get referrals?"](https://www.jointaro.com/question/FQIi8us9uoTDIYdzMhvg/how-to-get-referrals/?playlistId=roKqDHgxu4C5CioEFpJY)
- ["How to get interview calls?"](https://www.jointaro.com/question/MWJfUBnnUr8CKYFCO8bp/i-want-to-land-a-job-in-a-big-tech-as-a-swe-how-to-do-it/?playlistId=roKqDHgxu4C5CioEFpJY)
- ["What are the best websites for applying for tech jobs?"](https://www.jointaro.com/question/VkuG4W88SZ83Ek7AfLP6/what-are-the-best-websites-for-applying-for-tech-jobs/)
- ["How to figure out why I'm not passing onsite interviews?"](https://www.jointaro.com/question/CdmrIsMFPFbsRqRUvueu/how-to-figure-out-why-im-not-passing-onsite-interviews/?playlistId=IPFmEPUhAmizNe9ZUWV5)
- ["I want to land a job in a big tech as a SWE - How to do it?"](https://www.jointaro.com/question/MWJfUBnnUr8CKYFCO8bp/i-want-to-land-a-job-in-a-big-tech-as-a-swe-how-to-do-it/?playlistId=roKqDHgxu4C5CioEFpJY)

How Do Effective Engineering Leaders Help Their Teams Achieve More?

3 questions engineering leaders ask to increase the impact of their team without burning the midnight oil: 

1. What parts of this project are most critical? Who is most important for success? 
2. Can I optimize/shortcut some part of this project? 
3. Can I propose scope reductions for this project? 

Rachel also talks about the iron triangle often used for project management (time, scope, cost).

For more resources on engineering leadership:
- [This Is Why Most Engineering Managers Are Terrible](https://www.jointaro.com/lesson/4NJbAn0uTDUPfYfa859V/this-is-why-most-engineering-managers-are-terrible/)
- [[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/)
- [[Case Study] Becoming A Tech Lead Again In Just 1 Month After Joining Robinhood From Meta](https://www.jointaro.com/lesson/X8vpfJooDpsX915ouC00/case-study-becoming-a-tech-lead-again-in-just-1-month-after-joining-robinhood-from-meta/)

[Masterclass] How To Have Impactful 1 on 1 Meetings

Related resources:
- [[Taro Top 10] Communicating Effectively As An Engineer](https://www.jointaro.com/playlist/yJ6oybePeu93sDSZ1GiQ/)
- [How To Effectively Leverage Skip Level 1:1s](https://www.jointaro.com/lesson/TToehFEc738PBhJcALwL/how-to-effectively-leverage-skip-level-11s/)
- ["Coffee Chat Questions With a Tech Lead - What to ask?"](https://www.jointaro.com/question/jGNZthqhvzYPiMckPEl1/coffee-chat-questions-with-a-tech-lead-what-to-ask/)
- [Presentation Slides](https://docs.google.com/presentation/d/1O1bUrK1NgyfYoMkIqCFJ0SvXv-IQlPhP1gYzBp95abU/edit?usp=sharing)

[Masterclass] How To Ace Your Big Tech Interview - System Design

System design is a crucial software engineer interview skill, especially for FAANG and Big Tech in general. It is effectively a requirement to be leveled at a senior software engineer or higher and will show up in mid-level engineer interviews as well (with the occasional appearance in even junior engineer interviews). The cool thing about system design (unlike data structures and algorithms) is that it's something you actually need to do on the job.

Here are our Top 5 points from the session (in no particular order):
- **Leverage engineering blogs of top companies** - And if you're applying to one of these companies, definitely read their blog. This will help you understand their high-level design and gives you a real-world example to anchor off of, as opposed to something more abstract and high-level that you would get from a traditional book.
- **Do NOT write code** - System design is a *high-level* exercise meant to gauge seniority. Writing raw code is the mark of a more junior software engineer, which is why you should never be writing code in a system design interview. Instead, draw boxes with arrows where the boxes represent components and the arrows represent how they interact.
- **There is no right answer** - One of the main reasons software is hard is because of how open it is. For any complex technical problem, there will be several good solutions, each with varying tradeoffs. System design is not like school or DSA where there is a singular right answer.
- **Understand the problem requirements** - System design problems are, by design, very open-ended. For example, if you get "Build the Twitter feed", there are so many features that make it up: There is no way you can design the entire thing in 1 interview round. Work with your interviewer to understand the scope of the problem and which parts should be prioritized.
- **Follow mature software principles** - The 5 covered in this presentation are robustness, scalability, performance, extensibility, and resiliency. Don't just get the happy flow working - Think about how your system will react when edge cases are hit and things go wrong.

Related resources:
- [How To Ace Your Big Tech Interview [Data Structures & Algorithms]](https://link.jointaro.com/iTNxPCvkdGite4wT9)
- [System Design Series: Taro Playlists [Part 1] - What REAL System Design Looks Like](https://link.jointaro.com/4obaFizTZAdAcStY6)
- [Presentation slides](https://docs.google.com/presentation/d/1z4yX5LiiSxbHiNrBOTPIiDfhBL5qmwRUrDojT71OROY/edit)

[Masterclass] How To Choose A Good Company And Team As A Software Engineer

Choosing the right company (or team) is one of the highest leverage decisions you'll make in your career, so it's worth doing some reflection!

It’s all about your priorities

- Figure out what’s important to you and what’s not. Create a stack-ranked list of all of these and work backwards from the top 2-3 to figure out the best opportunities for you
- People don’t realize how many angles there are to this. Here’s all the ones from the presentation: *Compensation, work-life balance, company prestige, supportiveness of team, growth opportunities, stability, maximum outcome (risk), remote work, product space, company ethics, technical space, level/title, benefits, location*

Supportiveness and overall quality of the team are often underrated

- It’s really hard to grow and have a healthy work life without this
- If you like your manager/teammates and you feel like you’re regularly learning/being challenged by them, deeply cherish that. People underestimate how hard it is to find an environment like this. Even in a prestigious company like Big Tech, this is difficult to find.

Big Tech vs. Startups

- At the end of the day, it’s all about your risk tolerance - Startups can have insane monetary/promotion outcomes, but they also might collapse the next year.
- In a vacuum: Start off at a Big Tech company to build a good foundation and then switch into smaller companies to have more scope/ownership

Some things you should NOT spend time on:

❌ Don't focus on how much you liked (or did not like) the people in the interview process. The recruiter/interviewer is NOT representative of your life at the company. Instead, focus on trends of the people joining the company, rather than individual data points.

❌ Don't spend time looking at the financials of the company. Even if you do decide to dig into the numbers, there's a good chance you'll screw up the interpretation -- humans have a really hard time with exponential growth.

Learning the quality of a team

- Talk to engineers/ICs if you can - The manager will inherently be biased towards their own team as they are often goaled on hiring
- Make sure that the team has a healthy oncall process and fast code review iteration

Related resources:

- [\[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/)
- [“How can you tell if a large public company is going in the right direction?”](https://www.jointaro.com/question/TrlweQQ7DveTnYBP9VUH/how-can-you-tell-if-a-large-public-company-is-going-in-the-right-direction/)
- [“What does it mean to not have enough scope to be promoted?”](https://www.jointaro.com/question/bJuagPwOEEy5vkcXKkqh/what-does-it-mean-to-not-have-enough-scope-to-be-promoted/)
- [“What should I look for in a new team in terms of growth?”](https://www.jointaro.com/question/i2bOMPrqaRc0NUZ7918F/what-should-i-look-for-in-a-new-team-in-terms-of-growth/)
- [Presentation Slides](https://docs.google.com/presentation/d/1S_kULq5zzVLkcoKy0bKJ2IHSrjL3s2VbOLe8p1TQJ7s/edit?usp=sharing)

A Powerful Tool For Software Engineer Productivity - Focus Blocks

So many junior software engineers don't manage their calendar well, and this especially hurts their ability to write code and finish tickets efficiently. Don't blindly go into every meeting, especially as a junior software engineer who is often not relevant to the meeting. Be deliberate with your calendar and establish focus blocks.

Here are the core points from the video:

- **So what is a focus block?** - It's a long, uninterrupted period of time for you to focus on a singular track of work. A true focus block should be 4+ hours, ideally an entire work day.
- **Why are focus blocks important for coding?** - Humans are naturally bad at context switching, so focus blocks are just important for productivity in general. Having a focus block allows you to enter a "flow state" where you rate of work ramps up over time and you get more and more into the groove. When it comes to coding in particular, the focus time is crucial as context switching with code is especially painful. It takes a while to deep back into a codebase when you return to a coding task, and there's also practical reasons like rebasing your local and setting up your build environment again.
- **How can I set up a focus block?** - The main "culprit" behind hurting your focus blocks is meetings. Be aggressive about shaving meetings off your calendar where you aren't a core player, especially if you're earlier-in-career. Group the remaining meetings you have onto certain days with the goal of freeing up 1-2 days entirely for coding. 1 on 1 meetings will be the easiest to move. For the meetings you do end up going to, [follow this advice to really participate and get maximum value out of them](https://www.jointaro.com/question/3E3SBCa59z5oDb7AEciw/i-struggle-to-come-up-with-things-that-add-value-to-a-meeting-what-do-i-say/).

Related resources:

- [\[Masterclass\] How To Manage Your Time Optimally In Tech And Achieve More Results](https://www.jointaro.com/lesson/rnX9EKpzc43TgGW9MozG/masterclass-how-to-manage-your-time-optimally-in-tech-and-achieve-more-results/)
- ["How do I optimize my sacred hour at work?"](https://www.jointaro.com/question/l8dzUVTu99CahofQsYAi/how-do-i-optimize-my-sacred-hour-at-work/)

[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 do you get the most out of mentorship?"](https://www.jointaro.com/question/IbuZydz0QzsVVqESVaxQ/how-do-you-get-the-most-out-of-mentorship/)

Ace Your Tech Interview As A Software Engineer [Part 1] - How This Course Works

Let's not mince words: Looking for a job as a software engineer is *brutal*. It is so easy to lose heart on the journey and stop believing in yourself. This video (and broader course) will solve that for you by giving you the tools to overcome any job search adversity and stand out from the hordes of other candidates. 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 across top companies like PayPal, Course Hero, Meta, and Robinhood, explaining how he increased his TC (total compensation) by a whopping +800% across just 7 years and led thousands of engineers to interview success at top companies like Meta, Google, and Amazon.
- You'll understand why the existing landscape about interview preparation resources fails software engineers so miserably, particularly when it comes to data structures and algorithms (DSA) and LeetCode.
- We walk you through the course objectives. By the end of the course, you will understand how to organize your job search, learn interview skills properly, get job opportunities effectively, follow a framework to come prepared into any interview, and understand all the common software engineer interview round types.

If you want to learn how Alex cracked the FAANG interview, you can check out his story 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/)

[Masterclass] How To Write A Stellar Tech Resume That Gets You More Job Opportunities

Writing an effective resume is crucial for succeeding within the tech industry, especially for software engineers. It's the primary step you need to clear before getting a chance with an interview opportunity. Unfortunately, there is a lot of misinformation around how to write a good resume: For 80%+ of junior software engineers struggling to break into tech, a poorly written resume is one of the main causes.

All that being said, here are our Top 5 points from the sessions (in no particular order):
1. *Remember that a recruiter is reading your resume and will, on average, only spend ~10 seconds on it*
    - They are almost certainly non-technical. Make things very accessible and easy to understand: Avoid jargon!
    - Be ruthlessly concise. For the vast majority of cases, your resume should only be 1 page.
2. Having a spelling or grammar mistake is the easiest way to get your resume thrown out
    - You have an effectively infinite amount of time to polish your resume. If you can't even catch basic mistakes like these, it shows that you have poor attention to detail or bad prioritization.
3. Show, don't tell
    - Don't just say that you're great, prove it
    - Example: Talking about the Android apps you've built with 100k+ users is much more effective than just saying you're a great Android engineer
4. Traps to avoid:
    - Having a summary section at the top
    - Self-rating yourself across skills
5. In the end, your resume needs to be approved by a human, not just an ATS
    - Making your resume very weird to "optimize" for the ATS is the epitome of winning a battle to lose the war. It's pointless

For an effective example + template you can use, [check out Alex's latest resume here.](https://firebasestorage.googleapis.com/v0/b/tech-career-growth.appspot.com/o/articles%2FAlex%20Chiou%20Resume%20-%20FINAL%20FOR%20SHARING.docx?alt=media&token=3a75b8b2-09e8-4b68-b80d-22761055c3b2) You can import it into Microsoft Word online and swap out all of his content with yours.

Related 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/)
- [Presentation Slides](https://docs.google.com/presentation/d/15eLqE_WmePLA--lYTG0ZJVcHhpEld2qNTck_w0t_E9k/edit?usp=sharing)

Truly Mastering A Data Structures And Algorithms Problem  - 2 Sum Example

Why is the following not a good way to remember the solution to 2 Sum?
        
def twoSum(self, nums, target):
    required = {}
    for i in range(len(nums)):
        if target - nums[i] in required:
            return [required[target - nums[i]],i]
        else:
            required[nums[i]] = i

Why is [Look for the difference and use a HashSet] a great way to remember the solution to 2 Sum?

What more general higher-level learning principle is also exercised alongside the proper mastery of data structures and algorithms problems?

Data structures and algorithms are a core part of FAANG software engineer interviews, and they're seemingly the bane of every software engineer's existence. However, so many software engineers don't learn these concepts properly.

Here are the core points from the video:
- In this example, we cover 2 sum, a classic data structures and algorithms problem that many companies use on phone screens. Here's how to learn it properly:
  - **Bad:** Memorizing all the code behind the optimal implementation.
  - **Good:** "Look for the difference and use a HashSet."
- All DSA problems will have this core insight that "unravels" the entire thing. Once you find and truly understand this insight, the implementation should flow naturally.
- This is also a sign of higher learning via "thinking in terms of abstractions". Your brain is a lot more powerful if it is able to take something more singular and high-level and convert it into the nitty gritty. Memorizing everything at the lowest level simply isn't scalable.

Related resources:
- [[Masterclass] How To Ace Your Big Tech Interview - Data Structures & Algorithms](https://www.jointaro.com/lesson/V4sTACzfOh22nMVcUV3w/how-to-ace-your-big-tech-interview-data-structures-and-algorithms-7172021/) - This is the full video this clip is taken from
- [[Masterclass] How To Ace Your Big Tech Interview - System Design](https://www.jointaro.com/lesson/J3I9fTW9ulr6T9KjxpqY/how-to-ace-your-big-tech-interview-system-design-1162021/)
- [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/)

3 Ways To Write Deeper, More Impactful Code Review Comments

In this video, we explore how to give more impactful code reviews by moving beyond surface-level feedback and investing in deeper understanding and learning from experienced peers. The focus is on practical habits that help us become more thoughtful, effective reviewers.

- **We rely on automation for style and formatting.** It's not our job to catch syntax or stylistic issues—those should be handled by IDEs and CI systems with pre-agreed style rules.
- **We review code with a clear perspective.** Before reading the diff, we mentally plan how *we* would solve the same problem, which helps us offer more meaningful, constructive feedback beyond just approving what “looks fine.”
- **We learn by watching the best.** One of the fastest ways to improve as reviewers is to observe how senior engineers reject code—what they flag, how they communicate, and the patterns they look for.
- **We replicate good habits.** By studying thoughtful reviewers—like those who consistently flag performance issues like mobile frame drops—we can develop our own review instincts and level up faster.
- **We treat reviewing as an intentional skill.** There are no shortcuts; it takes practice, pattern recognition, and curiosity to become great at it. But by mimicking smart peers, we shortcut years of trial and error.

This Is How You Get Feedback - Making The Process Smooth

The best way to improve as a software engineer is to get feedback, especially when you're new to a team or company. However, this is much easier said than done - Simply having the mentality of being open to feedback isn't enough.

Here's the core points from the video:

- **Don't just ask "Do you have any feedback for me?"** - The cognitive load for the person you're seeking feedback from is simply too high: They need to mentally comb through everything you're doing and then think through every aspect of it to find feedback to give you. Instead of doing this, they'll often default to the "lazy" response of "Nope, you're doing great!". Lazy inputs result in lazy outputs, and you definitely shouldn't be lazy when asking for feedback.
- **Reduce feedback requests to yes/no questions** - Regularly retrospect on your own and use that to craft more pointed questions when asking for feedback. Let's say you're not happy with how clean your code is, evidenced by a lot of pushback when you submit it for review. Using this, you can ask something like, *"I feel like I could do a better job polishing my code; my PRs get a lot of thrash. Do you think I can improve here?"* If they say "Yes", you can then ask for tactics you can apply to get better here.
- **Core areas for onboarding feedback**
  - Overall velocity and output
  - Code quality
  - How good your questions are

Related resources:

- [Suppress Your Instincts And Treat All Feedback As A Gift](https://www.jointaro.com/lesson/dpTu1KBbXJdnHdrQLxsG/suppress-your-instincts-and-treat-all-feedback-as-a-gift/)
- [How To Get Real Feedback So You Can Actually Improve](https://www.jointaro.com/lesson/srTbalkn0HMwEH7HoOpY/how-to-get-real-feedback-so-you-can-actually-improve/)
- ["How can I find more opportunities to grow when I'm getting very little real feedback?"](https://www.jointaro.com/question/7nrslKZuiFdYeutpeX5k/how-can-i-find-more-opportunities-to-grow-when-im-getting-very-little-real-feedback/)

What Gets Communicated Gets Done: Why Slack Sucks

You Should Be Vulnerable With Your Manager

You are feeling burnt out at work. Should you share this with your manager?

You feel like you are slower than your other teammates and are afraid that you look bad amongst the team. Should you share this with your manager?

Your dog just died, and you are having a really tough time concentrating at work because of this. Should you share this with your manager?

Here are the core points from the lesson:

- Your manager is responsible for your performance at work. Therefore, it's in their best interest to help you resolve anything that is negatively affecting your work performance, even if it's something non-tactical.
- If you are having a deeper issue (e.g. you have imposter syndrome), this is something you should talk with your manager about. You shouldn't expect them to act as a full psychologist, but they should at least be receptive of your problem and lend an understanding ear.
- Venting and complaining are very natural and can act as a therapeutic exercise. Don't be afraid to do this with your manager once you have a good enough relationship.
- This gets easier over time. Once you start being honest and more transparent in your manager meetings, the trust between you two increases, making it smoother to continue being open in the future.

Related resources:

- [\[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/)
- [\[Course\] Networking Guide: Build Deep Relationships Quickly In Tech](https://www.jointaro.com/course/networking-guide-build-deep-relationships-quickly-in-tech/)

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.