91–100 of 583 posts
The article doesn't mention the #1 problem with tech hiring: leetcode. Some advice for recruiters: try starting your emails with "NO LEETCODE" in the subject line and watch your response rate from senior experienced engineers skyrocket! There is an artificial "shortage" caused by this barrier.
Another broken thing is LeetCode style of programming exercises asked for a job asking 15+ yrs of experience. Not saying we do not solve complex stuff on a day to day basis, but foundational problems are already solved & we have patterns/solutions/libraries available. We do not do DFS/BFS on a day to day. We do have Stackoverflow, Google to figure things out. FAANG companies - filtering candidates by asking tough Lee…
Earlier quoted context omitted.
Just as a counter point, developers that have such a knowledge about algorithms and efficiency tend to be able to sort through different possibilities and branches investigation for new problems much quicker than a developer that has to look up everything on the way. Although that's something that can just come from experience too.
I can't tell during my limited time in an interview if a developer has that knowledge because they crammed (and therefore will forget quickly on the job) or if they actually study and understand this stuff. I can tell during my limited time in an interview if a developer is capable of making logical deductions and not flail when exposed to a problem they may not have seen before. And, better yet, if they do study alg…
Earlier quoted context omitted.
Yeah, hiring someone with no c++ experience and expecting them to OJT is a great way to farm memory corruption vulnerabilities...
I have been told multiple times by C++ advocates, that C++ (whatever year is latest) doesn't have memory management issues... Is that not true?
This person sounded really experienced, so I looked them up on LinkedIn. 7 months at their first company. 9 months at their current company. That's it, aside from non-programming jobs before their bootcamp. The whole thing reads like inventing scenarios that didn't happen or embellishing them. > A bad interview is when you ask them the definition of some specific thing in some specific framework like “Tell me what a…
No software eng. experience 2015.
2016 Bootcamp
2017 Salesforce
2018 - today - our company: TS, React, Vue, NodeJS, Python, Main devops developer that brought up our docker infra.
> Didn't happen.
Yikes...
""" You should not be testing people’s ability to recall some obscure definition in an interview. You should be testing people’s ability to tackle something they can’t recall off the top of their head. And, you should allow them every tool they have available. If they’re totally unfamiliar with the problem, and yet they make significant progress in just one hour that should be interpreted as a good sign this person w…
> just as good as a developer who can tell you the big-O efficiency of reversing a red-black tree off the top of their head I’m not really interested in whether or not they know this. I’m more interested in whether they can explain it to me.
I'm more interested in knowing if they can debug something nasty or opaque with patience and using deduction instead of flailing. Chances are the person who can do this might also be able to explain why a red-black tree inversion is a certain O-notation, but its not strictly necessary.
The article doesn't mention the #1 problem with tech hiring: leetcode. Some advice for recruiters: try starting your emails with "NO LEETCODE" in the subject line and watch your response rate from senior experienced engineers skyrocket! There is an artificial "shortage" caused by this barrier.
Companies use Leetcode because they don’t want to pay for experience.
This person sounded really experienced, so I looked them up on LinkedIn. 7 months at their first company. 9 months at their current company. That's it, aside from non-programming jobs before their bootcamp. The whole thing reads like inventing scenarios that didn't happen or embellishing them. > A bad interview is when you ask them the definition of some specific thing in some specific framework like “Tell me what a…
I get some very crappy spam offers like that every few weeks. 35K to be a Java dev in Atlanta kind of thing. They do happen.
I literally can’t relate to this on any level. I’m an HM at a company that pays on the order of a FANG and at best matches one of these credentialist barriers and yet we can’t come close to hiring targets on devs. I don’t get how people can see the plethora of individuals under 10yrs experience in SWE and other tech roles in SV/NYC/SEA with incomes of $250-600k/yr and think this happens without a “shortage” of talent…
I'm also a HM. It's unbelievable to see the number of people who are "Senior" after 12 months of actual experience. Some of them are actually legitimately senior, despite short tenures on paper - but many are barely entry level qualified.
Another broken thing is LeetCode style of programming exercises asked for a job asking 15+ yrs of experience. Not saying we do not solve complex stuff on a day to day basis, but foundational problems are already solved & we have patterns/solutions/libraries available. We do not do DFS/BFS on a day to day. We do have Stackoverflow, Google to figure things out. FAANG companies - filtering candidates by asking tough Lee…
Not sure that I agree it is understandable but I definitely am glad they make this bad decision. I dodged the bullet on interviewing with a FAANG and failing on one question (the recruiter told me it was the answer on a single question that kept me from getting an offer) after doing an onsite in SV.
I did not know what I was worth and would've felt compelled to accept an offer that would've been 30-50% less than I could command at the time and I would've had to move somewhere with 4-5x the cost of a home than where I live now. I didn't get that offer, and after a little bit more time I got an offer somewhere where I earn 2-3x as much as I originally said I was worth to the FAANG (based on places like glassdoor, etc.).
The culture is better, I can work wherever and whenever I want, and would have to go out of my way to not make impactful decisions that go to prod for millions of customers multiple times a week. It'd take 2-4x my base salary to get me to walk, which I could possibly command, but I don't feel any desire to look because I didn't fall into the FAANG trap and enter a cycle of pretending consultants selling quiz books know what software engineering is and jumping to be able to survive in SV.
I messed up something on a whiteboard with an apathetic interviewer about a special tree inversion or something - who gives a shit - and I have been extremely happy that happened every day since.