I found this interesting, although I wish they linked to their
guidelines for the various flavours of developers they talked about.
While the article mentioned 5 levels (associate, dev, senior, lead,
principal) the article is devoted to the distinction of “regular”
developers and senior developers. Yet, they pointed out that they have
to communicate these levels to aspiring candidates—so why not just
link to them from the article?
You can call me King Banana for all I care as long as you pay me what I’m looking for. It doesn’t take very long in this industry to realize that a title has zero relevance to just about anything.
That being said, it’s nice that they’re trying to offer some sort of career advancement in an otherwise flat organization.
I found this interesting, although I wish they linked to their guidelines for the various flavours of developers they talked about. While the article mentioned 5 levels (associate, dev, senior, lead, principal) the article is devoted to the distinction of “regular” developers and senior developers. Yet, they pointed out that they have to communicate these levels to aspiring candidates—so why not just link to them from the article?
You can call me King Banana for all I care as long as you pay me what I’m looking for. It doesn’t take very long in this industry to realize that a title has zero relevance to just about anything.
That being said, it’s nice that they’re trying to offer some sort of career advancement in an otherwise flat organization.