5 ms·
Evaluate people on past projects. If you have a project, show the code and walk through the code in a screen sharing session. Only show code that is non-confide
by b20000 4y ago
Evaluate people on past projects. If you have a project, show the code and walk through the code in a screen sharing session. Only show code that is non-confidential.
If you do not have code, then first create a small project. That can be done in a week or two. This requires less time than grinding leetcode.
Some people will say: but you need to be able to solve a problem in under a few minutes. That is utter bullshit. We all know that development doesn't work that way in reality.
- PainfullyNormal 4y ago> Only show code that is non-confidential. Back in the day, it was normal to get your former boss to sign off on showing a piece of code in your next round of interviews.
- b20000 4y agoI am self employed so I can sign off on anything.
- 8note 4y agoAre you going to convince someone with another day job to do this so you can try to convince them to work at your company instead? This filters out the best
- 7speter 4y agoThose people can’t take a few hours to make a small project? They can just make one and take it to multiple interviewers
- b20000 4y agoIf you cannot manage to build something in a few weeks time in your spare time then there is absolutely no way you can be "the best".
- maxbond 4y ago"The best" may spend their "spare" time raising children, doing volunteer work, or simply unwinding - just because you didn't sell that time to an employer doesn't mean there aren't demands on it, or that you're obligated to spend every waking moment engaging in some form of labor. Having personal time to devote to programming isn't a function of job performance, it's a function of your particular life circumstances. And if you created a huge incentive to fabricate personal projects, a cottage industry of people who will create something cool on your GitHub in a way that looks authentic would spring up, and you'd be prioritizing people with the wealth and inclination to cheat over other candidates.
- b20000 4y agogrinding leetcode to prep for interviews takes a lot more time. how can you have a CS degree and a career and have no personal projects? i graduated in CS with 4 programming projects done. all the arguments you give are the same for leetcode prep. the difference is that if it is your own code that you walk through you need to prep a lot less. and that is good because in your situation you would not be able to grind hundreds of irrelevant problems in your spare time for each interview. as far as your cottage industry argument… you can tell if someone did not write his own code and the system is being gamed right now anyway by people taking interviews for others and so on. and this thread shows people are medicating which is the worst.
- maxbond 4y ago> how can you have a CS degree and a career and have no personal projects? Other people's lives differ from yours in ways that are difficult to imagine. Plenty of people have a career in programming without ever going to college. Just because one can't imagine it doesn't make it invalid, or even that it is one's business. If it isn't about their job performance, don't measure it. > all the arguments you give are the same for leetcode prep. An interesting point, but of course I wasn't defending leetcode interviews, I was responding to your assertion that people who have the requisite skills necessarily have free time, and the subtext that any time not spent working was available for more working.
- ugh123 4y ago>Evaluate people on past projects. If you have a project, show the code and walk through the code in a screen sharing session. Only show code that is non-confidential. Lots of bullshitters out there will find some code they don't own, study it and become well-versed in how it works, and fake their way through. >If you do not have code, then first create a small project. That can be done in a week or two. This requires less time than grinding leetcode. Do you mean one of those "interview projects"? Lots of people, especially on HN, would balk at this as "blah blah don't do free work". Those same people will then go back to your first point and say "just evaluate people on their experience.