News for hackers. Stuff that matters.
Re:Where the hell are great senior developers and hands-on e... by brudgers on Wednesday April 13, 2016 @11:40AM (#11489111)
Looking at the company's careers page, I get the impression of old school enterprise meets academia. Entry level administrative positions [clerks] require a bachelor's degree. Senior administrative positions want a CPA or a JD. An employment office position prefers a Master Degree.

What about software engineers you might ask? Software engineer positions include "Senior", "IV" "III" "II" etc. I'd say this is poor signaling. If Roman numerals ever suggested an engineering culture, it's one that was well over by 476 CE [when Odacer became King of Italy rather than Emperor of Rome and an important milestone for Gibbon].

What does that structure optimize for? The Techonolgist II at some college or government who wants to be a III and the IV who wants to become a Senior. These are people who are fine as part of formalized bureaucracies. Who else? People taking a shot bullshitting through an interview structured around categorizing a software engineer as a II or III or IV or a Senior.

My intuition is that the problem of attracting the right sort of engineering talent is cultural fit. As Salvor Hardin quipped "an atom-blaster is a good weapon, but it can point both ways."

Good luck.

Re:Where the hell are great senior developers and hands-on e... by obiefernandez on Wednesday April 13, 2016 @01:41PM (#11490375)
Thanks for the critical feedback. We hadn't considered bad signaling with the leveling. It's fairly new and replaces senior designations that had their own problems.
Re:Where the hell are great senior developers and hands-on e... by brudgers on Wednesday April 13, 2016 @01:57PM (#11490553)
Since I am on a roll, toss out "engineer" and go with "developer" or "programmer". In the world of real-honest -to-Uncle-Bob-engineers, a senior engineer has a license and is often legally responsible for the work done under their supervision to the point of direct personal liability. That's why in a Civil Engineering context "I,II,III" make sense, there's a progression of credentials and responsibility.

Choosing "engineer" also says something about culture. Combined with a no formal credential job description, there's a cultural tension.

Incidentally, I gave up on a meaningufl use of "architect" years ago.