Agree that 99% of the leetcode interviews are divorced from everyday coding work. However, this article goes in the wrong direction in trying to keep the LinkedList premise - how often do programmers see a raw linkedlist anyways? Directly ask coding questions from your everyday work, and skip the linkedlist stuff as 3rd level detail questions; the signal that the candidate can do the job is much higher then. Ex: here…
that sounds like a takehome and should be paid for.
Code Interviews
81–90 of 98 posts
Re: Code Interviews
#82Earlier quoted context omitted.
It is absurd, but is so easy to counteract by just prepping. I’d be a lot more negative about it if it wasn’t so easy to game.
I think this is the point - that it's so easy to game (albeit a waste of time) and that this doesn't reflect on the quality of the hire coming through this process. Assuming this is the test for senior engineer, the greatest candidacy pool would be second-year CS students.
Re: Code Interviews
#83It's also frustrating for job mobility, as you need to move jobs (or at least have offers) to get employers to pay your market rate. But in order to get offers you need to basically start a part time job studying and interviewing. If you just interview with a company you want to work for with no competing offers you will get lowballed - you might also just get rejected because companies prefer high-false positive rat…
why spend 3 months full time studying when you can spend one month full time writing code for a product you can talk about in the interview?
Re: Code Interviews
#84I 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…
You 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 asc…
I'm a unique talent. I'm not God's gift to Programming, but I have a very different kind of backstory from most that you find. I had a hard road, and the uneven terrain that I traveled, has a lot to do with how I became as good as I am. When no one gives you breaks, you are forced to make your own, prove yourself, at every step, and accomplishment becomes habitual. You learn not to overpromise, figure out how to learn new stuff, and check your own homework.
Many of the team I led, had similar eclectic backgrounds. They were all senior-level C++ algorithm developers, with decades of experience. Most were smarter and better than I am.
We all would have been immediately rejected, in barbarous fashion, from today's hiring process.
As it turns out, they have all gone on to do very well, and that makes me happy. I am glad to have been a part of their career. Working with them was a signal honor. They are making their new employers quite happy, indeed, but it took each of them over two years (in a couple of cases, well over two years), to really land, which is quite telling.
In my first three jobs, I never worked with one single engineer that had actually had real software training. I worked with astrophysicists, mathematicians, MBAs, chemists, designers, economists, teachers, electrical engineers, and even other high school dropouts, like me. Even my last, long-term job, was mostly with EEs and physicists, but all the Japanese folks had serious sheepskins. It was a fairly marquée corporation.
Re: Code Interviews
#85Earlier quoted context omitted.
I think this is the point - that it's so easy to game (albeit a waste of time) and that this doesn't reflect on the quality of the hire coming through this process. Assuming this is the test for senior engineer, the greatest candidacy pool would be second-year CS students.
True, but I guess they are also judging our pliability in jumping through hoops, because even us senior engineers have to jump through many. To be honest, I'm probably not jumping through enough of them, cramming for a coding interview is one thing, but jumping in on every welcome!/goodbye! email is something that I really wasn't ready for.
Re: Code Interviews
#86Earlier quoted context omitted.
> Most candidates (>99%) have no work you could actually look at. Most inexperienced candidates... One of my favorite pastimes, is following up on GitHub, with people from this joint, or others, that pique my interest. There's a lot of really awesome stuff out there! You guys rock ! Of course, many of these folks, are... chronologically challenged , let's say. If you've already decided that you will only be hiring fo…
why is this voted down?
Most people have various interests and obligations. The number of people who after a day of work in software engineering go on to continue to do that in their free time instead of pursuing other interests is vanishingly small.
Additionally you have people who also just can’t do this, even if they wanted to, due to other obligations.
Obviously there are people who have a very narrow set of interests and leave their office to go to a hacker space but that is such an absurdly small group that it’s ridiculous to even consider them in hiring.
In fact you probably want to avoid having an entire team of people like this in favor of a more diverse group of people.
Re: Code Interviews
#87Earlier quoted context omitted.
You 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 asc…
Oh, yeah...one last thing, before I go... I'm a unique talent. I'm not God's gift to Programming, but I have a very different kind of backstory from most that you find. I had a hard road, and the uneven terrain that I traveled, has a lot to do with how I became as good as I am. When no one gives you breaks, you are forced to make your own, prove yourself, at every step, and accomplishment becomes habitual. You learn…
The job of ‘programmer’ takes on many shapes and sizes. Businesses evolve and are different from one another.
You may be very successful in some clusters of business, but how representative is this, let alone your unique experience, to the rest of the industry?
If you’ve never worked with anyone with “real” software training, why would I hire you into a senior position when there are plenty of candidates who have?
I’ve worked at companies back in the day where experienced non traditional programmers have both kick started and ruined businesses within the same job. You may be successful enough to grow a business, but that’s different from scaling or pivoting one.
If you can’t grok a homework program from the first week of a data structures course, why should I trust you to self learn more advanced topics? Why would I spend a ton of time evaluating massive GitHub contributions vs. just watching you code a problem your team would work on for 1 hour?
I have to pay smug kids 100s of g’s because the labor market is so fucked, and there’s no way I’d either trust them to evaluate candidates via code review, nor would I spend their time on that vs. building and learning.
I’d love to not pay children small fortunes, but most very experienced journeymen I’ve interviewed over the years can’t string together dynamic api calls or tell me how things scale, and I get to hire for experience first every time.
If you were able to self teach, then the kid that just spent 4 years snorting adderall and interning and google sure as hell has a chance to, too, and he’s willing to solve my dumb riddles.
The other thing you won’t read: firing people for most managers is awful. A manager only takes so many risks before they learn how to mitigate having to experience this horrible experience. I’d rather reject you than fire you.
Edit: I was one of the impressionable young readers once upon a time, and I set myself back quite a bit taking advice from strangers on the internet. Genius programmers on GitHub don’t sign your paychecks.
Re: Code Interviews
#88Earlier quoted context omitted.
> .. I see have almost zero history of contributing to OSS or maintaining side projects. Not sure about US, but in EU, the contract from employers doesn't allow you to contribute code without permission (e.g. contributing to OSS, working on side projects, etc), it's very very rare to find an exception. You can check this discussion few weeks ago: https://news.ycombinator.com/item?id=27843198 > I have to rely on that…
I never heard of that. I'm originally from the EU and in the country I'm from, employers cannot control what you do in your spare time, and do not automatically own what you do outside your day job. In the US that's much more complicated.
Re: Code Interviews
#89Earlier quoted context omitted.
Oh, yeah...one last thing, before I go... I'm a unique talent. I'm not God's gift to Programming, but I have a very different kind of backstory from most that you find. I had a hard road, and the uneven terrain that I traveled, has a lot to do with how I became as good as I am. When no one gives you breaks, you are forced to make your own, prove yourself, at every step, and accomplishment becomes habitual. You learn…
Sorry, need to call BS for all the impressionable young readers. The job of ‘programmer’ takes on many shapes and sizes. Businesses evolve and are different from one another. You may be very successful in some clusters of business, but how representative is this, let alone your unique experience, to the rest of the industry? If you’ve never worked with anyone with “real” software training, why would I hire you into a…
I was merely recounting my own personal experience, and, a bit more cautiously, opinions. I say “cautiously,” because I know that opinion is a different thing from fact, and I need to be careful to avoid presenting my opinions in a manner that frames them as “facts.” In another thread, I needed to do a mea culpa, where I did just that, and was [rightly] called out for it[0].
No BS at all. It actually happened. Are you calling me a liar? Because that is what it appears to be, and I was under the impression that we don’t do that kind of thing, here. One of my personal postures, is that I stand behind my own words. Please note that I have links to my entire portfolio, and many, many ways to back up (or refute) what I say. I deleted my last anonymous posting account, years ago.
One of the issues that I have, with today’s Internets Tubes, is that people like to anonymously spew out opinion as fact, and take every opportunity they can, to insult and demean others. I make every effort to avoid that, in my own interactions. Feel free to go through my posting history, and show me otherwise. If I am wrong, I live a lifestyle, where I am required to promptly admit it, and make amends. I believe that I do this.
I have merely written my own experiences and personal story.
It makes me very, very glad to know that I never have to put myself into a position again, where certain types of folks have power over me. I am quite aware that my own story is different from the run of the mill, but being called a liar for telling it, is beyond the pale.
This new world seems dark and depressing, to me. A Lovecraftian “food chain” world, where everyone is constantly battling everyone else; including their own teammates. I used to look forward to a career of excitement, adventure, learning, and being a member of teams, where I was the dumbest member, and it was an honor to be included. I have never been interested in competing with others. I have always wanted to collaborate with others. I am rather saddened to learn how unique this approach is.
In a lot of ways, I got that, and I’m grateful, but I now see that I probably dodged a bullet.
If there were anything I would say to “impressionable young readers,” it would be:
At one time, some of us looked forward to careers that were not gladiatorial arenas. We woke up, every day, anticipating learning new stuff, and felt honored to be part of a team, composed of people that humbled us, but never humiliated us. We made enough to have a comfortable living, never worried about putting food on the table, and didn’t have envy for our coworkers. We didn’t measure our own self-worth, by demeaning others, and we felt as if we were riding the crest of thrilling new discoveries and technologies. We stayed at companies for many years, because we believed in the aggregate mission, and liked the idea that we were making a positive difference in the world. We became lousy interviewees, because it was an unnecessary skill. We never “hazed” one another, and embraced our differences, as they brought new perspectives into our worlds, challenging us to constantly review our own opinions and worldviews.
There was, once, a happier time, before The Great Old Ones burst through the portal, and made the world as it is, today. I lived in that time, and am reporting from *experience*.
Damn. Did it again. Forgot to give advice, and only gave experience. I feel very, very fortunate to have had mine. Reading the experiences of others, reinforces this gratitude. I do believe that living a life of Gratitude has helped me, in many ways. I also believe that it has helped others, in my orbit, as well. I’m told that I was a pretty good manager, and I have done a significant amount of unpaid Service work (see: Portfolio).If merely recounting my own experience and personal worldview is considered a threat, I have no words, other than I truly feel badly for others.
Now, I truly am done with this thread. Have a great day! I sincerely wish you and your family, health, success, happiness, and fulfillment, in all your affairs.
Re: Code Interviews
#90Earlier quoted context omitted.
why is this voted down?
He’s obviously wrong. Most people have various interests and obligations. The number of people who after a day of work in software engineering go on to continue to do that in their free time instead of pursuing other interests is vanishingly small. Additionally you have people who also just can’t do this, even if they wanted to, due to other obligations. Obviously there are people who have a very narrow set of intere…
It is, however, an advantage that some folks have, and my suggestion is that we should not be required to deliberately hobble ourselves, just because everyone does not have the same advantage.
Of course, a hiring corporation has every right to ignore things like this, and they likely won’t go out of business, as a result. They, may, however, miss talent that could take their business to “the next level,” and risk hiring folks that have become expert at “gaming the system,” and presenting style, over substance.