Unless you've made it to your "endgame" company that you're happy to stay at for a while, I feel investing anything more than the bare minimum to get your assigned work done is worth less than just grinding leetcode and otherwise studying for interviews. Doing an actual good job, above and beyond, is not going to be worth much when you're looking for your next job. Thus we're now seeing the rise of Professional Inter…
Our industry feels like it's in the decline of the Roman Empire right now. Our craft is becoming arcane: Microsoft is building VSCode for the cloud. Few people own desktop computers anymore. Apple is locking down MacOS to signed binaries. Soon we'll all have thin clients and will write software in the cloud for the cloud. Few will be able to learn how to engineer at home anymore - you'll have to go to a university or…
“I've had to relearn coding to get through the new interviews”
81–90 of 731 posts
Re: “I've had to relearn coding to get through the new interviews”
#82Unless you've made it to your "endgame" company that you're happy to stay at for a while, I feel investing anything more than the bare minimum to get your assigned work done is worth less than just grinding leetcode and otherwise studying for interviews. Doing an actual good job, above and beyond, is not going to be worth much when you're looking for your next job. Thus we're now seeing the rise of Professional Inter…
This is inconsistent with my experience in my most recent round of interviews. I interviewed at a few places at a senior/staff level, and most of my interviews were behavioral, architectural, or discussions about past work. The few leetcode-style or coding questions I had were easily prepared for from my ~40 hours of interview-specific coding prep. There is zero chance I would have gotten those interviews or passed t…
Leetcode is "easy" to crack with some (considerable) amount of hard work and they know that. But you can't make up past experience in behavioral interviews as you get found out very quickly.
Re: “I've had to relearn coding to get through the new interviews”
#83I do sympathize, but there is a flip side to this. I have worked in large orgs with many developer and engineer titled employees that can’t code at all. Zero coding skills. And their title would be things like “Senior Enterprise Application Engineer”. Unfortunately their resume doesn’t read that differently than a similarly experienced engineer that actually writes code.
Re: “I've had to relearn coding to get through the new interviews”
#84Generally, I'm more likely to hire someone with interesting hobbies than someone who has completed HackerRank tests. I don't find it compelling to see that a candidate has accomplished standardized metrics; but I am swayed by non-computing hobbies. Synthesizers, painting, rock climbing, volunteering, and so on are indicators of a curious mind that's happy to apply itself.
How many Petabytes of data are you working with? Maybe your company is too small for data structures and cutting every 0.1ms latency count. As an example at Google I needed director level exception to introduce 0.1ms latency to the ads server (which wasn't needed at the end, but the monetary damage for timeouts is real). Understanding basic data structures and how the computer works is important in these cases, even…
Probably >99% of developers will never encounter something like this in their career.
Re: “I've had to relearn coding to get through the new interviews”
#85> It's also an opportunity to excuse ageism. Yep!
That unintended benefit seems to be found in most every hiring process.
Re: “I've had to relearn coding to get through the new interviews”
#86> It's also an opportunity to excuse ageism. Yep!
Re: “I've had to relearn coding to get through the new interviews”
#87Generally, I'm more likely to hire someone with interesting hobbies than someone who has completed HackerRank tests. I don't find it compelling to see that a candidate has accomplished standardized metrics; but I am swayed by non-computing hobbies. Synthesizers, painting, rock climbing, volunteering, and so on are indicators of a curious mind that's happy to apply itself.
How many Petabytes of data are you working with? Maybe your company is too small for data structures and cutting every 0.1ms latency count. As an example at Google I needed director level exception to introduce 0.1ms latency to the ads server (which wasn't needed at the end, but the monetary damage for timeouts is real). Understanding basic data structures and how the computer works is important in these cases, even…
Algorithms absolutely matter, and that will be evident from work experience and education.
Re: “I've had to relearn coding to get through the new interviews”
#88Yes, I'm a bit salty.
The best advice I received recently came from someone 10 years my junior in the industry: politely refuse hackerrank, algorithmic code challenges, array shuffling, or anything unrelated to the work you've done or the work the interviewers are doing on a daily basis. Instead, offer to pair/group program or troubleshoot on a problem they're currently trying to solve, offer to walk through an open source project you've worked on or authored and speak to the problems you encountered. Let the gatekeeper/recruiter know you decline the kinds of interviews I mentioned above, and let them know you're looking for an org that thinks outside of that box, that values a person beyond their ability to regurgitate for-sale interview prep.
That approach has an effect of weeding out companies mired in corporate lockstep. I had told a recruiter at a national, Austin based real estate firm that I decline those types of questions and interviews. Was assured that they would not happen, and in the first round of the process was asked to sort an array of phone numbers. The interviewers had no idea I would decline the challenge, and I politely ended the call.
I recently adopted this approach with great success, speaking with a number of high quality orgs and all around great people who were truly interested in what I could bring to their effort. Granted, not everyone is in a position to take a bold stance, but I found that it made me more interesting to companies who were doing more than going through the motions.
Re: “I've had to relearn coding to get through the new interviews”
#89Unless you've made it to your "endgame" company that you're happy to stay at for a while, I feel investing anything more than the bare minimum to get your assigned work done is worth less than just grinding leetcode and otherwise studying for interviews. Doing an actual good job, above and beyond, is not going to be worth much when you're looking for your next job. Thus we're now seeing the rise of Professional Inter…
I am not professional leetcoder, but good enough if I need to in addition to my experience that has been good enough so far.
Re: “I've had to relearn coding to get through the new interviews”
#90Unless you've made it to your "endgame" company that you're happy to stay at for a while, I feel investing anything more than the bare minimum to get your assigned work done is worth less than just grinding leetcode and otherwise studying for interviews. Doing an actual good job, above and beyond, is not going to be worth much when you're looking for your next job. Thus we're now seeing the rise of Professional Inter…
Our industry feels like it's in the decline of the Roman Empire right now. Our craft is becoming arcane: Microsoft is building VSCode for the cloud. Few people own desktop computers anymore. Apple is locking down MacOS to signed binaries. Soon we'll all have thin clients and will write software in the cloud for the cloud. Few will be able to learn how to engineer at home anymore - you'll have to go to a university or…
I would say is that a lot of hard problems (of last 20-30 yrs) are getting commoditised (e.g. S3, DynamoDB, Redis) and barrier to entry reduced. This would mean increasing the work is "glue & pipes".