The engineers who plateau aren’t the ones who lack talent.

Аналитика рынка

Стек

Откликнуться

Загрузите резюме — мы свяжем вас с работодателем напрямую через нашу базу.

Описание

The engineers who plateau aren’t the ones who lack talent. They’re the ones who stopped volunteering for the scary tickets. I’ve been thinking about why some engineers level up fast and others sit at the same level for years, and I don’t think it’s raw ability. I’m currently in a position where I have less total experience than someone I regularly help with cloud problems. For a while that felt like an accident. It’s not. The difference is exposure — and most of it is self-inflicted, in both directions. Early on I made a deliberate (and at the time, terrifying) decision to grab the problems no one else wanted. The production incident no one could figure out. The migration everyone was avoiding. The “why does this keep breaking” ticket that had been rotting in the backlog. Not because I was confident — I wasn’t — but because I’d noticed something: those problems forced me to read the actual docs, ask uncomfortable questions, and understand systems instead of copy-pasting fixes. Three years later, the infra I own hasn’t had a day of downtime. That’s not talent. It’s that I got reps on the hard stuff while it was still scary, instead of waiting until I “felt ready.” The engineers I see plateau are almost always the ones optimizing for comfort — staying in the lane they’re already good at. Totally understandable. Also the exact thing keeping them mid-level. Curious if others have seen the same, or if I’m wrong: did your biggest jumps come from time, or from deliberately taking on stuff that scared you? [link] [handle]

Контакты работодателя (email/phone/telegram) скрыты из публичного превью — отправьте резюме, чтобы мы связали вас напрямую.