The irony is that with more coding interview prep available, the harder the questions get. Don’t get me wrong DSA interviews are still the best way to interview for large tech companies. Because your applicant pool is so diverse and insanely large (different experience and tech stacks), that testing fundamentals in an agnostic way is the only way to ensure fairness. But seems like, everyone is capable of the fundamentals now and the questions are reaching their peak difficulty and straying farther from core computer science. What do you guys think will be the next popular method of interviewing at FAANG? Tc: 280 Yoe: 2 #faang #amazon #meta #apple #google #netflix #microsoft #uber #nvidia #interview
The problems aren’t really getting harder. The expectations are higher. Now you must fully dissect the problem perfect with questions, and then optimally implement and state the complexities.
Fair assessment. From my understanding, “back in the day” (2010-2020), it was more common to not completely solve a question optimally and still pass.
Doesn't matter for senior hires, coding interviews are just a box to tick. The real hiring decisions are made using performance in system design, behavioral and team match/skill match. Coding is just a first stage filtering round for senior plus hires.
Are you implying that a senior hire doesn’t need to perform well in a coding round? Or the the coding round is just a formality before the real assessment?
The expectations are actually lower on getting a working solution and more on the discussion you have around the problem. Communication is more important for senior hires. Correctness is more important for Junior and mid-level hires. One exception is Meta where they expect 100% working solution from what I've heard.
and copilot is getting smarter. people in adobe are promoted for creating wikis
Either solve alien dictionary in <10min or go work at Chipotle 😤
Omg I love alien dictionary problem though
As a software developer or guac scooper
I think good devs can generally detect other good devs with some number of false negatives. So an effective method is to have your best devs interview, ask a mix of technical problems and more knowledge based questions. Ideally have a written section where they can discuss some topics in more detail with a little more time to think. And let reviewers give a little bit of gut feel based feedback. But big companies want interviews to be an industrial inputs/outputs process, with controllable inputs, very standardized formats, very standardized rubrics. This is always going to reward studying for the test type behavior. The difficulty will match the supply/demand situation. I think people still have a hard time BSing through interviews, but a few algo questions is a very shallow IQ-type test, especially past entry level. You want more depth than that
Don’t worry most people don’t give a shit enough to ask harder questions, or even capable of understanding them. If you want 500k+ jobs, leetcode should feel very trivial for you otherwise it will be an uphill battle
Nah. 2 yrs ago the bar was literally 6 feet under the floor that they were not even asking medium questions. Now it's got back to normal.
The point of interviews is to act as a funnel for the thousands of candidates. More and more people enter the field every year and more prep content means they gotta make the funnel better.
India
8h
684
Rahul Gandhi is poison but the people who believe in him are a lot worse
Health & Wellness
Yesterday
1250
Low Testosterone
Tech Industry
Yesterday
5532
BREAKING: Internal sources confirm another round of layoffs just hit emails at Tesla. For real.
Tech Industry
4d
45093
What happens when most of your team is Indian?
Tech Industry
Yesterday
347
Who is excited about Apple new iPads?
I think in the future companies will start asking non leetcode-able questions, like domain specific questions for specific roles. For instance, they can ask about energy conservation in rendering, how compiler optimization actually works, etc
For sure. Smaller companies should definitely be domain specific. In larger tech companies, I don’t see this as a scalable option. Usually (entry-mid level) engineers are hired agnostically and should be able to ramp up and contribute in any domain.
They can probe to see if you’re interested in the subject. If you’re just writing CRUD, you probably won’t look into the system or the hardware too much…