Why Amazon?
Because I know Amazon is a top internet retailing company with a strong focus on customer experience. And there are a lot of talented people in amazon creating amazing products to make people’s life easier. They are always showing strong ownership to their projects and they always want to make things perfect. Those spirits do touch my heart. I remember when I just started to lead smart log analyzer project, everything is new to me. And I’m so passionate about creating great services for customers to save their precious time and money. They could have people hired to sit there watching the visuals we provide, and trying to do treat hunting, to see if there are malicious events among them. But we want it to be more convenient. We want our system to take care of all the stuff automatically. It will detect the malicious stuff, evaluate them, report them and provide suggestions and solve them automatically. The customer only needs to do clicks on the website to make simple decisions based on the suggestions system provide and they can focus more on their own things. That is really similar with Quilt. Quilt also does a great job to help customers focus on their codes. It will take care of patching automatically for hosts. That’s really amazing for customer. So, we have similar spirits. That’s one big reason why I want to join Amazon.
Secondly, the growth of amazon is so impressive, it is not only an online retail shop, it also has a wide range of products like Alexa, kindle, fire tablet and TV, Amazon web service, etc. There are so many fantastic technologies and products here. I will never feel boring if I am in amazon. And I’ll be excited about all the amazing things around me everyday. I can learn a lot of new technologies here. Beside that, I can also learn to work with solutions with full-stack point of view, by engaging requirements, front-end, back-end, storage and all the other stuff. I can understand the problems and solutions thoroughly.
Why you choose this position?
The job I applied is Software development engineer in Amazon web service quilt team. The reason why I choose this job is I have the similar experience. I remember when I just started to lead smart log analyzer project, everything is new to me. And I’m so passionate about creating great services for customers to save their precious time and money. They could have people hired to sit there watching the visuals we provide, and trying to do treat hunting, to see if there are malicious events among them. But we want it to be more convenient. We want our system to take care of all the stuff automatically. It will detect the malicious stuff, evaluate them, report them and provide suggestions and solve them automatically. The customer only needs to do clicks on the website to make simple decisions based on the suggestions system provide and they can focus more on their own things. That is really similar with Quilt. Quilt also does a great job to help customers focus on their codes. It will take care of patching automatically for hosts. That’s really amazing for customer. So, we have similar spirits. That’s one big reason why I want to join Amazon.
Another big reason is amazon. the growth of amazon is so impressive, it is not only an online retail shop, it also has a wide range of products like Alexa, kindle, fire tablet and TV, Amazon web service, etc. There are so many fantastic technologies and products here. I will never feel boring if I am in amazon. And I’ll be excited about all the amazing things around me everyday. I can learn a lot of new technologies here. Beside that, I can also learn to work with solutions with full-stack point of view, by engaging requirements, front-end, back-end, storage and all the other stuff. I can understand the problems and solutions thoroughly.
The biggest mistake you made and what did you learn from it? (earn trust, customer obsession)
Case 1: The biggest mistake I’ve made happened when I led the smartloganalyzer project for the first time. The original schedule is week, but I suddenly received a message from my manager says that he will show a smartloganalyzer demo to one customer after two days. And at that time I was working on building the alerting system, that will be an important part of the demo. But I paid too much atten
sorflow. Cause one of our core features is to analyze the behavior of network. But each network has its own environment and their behaviors are definitely different, so we need to build specific judging rules and awarding rules to let it train itself. So that it can always have good performance regarding to each environment. And I’m still working on that.
9. Bias for Action Speed matters in business. Many decisions and actions are reversible and do not need extensive study. We value calculated risk taking.
• Describe a time when you saw some problem and took the initiative to correct it rather than waiting for someone else to do it.
• Tell me about a time when you took a calculated risk.
• Tell me about a time you needed to get information from someone who wasn’t very responsive. What did you do?
10. Frugality Accomplish more with less. Constraints breed resourcefulness, self-sufficiency, and invention. There are no extra points for growing headcount, budget size or fixed expense.
• Tell me about a time when you had to work with limited time or resources.
11. Earn Trust Leaders listen attentively, speak candidly, and treat others respectfully. They are vocally self-critical, even when doing so is awkward or embarrassing. Leaders do not believe their or their team’s body odor smells of perfume. They benchmark themselves and their teams against the best.
• What would you do if you found out that your closest friend at work was stealing?
• Tell me about a time when you had to tell someone a harsh truth.
12. Dive Deep Leaders operate at all levels, stay connected to the details, audit frequently, and are skeptical when metrics and anecdote differ. No task is beneath them.
• Give me two examples of when you did more than what was required in any job experience.
Create elastalert rules, not only the rules, but also automate them.
Create a vis timeline to visual the tickets.
13. Have Backbone; Disagree and Commit Leaders are obligated to respectfully challenge decisions when they disagree, even when doing so is uncomfortable or exhausting. Leaders have conviction and are tenacious. They do not compromise for the sake of social cohesion. Once a decision is determined, they commit wholly.
• Tell me about a time when you did not accept the status quo.
• Tell me about an unpopular decision of yours.
• Tell me about a time when you had to step up and disagree with a team members approach.
• If your direct manager was instructing you to do something you disagreed with, how would you handle it?
14. Deliver Results Leaders focus on the key inputs for their business and deliver them with the right quality and in a timely fashion. Despite setbacks, they rise to the occasion and never settle.
• By providing an example, tell me when you have had to handle a variety of assignments. Describe the results.
• What is the most difficult situation you have ever faced in your life? How did you handle it?
• Give me an example of a time when you were 75% of the way through a project, and you had to pivot strategy–how were you able to make that into a success story?
Q: Why Amazon?
I enjoy creating great servers for customers to save their time.
I can learn various new techniques on amazon and contribute to the amazing production.
+ I would like to build new techniques to make life easier. Working in Amazon will give me the chance to impact billions of people with the new techniques.
+ 对于为什么要做一件事情,我喜欢回答,因为我想做xxxx。主动语气。
Q: Why did you choose this position?
The reason why I choose this job is I have a similar experience.
+ I would like to build new techniques to make life easier. Working in this position will let me be able to impact billions of people with the new techniques.
+ 同上,采用主动语气回答。 大问题从大角度出发回答。
Q: The biggest mistake you made and what did you learn from it? (earn trust, customer obsession)
case 1: I received another request before deadline. But I still want to make everything perfect. I didn't finish the feature in the last day. After the communications, I am able to implement the key features to face the requirements in the demo.
+ There is one mistake at the beginning of my career that I didn't prioritize the tasks very well. (This may not be a good example of "biggest mistake" if you have 1-2 yr experiences.)
++ 遇到的错误和对应的级别往往有关系,尽量选择大项目/大impact中的错误。但是这边的mistake可以当做失误来理解。即如果向后我应该可以这么做,可以达到更好的效果,那么那时候的做法就是“mistake”。不一定最后的结果一定是坏的。所以可以拿这个问题作为一个展示的机会,而不是救赎的机会。
case 2: In one project, the system failures after deploying the features to customers. The root cause is the inconsistent of environments in dev and deployment. I fixed them as soon as possible for the customers. And I also document them in time to avoid issues in the future.
Most challenging project
It is my recent project as I need to implement all new features on my own. There are new stacks in this project. I need to put my private time into this project.
+ My recent project is super challenging of the complexity of the system and the tight timeline. I am able to make a good project plan based on the short time. Catch new techniques quickly. Collaborate with different teams to make the good alignment. The features are delivered and create xx impacts.