4 ms·
I've been in software tech for nearly 30 years. Never had a "technical" interview, puzzle solving, or anything like that. I would not take a job that screened c
by ams6110 10y ago
I've been in software tech for nearly 30 years. Never had a "technical" interview, puzzle solving, or anything like that. I would not take a job that screened candidates that way.
If references and credentials and track record aren't enough, I would look elsewhere.
- treve 10y agoGood for you that the market is so good, you can be insulted and walk away from an interview and still find a different job that doesn't do an extremely standard thing: basic technical screening. Your credentials might speak for themselves. After all, you've been working for 30 years. 80% of the people I've hired have between 0 and 5 years work experience and without a technical screening I might as well just give them the job based on dice roll. Usually I don't check credentials, and only use a resume to make a selection but don't use it _at all_ to determine if you're a good candidate after you've come in for an interview.
- white-flame 10y agoI think most experienced people would agree that a technical interview could be appropriate for someone with 0-5 years of work experience. For somebody with 10+ years of experience, who you can find that talks the talk during a real interview, CS101-level quizzes are insulting and inappropriate.
- pklausler 10y agoIME it's not about asking easy questions, it's about asking questions about "programming in the small" that are relevant to day-to-day work. I conduct lots of technical interviews and I've found that it's just as important to ask the 10+ year veterans about the fundamentals as it is to ask the new grads. It's just way too easy to talk about programming while actually being incompetent at it. Only by having a candidate write real code can an interviewer detect the difference.
- wpietri 10y agoI have worked with people who have 10+ years of experience and can talk the talk, but are still pretty bad at the day-to-day work of writing software. I also have worked with some great developers who aren't so good at interview-style conversations. I agree CS quizzes are a bad interview technique, which is why I favor pair programming. But I've never had a good candidate feel insulted by asking to sit down and code together for a while. Indeed, the #1 thing good programmers have in common is they like programming.
- inputcoffee 10y ago1. You are fortunate to have that option. 2. Do you think you might have sold yourself short? In other words, if you had practiced one of these do you think you might have ended up in a place which you enjoyed more? The premise of question 2 is that the interview process does not represent the job or company. In many cases, I think this premise is valid.
- btilly 10y agoI've been in software tech for nearly 20. Only once did I take a job which didn't require coding in the interview process. I quickly regretted it. It is amazingly easy for BS artists to look good on references, credentials, and their presented track record. And yet fail fizzbuzz.
- stanleydrew 10y ago> It is amazingly easy for BS artists to look good on references, credentials, and their presented track record. And yet fail fizzbuzz. So what? Just fire them quickly. Or put people who aren't so naive in charge of the hiring process. Most of the time the actual problem is that "hiring managers" aren't practicing their trade anymore, and even in a simple conversation aren't sufficiently able to sniff out extremely obvious underqualified candidates who wouldn't be able to solve fizzbuzz. Here's perhaps a good test for hiring managers. Have them interview 10 people who would normally apply, and just have a conversation. Make sure at least one person can't solve fizzbuzz. Ask the hiring manager to predict whether each candidate can or can't solve fizzbuzz based on their conversation. Anything less than 100% predictive accuracy and you can't be a hiring manager.
- robotresearcher 10y agoCan't you just find out if your hiring manager is good in a simple conversation?
- stanleydrew 10y agoI would hope so I guess, but apparently according to OP a lot of hiring managers are duped by people who give off the appearance of software engineering aptitude but who can't solve fizzbuzz.
- mrkurt 10y agoWork that requires creative output needs auditions.
- drakenot 10y agoFlip side -- I view it as a strong negative if a company has what I consider a weak interview or vetting process. The interview doesn't have to be all whiteboard coding but I want to at least feel like the person got some grasp of my technical ability. If the entire thing is basically a "personality interview" I start to think that it is very possible technically weak people may have been able to schmooze their way into a place in the company and I'd prefer to not work with a high ratio of bozos.
- pnathan 10y agoThat's a definite possibility, and something I've observed in my travels. :-} I don't know that I want to be scribbling code on a whiteboard, but I do know that I want to work with an organization which carefully vets its hires.
- legohead 10y agoCurrent company I work had me write FizzBuzz on paper, and that was mostly it for the technical interview. They asked about my history and I talked about projects and such, but it was probably the easiest interview I've ever had. And this is my favorite job I've ever had as well.
- stanleydrew 10y agoWouldn't simply taking an IQ test, or submitting your SAT score along with your resume serve the same purpose then? If the goal is to reveal "technical ability" this would save a lot of time.
- driverdan 10y agoI can't tell if you're being sarcastic. IQ and SAT score show nothing about your coding abilities.
- stanleydrew 10y agoI'm not being sarcastic at all, but I can see how my comment could be interpreted that way. I don't have evidence (though I'm sure I could find it) but I think IQ and SAT scores are probably very highly correlated with coding abilities. Coding is just analytical problem solving after all. So I honestly do think IQ and SAT score have almost as much predictive power of your ability as a software engineer as a simple coding exercise. Honestly, I'd bet the only extra predictive power comes from the fact that correctly solving fizzbuzz reveals an underlying motivation and interest in software engineering. "Coding abilities" aren't innate. Writing a for loop in Java isn't something you're born knowing how to do. Everybody learns it at some point. Think about it this way. Take two people with the same IQ test result. One of them can solve fizzbuzz, and one of them can't. How much would you be willing to bet that the other one won't be able to solve fizzbuzz if you or I teach them about Java for two weeks?
- wpietri 10y agoHuh. I agree that puzzle interviews are useless, which is why I do interview that involve work-ish activities like coding and technical design of features. But I'd never go with references and credentials on their own. On one side, that allows bluffers and bullshitters in. And on the other, it excludes people who would be perfectly good, but either aren't good at selling themselves or don't yet have a track record.
- Pyxl101 10y agoPeople claim all kinds of things as part of their resume and track record that aren't true. It's simply routine. People who were on a team that worked with a technology list their technology as something they know. People who were on a team that delivered a product claim the product delivery as their own. Drill into what exactly their role was during conversation and you'll get a much different story. Ask them details about the technology listed on their resume, and you'll quite often find that they know little about it. Resume inflation is so standard that filtering it out is not even a question. You know what's honest and true? Put someone in a room and talk to them, and see how they react to a situation and perform. See what they can figure out from first principles. Strong performance in these situations (problem solving, i.e. reasoning from first principles) correlates very well in my experience with strong performance on the job as a software engineer.