3 ms·
I actively interviewed job candidates while my wife went through her licensing process to be a doctor. A doctor's job interview spends no time making sure that
by gwbas1c 10y ago
I actively interviewed job candidates while my wife went through her licensing process to be a doctor.
A doctor's job interview spends no time making sure that a doctor is competent. Why? Because the licensing process does that.
The most frustrating part of interviewing a software engineer job candidate is that a degree doesn't show that the candidate is competent. Thus, we need to waste our time on imperfect ways to verify competence when instead we should be selling the organization and judging team fit.
IMO, we need some kind of licensing process where, as an industry, we agree on a way to judge that someone is a competent software engineer.
- jpttsn 10y agoGreat description of the problem. Licensing is going to be difficult in quickly changing fields.
- wapz 10y agoI can imagine licensing being a terrible PIA for programmers. If you work only in c# at work and learn some new language during your free-time, getting a license for the new language could be so time-consuming and not worth it (studying the obscurities of the language and actually taking a test). That is if there is a new license for every language and job type.
- Apocryphon 10y agoJust create a license for algorithms and data structures, since that's the bulk of whiteboarding anyway, since they "don't ever change."
- geebee 10y agoI feel ambivalence about formal licensing, but I do agree this would be a positive element. I would be, even 15 years after the fact, perfectly happy to study intensely for an exam on basic math, data structures, and algorithms, similar to the initial mathematics exams used for the actuarial field. Such an exam would be a lasting and widely respected credential, consistently administered and graded. I wouldn't want to put this kind of effort into a single corporation's exam, because those are graded in secrecy, I have no idea what the credentials are of the people who evaluate it, and I don't get much (any) feedback other than "we decided not to continue with your application at this time...". My worry comes from regulatory capture. I'd hate to see something like a bar association that forces people to go through a very expensive three year post graduate degree, putting them deeply in debt, in order to meet licensing requirements. Would the governing body be allowed to deny math or physics or non-cs engineering related majors the right to take the exam? Also, imagine if people who wrote the EJB spec or the ones who decided all client side code should be written in tag libraries gained control over the licensing procedure? Would the test-driven advocates be able to revoke the license from anyone who publicly questions the value of test-driven methodologies? This could be great - something along the lines of the actuarial exams are appealing to me, as they are rigorous but allow different educational paths to prepare. But this can also go very wrong, it is a real risk.
- WkndTriathlete 10y agoI'm skeptical of licensing as a means of determining ability. No other engineering discipline uses licensing (with the exception of PE roles, for obvious reasons) to determine ability. Think about how mechanical engineers get hired, for instance. "What were some technical challenges you had in your last project? How did you solve them?" would be a couple of leading questions into technical discussions with a candidate. Note that those questions are not specific to mechanical engineering: they are applicable to every engineering and software role. In the interviews I have conducted, asking these types of questions exactly has generally given me a pretty good sense of the technical ability of every candidate, with no whiteboard session or coding homework required. It only takes 30-45 minutes, and I have also found that this amount of time is enough to get a sense of a candidate's culture fit as well. Whiteboard interviews only test how much of a candidate's memorized corpus overlaps with the question presented; as a result, I find that process is only 5-10% as effective as a technical discussion. I want to know if and how (and how well) a given candidate thinks, not if they know the same things I do. Code homework is only marginally better. Most (better) companies have a 90-day probation period anyway. After hire, if a developer is not performing up to expectations for a given role, they can be let go. This is exactly how it happens in every other engineering profession.
- Apocryphon 10y agoCalifornia is an at-will state. Silicon Valley is in California. Tech employers should just embrace the fluidity of the market and mandate probationary periods instead of long, arduous interview processes. Candidates are already mobile enough anyway, if they're let go then let them work to improve themselves until the next gig.