Introduction
It is my research topic this long weekend. I had over 60 interviewer experience on interviewing.io since this January 2018. And I have over 350 mock interviews and 30 minutes each time as an interviewer. Recently I experienced with professional interviewers, I learned so many lessons and will pay the lesson of my mistakes.
I like to write down some notes and will come back to look into. I may not make it sense today.
Difference is huge
I do not know why I choose this research topic. It is hard for me to write on this topic. I will write very carefully and see if it makes sense.
Professional interviewer working for giant software company may not have thousand interview experience. But those working for phone screen may have thousand experience. They know what they are looking for. They like to evaluate so many things in those 45 minutes.
There are two algorithms in 45 minutes.
Normal structure I like is to write down keywords, and write down constraints, and write down asking. And write down possible time complexity for the function I like to write, what is my target to get the optimal. And then I start to talk about brainstorm ideas. This can be easily processed with an amateur interviewer. But it may not work very well under the stress.
There are two algorithms in 45 minutes for top software programming companies.
You have to communicate your ideas instead of writing. I guess that 20 minutes for one hard level algorithm first. First five minutes is for brain storm and come out multiple ideas. And then next 10 minutes I should write code for brute force or optimal idea.
I like to do some study:
1. How do I find the interviewer's personality through the first two or three minutes?
2. How do I know if nervousness comes in? How should I overcome the nervousness?
3. Do not write down code if you do not have ideas. Try to push hard for one more clarification by yourself.
4. How to focus on the algorithm itself? Do not focus on what you feel.
5. What to say? Time complexity! Think about optimal solution. Talk about brute force solution first.
6. Go over one example.
7. How to follow the structure the interviewer layout for you? It is important to follow the instruction. It is different to work with amateur interviewer.
8. It is zero percentage to try to do something you like to do.
9. Need to find ways to expedite some code using abbreviation or test case handling etc.
10. It is hard to perform with professional interviewer. Expect to perform 50% of normal performance. Really train hard and work on more depths and widths for any algorithm.
11. Need to learn what professional interviewer will communicate with you. When the tip will come in, what is final and nonnegotiable.
12. Very strict on the timeline. There are some estimations for those 45 minutes. I should figure on those structures as well.
13. Why I as an experience amateur interviewer, I still have so many difficulty to perform with professional interviewer.
14. How to approach the algorithm and also work with professional interviewer?
15. What is maximum range I can go up-and-down because of impulse behavior in the interview?
Top 20% to bottom 20%. Hard level performance range?
Professional interviewer working for giant software company may not have thousand interview experience. But those working for phone screen may have thousand experience. They know what they are looking for. They like to evaluate so many things in those 45 minutes.
There are two algorithms in 45 minutes.
20 minutes for a hard level algorithm
There are two algorithms in 45 minutes for top software programming companies.
You have to communicate your ideas instead of writing. I guess that 20 minutes for one hard level algorithm first. First five minutes is for brain storm and come out multiple ideas. And then next 10 minutes I should write code for brute force or optimal idea.
Topics to study
I like to do some study:
1. How do I find the interviewer's personality through the first two or three minutes?
2. How do I know if nervousness comes in? How should I overcome the nervousness?
3. Do not write down code if you do not have ideas. Try to push hard for one more clarification by yourself.
4. How to focus on the algorithm itself? Do not focus on what you feel.
5. What to say? Time complexity! Think about optimal solution. Talk about brute force solution first.
6. Go over one example.
7. How to follow the structure the interviewer layout for you? It is important to follow the instruction. It is different to work with amateur interviewer.
8. It is zero percentage to try to do something you like to do.
9. Need to find ways to expedite some code using abbreviation or test case handling etc.
10. It is hard to perform with professional interviewer. Expect to perform 50% of normal performance. Really train hard and work on more depths and widths for any algorithm.
11. Need to learn what professional interviewer will communicate with you. When the tip will come in, what is final and nonnegotiable.
12. Very strict on the timeline. There are some estimations for those 45 minutes. I should figure on those structures as well.
13. Why I as an experience amateur interviewer, I still have so many difficulty to perform with professional interviewer.
14. How to approach the algorithm and also work with professional interviewer?
15. What is maximum range I can go up-and-down because of impulse behavior in the interview?
Top 20% to bottom 20%. Hard level performance range?
How far I can improve
I like to write down some notes to help me work on when I practice as a mock interviewer next 10 or 20 mock interviews as an interviewer. I know that I have so many personality weakness, in order to be a professional interviewer or get to understand better and work better with professional interviewer. I need to learn how to plan, how to prepare, how to discipline. I like to write down a list of things to check.
As a professional interviewer working for giant software company, they are more responsible and more disciplined.
1. Do not write down my personal email and name on the mock interview.
2. Try to give some instructions what to next. Learn how to guide the interviewee to next step.
3. I need to practice more as an interviewee instead of interviewer.
Follow up
August 6, 2018 9:44 AMAugust 6, 2018
It is hard to say it. I may be slow to comprehend the algorithm in the first 10 minutes. I recalled the article what to look for. Here is the article.
August 19, 2018, 11:45 PM
I have to learn to work with people, specially on algorithm and data structure problem solving. In order to stimulate good conversation and discussion, I should be well-prepared. I think that it is best for me to work on 190 easy level algorithms first, and then work on 100 to 200 medium level algorithms.
With 400 more Leetcode practice, I definitely will learn a lot of things include hard working people, how they train themselves using Leetcode, how many ideas I can come out to solve an easy level algorithm. How comfortable I am to meet a person and discuss solutions for an algorithm problems.
August 31, 2018
I study one young graduate who solved over 800 Leetcode algorithms today. Here is the profile I studied.
I need to figure out ways to solve at least 20 easy level algorithms on Leetcode.com a week.
Sept. 22, 2018
I start to play Leetcode contest, and also study Leetcode contest global ranking. I like to improve my global ranking from 14000 to top 5000 as soon as I can.
I continue to practice mock interviews on interviewing.io. I just had my fourth interview as an interviewee.
I learn how to adjust my feeling using data, Leetcode data. I have to read the data first and then figure out what I can work on.
Sept. 5, 2019
I wrote the blog after facebook phone screen back in August 1, 2018. I just could not believe what I wrote down, and there are some good ideas for me to think about again.
This year I went to Facebook onsite on August 20, 2019. I like to write down something better.
No comments:
Post a Comment