7 ms·
> i would correct this to "if you haven't been switching software engineering jobs every few years", which forces you to grind leetcode for months every time.
by josephg 5y ago
> i would correct this to "if you haven't been switching software engineering jobs every few years", which forces you to grind leetcode for months every time.
I know how obnoxious this is, but there are engineers out there (hi!) who can pass leetcode style coding interviews without studying because we love this stuff. I love algorithms and data structures. I'll happily discuss the relative advantages and disadvantages of vectors, linked lists, b-trees, etc for different tasks in a job interview. Or over dinner, or at the beach, or any and every time people let me get away with it. I've spent the last month or two optimising CRDTs, and I've used a bunch of data structure changes to improve performance in one of our benchmarks by 4500x (!)
The goal of the interview isn't to "force you to grind leetcode for months". They're trying to filter out candidates who would need to grind leetcode in order to explain how a hash table works. They're looking for engineers like me, who graduate at the top 15% or so CS classes. Algorithm and data structure questions are asked because lots of programmers never touch this stuff in their day jobs. The people who actually know this blindfolded are in demand because we're useful on large projects with novel systems architecture.
Thankfully, there's lots of other jobs out there where all they're looking for is a warm seat, closed jira tickets and happy customers. I go crazy doing jobs like that - so I'm glad lots of folks are around to do that work. If everyone was like me, we'd have 18 different web frameworks for every working website.
I sometimes wish we used two different names for our profession in the same spirit as "electrician" and "electrical engineer" being different roles. Then we might all waste less time applying for the wrong kinds of jobs.
- abhijat 5y agoSomewhat related to your experience, does anyone else feel that the present interviewing scene is a lot more focused on algorithms rather than data structures? Many leetcode questions rely on very specific tricks like using a fast and a slow pointer, or two pointers at opposite ends of a sequence. So one might know about many different types of self balancing trees and which ones are best to implement a database index on disk, but these things do not come up very often in leetcode style interviews, although these are quite real problems in the realm of algorithms and data structures. To be fair though I do not know how you can test this kind of knowledge in an interview.
- villasv 5y ago> They're trying to filter out candidates who would need to grind leetcode in order to explain how a hash table works. This is obviously a generalization rounded down. Most of my whiteboard interviews were fine, like you’re saying, but some did ask ludicrous puzzles that required specific knowledge of existing algorithms like “largest sum consecutive array”.
- zozbot234 5y agoBut you're not passing "without grinding", you're just someone who loves the grind. Good for you I suppose but it's nonetheless very far removed from the skills one would actually find worthwhile even on the highly non-trivial, greenfield projects you're talking about (which BTW are quite rare and not what most people are working on). There's a lot more to CS and software/system design than just this l33tcode stuff.
- josephg 5y agoI don't love leetcode. I've spent maybe 10 minutes on the site in my entire life, because I was curious. I learned all this stuff in CS classes 15 years ago, and I've expanded my knowledge since then by playing with this stuff for work and pleasure. Maybe thats what you're calling "loving the grind"? Its not a grind for me, in the same way playing a video game I love, or reading a great book isn't a grind. Its not a grind because algorithms are beautiful. I know and agree that algorithms knowledge is rarely useful in practice. Most professional programming work is in feature factories. But people who know algorithms well can usually also figure out react. The reverse isn't true. > There's a lot more to CS and software/system design than just this l33tcode stuff. I agree, though I'm curious what else is on your list? My favorite interview question was: "Here's some code we wrote with bugs and failing test cases. You have 30 minutes. See how many of the bugs you can find and fix." It takes some work to write a question like that, but its so worth it. I wish more companies invested the time into assessments like that. > it's nonetheless very far removed from the skills one would actually find worthwhile I literally found these skills worthwhile in my job just last week. They're usually not useful at small startups or at most product companies. But the field of programming is bigger than the set of things you and your colleagues work on.
- tolbish 5y ago> I know how obnoxious this is, but there are engineers out there (hi!) who can pass leetcode style coding interviews without studying because we love this stuff ____ > I don't love leetcode.
- 5y ago
- ZephyrBlu 5y agoWhat an arrogant comment. > The people who actually know this blindfolded are in demand because we're useful on large projects with novel systems architecture > Thankfully, there's lots of other jobs out there where all they're looking for is a warm seat, closed jira tickets and happy customers As if there is no in between and only your specific type of job is in demand. Why are you so condescending towards any role that doesn't perfectly match your interests and skillset? I guess product-focused developers, partner engineers, embedded engineers, etc are all useless because they're not working on "large projects with novel systems architecture". In any case, this is also a false dichotomy. See this person's comment about being a PhD compiler and algorithms student yet still struggling with LeetCode: https://news.ycombinator.com/item?id=27312674 https://news.ycombinator.com/item?id=27312674
- delayclose2 5y agoI didn't read his comment as condescending. He said the world needs both engineers and plumbers. The world needs more plumbers than engineers, that doesn't mean that plumbers are useless. Your example is not a good one because 1 month of practice would not be sufficient for most people to get into FAANG. See: the guy who grinded Leetcode for a year and failed to get into Google (though he did get into Amazon). If you only need to grind Leetcode for 1 month to get into FAANG, then that means you're already pretty good algorithms wise.
- ZephyrBlu 5y agoHe classified his work as engineering and everything else as plumbing. That is condescending. > If you only need to grind Leetcode for 1 month to get into FAANG, then that means you're already pretty good algorithms wise That's the point. That person should be pretty damn familiar with LeetCode questions, yet they still had to grind for a month and they're scared of it.
- josephg 5y ago> He classified his work as engineering and everything else as plumbing. That is condescending. Most real world programming work kind of is plumbing though? We take data from over here and put it over there. We build pipes. And for good, sensible reasons, most of the pipes we make use standard fittings (REST, JSON, etc). This is the whole point of this thread - you don't need to be good at leetcode questions to do this sort of work. I agree with that and I think we're all on the same page here. Leetcode tests something else. That other thing is also a real skillset. I hear you that calling it engineering is condescending. But I still wish we had a good name for it..?
- tekkk 5y agoTo me learning algorithms on my leisure time is the epitome of boredom. Not because I wouldn't be able to learn them but because life is finite. I'm happy that you have found your niche but don't look down on people who prioritize getting things done without knowing much about algorithms. Although I agree that jobs that apply theoretical CS should have it clearly stated. But, contrary to your belief, some seem to just require it for the sake of it. Not because it's needed.
- tester34 5y ago>who graduate at the top 15% or so CS classes. I have totally no idea what does it even mean is top 15% good? In $my_country, maybe 2 "schools" of CS are good, the rest is mediocre at best (I guess) so it'd be like 1% is really good I kinda compare edu with ELO based games like chess or even league of legends In league of legends top 1% people are somewhat decent, but still nowhere even close to $PRO >Algorithm and data structure questions are asked because lots of programmers never touch this stuff in their day jobs. Why not Security then? it's way more important - poorly performing algo can be rewritten, leak cannot be reverted as easily if at all
- MikeDelta 5y agoAnd the damage of a security issue can be much larger than less-performing code.
- josephg 5y agoYeah I 100% agree. Ideally in a good interview you want to assess a whole range of things - data structures, security, personal background, systems design, real coding, communication skills, etc. Most people are weak in some areas, and you want to give candidates lots of opportunities to impress you.
- nsonha 5y ago> They're trying to filter out candidates who would need to grind leetcode in order to explain how a hash table works Well if anything they select these people because grinding leetcode does work Why do they presumably even need to select people who doesn't need to prepare to do a specific job? Is that because at those companies you're supposed to do that kind of work without preparation? I don't think that's anything more than what you think they think.