Low Level System Design [An interview perspective]

Low Level System Design [An interview perspective], available at $69.99, has an average rating of 4.77, with 73 lectures, 2 quizzes, based on 425 reviews, and has 4983 subscribers.

You will learn about Getting ready for System Design [Low Level Design] interviews Learn different ways to approach a problem and underline key points Discussing the trade-offs with the interviewer and playing to your strengths Optimizing code using better data structures, according to the scenario Insights into problem extensibility, and begin coding with this as the end goal in mind. Learn to weed out unnecessary information from the problem definition, identify traction, and create a class diagram with it Learn to write test cases for the problem as and when required Necessary exposure and modifications to the API for code sustainability Using encapsulation when required and generate desired accessors and mutators Learn code completion in due interview time. Gain insight into fallback plans in emergency cases This course is ideal for individuals who are Software Engineers or Aspiring Software Engineers It is particularly useful for Software Engineers or Aspiring Software Engineers.

Enroll now: Low Level System Design [An interview perspective]

Summary

Title: Low Level System Design [An interview perspective]

Price: $69.99

Average Rating: 4.77

Number of Lectures: 73

Number of Quizzes: 2

Number of Published Lectures: 73

Number of Published Quizzes: 2

Number of Curriculum Items: 75

Number of Published Curriculum Objects: 75

Original Price: $89.99

Quality Status: approved

Status: Live

What You Will Learn

Getting ready for System Design [Low Level Design] interviews

Learn different ways to approach a problem and underline key points

Discussing the trade-offs with the interviewer and playing to your strengths

Optimizing code using better data structures, according to the scenario

Insights into problem extensibility, and begin coding with this as the end goal in mind.

Learn to weed out unnecessary information from the problem definition, identify traction, and create a class diagram with it

Learn to write test cases for the problem as and when required

Necessary exposure and modifications to the API for code sustainability

Using encapsulation when required and generate desired accessors and mutators

Learn code completion in due interview time. Gain insight into fallback plans in emergency cases

Who Should Attend

Software Engineers

Aspiring Software Engineers

Target Audiences

Software Engineers

Aspiring Software Engineers

Software Engineering interviews focus on the coding and software designing skills in an interview. These are fondly known as Algorithm and Design rounds respectively. The Algorithms round check the raw coding skills of a candidate, by the application of Data Structures and Algorithms mostly practiced in school, while the Design round tests the System design skills, which can be High Level Design [HLD] or Low Level Design [LLD].

Low Level Design is also known as Object Oriented Design [OOD] or Object Oriented Analysis and Design [OOAD]. From interns to Senior Software Engineers, top companies dedicate at least one round in the entire interview process for system design. For candidates having less than 3 years’ of experience, Low Level Design plays the most crucial role because these candidates are inexperienced, hence not supposed to have knowledge of High Level Design. Candidates having experience of more than 3 years usually face the system design interviews with a mix of both HLD and LLD.

This course Low Level System Designfocuses on the low level aspects of the design. The only way to get better at interviews is by practicing lots of similar problems. In this course, based upon my research, a list of most frequently asked questions in interviews is compiled. Not only is this useful for the interviews, but also for general problem solving and application design.

Every problem is broken down and discussed in a comprehensive manner:

1. Making the problem statement clear of any ambiguity. Terminologies related to the problem are explained and expectations well laid out.

2. Class Diagram construction serves as a road map for coding the problem

3. The coding is done in the most elegant manner such that the users learn to approach the problem top-down. This is important because even if the class diagram is in place, it’s imperative to know the sequence of class construction in program, for a smooth experience.

4. Wherever applicable, the code is optimized further. Trade offs related to optimizationare also discussed.

5. At last, test case construction is shown to make the candidate wary about writing good test cases, and their impact on the application.

All this is done while following industry best practices. Proper time utilization during the interview is also talked about intermittently, and ways to deal with a situation when the candidate is stuck at a problem for a long time. The coding is done in C++ but the code is language agnosticto a great extent.

The course also sports Closed Captions [English Subtitles] for all the videos. They are hand-crafted, not auto-generated. This feature is helpful when the student is having problem with the accent, there’s a lot of background noise present, or when you want to make detailed notes from the explanation.

After taking this course, you

1. Will be in a better place to face LLD interviews.

2. Can participate in design discussions related to such problems

3. Write better code than before

4. Have a proper theater to break the problem into pieces and deal with them independently

Guaranteed Takeaway

If you understand all the problems presented in this course, there won’t be any fear of solving LLD questions. You’ll be asking the right questions about the problem, and will be confident to jab at any design.

Course Curriculum

Chapter 1: Introduction

Lecture 1: Introduction

Chapter 2: Basic ride sharing application

Lecture 1: Problem Definition

Lecture 2: Design the class for booking a ride

Lecture 3: Design the Rider class depicting the user

Lecture 4: Testing the code for meeting requirements

Lecture 5: #Assumption 1: Single user booking multiple rides at a time

Lecture 6: Exercise: Design an interface for user interaction

Lecture 7: Solution: Design an interface for user interaction

Chapter 3: Meeting Scheduler

Lecture 1: Problem Definition

Lecture 2: Design the Room class, which hosts a meeting

Lecture 3: Design the class Meeting, which contains meeting details

Lecture 4: Design the class Scheduler

Lecture 5: Core logic for scheduling a meeting

Lecture 6: Testing the code for the given requirements

Lecture 7: Exercise: Extend the application to book meetings across days

Lecture 8: Solution: Extend the application to book meetings across days

Chapter 4: Task Planner

Lecture 1: Problem Definition

Lecture 2: Design Sprint class

Lecture 3: Design Task class

Lecture 4: Design the User class [1/3]

Lecture 5: Design the User class [2/3]

Lecture 6: Design the User class [3/3]

Lecture 7: Testing the code for the given requirements

Chapter 5: Bowling Game System

Lecture 1: Problem Definition

Lecture 2: Design a game session for the play

Lecture 3: Design the Game class

Lecture 4: Design the Player class [1/2]

Lecture 5: Design the Player class [2/2]

Lecture 6: Testing the code for the given requirements

Chapter 6: Snakes And Ladders

Lecture 1: Problem Definition

Lecture 2: Design the base classes for the game

Lecture 3: Design the Game class of the problem

Lecture 4: Testing the code for the given requirements

Chapter 7: Money share/transfer application like Splitwise

Lecture 1: Problem Definition

Lecture 2: Design the User class

Lecture 3: Design the Expense class

Lecture 4: Designing the class Splitwise [1/3]

Lecture 5: Designing the class Splitwise [2/3]

Lecture 6: Designing the class Splitwise [3/3]

Lecture 7: Testing the code for the given requirements

Lecture 8: Optimizing the code

Lecture 9: Exercise: Simplify Expenses

Lecture 10: Solution: Simplify Expenses

Chapter 8: Facebook Comment System

Lecture 1: Problem Definition

Lecture 2: Design the Comment class

Lecture 3: Design the Post class

Lecture 4: Design the User class

Lecture 5: Testing the code for the given requirements

Chapter 9: Sales Management System

Lecture 1: Problem Definition

Lecture 2: Design the Store class

Lecture 3: Design the City class

Lecture 4: Design the State class

Lecture 5: Design the System class

Lecture 6: Testing the code for the given requirements

Chapter 10: Text Editor application

Lecture 1: Problem Definition

Lecture 2: Designing the Notepad class [1/2]

Lecture 3: Designing the Notepad class [2/2]

Lecture 4: Testing the code for the given requirements

Chapter 11: Employee Management System

Lecture 1: Problem Definition

Lecture 2: Design the Employee class

Lecture 3: Design the System class

Lecture 4: Testing the code for the given requirements

Chapter 12: Book Catalog System

Lecture 1: Problem Definition

Lecture 2: Design the Book class

Lecture 3: Design the Catalog class

Lecture 4: Testing the code for the given requirements

Chapter 13: Job Scheduler

Lecture 1: Problem Definition

Lecture 2: Design the Job class

Lecture 3: Design the Scheduler class [1/2]

Lecture 4: Design the Scheduler class [2/2]

Lecture 5: Understand the Test Cases

Lecture 6: Testing the code for the given requirements

Chapter 14: Addendum

Lecture 1: Extra tips for beginners

Instructors

Abhishek Ghosh
Software Engineer, Programmer and Design enthusiast

Rating Distribution

1 stars: 24 votes

2 stars: 17 votes

3 stars: 67 votes

4 stars: 149 votes

5 stars: 168 votes

Frequently Asked Questions

How long do I have access to the course materials?

You can view and review the lecture materials indefinitely, like an on-demand channel.

Can I take my courses with me wherever I go?

Definitely! If you have an internet connection, courses on Udemy are available on any device at any time. If you don’t have an internet connection, some instructors also let their students download course lectures. That’s up to the instructor though, so make sure you get on their good side!