I've worked at places that are loaded with senior engineers/developers. It can be awkward from a business sense because: a) Most of your developers are too expe

I've worked at places that are loaded with senior engineers/developers. It can be awkward from a business sense because: a) Most of your developers are too expensive, so you put very few of them on any project, b) Senior engineers usually have a lot of ongoing efforts that require their attention, while a mid-level or junior might be able to to focus more on your current spring, c) Senior engineers can (but not always) be more set in their ways on technology or methods and be resistant to embrace newer/riskier approaches, and d) There's no room in the org to promote your mid-level engineers, so they leave and become senior devs elsewhere. At my first full-time development job, we had only entry-level and senior devs with no mid-level folks. As one of the entry-level folks, let me tell you-- what a mass of confusion that was. Hopefully Red Hat's targeting more of a well-rounded or balanced organization, rather than purely cost-cutting measures.