„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
#interview #prep #guide
13 лет давности, но все еще актуально. На тему подготовки к интеврью в Гугл (и другие топы)
http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html
#interview #mock

Вначале он говорит, что она не компететив программист, хотя по решению которое она сразу предлагает (на мой взгляд, без детального проблем солвинга, а больше на интуиции и опыте) и как она пишет код, плюс выборя язка, очень похоже на то, что она как раз таки практикующий компететив программист.

Интересная задачка и решение.

https://www.youtube.com/watch?v=rw4s4M3hFfs
Forwarded from DevBrain
Курсы по Redis стали доступны в режиме self-paced обучения бесплатно: https://university.redislabs.com/
Как и ожидалось, Python обогнал Java 😅

https://www.tiobe.com/tiobe-index/
Niiice :)
From a staff level engineer at Google
Forwarded from Nodir's notebook
I must clarify that my interest is frameworks/libraries and developer tools, where *the customer is a developer*. My first piece of generic reusable code was a rainbow-colored button control in Delphi when I was ~14. At NetDec (Tashkent) I led the team to create UZTO framework, a la 1C:Enterprise in C#. Then at ComponentOne, the whole business is to sell software components, e.g. supercharged DataGrid for .NET. Those years my ultimate dream was to live in Redmond and work on .NET or Visual Studio. Then I joined Google where the job is to create the developer infrastructure used by Chrome engineers. I also fell in love with Go, hence the dream to join the Go team; but that didn't work out.

I learned that the higher you go in the career/level, the more it is important to work in a domain you care about. This is because at Staff+ level an engineer no longer can just write code or design systems, but must think about the business side - which is hard if you don't care about the domain of the business. For example, I don't want to go to Facebook or Netflix because I don't care about social networks or movies that much. Chrome isn't perfect either: people come here because they care about the *Web* - this ended up being the main limiting factor of growth in my team.

With such narrow speciality, there isn't a lot of choice really: if I don't know about a product, then it is probably not interesting. Also, the more developers use tool/framework, the better; this basically narrows down the choice to the most popular frameworks and tools. There are not a lot of teams like that, so where do I go?

To be continued...
#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