|
|
|
|
|
|
by dvcrn
3557 days ago
|
|
|
I'm also agreeing with leadership and mentoring. Be able to make unbiased technical decisions, troubleshoot systems / apps and get up to speed on new projets independently fairly fast. Have confidence in what you do and don't ask about everything. A solid general code understanding is also needed in my opinion. This includes things like using documentation over googling everything. If I pair with a senior and he types "golang how to do x" on every problem, I probably wouldn't consider him senior. (Not saying googling is bad. Just don't be a copy-paste-from-stackoverflow engineer) With that, I also hate the term "senior engineer". I got friends with 3 years of work experience that are now "senior" because a company hired them under a senior position (basically more salary) and the companies after that just did the same because "well he already is a senior, right"? This also generates a strong in-balance inside the team with a hierarchy that shouldn't be there. I am usually advocating for getting rid of job titles and calling everyone just "Software Engineer" I am now 6-7 years into my career and don't consider myself senior. When people in interviews ask me what my career goal is, I usually mention I want to be able to consider myself senior as the next step. |
|
|
Heed your own advice. You might not like the current system of hierarchy, that's fine. And change it when/if you get the chance.
But in the meantime, don't abstain from senior positions (and salaries) that others get just because you don't like a concept. Play inside the system until you can change it.