As a software engineer for 20+ years, I've talked with my sister, who is an ER doctor about this often. Most folks outside of engineering think our interview processes are crazy.
Keep in mind, there's significantly more training that goes into the medical field, so there's more emphasis on the institutions. Where did you go to school? What hospitals or facilities did you work with? Your resume and references speak more strongly.
Other hurdles in software engineering hiring:
- It's both a technical and (often) a creative field.
- Most work requires teams to complete and there's very little insight into who contributed what into a project.
- You don't have many of the signals from other fields, such as published papers, law cases, or hard numbers such as sales, certifications, etc.
Long story short: we don't have good mechanisms within companies to measure engineering productivity, let alone measure programmers outside of an institution.
I'm reminded of Steve McConnell's intro to "Software Estimation":
"Meanwhile, the typical software organization is not struggling to improve its estimates from +/-10% to +/-5% accuracy. The typical software organization is struggling to avoid estimates that are incorrect by 100% or more."
We have certs in software engineering, but in my experience, they've largely failed as an indicator of qualifications. Some hiring managers see them as nice to have, but I've also met hiring managers who are actively skeptical of certifications.
We also don't have differentiation of software levels or skills. If you're a programmer, you could, in theory, go program anything from web to AI to robotics. You don't have to be certified to work in nearly any industry. And we don't have formal hierarchy of skilled work, such as EMTs, nurses and doctors.
We're a relatively young industry that just hasn't worked things out yet and, to be honest, in the United States, there isn't pressure by employers to get our act together. The engineers themselves are in charge often and we're skeptical of boards and authority. We have too many stories of folks making it big with no formal education. Those with the money aren't demanding change because the current system "works."
It's possible software engineering will someday evolve into a boring respectable profession, but right now it's still a creative field of fads, trends, rock stars and super stars (let alone ninjas and wizards).
To me they are a red flag. Someone couldn't get a good job in a bull market straight out of undergrad and felt the need to get additional training...
> We also don't have differentiation of software levels or skills. If you're a programmer, you could, in theory, go program anything from web to AI to robotics. You don't have to be certified to work in nearly any industry. And we don't have formal hierarchy of skilled work, such as EMTs, nurses and doctors.
It still exists, it's just that it's informal.
Hi I'm Ed Barns I'm here for the interview of ER Physician.
QUICK Put on your scrubs we've got a patient here with a bone dangling out of his arm.
No you don't understand I'm just here to interview.
THIS IS THE INTERVIEW HURRY UP.
It's also a big part of residency (having to treat patients with diminishing supervision from senior doctors). So it's not that far fetched.
They do, but not for the reason you think.
A hospital administrator would be mad to hire some rando from the street who calls himself a doctor, who has no formal schooling in medicine, a dropped two-year degree in chemistry, but who reads a few medical blogs, on nothing more than 'They have four years experience working at a startup and a good reference and they can answer some second-year whiteboard questions about the lymphatic system.' [1]
Other professionals front-load the interviewing effort into a rigorous schooling, testing, and accreditation process, that costs hundreds of thousands of dollars and years of your life. Meanwhile, software engineers grouse about whiteboard interviews.
[1] Despite the highly dramatized performance by Leonardo DiCaprio as Frank Abagnale, that's not generally how doctors get hired.
With software you can write a TODO app with a million lines of code or 7.
Fundamentally though I think that system of high priests and laypeople who are barely allowed to code at all can't be sustained. I strongly suspect all professions will eventually require a little programming, and certification will be hard for those cases.
That, and the field moving so quickly and being so broad. I interview for ML. I assume interviews for front end are extremely different.
This exists in Canada for some areas of software development that falls under the requirements of being a licensed software engineer.
Many people, including CS graduates in Canada, think it’s ridiculous. The requirement for certification is pretty strict in that you need a computer engineering undergrad degree or a degree in software engineering from an accredited program. This is probably how most people would be accredited, but there are some other ways too. All of them, as far as I can gather, require formal educational credentials.
You then need to go through a formal apprenticeship while working under someone who is licensed. It’s probably an 8 year process in total.
Further to that, there is a limitation on what you can practice. There are different disciplines (e.g., mechanical, civil, electrical) and there are fields and scopes of practice within each of those disciplines. What this results in is someone who is licensed in, for example, embedded systems wouldn’t then be able to go and work on websites or back end databases.
The field is further divided into technologists and technicians that require less education than engineers and have much less autonomy and scope of authority.
I'd hire that one over anyone pushing horse de-wormer, anti-malarial drugs, or homeopathic remedies.
Meanwhile in Software there are initiatives for "Gender X of Minority Y can Code" and "Everyone can be an Engineer after 3 months of BootCamp".