algorithm/tech-interview-handbook
1
0
Fork 0
mirror of https://github.com/yangshun/tech-interview-handbook.git synced 2025-07-29 13:13:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix grammatical errors (#83)

Browse Source 
* docs: fix grammatical errors

* Update README.md
This commit is contained in:
Jim Poulakos
2017-10-31 10:09:45 -05:00
committed by Yangshun Tay
parent 9ce52c02dd
commit d1688df5ed
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
preparing/cheatsheet.md
View File

@ -1,7 +1,7 @@
Interview Cheatsheet
==
This is a straight-to-the-point distilled list of technical interview Do's and Don'ts, mainly for algorithmic interviews. Some of these may apply to only phone screens on whiteboard interviews but most will apply to both. I revise this list before each of my interviews to remind myself of them and eventually internalized all of them to the point I do not have to rely on it anymore.
This is a straight-to-the-point, distilled list of technical interview Do's and Don'ts, mainly for algorithmic interviews. Some of these may apply to only phone screens or whiteboard interviews, but most will apply to both. I revise this list before each of my interviews to remind myself of them and eventually internalized all of them to the point I do not have to rely on it anymore.
For a detailed walkthrough of interview preparation, refer to the ["Preparing for a Coding Interview"](./) section.
@ -30,7 +30,7 @@ For a detailed walkthrough of interview preparation, refer to the ["Preparing fo
|✅|Introduce yourself in a few sentences under a minute or two.|
|✅|Mention interesting points that are relevant to the role you are applying for.|
|✅|Sound enthusiastic! Speak with a smile and you will naturally sound more engaging.|
|❌|Spend too long introducing yourself. The more time you spend talk the less time you have to code.|
|❌|Spend too long introducing yourself. The more time you spend talking the less time you have to code.|
### 3. Upon Getting the Question