|
12 | 12 | - [Solve follow up questions](#solve-follow-up-questions)
|
13 | 13 | - [Interview mindset](#interview-mindset)
|
14 | 14 | - [Understanding what interviewers really wants](#understanding-what-interviewers-really-wants)
|
15 |
| - - [When met with easy/hard/tricky problems \(although most time medium problems\):](#when-met-with-easyhardtricky-problems-although-most-time-medium-problems) |
| 15 | + - [Interview strategies](#interview-strategies) |
16 | 16 | - [Whiteboard coding pros and cons](#whiteboard-coding-pros-and-cons)
|
17 | 17 | - [Practice mindset](#practice-mindset)
|
18 | 18 | - [Goal](#goal)
|
|
306 | 306 | * Global variables
|
307 | 307 | 4. Synchronize with interviewer: "***I think I am done with the problem***".
|
308 | 308 |
|
| 309 | + |
309 | 310 | #### Solve follow up questions
|
310 | 311 | * Typical follow-up questions
|
311 | 312 | * No duplicates -> duplicates exist
|
|
332 | 333 | | Write code to solve problem | <ul><li>Jumps into writing code</li><li>Awkward silence</li></ul> | <ul><li>Would I want to work with them everyday</li><li>Have they actually written production grade code</li><li>What do they do when stuck</li></ul> |
|
333 | 334 | | Maybe you could try this ... | <ul><li>Take advice without serious thinking</li></ul> | <ul><li>Do they think independently</li><li>How fast can they absord new information</li><li>Do they take advice/directions well</li><li>Do they learn quickly and run with it</li></ul> |
|
334 | 335 |
|
335 |
| -#### When met with easy/hard/tricky problems (although most time medium problems): |
336 |
| -* Always smile no matter how easy/hard/tricky the problem is, ;) |
| 336 | +#### Interview strategies |
| 337 | +* For big companies, before onsite interview, practice all algorithm problems on Leetcode under the company's tag. Practice all algorithm problems on 1acre3points. |
| 338 | + - Come up with multiple solutions for each algorithm problem, know their tradeoffs and proficient in the best solution. |
| 339 | + - Practice algorithm questions under each problem category. |
| 340 | +* What if the interviewer just could not understand |
| 341 | + - Relax. Do not repeat the same explanation again. Walk through an example and know where he could not understand. |
| 342 | +* Behavior interview |
| 343 | + - Smile/handshake/look into eyes |
| 344 | + - ***Thank you so much for speaking with me and sharing your insights about the new position inside XXX. I am looking forward to working with you in future.*** |
337 | 345 | * For easy problems,
|
338 |
| - * Although interviewer says "I will only give you an easy question". Every interviewing question has its purpose. It might be the corner case, coding style or communication. |
339 |
| - * There might be some follow-up questions. The easy problem is just for warming up. |
| 346 | + - Although interviewer says "I will only give you an easy question". Every interviewing question has its purpose. It might be the corner case, coding style or communication. |
| 347 | + - There might be some follow-up questions. The easy problem is just for warming up. |
340 | 348 | * For problems I have seen before,
|
341 |
| - * Notice that the assumption might have been changed. |
| 349 | + - Notice that the assumption might have been changed. |
342 | 350 | * Still need to walk through the entire thought process instead of jumping to the right answer directly.
|
343 | 351 |
|
344 | 352 | #### Whiteboard coding pros and cons
|
|
0 commit comments