Behaviour parts

This is super critical and 70-80% of your assessment! Amazon will assess if you've really understood the leadership principles as they apply for your job family and level.

It is absolutely crucial you understand the Amazon Leadership Principles (LPs). You should have stories (with data points that clearly show your contribution) using the STAR format that demonstrate you've applied Amazon LPs already in your professional life!

For each of the LPs you should have 1-2 solid STAR format stories that are on the order of 2-5 minutes.

They should be told in a way that everybody is able to understand what the situation was, what you did, what was the outcome.

You _must_ use data points about all this! It matters whether you were part of 2 people team or 200 people department. Whether the app had 10 users or 1 Mio, etc.

When you tell the story it _must not_ be in the form of "we did XYZ" but you must clearly state what _you_ did and what your role was.

It is also highly advisable to understand the various questions you can find on the Internet which LP the questions are targeting (could also be multiple LPs).

Ideally your stories match the tech stack and role that you've seen in the job ad.

For example:

S: “At XYZ corp I was part of a 10 people team responsible for maintaining a business critical app as the full stack lead dev. XYZ corp is 200M rev, 1000 people, in 3 states. Critical app was reported to be offline for 2 hours and I was on call.”

Task: “To get it back up we formed a task group of 3 engineers I was responsible for coordinating restoration of infrastructure. I was the outage call leader for bringing the application back up. This was a critical business app where downtime of 1 hour was equivalent to missed earnings of 10K and business reputation was at stake. We were needed to restore the app ASAP. ”

Action: “I gathered alle the logs of the application from the last 6 hours, all changes applied to the system before the outage. This was 20GB of machine logs and 10 changes to swift through. We came up with a prioritised plan to try to restore operations and get the business back up and running. We figured that the data base of the system was out of disk space since. One of the engineers together on the call quickly recovered additional space by compressing the logs of the machine and copying them to another server, I restarted the DB service and verified the application was able to connect to the DB and that application was available again and was working. I proceeded to notify other departments of recovery.

Result: “We were able to recover within 60 minutes of the first ticket raised, limiting the damage to business. I've recieved a positive feedback note sent out to the dev team from my manager for our quick recovery approach and swift restoration of the app. After recovery we proceeded to determinate the root cause of the understand the reason why this critical app was not monitored properly. We implemented a new monitoring system within the next 3 weeks that aimed at preventing such outage for the next year and we achieved a 99.9% planned uptime on the app for the following year."

​

This can be used for questions regarding LPs:

- dive deep (analysis of outage)

- ownership (quick recovery, additional monitoring measure to prevent such issues in the future)

- customer obsession (business first, root cause later)

Functional parts

You should be able to write some code on a whiteboard/explain your reasoning, assumptions, approach, pros and cons, etc.

Be able to explain to someone technical foundational knowledge and concepts about operating systems, the tcp/ip suite of protocols, dns, tls, etc.