Introduction
It is my personal finance research. I am preparing for Amazon phone screen. As a software programmer, I like to code every day. Of course, I love to go through the preparation, and also blog about my experience. What if i can pass Amazon phone screen in 2019 July.
Short research
I had a conversation with my young sister this weekend. She said if I did not get a job offer from 2016 after the first onsite, why I still continue to try second onsite interview. I do believe that my job is to solve problem by writing software. I like to work on algorithm and data structure every day. It is so pleasant to meet another engineer, and have a short conversation through the phone screen.
That is my job as a software engineer, good engineer should love to meet people, and demonstrate good problem solving skills to the world.
My Amazon phone screens
I had one Amazon phone screen in May 2018, and also one in January 2017, one in May 2016.
I will have a phone screen from Seattle Amazon AWS team. The engineer also worked for Microsoft before. I am surprised that I will have challenge job to do to prove that I am worthy for another onsite interview.
In 2016 the phone interviewer is a young graduate. In January, 2017, the interviewer is a young engineer and I failed the phone screen.
In 2019 the phone interviewer has more than a few years in Microsoft, and now has more than a few years in Amazon AWS team Seattle as well.
My role model
I met an engineer who has more than 10 years experience less than two weeks ago, I asked him to solve lowest common ancestor algorithm. He is senior lead, worked for Microsoft before. I just remembered the conversation we had. I said that you will pass the phone screen since you work hard, and test your own code; I will fail as an interviewer, since I memorize the answer, I wrote a line of code with a bug, and interviewee went through the test case and found it.
So the interviewee demonstrated how serious he is in mock interview. He went through the test case and line by line test the code.
No comments:
Post a Comment