Promotable engineer habits
A thread shared by Andrea recounts inheriting a team with no formal authority and argues that influence, not title, drives leadership progression. Another post outlines 14 promotable engineering habits — shipping quietly, seeing around corners and treating incidents like interviews — that map to trust and business awareness. (x.com) (x.com)
Software engineers are swapping promotion checklists for a simpler rule: the people who move up are the ones other teams already trust. (staffeng.com) That idea showed up in two widely shared posts this month. In one, Andrea wrote that she inherited a team without formal authority and learned that “influence,” not a manager title, was doing the work of leadership; in the other, an engineer listed 14 “promotable” habits, including shipping quietly, spotting risks early and handling incidents as if every outage were an interview. (x.com 1) (x.com 2) The posts landed in a career system that already rewards scope, judgment and reach more than raw output. Dropbox’s engineering framework says impact includes results, leadership, mentorship and “collaborative reach,” and its Staff level expects engineers to set multi-year, multi-team technical strategy. (dropbox.github.io 1) (dropbox.github.io 2) Will Larson’s Staff Engineer guide makes the same point in broader terms. It says Staff-plus engineers usually work on efforts with “strategic value for the company,” and identifies four common patterns for the role: Tech Lead, Architect, Solver and Right Hand. (staffeng.com 1) (staffeng.com 2) That framing shifts promotion away from visible busyness and toward repeatable trust. “Ships quietly” maps to execution without drama; “sees around corners” maps to risk management; “treats incidents like interviews” maps to judgment under pressure. (x.com) (dropbox.github.io) It also explains why engineers can feel stuck even when they write strong code. Staffeng’s guide says many senior engineers expect that once they are promoted they will control the work and people will listen, but Katie Sylor-Miller said the opposite is often true: the role requires influence without relying on authority. (staffeng.com) Career ladders increasingly spell that out. Dropbox says its framework is “not a promotion checklist,” and its promotion principles warn against playing a checkbox game, pushing engineers to show sustained impact over time instead of isolated wins. (dropbox.github.io) (dropbox.github.io) The practical takeaway is narrower than the social-media language suggests. Promotion systems still depend on managers, level definitions and business need, but the habits getting attention all point to the same test: can this engineer reduce risk, move work across teams and make other people more effective. (dropbox.github.io) (staffeng.com) That is why the posts resonated beyond one thread. In most engineering ladders, the title tends to arrive after the job is already being done. (staffeng.com)
