Skip to content

Commit c4ceb00

Browse files
author
freemanzhang
committed
summarize lessons learnt from Microsoft onsite interview
1 parent 41401df commit c4ceb00

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

README.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -234,7 +234,9 @@
234234
* Divide and conquer "***The problem could be decomposed into X subproblems.***"
235235
3. Brainstorm DS/Algo which might be used / Give it a try
236236
* Give it a try: "***Let's try a graph-based solution***"
237-
3. Calc time/space complexity: "***The time complexity of the algorithm is O(XXX) and space complexity is O(XXX)***"
237+
3. Talk about the data structures to be used.
238+
4. Talk about the algorithm to be used.
239+
5. Calc time/space complexity: "***The time complexity of the algorithm is O(XXX) and space complexity is O(XXX)***"
238240

239241
#### Optimize the brute force solution
240242
1. Synchronize with interviewer "***The time/space complexity of the brute force solution is too high and will be impractical.***"
@@ -338,6 +340,11 @@
338340
* Ignore first impression importance: Don't smile/handshake/look into interviewers' eyes.
339341
* Wrong expectations about interviewers: You need to acknowledge that there are so many different types of interviewers. Some like to follow rules but others don't. For example, expecting all algorithm interview questions are under leetcode's company tag or from past interview experiences in 1acre3points is not practical. Some interviewers are bored with Leetcode and really want to ask unique questions to truely evaluate interviewees.
340342
* Anxious because too many things need to be prepared: Always prioritize and then act. You just cannot practice every possible question before interviews because there are too many. What you can do is to practice typical problems under each category and practice the most popular interview questions. Make sure that you practice each problem as if you are interviewing.
343+
* Preparation time allocation: 70% should be on coding. 15% on system design. 15% on behavior questions.
344+
* Do not go straight to coding during interviews, give yourself a minute to think before speak. Thought well before speak and coding.
345+
* I am used to good words. When interviewer doubts/challenges me, I become kind of sad. Always stay in calm and smiles.
346+
* Give myself a little break between interviews. Either sit down or drink some beverages.
347+
* When interviewers keep interrupting me, do not be nervous. They are trying to help me!!! Always stay in calm and take their hints. No matter whether I could finish my current solution. Communication is the most important thing.
341348

342349
#### Whiteboard coding pros and cons
343350
* Pros

0 commit comments

Comments
 (0)