14 habits for promotion
A widely shared social thread laid out 14 practical habits engineers can use to build trust and earn promotions, emphasizing visibility, clear communication, and structured updates that summarize impacts. (x.com) The post highlighted actions like shipping reliably, making work legible, escalating early, and acting at the next level with 'clear updates.' (x.com)
A social post about engineering promotions spread by turning career advice into a checklist: ship on time, surface blockers early, and write updates that show business impact. (x.com) The thread listed 14 habits and centered on behaviors managers can observe repeatedly, not one-off heroics. Its examples included reliable delivery, legible work, early escalation, and “clear updates” that explain what changed, why it mattered, and what comes next. (x.com) That framing matches how many engineering organizations actually make promotion decisions. LeadDev wrote in 2020 that career ladders define expected impact at each level, but companies still need a process that shows “who else needs to be convinced,” “with what data,” and on what timeline. (leaddev.com) Will Larson, author of *Staff Engineer*, makes the same point in a more tactical way. His guide says engineers often start a promotion packet long before a formal review and fill it with projects, quantified impact, mentoring, cross-team “glue work,” and named advocates. (staffeng.com) The common thread is visibility without theatrics. LeadDev wrote in September 2023 that weak visibility in remote teams can turn into weak trust, and that regular demos and context-setting updates help other teams see goals, progress, blockers, and dependencies. (leaddev.com) That is why “clear updates” keep showing up in promotion advice. In LeadDev’s guidance on high-impact engineering launches, updates are described as strategic events tied to business goals, not just technical milestones, and leaders expect transparency while a project is in flight. (leaddev.com) The same logic applies to work that is easy to miss. LeadDev has also argued that migrations, deprecations, on-call work, and other low-visibility tasks need explicit recognition because they reduce systemic risk even when they do not produce a flashy feature launch. (leaddev.com) Promotion systems also try to reduce bias by making those signals concrete. LeadDev’s 2020 piece said clear levels and a standard review process make it less likely that promotions hinge on office politics or inconsistent manager interpretations. (leaddev.com) So the viral checklist landed in a gap many engineers already recognize: strong work often does not speak for itself inside a large organization. The habits that travel furthest are the ones a manager can point to in a packet, a calibration meeting, or a weekly update. (staffeng.com)
