Jason GormanIf the only opportunities for advancement in your organisation beyond "senior developer" require a move into mgmt or team leadership, that will work against the stability of your teams. Seriously consider hands-on dev career paths with equivalent status and rewards.
I see no real reason why a developer can't reach CTO-level status (and pay) within an organisation, while continuing to work where they offer the most value: mentoring and setting an example for teams.
Daniel Barlow@jasongorman for the developer to negotiate a CTO-equivalent pay deal, they need to understand and communicate their value to the business which means having at least as good an understanding of how the business operates as they would in any of the "management" positions they're trying not to end up in.
@jasongorman nobody in the C suite is going to say "hey, we noticed you're worth 3x as much as we're paying you - here, have a pay rise" (unless a competitor is offering 4x as much....)
@dan In some major software companies like Apple and Google, a Distinguished or Principal Engineer can get paid > $1M a year.
@dan A bank or a supermarket chain is every bit as reliant on these skills as Apple and Google, for example.
@jasongorman going to go out on a limb her and suggest that in a bank or a retail chain the programmer's job is to take the top card off the backlog, and the "product owner" is the one who decided to put the card there in the first place.
Ours not to reason why, etc etc
Ours not to reason why, etc etc
@dan That's often true today. But as smaller, nimbler competitors start taking market share, it might not be true forever. e.g., a major car manufacturer I've done training are spinning off a chunk of development because their legacy mindset was working against them (unions, pay grades, command-and-control etc). I'm seeing more businesses realise "We're not built to succeed at this" and finding ways to restructure so that development is done in orgs that work more like tech start-ups.
@dan And pay and career paths very much a part of it.
@jasongorman yeah, though the reverse can happen too. Company gets bigger, decides it needs a "product org" that sets direction,with the side effect that it keeps developers away from customers