不是每个人都有时间做几百个 LeetCode 问题。这个开源项目就是为忙碌的工程师准备的免费技术面试准备材料,超过 500,000 人从这本手册中受益!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
Andrew 30e5d8bccb
Grammar fixes for tense, punctuation and wording. (#17)
7 years ago
algorithms Reformat algorithms and preparation sections 7 years ago
assets Rename logo to purge CDN cache 7 years ago
design Clean up apostrophes 7 years ago
domain Squash commit 7 years ago
front-end Added Writeup for CSS in front-end folder resources (#10) 7 years ago
non-technical Clean up apostrophes 7 years ago
preparing Grammar fixes for tense, punctuation and wording. (#17) 7 years ago
utilities Use const 7 years ago
.editorconfig Squash commit 7 years ago
.travis.yml Allow 429 in awesome bot 7 years ago
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 7 years ago
LICENSE Create LICENSE 7 years ago
README.md Couple of grammar/typo edits to README.MD (#16) 7 years ago

README.md

Tech Interview Handbook

Carefully curated content to help you ace your next technical interview, with a focus on algorithms and the front end domain. System design questions are in-progress. Besides the usual algorithm questions, other awesome stuff includes:

This handbook is pretty new and help from you in contributing content would be very much appreciated!

How is this repository different?

There are so many awesome books like Cracking the Coding Interview and interview-related repositories out there on GitHub, what makes this repository different? The difference is that many existing interview repositories contain mainly links to external resources whereas this repository contains top quality curated content directly for your consumption.

Also, existing resources focus mainly on algorithm questions, and lack in coverage for more domain-specific and non-technical questions. This handbook aims to cover content beyond the typical algorithmic coding questions. 😎

Contents

Contributing

There are no formal contributing guidelines at the moment as things are still in flux and we might find a better approach to structure content as we go along. You are welcome to contribute whatever you think will be helpful to fellow engineers. If you would like to contribute content for different domains, feel free to create an issue or submit a pull request and we can discuss further.

Maintainers