Skip to content

Commit 992cd5b

Browse files
committed
Rework motivation and guide
1 parent ed2d35e commit 992cd5b

File tree

1 file changed

+17
-23
lines changed

1 file changed

+17
-23
lines changed

README.md

Lines changed: 17 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,13 @@
77

88
## Motivation
99

10-
> Learn how to design large scale systems from the open source community.
11-
>
12-
> Understand real-world architectures.
10+
> Learn how to design large scale systems.
1311
>
1412
> Prep for the system design interview.
1513
1614
### Learn how to design large scale systems
1715

18-
Learning how to design scalable systems will help make you a better engineer.
16+
Learning how to design scalable systems will help you become a better engineer.
1917

2018
System design is a broad topic. There is a **vast amount of resources scattered throughout the web** on system design principles.
2119

@@ -41,24 +39,6 @@ Additional topics for interview prep:
4139
* [Object-oriented design interview questions, **with solutions**](#object-oriented-design-interview-questions-with-solutions)
4240
* [Additional system design interview questions](#additional-system-design-interview-questions)
4341

44-
#### For interviews, do I need to know everything here?
45-
46-
**No, you don't need to know everything here to prepare for the interview**.
47-
48-
What you are asked in an interview depends on variables such as:
49-
50-
* How much experience you have
51-
* What your technical background is
52-
* What positions you are interviewing for
53-
* Which companies you are interviewing with
54-
* Luck
55-
56-
More experienced candidates are generally expected to know more about system design. Architects or team leads might be expected to know more than individual contributors. Top tech companies are likely to have one or more design interview rounds.
57-
58-
#### Any resources to prep for coding interviews?
59-
60-
Check out the sister repo [**interactive-coding-challenges**](https://github.com/donnemartin/interactive-coding-challenges) for coding interview resources.
61-
6242
## Contributing
6343

6444
> Learn from the community.
@@ -166,7 +146,21 @@ Review the [Contributing Guidelines](https://github.com/donnemartin/system-desig
166146

167147
> Suggested topics to review based on your interview timeline (short, medium, long).
168148
169-
![Imgur](http://i.imgur.com/Klsu4cw.png)
149+
![Imgur](http://i.imgur.com/ciJelTB.png)
150+
151+
**Q: For interviews, do I need to know everything here?**
152+
153+
**A: No, you don't need to know everything here to prepare for the interview**.
154+
155+
What you are asked in an interview depends on variables such as:
156+
157+
* How much experience you have
158+
* What your technical background is
159+
* What positions you are interviewing for
160+
* Which companies you are interviewing with
161+
* Luck
162+
163+
More experienced candidates are generally expected to know more about system design. Architects or team leads might be expected to know more than individual contributors. Top tech companies are likely to have one or more design interview rounds.
170164

171165
Start broad and go deeper in a few areas. It helps to know a little about various key system design topics. Adjust the following guide based on your experience, what positions you are interviewing for, and which companies you are interviewing with.
172166

0 commit comments

Comments
 (0)