≡
F
ile
E
dit
V
iew
H
elp
_
↕
1
COVER LETTER
1:1
My excellent ex-colleagues taught me the principles of a good engineer quite early on. They didn't directly articulate them; they just formed in my mind after several projects and collaborations. I always strive to be honest and transparent, both about my work and with my colleagues. If something isn't working for me, I'll definitely speak up. If I notice a flaw in the code, I'll try to fix it if there's enough time. Doing things well is crucial. In my view, what sets a good engineer apart from a bad one is the internal desire to understand how a system works. This doesn't mean you have to know every line of code in the Linux kernel. We've outgrown the 1990s, and we don't need to write drivers and shells from scratch. However, understanding and visualizing the internal processes of a system in your mind is essential. It saves time when investigating any incident: you don't randomly check the first idea that comes to mind; instead, you visualize how the entire system works and try to understand what might have gone wrong. You should treat your systems with love. In a good team, you should proactively help colleagues make systems better: through constant code reviews, collaborative problem-solving, participating together in hackathons. If something doesn't work out, don't be afraid to spend your time deeply studying the material. I hope these principles resonate not only in my soul but also with others.
🔚
MAIN SCREEN
💾
WORK
☎️
CONTACTS