2 ms·
To be clear: if you fail a coding interview question and your self-judgement is accurate then either the interview question is a bad question, or the interviewe
by mike_hearn 7y ago
To be clear: if you fail a coding interview question and your self-judgement is accurate then either the interview question is a bad question, or the interviewer is a bad interviewer, or the process has a problem.
I don't think many (any?) of the people I've hired this way have spent time practicing coding interviews, let alone on HackerRank. The questions asked are simply not challenging enough to require drill. If you can code competently in your daily job you can pass them.
- ChrisMarshallNY 7y agoOh, heck. I didn't even see the reply. Probably right. Depends on the question, I guess. You know what I mean, use questions straight out of textbooks that have only been in circulation in the last five or ten years. I've found that it's easier all around if I simply don't hide that I'm over 40. It means a lot fewer responses to inquiries, but also a lot less wasted time. Avoids that crestfallen look when you walk in the door. Apparently, the industry is crawling with folks that are under 35, but have the judgement and expertise you get from 30 years' of programming. I'm also puzzled why folks would think they can learn more about me from a twenty-minute test, than by looking at ten years' worth of code in dozens of repos. I was a hiring manager for many years. I would have drooled to see that kind of background on any one of my candidates. Still, I generally found that I was able to accurately judge their competence after about a half-hour chat (at least, I never seemed to get it wrong), and it was all about cultural fit, after that. I suppose being an up-to-date engineer, myself, helped.
- ChrisMarshallNY 7y agoAlso, I know that no one will ever read this, but I figgered I'd put it there for posterity. It's amusing, when I say "I have a published open-source portfolio that consists of XXX LoC, ten years' worth of checkin history, in XX numbers of repos.", the response is "IF what you say is true..." Look for yourself. I can back up every single claim I make. I don't pretend that all my code is screamingly efficient or the best-written code on Earth, but what I do have, is tens of thousands of lines of super-high-quality, well-documented, code, graphical assets (including the original vector masters), clever designs, design documents (including things like OmniGraffle originals), Medium and blog postings -often going into very deep detail about my designs, architectures -and the decisions while developing them-, GitHub issues and responses, Apple RADAR reports, and multiple published, high-quality, well-branded apps on the App Store. Sheesh. Don't take my word for it. See for yourself. Now, THAT being said, why doesn't everyone have a portfolio? You ever see a designer or graphic artist going to an interview? They bring along these big black cases (although nowadays, it's probably more like a laptop case). These cases contain drawings, printouts, raw materials and sketches, etc. They are called "portfolios." Even students, fresh out of school, have them. It's considered a requirement. No design firm on Earth would ever consider ignoring one of these, and instead, pull out a matchbook with "Draw Spunky" on the cover, and insist on that being the hiring criteria. Which is EXACTLY what most software shops are doing, these days.