How to Crack System Design Interviews - Part 7: System Design Scorecard

This video explains how candidates are evaluated and scored in system design interviews at large tech companies. We learn about the scorecard used to assess performance across five key parameters:

- **Problem Scope:** This includes listing and clarifying product requirements, discussing user interactions and expectations, and considering system scale.

- **Technical Design:** This involves making appropriate design choices, leveraging design patterns, and demonstrating knowledge of relevant technologies.

- **Scalability:** This encompasses designing a system that can handle increasing amounts of data and traffic.

- **Reliability:** This involves ensuring the system is fault-tolerant and can handle failures gracefully.

- **Communication:** This includes effectively conveying ideas, actively listening to the interviewer, and incorporating feedback.

Each parameter is scored from 0 to 5, with a total score ranging from 0 to 25. A higher score indicates a stronger candidate, and the acceptable score range varies depending on the target seniority level.

[Gaurav Sen](https://www.linkedin.com/in/gkcs/) has conducted 1000s of system design interviews while working at Uber and building his [YouTube channel](https://www.youtube.com/@gkcs) to 500K+ subscribers. His platform [InterviewReady](https://interviewready.io/?_aff=JOINTARO) combines video explainers, live Zoom classes, and an automated System Design Judge.

Master The DSA Interview [Part 11] - Space Analysis

**CORRECTION:** Recursive solutions can also have O(n) space for non-binary search style problems where you don't eliminate half of the problem space with each iteration. The classic example here is using recursion to calculate fibonacci numbers.

Run-time analysis is important, but it isn't everything. When it comes to FAANG, run-time on its own can actually be sorely lacking. This lesson teaches you:

- Why space complexity is also important when it comes to data structures and algorithms
- What a great space complexity analysis looks like, explained with an in-depth example
- A common mistake engineers make with space complexity concerning a very common data structures and algorithms pattern

Break Into Tech And Become A Software Engineer [Part 24] - Wrapping Up

In this final lesson, Brian provides key insights and encouragement as you wrap up your journey into software development.

This lesson covers:

- The importance of recognizing that everyone's timeline for getting hired is unique, and consistent effort on your technical skills will prepare you for success
- Building a supportive community or "tribe" through building in public, which will help you grow and find accountability
- Staying committed to learning and growing even after getting hired, as career development is a long-term game, and keeping your skills sharp will open doors for better opportunities

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

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

Break Into Tech And Become A Software Engineer [Part 23] - Exercise!

Brian's life before coding: <https://youtu.be/3pqgSaE6Zs4>

In this lesson, Brian shares how adopting an exercise routine can positively impact your journey as a software developer, fostering optimism and habit formation.

This lesson covers:

- How exercise builds optimism, as both working out and coding require patience, consistency, and incremental progress that may not be immediately noticeable
- The parallels between fitness and coding, such as overcoming self-doubt and creating habits that lead to long-term success
- Practical tips on habit creation, like using cues and triggers to make coding and exercise a natural part of your daily routine, emphasizing that it's never too late to start either

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

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

Break Into Tech And Become A Software Engineer [Part 21] - Developing Optimism

In this lesson, Brian shares the importance of cultivating optimism as a foundation for achieving success and overcoming challenges in your career and life.

This lesson covers:

- How optimism, rooted in effort and persistence, is essential for progress, as demonstrated by Brian's own journey from addiction to engineering manager
- The negative impact of social media on optimism, as it skews reality by focusing on extremes rather than everyday successes
- Practical strategies for maintaining optimism, such as keeping a tech journal to track your progress and reinforce your belief in your ability to improve and succeed

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

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

Break Into Tech And Become A Software Engineer [Part 13] - Establishing Your Brand Online

In this lesson, Brian discusses the importance of focusing on valuable content when writing online, rather than chasing likes or negative engagement.

This lesson covers:

- Avoiding negative or clickbait content that might gain attention but harms your professional reputation, such as romanticizing rejection or posting rage bait
- The value of sharing interesting challenges, technical problems, and personal experiences with solutions, which fosters meaningful conversations and builds credibility
- Posting about specific technologies, problems you’ve solved, and snippets of code to engage with professionals and attract potential career opportunities

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

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

Break Into Tech And Become A Software Engineer [Part 11] - The Value Of Writing Online

In this lesson, Brian highlights the importance of documenting your coding journey and writing online, not for fame but for personal growth and community building.

This lesson covers:

- Writing online as a way to document your progress, overcome imposter syndrome, and differentiate yourself in a crowded job market
- How being genuine in your writing attracts like-minded people and builds a valuable network
- The long-term benefits of writing consistently, even without immediate engagement, and how it helps organize your thoughts and improve communication skills

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

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

How To Get Interviews, Secure Offers, and Make More Money in Big Tech

Alan Stein, former executive and hiring manager at Google, Meta, Salesforce, and Tableau shares how jobs are really acquired at the world's top tech companies. 

No BS about resumes, cover letters, or LinkedIn profiles. Rather, Alan shares what actions you should actually take to land more interviews, offers, and earn more money.

Feel free to connect with [**Alan and say hi on LinkedIn**](https://www.linkedin.com/in/alanjstein/).

Become An Open Source Master [Part 15] - Find The Project Community

It's important to understand the bigger picture instead of focusing on every single line of code. Some questions worth asking when approaching a new codebase are: 

- what is the purpose of the code
- what are the opinions of the developers
- how is the code structured?

Connect with James:

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

Become An Open Source Master [Part 5] - The Benefits Of Open Source

We'll discuss the reasons why you should get involved in open source and the benefits it can bring, both professionally and personally.

- **Work on code that matters:** Contribute to projects used by others, gaining a sense of achievement and pride.
- **Improve your coding skills:** Receive feedback and learn from experienced developers, improving your coding abilities and knowledge.
- **Build relationships:** Connect with maintainers, contributors, and users, expanding your network and learning opportunities.
- **Enhance your professional portfolio:** Showcase your skills and experience to potential employers through your open source contributions.
- **Grow your personal reputation:** Gain recognition and build valuable connections within the open source community.

Connect with James: 

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

Grow From Junior To Mid-Level Engineer [Part 16] - Show Your Work

It's not enough to do the work - You also need to do the work to get full credit for it. This lesson teaches you:

- The 2 big components behind showing your work properly
- The differences between junior engineers and mid-level engineers when it comes to showing their work
- How mid-level engineers give far more effective status updates compared to junior engineers, explained with an in-depth example

Learn how to write an excellent project update post here: ["How to get more visibility on work?"](https://www.jointaro.com/question/XA0X51AypDLCeVeleJv4/how-to-get-more-visibility-on-work/)

Grow From Junior To Mid-Level Engineer [Part 4] - Structuring Your Growth

Even though junior engineer to mid-level engineer is the 1st and easiest promotion, it's still a meaningful evolution with many parts. This lesson teaches you:

- The 3 core areas of improvement to grow from junior -&gt; mid-level
- The most important area to improve to make the junior -&gt; mid-level promotion
- How you should process the advice from this course

Clear Communication For SWEs [Part 7] - The PREP Method

In this video, I delve into the Prep Method, a framework that simplifies communication by structuring messages into four key components: Point, Reason, Example, and Restate. I explain how each element contributes to clear and concise communication, making it ideal for software engineers and various communication scenarios.

Connect with me on LinkedIn: <https://www.linkedin.com/in/ryan-wiens/>

Clear Communication For SWEs [Part 6] - The Pyramid Principle

In this video, I explain the Pyramid Principle, a powerful communication framework that structures information hierarchically for clear and logical communication. I discuss how to apply it in presentations and communications, emphasizing starting with the main idea, supporting it with arguments, and providing detailed evidence.

**Action requested:** Understand and apply the Pyramid Principle for efficient and effective communication.

Connect with me on LinkedIn: <https://www.linkedin.com/in/ryan-wiens/>

Grow From Senior To Staff Engineer [Part 10] - Oncall

"Oncall" is a term that strikes fear into the heart of engineers. However, it's crucial for engineers to embrace oncall as an honorable duty and a place of opportunity as they become more senior, especially as they progress to staff. This lesson teaches you:

- The differences between senior and staff engineers when it comes to their scope within oncall
- How senior and staff engineers respond differently to oncall issues

Watch Alex's oncall case study here: [\[Case Study\] Revamping Oncall For 20 Instagram Engineers - Senior to Staff Project](https://www.jointaro.com/lesson/esVxIGXYC5BdgxXUkO6H/case-study-revamping-oncall-for-20-instagram-engineers-senior-to-staff-project/)

Grow From Senior To Staff Engineer [Part 6] - You Need Tenure

Software engineers like to give up when their team isn't going perfectly, often interviewing with another company entirely to jump ship. While this can work earlier in your career, it almost always stops as you're approaching staff. This lesson teaches you:

- Why job hopping to a staff uplevel at a top company is almost impossible
- Why you need to be in the same team for 2+ years in order to have a real case for staff
- The ingredients to develop the presence and impact of a staff engineer

Asking Great Questions [Part 25] - How You Should Evolve

It's important to make sure that you're always getting better - As long as you're improving, you will eventually become a rockstar engineer. So how does that work when it comes to judging your question asking ability? This lesson teaches you:

- What seniority does not mean when it comes to asking questions
- What seniority actually means when it comes to asking questions
- A simple framework you can use to evaluate the level your questions are at, split by junior/mid-level/senior+

Asking Great Questions [Part 20] - Make Fulfillment Easy

In order to get what you want, you need to know *exactly* what you want. This can be harder than many engineers realize. This lesson teaches you:

- The importance of reducing fulfillment friction, presented through the perspective of the person fulfilling the favor
- What it means to make fulfillment of your favor easy, shown with an in-depth example covering a common engineering ask
- How the spectrum behind fulfillment friction reduction is actually incredibly deep, especially if you're creative
- Ideas to make fulfillment easier with examples covering 3 more very commonly asked for favors

Asking Great Questions [Part 9] - Be Appreciative

The people who give the best help often have some degree of altruism. When you learn how to appeal to that altruism, you supercharge your chances of getting great answers quickly on your questions. This lesson teaches you:

- How many engineers view showing appreciation incorrectly, seeing it as a transactional action instead of a proactive action
- When to show appreciation proactively
- What it looks like weaving appreciation into your question, explained with an in-depth example
- A lazy way of showing "appreciation" that you should definitely avoid by spending an extra 10 seconds

[Become A Go-To Person 6/18] Become The Product Expert

A course by [Jordan Cutler](https://www.linkedin.com/in/jordancutler1/), Senior Software Engineer at Pinterest and Author of the [High Growth Engineer Newsletter](https://read.highgrowthengineer.com/)

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.