The game is changing
Currently interviewing a bunch of companies. All of them allow laptop coding. Half of them are focused on practical problems (project/debugging/scripting), no leetcode. The other half is still leetcode but ones where naive solution is easy to get. Phone screen difficulty has gone up, now they are just as tough as onsites. The game is changing.
What companies are you interviewing at? Lol.
He said he’s interviewing at all the tier 1 companies so I assume IBM
🤔
Could also be that you recently leveled up. What level is this for and how many yoe?
Senior, 5-6
Damn, nice job. Yeah I'm still L4 (L3 for Google) but I feel like mid to senior eng is a big jump so of course it would be harder if the last time you interviewed was for mid level
Are you senior or above? I usually give senior candidates a piece of real production code to review and refactor as part of the coding exercise instead of leetcode.
Yep
Yes LC is dieing. Next up, laptops.
Maybe you're just getting more yoe?
But why do they stop asking LC?
Because nobody who is senior and actually is good worker got time for this shit
Lapcode
Lol. This is what me and some others were doing 12 years ago. I guess we were ahead of our time. The leetcode thing is just stupid.
It got out of hand. I heard from recruiters that ppl were crushing these leetcode style interviews and ended up being bad hires
Doesn’t surprise me at all. It’s a moronic way to interview that bears almost no resemblance to what’s required of most software engineers on a day-to-day basis. Far more important IMO is figuring out new ideas, asking questions, how well code is structured and commented so others can maintain it, and so on. That’s why I mentioned 12, it was maybe even 15 years ago, me and my coworkers moved away from purely algorithmic and data structure-oriented questions (there was no leetcode then) which you you need to be fresh out of school or purposefully study for, to one where we leave someone in a room with a basic one page exercise, a laptop, and tell them they could use all the resources of the Internet to solve it, come ask us questions at any time, and that we’d just discuss how far they got, what they prioritized doing first, and the quality of the code at the end of two hours. And we said it was fine if they didn’t finish (and it was). We purposefully tried to make it as close to how people actually program as we could and didn’t index heavily on getting it done or it being perfect. We really hired great people IMO as a result. There was no way to fake that and it didn’t index on stuff that, IMO, isn’t really that important.
Wtf is phone screen difficulty?
Once I was asked BST, LRU cache, and design Twitter in one interview. Went into detail about db query under the hood, index representation
Another time a vague problem was given, I clarify it and do back of envelope calculations, then give some solutions and trade off, which leads to an algorithm question. Intersrction of k sorted arrays
What sort of practical questions do you see? Do you mean the “design and implement this in four hours” interviews, or just cases where they have you run and debug your leetcode problems?
pray that it's not just confirmation bias on a small sample size
There's not many tier 1 companies and I'm talking with almost all of them
mm good to know