How do you spot a dev or engineer who is ready for management?

1.7k views3 Comments

VP of Engineering in Banking, 201 - 500 employees
A few things that may be good indicators:
* Care for others and can build good rapport within the team and also outside the team.
* Big picture thinking, not always thinking at the task level.
* Able to prioritize with good trade-off analysis.
* Care for how to unblock the team vs only how to unblock self.
* Taking interest in management/leadership through upskilling, mentoring, etc.
* Dare to raise important issues that others do not think about or care to talk about.
Senior Director Engineering in Travel and Hospitality, 10,001+ employees
It's a two way process, there should be intent from a developer who wants to take the management path, and the second being another spotting those traits.
Management is leadership, so all traits of leadership - empathy, teamwork, communication, accountability, strategic thinking, self motivation gets that tick.
Director of Technology Strategy in Services (non-Government), 2 - 10 employees
You don't spot them, you ask them! 

And you don't just promote them, you give them the skills you need first.

Organisations fail when they promote people before they are ready

Content you might like

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
43.2k views132 Upvotes319 Comments

We lack AI governance policies28%

We’re banned from using these tools37%

Our staff and/or leadership are resistant40%

We have concerns about the results being generated46%

We have third-party security and risk concerns25%

We don’t trust current vendors5%




Community User in Software, 11 - 50 employees

organized a virtual escape room via - even though his team lost it was a fun subtitue for just a "virtual happy hour"
Read More Comments
11.3k views26 Upvotes63 Comments

Deployment frequency32%

Cycle time48%

Change failure rate50%

Mean time to restore33%


Coding time22%

Pull request pick up time16%

Pull request review time11%

Pull request size10%

Deploy time22%

Deploy frequency19%

Rework rate13%

Another metric (please share in a comment)2%


314 views1 Comment