3 ms·
I wish we had an option to move more towards how other engineering disciplines handle a lot of these problems: standardized training/college course work (ABET a
by WorldMaker 10y ago
I wish we had an option to move more towards how other engineering disciplines handle a lot of these problems: standardized training/college course work (ABET accreditation being a major deal), licensure boards and procedures and certifications (EIT [Engineer in Training], PE [Professional Engineer], certifications in various specialties).
To a general (classical?) engineering firm (like my current employer), my two ABET accredited degrees mean a great deal. To most software companies they don't seem to mean anything, but at the very least I wish they meant "can handle a FizzBuzz". (A recent derail for me in an interview a couple years back was someone scoffing at me when I said "Oh yeah, I saw problems like this back in college" as if I couldn't possibly have... It is quite frustrating that the default seems to be that academic background and resume experience are "lies" compared to ability to run a puzzle gauntlet.)
In my current job I could get a small favor/title bump if I did all the hard work to get an EIT/PE after my name (and there is a Software PE now; unlike back when I graduated), but all that hard work would probably not be worth it because it wouldn't be recognized by most software jobs.
There's a chicken and egg problem here with jobs not trusting certifications because the certifications aren't common enough, or comprehensive enough/well suited enough for that particular businees, because no one gets certifications if companies won't hire them or won't privilege them at least enough to skip interview shibboleths like FizzBuzz and some of the puzzle gauntlets.