Education
Technology
Career Development
coding
Career Advice
Job Preparation
Job Applications
Coding Interviews
I have taken 200+ coding interviews.
10 blunders that are keeping you from getting hired (and how to fix them): π§΅
10 blunders that are keeping you from getting hired (and how to fix them): π§΅
β‘ Coding Interview Mistake #1
β Not understanding the problem
Fix:
β Re-read the question until you understand constraints and edge cases.
β Re-phrase question in your own words and verify understanding with the interviewer.
β Not understanding the problem
Fix:
β Re-read the question until you understand constraints and edge cases.
β Re-phrase question in your own words and verify understanding with the interviewer.
β‘ Coding Interview Mistake #2
β Not asking questions
Fix:
β Clarify any detail about the problem you find ambiguous.
β Ask for problem constraints. Range of values, size of input, etc.
β Ask the interviewer if they prefer time or space optimized solution.
β Not asking questions
Fix:
β Clarify any detail about the problem you find ambiguous.
β Ask for problem constraints. Range of values, size of input, etc.
β Ask the interviewer if they prefer time or space optimized solution.
β‘ Coding Interview Mistake #3
β Not planning before coding
Fix:
β Determine starting and ending points for solving the problem.
β Develop a high level algorithm before refining details.
β Not planning before coding
Fix:
β Determine starting and ending points for solving the problem.
β Develop a high level algorithm before refining details.
β‘ Coding Interview Mistake #4
β Not thinking out loud
Fix:
β Discuss solution approach with the interviewer.
β Walk them through your implementation by dry running code.
β Not thinking out loud
Fix:
β Discuss solution approach with the interviewer.
β Walk them through your implementation by dry running code.
β‘ Coding Interview Mistake #5
β Not using hints
Fix:
β Acknowledge the hint and how does it help.
β Expand on hint and see where else can it improve the solution.
β Not using hints
Fix:
β Acknowledge the hint and how does it help.
β Expand on hint and see where else can it improve the solution.
Coding Interview Mistake #6
β Not giving brute-force solution
Fix:
β Start by sharing simplest brute force solution.
β Explain why the approach is sub-optimal.
β Not giving brute-force solution
Fix:
β Start by sharing simplest brute force solution.
β Explain why the approach is sub-optimal.
β‘ Coding Interview Mistake #7
β Not optimizing the solution
Fix:
β Go through the solution step by step and identify the inefficiencies.
β Resolve inefficiencies by using right data structure or algorithm for the task.
β Not optimizing the solution
Fix:
β Go through the solution step by step and identify the inefficiencies.
β Resolve inefficiencies by using right data structure or algorithm for the task.
β‘ Coding Interview Mistake #8
β Not speaking while coding
Fix:
β Keep explaining to the interviewer what you are coding.
β Donβt speak code verbatim, also explain why you made a decision.
β Not speaking while coding
Fix:
β Keep explaining to the interviewer what you are coding.
β Donβt speak code verbatim, also explain why you made a decision.
β‘ Coding Interview Mistake #9
β Not knowing Big O notation
Fix:
β Know time and space complexity of classic algorithms.
β Practice calculating complexity of your code.
β Not knowing Big O notation
Fix:
β Know time and space complexity of classic algorithms.
β Practice calculating complexity of your code.
β‘ Coding Interview Mistake #10
β Not testing the solution
Fix:
β Dry run the code with sample inputs and edge cases.
β If code doesnβt work, show that you understand why is that so.
β Not testing the solution
Fix:
β Dry run the code with sample inputs and edge cases.
β If code doesnβt work, show that you understand why is that so.
TL;DR
Not understanding the problem
Not asking questions
Not planning before coding
Not thinking out loud
Not using hints
Not giving brute-force solution
Not optimizing the solution
Not speaking while coding
Not knowing Big O notation
Not testing the solution
Not understanding the problem
Not asking questions
Not planning before coding
Not thinking out loud
Not using hints
Not giving brute-force solution
Not optimizing the solution
Not speaking while coding
Not knowing Big O notation
Not testing the solution
That's a wrap!
If you enjoyed this thread:
retweet, like and leave a comment on the top tweet.
Follow @codewithvoid for:
π¦ tweets
𧡠threads
ποΈ spaces
β¦that will help you become a top 1% developer.
If you enjoyed this thread:
retweet, like and leave a comment on the top tweet.
Follow @codewithvoid for:
π¦ tweets
𧡠threads
ποΈ spaces
β¦that will help you become a top 1% developer.
Loading suggestions...