6 ms·
I won't bother with coding interviews. I consider them to be "hazing rituals"; not actual qualification assessment. I am very, very fortunate, in that I don't h
by ChrisMarshallNY 5y ago
I won't bother with coding interviews. I consider them to be "hazing rituals"; not actual qualification assessment. I am very, very fortunate, in that I don't have to deal with them. I am not looking for work, and plan to never look for work, ever again.
I have a giant portfolio[0]. It has links to 40 or so repos, with tens of thousands of lines of code, spanning decades. Just about every project can be cloned, built, and submitted to the App Store, or SPMed into your own work, in about thirty seconds.
I've written stuff that is now a worldwide standard infrastructure, and the links to that work is in my portfolio, as is a blog entry, where I discuss the strategic thinking that informed its genesis.
I've written dozens of articles, tutorials, and blog entries, that detail the way I think, work, document my code, evaluate and implement architectures, and work with others. Links to all that is...you guessed it...in my portfolio.
There are years of checkins, so things like development velocity can be measured. My GH ID is solid green.
If you aren't willing to even look at it, then we probably won't get along, and we're both better off, avoiding each other.
[0] https://stackoverflow.com/story/chrismarshall https://stackoverflow.com/story/chrismarshall
- leet_thow 5y agoI'm in the same boat. Fortunate to have worked at startups that exited succefully and now in cushy corporate job. If I went out and did interviews I would just make enemies.
- ___luigi 5y agoGREAT work! I can understand why big companies use LC type of questions to assess coding skills of those who graduated recently or didn't enough experience to show their work, but I struggle to understand why many Startups adopted such way of evaluating engineers. I see many startups nowadays asking to candidates to reverse a tree, a task that doesn't reflect the daily work in a startup (where people change gears frequently). I understand that people interview to join the big company, pass a certain bar and then get matched to a team, the startup is too small to not have clarity on what skillset they are looking for.
- deleted 5y ago[deleted]
- b20000 5y agoreversing a tree does not mean you are capable of getting anything done, it just means you bought that shitty book called "cracking the coding interview" and grinded enough of the sort of questions the book covers. besides, you have grinded enough of that stuff in college, if you went to any reasonable quality college anywhere in the world with a CS program.
- lumost 5y agoAs an experienced engineer Apple I'm sure that you've noticed a few trends such as. 1) There are those who are unfamiliar with core comp sci concepts, and are still very productive in many kinds of engineering work. 2) It can be difficult for a team that codes frequently and sometimes does need to deal with algorithms and other items to onboard a new team member who's not very good at the act of coding or very familiar with when to use what or how to make something that does one thing do another. 3) Very experienced and skilled people sometimes forget how to do the basics but with a little practice do fine. 4) Those who are experts at the fundamentals tend to learn any new product area relatively quickly, which is a much better approach to hiring than looking for Go + AWS engineers with 20 years of experience ;) As an interviewer/hiring company hiring many engineers you then have to decide whether you should have a different process for hiring experienced engineers compared to junior engineers or otherwise deal with the awkward circumstance that an experienced candidate maybe isn't just rusty but doesn't have the knowledge or execution ability to code. When hiring an internal transfer it's fairly easy to vet the latter criteria, but when hiring externally it's substantially harder.
- ChrisMarshallNY 5y ago> 1) There are those who are unfamiliar with core comp sci concepts, and are still very productive in many kinds of engineering work. That's me! But...wanna see something cool?[0] That's a link to the maintenance manual for my very first engineering project, started in 1986-7 (PDF doc). I wrote it, as well as the project it describes. It contains full source code for the firmware OS, strategic discussions, user guidance, chassis, and electrical diagrams. My very first project. At the time, I was a high school dropout, with a GED, and some tech training school. I'd never attended one single "core comp sci" class. In fact, I had no idea that "core comp sci" even existed. The engineering team I worked with were all EEs. The firmware team was separate (and a bit arrogant -hard to work with), and my team liked having their own firmware geek, who was quite grateful, for being given the chance. Not too shabby. > 2) It can be difficult for a team that codes frequently and sometimes does need to deal with algorithms and other items to onboard a new team member who's not very good at the act of coding or very familiar with when to use what or how to make something that does one thing do another. I code every single day. How's that work out for you? In my experience, others have a hard time, keeping up with me. > 3) Very experienced and skilled people sometimes forget how to do the basics but with a little practice do fine. Define "the basics." If you mean LeetCode school curriculum algorithms, then, guilty as charged. Also, guilty of not being particularly interested in "a little practice." These represent things that I have seldom encountered, In Real Life. I won't bother wasting time practicing them, if the only place they have utility, is in a conference room that I'll never enter. If you mean "the basic structure of iOS applications," "device I/O concepts," "Shipping to the App Store," or "idiomatic Swift," then, you're in luck! Since these inform the work that I do every single day, I happen to be pretty up on them. No practice necessary. Although, TBPH, I frequently google even the most basic stuff. This will continue for the rest of my life. If you can't deal with that, then we're better off not interacting with each other. I forget stuff, all the time. I google it. This Internets Tubes thing is the pants! > 4) Those who are experts at the fundamentals tend to learn any new product area relatively quickly People who solve difficult problems -every single day- can also be pretty fast on the uptake. Just sayin'... [0] https://littlegreenviper.com/TF30194/TF30194-Manual-1987.pdf https://littlegreenviper.com/TF30194/TF30194-Manual-1987.pdf
- adxl 5y agoYou sound angry maybe you should see a therapist.
- _skhan_ 5y agoYou are proving exactly why we need a standardized way to judge whether a candidate is hirable. All the candidates I see have almost zero history of contributing to OSS or maintaining side projects. Their work history usually consists of some run of the mill experience. I have to rely on that and absolutely do not expect them to have a green GitHub. I would hate for that to become the norm. That is why we need to ascertain coding signal. And that is why we need some contrived problem to provide to ascertain within a reasonable amount of time whether a candidate is a yes/no. You are a unique data point and hundreds and thousands of other developers just don't have that kind of clout (I didn't look through your resume thing). Also, from a hiring perspective, it's not scalable going through a candidates repos and verifying their worthiness. However, it is fun to talk about them during interviews.
- ChrisMarshallNY 5y ago> Also, from a hiring perspective, it's not scalable going through a candidates repos and verifying their worthiness. However, it is fun to talk about them during interviews. I was a hiring manager for 25 years. I would have killed for this kind of information. The people I hired were no slouches. It was a big deal, and not to be taken lightly. I loved multi-page résumés.
- gravypod 5y agoFor a long time when looking for work I got absolutely no callbacks. A friend looked at my Resume and said "You have this huge block of skills you say you have but you have no explanation for how you have them." I explained it was because I got most of my experience from working on OSS software or software for myself and if I listed everything my resume would be ~2 pages & ~4 sides. He said to go for it despite everyone else telling me at my age (18 at the time) my resume shouldn't be that long. As soon as I listed everything I started getting calls back.
- b20000 5y agoso this basically means people assume you are lying and a fraud, which is another problem that is not talked about enough - it should not be assumed that you are like that, until proven otherwise.
- bastawhiz 5y agoOn the flip side, an interview where you're doing relevant work with another engineer is a way to evaluate whether you're a decent person to work with. I've hard-passed on candidates with immaculate resumes and huge open source portfolios because they were rude and insufferable. When you're hiring, you're building a team, you're not hiring individuals who work in isolation. In a previous life, I was forced to work under a very senior engineer who was/is a well-known thought leader with a handful of books published. His leadership was nothing short of abysmal: he had no people skills, answering questions with links to e-books he'd written for O'Reilly in lieu of responses. The best engineers got tired of being micromanaged and nit-picked and left. It doesn't matter how smart you are if the other people at the company hate working with you. There are many coding interview objectives (and I won't defend interviews which try really hard to ensure you know how to code) but pair programming and systems design questions are absolutely necessary to understand whether the person you're hiring isn't just qualified, but rather the kind of person who will make the team better overall.
- goodrubyist 5y agoBut, how are you qualified to make that determination (as in whether a person is decent enough to work with)? Isn't it likely that you either get a skewed impression of this from an interview or that you are biased yourself? The person you reject for lacking decency could be your interviewer in another situation, and reject you for the same reason. * not trying to imply that there is no objective way to define/measure decency
- bastawhiz 5y agoThere's no objective measure of decency. I'm qualified to offer my subjective input while evaluating the candidate because I'll be on the team that has to work with them. And frankly, I'll happily take the L if the candidate rejects me as the interviewer at another position. I have no right to assert that I'm the best possible candidate for their role because the job at hand isn't strictly about quantitatively measured qualifications. Though, if I rejected a candidate for being unpleasant, chances are I'll withdraw my application upon seeing they're and interviewer. Why would I change my mind about working with that person?