alt Hacker News> Interesting, you've got it absolutely the wrong way around.
Maybe. That's why you need to put your scope on the resume :)
I had a CTO title 15 years ago. The complexity of what we were building was a joke compared to what I own now as a lowly "tech lead manager". And in fact back then I wouldn't even be able to comprehend how complex things can get.
Replies
elevatortrim • yesterday at 8:45 PM
That may be your anecdote but CTO at a 30-50 person scale up would typically have much more management/accounting/signature/high-stake conversation/... experience than a senior developer at google.
➕ show 3 replies
zelphirkalt • yesterday at 10:02 PM
Well, what do you even mean by "put your scope on the resume"? Do you mean literally "Scope: blabla" for each occupation? Or do you mean something more implicit?
➕ show 1 reply
> That's why you need to put your scope
The problem is, "scope" is often equated to "how many people worked in my empire" rather than "how much business value did my work X generate".
The two things are vastly different, and I have seen the distinction/oversimplification play out over and over in my own career as well as many others around me.
As an extreme on the "individual technical expert side", there are things out there that can pretty much only be accomplished with a few people around the world who possess the dedicated expertise. These results can't be replicated by a cobbled together team of 10 or 100 people even though the latter sounds more impressive for "scope".
Some organizations do a decent job of recognizing these different "archetypes", many don't.