„Chillin‘“ at Amazon
621 subscribers
27 photos
1 video
7 files
370 links
Amazonian SDE is sharing, 'cause sharing is caring 👨‍💻

note: I do not represent any of my employers in this channel
Download Telegram
#amazon #leadership #principles
Importance of Amazon's LP "Deep Dive" for Engineers.

You ONCE spend slightly more time to understand how something works and then uses this knowledge as a super power. The easiest way to train this skill is to dig something you do not understand asking 5 Why's. Each time you ask Why you deepen your expertise and gradually get expertise to influence others with the knowledge. It works - I proved it myself several times at Amazon
An opinionated view from another Amazonian
For those who prepare for System Design interviews, this vid can be useful. It discusses types of DBs
#amazon #leadership #principles
Importance of Amazon's LP "Deliver Results" for Engineers.

Perhaps, the most important LP at Amazon is "Deliver Results". It is kind of a minimum requirement from everyone to consistently deliver result. Across all levels it is only about delivering results. No one cares about something cool and complex you learned if it has not customer impact.

"Deliver results" is about your ability to unblock yourself when problems arise: how you can handle conflicting opinions, being not unfamiliar with a technology, or even simply getting comments in the reviews that postpone your delivery.

"Deliver results" is NOT about high quality or high standards. However, the higher your level, the higher quality is expected. At the end of the day, let's be fair, "Deliver results" does not go in the isolation and is normally backed by the other LPs. This makes it very powerful for Amazon.

At the interview, you will be asked about a story when you demonstrated this quality. So be equipped with a story when you were able to deliver results despite difficult circumstances.
Для тех, кто готовится к Систем Дизайну, статья про Operational Transformation
Хорошие рекомендации по подготовке к СисДезу
if anyone is interested, a spontaneous mock coding (data structures/internship) interview (in 10 mins):

yb is inviting you to a scheduled Zoom meeting.

Topic: coding mock
Time: Sep 26, 2021 02:00 PM Amsterdam, Berlin, Rome, Stockholm, Vienna

Join Zoom Meeting
https://us05web.zoom.us/j/82022071848?pwd=endCMTd4UnlHWW91blNYTW8yUGNSdz09

Meeting ID: 820 2207 1848
Passcode: jbr6rX
Через 40 минут, будем мокать техническое интервью. Если кому интересно, подключайтесь

Topic: Tech Mock Interview, Graduate Level

Time: Oct 24, 2021 10:00 AM Amsterdam, Berlin, Rome, Stockholm, Vienna

Join Zoom Meeting
https://us05web.zoom.us/j/86504321926?pwd=azZkWGF5SkVoTW9YeFBhTzlKN1Z3UT09

Meeting ID: 865 0432 1926
Passcode: WFh80d
Some people still do not understand benefits of DI. I found this talk answers the question of why
Свою "карьеру" я начинал с Питона (первые шаги в программировании), но за время работы в Амазон (мой первый промышленный опыт) я писал много на чем, но не так то много на Питоне. Был опыт с Java, Kotlin, Typescript, Javascript, и немного Go c Perl. В итоге, я полюбил типизацию, понял прелести полиморфизма, и жить не могу без использования интерфейсов. В Питоне нету интерфейсов, но есть Абстрактные классы и Протоколы. На первый взгляд, это одно и тоже, но в по факту работают по разному. В этом хорошее видео отлично объясняют в чем же разница.