4 ms·
I can: A) Relate to the GP, and B) Answer the question For (B), my experience was that LeetCode was worthless, as I was looking for a senior-level engineer,
by ChrisMarshallNY 4y ago
I can:
A) Relate to the GP, and
B) Answer the question
For (B), my experience was that LeetCode was worthless, as I was looking for a senior-level engineer, to come into an established team, and start being a contributor, ASAP.
I spent 25 years, hiring experienced coders, and ran an established team, that was part of a much larger, established organization. Headcount was really difficult for me to get, and the company was cheap. They were a huge name, and assumed that everyone was fighting to join the company.
If you were a photographer, that was the case. If you were a programmer, that was definitely not the case.
So I had a challenge.
I suspect that the low-end salary chased away most people that were only looking to hop onto a short-term, salary multiplier gig. Pretty much everyone that I interviewed was serious about getting involved in some extremely interesting work (C++ image processing pipeline development).
I got folks to talk about their passions and projects. The best way to figure out how folks work, is to ask them to wax eloquent on problems they've solved, and projects they wrote.
I would have killed for large GitHub portfolios. I loved long résumés, and would definitely have spent a lot of time, reviewing them, if they were offered.
I think I basically made good choices. There was never a technical misfit. In a couple of cases, the person couldn't integrate too well into the team. I had a very relaxed environment, and each team member had their own proclivities and workflow. We made it work; I suspect the fact that they all had decades of experience, helped.
I kept people on board for decades (not an exaggeration). Remember I said that headcount was such a bitch to get? That was a big reason for me wanting to keep people. Also, the Japanese team would barely acknowledge their existence, until they had been at the company for at least a year.
In my experience, someone who is good at interview tech questions, is good at interview tech questions, but that does not give me any clue, as to how they will be, when they hit some of the rather hairy (often threaded) algorithms we had.
I had to take risks. If an employee did not work out for at least a couple of years, I got grief. So I got highly competent, experienced C++ engineers to join, for low-ish salaries, and I kept them, for many years. I guess that's not a valuable skill, in managers, anymore.
I think I did OK.
[UPDATE] I made it more about me, to try to make the comment a bit less abrasive.
- comfypotato 4y agoIt’s ridiculous to say that the go to hiring strategy for most of the highest paid positions in the world is useless. The only trend I see that I agree with from leetcode dissenters is that it doesn’t make sense when you have issues maintaining headcount. I’m a newb, and I definitely have no experience hiring, but it doesn’t take ANY intelligence to know that leetcode makes sense when you have a long list of halfway decent applicants. Whether or not it’s ethical. I don’t know. Having to take the time to practice for an interview is going to select privileged folks.
- ChrisMarshallNY 4y ago> It’s ridiculous to say that the go to hiring strategy for most of the highest paid positions in the world is useless. Hey, be nice. I was talking about my experience, in my career, which was fairly unique. I managed to make some very picky people fairly happy, for a long, long time.
- comfypotato 4y agoNeed to work on my writing. Was annoyed at your leetcode dissentism and and wasn’t able to contain the annoyance. My b, dog. Hope to have a similarly long and satisfying career.
- trhr 4y ago> leetcode makes sense when you have a long list of halfway decent applicants It lets you build a team of people who are good at leetcode, but I won't be on that team. Which is a shame, because my t-shape is wider and deeper than most engineers. I just can't solve fake problems about how many ways there are to combine a string quickly. Why isn't there a refactoring section of the tech screen? Hand me 5,000 lines of garbage code and let me figure out what it does, why it does it, and how we can improve it. Those are the kinds of problems I actually have practice solving.
- comfypotato 4y agoThe companies that use dsa puzzles in their interviews wouldn't do it if it wasn't reasonably good at avoiding false positives. Does it test for enthusiasm? Of course not. My company isn't big enough to use dsa puzzles in interviews, and I wish we were. Unfortunately, I've been on teams with a developer who couldn't crunch strings. Leetcode interviews get the job done of avoiding those people (at the cost of also cancelling people like yourself). It's just like tests in college. They suck, and everybody hates them, but they're around because they get the job done. Your example of 5000 lines is laughably to my point. That's a totally unrealistic filtering process.