4 ms·
One of the problems I've seen constantly, for 10+ years (been working for 20+, interviewing others for approx. 10+) is that there has never been a "baseline" sk
by ryandrake 3y ago
One of the problems I've seen constantly, for 10+ years (been working for 20+, interviewing others for approx. 10+) is that there has never been a "baseline" skill level that you could always count on when you got a candidate in front of you. Any given person's programming and problem solving skill level could be absolutely anywhere on the spectrum between 1. "super proficient, fluent in multiple languages, highly structured thinking, clearly articulates a solution, can mentally visualize over a range of 20 orders of magnitude" and 2. "literally has no idea how to solve a problem, program a computer to do it, or even describe coherently what they are thinking". And these two extremes can have the same resume.
Some first level of the hiring funnel (HR, recruiter, or something) screens the candidate by looking at the resume and maybe doing an initial phone screen, and then this person gets dumped on the interviewer, and they 100% could be anywhere on that skill scale. So you always seem to have to start at "how do you turn a computer on?" and "write code that finds a substring in a string." It's really frustrating for the interviewers and I'm sure also insulting to actually good candidates.
I've never been in one of these businesses, but I bet if a hospital interviews a doctor, they can at least count on basic knowledge of anatomy, and if a law firm interviews a lawyer, they can assume the person has read a law book. We have no such guarantees in software.
- majormajor 3y ago> I've never been in one of these businesses, but I bet if a hospital interviews a doctor, they can at least count on basic knowledge of anatomy, and if a law firm interviews a lawyer, they can assume the person has read a law book. We have no such guarantees in software. If the cost of those guarantees is formal specialized training costing hundreds of thousands of dollars, I'll stick with the world of phone screens - speaking as someone who's been both rejected-after-phone-screen and rejected others after a phone screen.
- ryandrake 3y agoI used to feel the same way, and yes, reliance on credentials and formal training often serves the credentialing and training industries. But, I don't think our industry's current 'free for all' ultimately serves anyone. We should consider an inexpensive, very basic "programmer's bar exam" to establish a (admittedly very low) proficiency baseline. I'm not asking for a test that gatekeeps software engineering only to people who can write a compiler. I'm asking for a reliable document that says this person can write a loop and a conditional statement and can reason about how it works. Is this a lot to ask for?
- mewpmewp2 3y agoI feel like it's quite quick actually. I think of software eng interviews as binary search type of thing. You ask a mid difficulty question. If they don't know answer to that, you'll ask 0.25 difficulty question and so on. Although obviously, if the first question was a fluke, you'll adjust your cursor, so in the end it's not entirely binary search, but it is similar in its approach. Perhaps there is a better analogous algorithm for that. The point is that, if they can answer very well more than 75% of your questions, you increase the difficulty, otherwise you decrease. And the better they answer, the more you try to challenge and argue them. What I do hate however is leetcode. I'll avoid that completely as an interviewer, as I feel like it would only help me determine whether they are the type of people to spend hours on leetcode. I'll want to try to understand their passion to build and produce a product that solves something and provides value for their customers. Leetcode culture is contrary to that to me. To me leetcode culture is something where you play the game to increase somewhat irrelevant skills to get to a prestigious company to optimise for your total compensation. Which is fine, but it's not something I think that would be great for me to try to find best members for my team. I haven't looked for a job in a while, but I'm bringing this up because in my experience when I was the candidate I remember people being quite rigid in their questions, for example questions being predetermined, which meant they ask me non-sensically easy questions, which considering what kind of questions I had answered before it would make no sense that I wouldn't know answer to those questions. So a lot of time-wasting. Or in the other direction they could be asking similar questions in similar difficulty and area of topic, where someone clearly shows they no experience with, instead of trying to understand all talents of the candidate.
- hinkley 3y agoFizz-buzz tried to set this, but I’ve run into people who have trouble making compound decisions with compound data, so I ask slightly tougher ones, like sort these users by name. First, last, middle, maybe age or date created. Or take this array of items and give me a map that uses the name as a key. I had one guy who could do a lot of front end work well but he could not pivot data to save his life. It was super weird. Like Derek Zoolander ambi-turner weird.
- nradov 3y agoThere's nothing weird about it. There are many programming domains where maps and pivot data are totally irrelevant. They just never come up. Developers who have specialized in those fields for years might just need a quick refresher on data structures.
- hinkley 3y agoIt was a situation where someone had to fix his code three times in six months. There’s a point you sit down and sort it out. Ajax data doesn’t always match the page structure.
- nextos 3y ago> [...] literally has no idea how to solve a problem, program a computer to do it > [...] but I bet if a hospital interviews a doctor, they can at least count on basic knowledge of anatomy Does the same situation arise if you pre-filter requiring a CS/EE degree from e.g. a top 1000 university? MD degrees are highly regulated, so you would need some stringent pre-filtering to make both situations comparable. Otherwise, I guess it is natural to find a lot more variability in candidates?
- constantly 3y ago1,000? Almost certainly. 100? Maybe not. 20? Probably not.
- nradov 3y agoCS/EE degrees aren't particularly focused on programming so if you want to hire programmers then that would be a rather silly filtering criteria. It's like if I need to hire a plumber I don't look for candidates with chemical engineering degrees.
- nextos 3y agoThis is a very contentious statement. I studied CS at two very different EU universities and there was a massive focus on theory plus programming. All courses had huge coding projects where we had to build real end applications, including courses with a very strong theoretical component, which made things really tough.
- majormajor 3y agoIME yes. I've worked with a couple folks from MIT - which I imagine is "top N" for a pretty small value of N for most anyone - who knew a lot but could build very little quickly or effectively. What you get graded on in schools for CS or even SWE is pretty different from what you get graded on on-the-job.
- ghaff 3y agoIn the case of the lawyer, if it's a big city firm, (whether this is right or not) they'll look at where they went to school, whether they were on law review, and who they clerked for. And with that done, it doesn't matter a lot anyway because they'll be an overworked associate who can be given lots of crap work to do and if they don't make partner, they'll probably be pushed out. Funnily enough, one of my best jobs in tech included an interview with who would become my hiring manager. (I don't think the company had actually figured that out at the time as they were writing the job description for me.) I don't think I had ever had an interview that I just couldn't read like that one. Years later, after he was no longer with the company, I sort of asked him if I had really bombed and he basically laughed and said he was always tough on interviewees. (And he was always really tough to read.) It also probably didn't help that I hadn't had a real interview in at least 10 years.
- D13Fd 3y ago> In the case of the lawyer, if it's a big city firm, (whether this is right or not) they'll look at where they went to school, whether they were on law review, and who they clerked for. This, plus grades and class rank. And there is a series of interviews, obviously. For a young associate, grades/class rank are a decent proxy for how hard working they are and whether they have an aptitude for the basic practice of law.
- mistrial9 3y agoyes agree and .. in the mid 2000s there was a concerted double-edged change in interviewing that I could see. One came from Redmond and was an exercise in intimidating the candidate with a whiteboard, and the second came from Google where they interview you like you just defended your PhD at a top University.. so do it again now with the problem of my choice. Like any trend, the third, fourth and fifth level players heard of this and imitated it. All of this combined with seniority not for coding, but for the mercantile aspects - if you formed and sold a company then you are senior, otherwise no.
- ReactiveJelly 3y ago> I'm sure also insulting to actually good candidates I don't mind it much. I don't have great social skills but I don't mind answering simple questions. If someone is insulted by simple questions, they're probably gonna be a bad mentor to junior devs, right?
- vl 3y agoI ask very simple question as a build-up for harder questions (write a function to reverse a single-linked list), probably half of the candidates fail to do in any reasonable time.
- vl 3y agoI suspect real truth OP is not sharing is that they are quick to fire. If this is default in their company, then it’s ok to pick up incapable coder, since it will be corrected in a month or two. Simple coding questions are invaluable at filtering, but of course do not guarantee the result. In last 3 weeks I interviewed 3 candidates, two of them failed to write 40 lines of code based on written requirements. One of them even used Copilot.
- ghaff 3y agoWhile I have never been in sales, the saying I've always heard is that "sales managers have no trouble firing people." There's a very quantitative output--your numbers--and, if you don't make them, even for reasons that may be out of your control--well...
- lnxg33k1 3y agoThe amount of time and energy wasted due to recruiters and hr is so frustrating for me, Ive solved live coding exercise so fast that people thought i was cheating, solved tests in a fraction of the time, etc, overall I can easily do tech stuff in interviews, and just be dumped because I am asked if I am willing to go to friday drinks or company parties and I say I don’t really want, yes, asking if one has the will to go to company parties is so important that its part of the interview process, this system is broken
- isoprophlex 3y agoYou have to be willing to game the system juuuust a little bit. "Yeah, sure, sounds fun". Then don't go. If your actual coworkers instead of the HR drone appreciate you, noone will care. If they do give you shit for "not being a team player", go find another job. But in my experience the former situation will be much more common. You just gotta get past the braindead HR stuff.
- ghaff 3y agoIf someone in an interview basically says they just want to be left alone to program (or whatever), that's at least starting to send a red flag up the flagpole. I'm sure there are some of those at many large companies but the most influential developers I've know were pretty good at working with people and casually interacting.
- lnxg33k1 3y agoI'm very active in companies chat, always step up to help when I have a solution, always step up first when I notice something can be improved, I am not sure how you went from not be willing to socialise/be drunk/be around drunk people, to "be left alone"/"not able to casually interact"
- mytailorisrich 3y agoOn the other hand, there are companies where devs are expected to wait for a Jira ticket to be assigned to them, code it, test it, merge it, goto 1. That's the reality of the job whatever they might claim externally. "I just want to be left alone to program" seems like a perfect fit: will do the job, will not ask for anything.
- hn_throw_127 3y ago>We have no such guarantees in software. To be fair, it's our own damn fault. "Poor stewardship over professional standards" is a succinct way of putting it. The reasoning comes down to poor training, lack of standard competency tests (which is a stable goal to train for), and probably heavy disagreements about what a candidate should be capable of as a junior/mid/senior/principal, or at year 1, 2, 3, 5, etc. of their career. Communication of these standards over blog posts and what you can find via search engines just won't - and hasn't - cut it for raising the competency of the industry as a whole. If you are competent, you can publish a book which becomes popular, but there would still be disagreement about what books are important. As an example, Designing Data Intensive Applications is probably one of the more well-known books, but it's not a requirement to read that. The reason it's not a requirement is that you can meander through most jobs by just googling stuff and no one denies you a job if you can't talk about its content. This problem has gone on long enough that most of us can't give a comprehensive list of what the "basic knowledge" is that we need. Most of us could try to make our own lists, but we'd be much less confident that that list should be the standard because it hasn't received any critical review and approval by a large sample of people. We need to get out of this free-for-all thunderdome. We do that by getting the companies aligned on what they expect. Then they simply don't hire people that don't meet those expectations. Then we can start writing competency tests towards meeting those expectations and simultaneously develop training material to pass those tests. Most importantly, those standards cannot change too quickly otherwise we end up with the same moving target situation we have now. You give me the training material, I pass a test, then I get a junior job and continue training for the expectations at various job title levels. It should be that simple.
- deleted 3y ago[deleted]
- bluedino 3y agoWhy does a doctor or lawyer get a pass? Plenty of admins etc are just cramming exams as well, I'm sure there are plenty of doctors out there that are as bad as some of the programmers/admins out there. Hopefully not as many, or as bad, but still.
- agent281 3y agoTBH, I don't really get the whole "insulting to good candidates" idea.* People who have been in industry long enough should understand that this is pretty common. If they get insulted, that's probably bad signal since they are taking it personally. On the other hand, if the person is annoyed or frustrated by the idea I don't blame them. * Caveat for people with high levels of experience going into more senior job titles.