They need us more than we need them. Don’t work for people who ask you to do party tricks for the privilege.
Stop Interviewing with Leet Code
171–180 of 675 posts
Re: Stop Interviewing with Leet Code
#172All of these supposed "flaws" of leetcode are by design. Big companies want people who are smart enough to do the work, but obedient enough to put up with all the bullshit that comes with working at a big company. What person better matches that than someone who's able and willing to study for and pass a tech version of the SAT? Every anti-leetcode article I read is some version of "leetcode is bad because it measure…
It seems like a huge inefficiency in the economy that thousands of people are studying and practicing for an entrance exam that has no value in the real work that the companies actually do.
But overall that may be a good thing for society. If Google fired all their leet coders and replaced them with real engineers they would not need as many. And the biggest problem may be that there is a limited number of real engineers in the world. Companies have to figure out a way to make so with the people that are available.
Re: Stop Interviewing with Leet Code
#173In my team we do technical interviews in three steps: - an algorithmic challenge. It's related to what we do day to day. I work in domain names so we ask to parse a domain name. There are oddities with domain names so we check multiple things: does the candidate know what basic string manipulation functions exist? do they ask questions to get more info? how do they react when we give additional info that break the co…
In my old job we used to have combined problems for job interviews.
First were some easy leetcode, little Big O, all that.
But then it got tricky, the problem turned into a "design" part were you could see how the applicant would setup a new system, wether s/he would overdo complexity etc.
Finally we had tests for communication skills. For a unprecise formulated requirement, would the applicant ask us or would s/he over-implement?
Usually there was also something which was noch archievable, for which we substracted points if attempted unsystematically and at all.
It was a good test, because the simple leet code calmed the apllicants, and for the rest you goto see something much more valuable. Their approach to work, their thought process, their output, wethere they would go for Quantity or Quality and could self-manage their workflow.
Re: Stop Interviewing with Leet Code
#174Earlier quoted context omitted.
Does it though? Often times all it tells you is that this person probably saw this question before.
Yes, it does. It shows that they at least shown an interest in this kind of thing.
it only shows that the person has an interest in solving leetcode problems, though
Re: Stop Interviewing with Leet Code
#175Is this a symptom that algorithmic/competitive coding will be considered the IQ test of future?
Re: Stop Interviewing with Leet Code
#176Earlier quoted context omitted.
That wasn’t actually true. He later said that he wasn’t asked to invert a binary tree. Also, nobody at google is using homebrew for work.
None of them own a Mac?
Google doesn't allow any code on laptops. Everything is done via web IDEs or ssh into a linux machine. So nobody is using brew to obtain dependencies.
Re: Stop Interviewing with Leet Code
#177All of these supposed "flaws" of leetcode are by design. Big companies want people who are smart enough to do the work, but obedient enough to put up with all the bullshit that comes with working at a big company. What person better matches that than someone who's able and willing to study for and pass a tech version of the SAT? Every anti-leetcode article I read is some version of "leetcode is bad because it measure…
This reminds me of the interview process at Thinking Machines, where the interview was working onsite for a week and then getting voted on. Or Pixar which required you to excel in atleast one thing in your life
i excel at training dogs, would Pixar like to hire me?
Re: Stop Interviewing with Leet Code
#178Earlier quoted context omitted.
That wasn’t actually true. He later said that he wasn’t asked to invert a binary tree. Also, nobody at google is using homebrew for work.
Anyone using a Mac for tech related jobs has a high probability of using brew. That includes a lot of googlers
Google doesn't allow any code on laptops. Everything is done via web IDEs or ssh into a linux machine. So nobody is using brew to obtain dependencies.
Re: Stop Interviewing with Leet Code
#179All of these supposed "flaws" of leetcode are by design. Big companies want people who are smart enough to do the work, but obedient enough to put up with all the bullshit that comes with working at a big company. What person better matches that than someone who's able and willing to study for and pass a tech version of the SAT? Every anti-leetcode article I read is some version of "leetcode is bad because it measure…
It seems like a huge inefficiency in the economy that thousands of people are studying and practicing for an entrance exam that has no value in the real work that the companies actually do. But overall that may be a good thing for society. If Google fired all their leet coders and replaced them with real engineers they would not need as many. And the biggest problem may be that there is a limited number of real engin…
In your opinion, what's the difference between a leetcoder and a real engineer?
In my mind, a real engineer really shines in the non technical aspect of things, like coordination, communication, prioritization, and getting hard questions answered. But that's just me, I'm curious what everyone else's experiences are.
Re: Stop Interviewing with Leet Code
#180Someone who builds a truly novel technology solution involving hundreds of hours of effort gets filtered out of an interview involving contrived scenarios. You may have built the next generation X, but given an array of strings and a fixed width, can you format the text such that each line has exactly maxWidth characters and is fully justified -- in the next 30 minutes? Maybe you should have cultivated that skillset…
I don't do leetcodes because I am not really into programming puzzles (or parlor tricks :D ), but I roughly tried to do what you described. ~45 minutes it took, deciding in the middle to not worry about the algorithm. Guess I won't get the job ... shrugs.
You won't get the job not because you "didn't worry about the algorithm" but because you didn't ask any questions about the problem; just went straightforward to the implementation. In FAANG interviews that would be a red flag.