Google has at least ten levels of engineering progression and arcane rules about moving from senior to staff to fellow (really?!) As you might expect, this is confusing and distracting and unfair; it's nearly impossible to align 20,000 engineers to a single company strategy, and you have to treat everyone as a statistic to have even a hope of keeping them straight.
Now Sundar is welcome to ring the Squirrel-Phone if he wants my advice on reshaping this setup (throw it out and decentralise!) but for some weird reason, lots of others with much smaller teams want to follow Google and create Byzantine spreadsheets to track the progression of their ten or 50 or 100 developers. I had someone ring yesterday asking for help creating a "skills matrix" for just one person! This is complexity for complexity's sake; stop it already!
Join me and my guests Jonny Burch and Neil Cameron of Progression, a company whose mission is creating effective growth frameworks, to discuss how to ensure every developer knows how you're going to help her improve skills and grow her talents. Sparks may fly, I don't know whether they agree with me, but I guarantee we'll help you create a positive, learning culture.