↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Thinking one level ahead: Your path to becoming a Senior Dev

The article argues that getting promoted requires a different approach than getting hired. It organizes that approach into three pillars: technical competence, professional communication and relationships, and getting feedback and credit for your work. It also says the focus changes by career stage, from junior developer to principal engineer.

Reading notes
#

  • Promotion depends on skills, value, and relationships inside the organization, not only on coding ability.
  • Technical competence includes understanding the link between tech and business, explaining your work process, and staying invested in learning.
  • The technical focus changes by level, from owning part of a codebase as a junior developer to handling big-picture design, writing, and ownership as a principal engineer.
  • Professional communication and relationships matter because managers and reviewers want someone who makes their work easier.
  • The article values time management, helping others succeed, taking responsibility for product outcomes, and professional communication.
  • Mentorship, manager alignment, explicit feedback, and not alienating yourself are presented as ways to strengthen your position for promotion.
  • Leadership should be genuine to the person and can take different forms.
  • A strategic brag document is recommended to record accomplishments, contributions, mentoring, improvements, and learning.
  • The document should use metrics and a problem-solving framing to show what was done, the result, and why it supports promotion.
  • The article says quality matters more than quantity and that goals should include more than a job title, such as responsibilities, freedoms, or leadership roles.