all good bro, i won't lie its just luck on the coding type of question you get, I hate how companies just do a leetcode question and never touch it again, I did stripe interview and the questions were real problems they solve there like parsing, no bs algo questions. plenty more to go through.
Weeeeell, not quite Yes the exact question is partially luck but they don't make them up. They are taken from a pool of leetcode or hackerrank or something like that. Also the topics behind those questions are the same so eventually, if you know all the algorithms, you can code em up at 3am within 1 minute, you should be fine. Also it requires a lot of repetition but eventually it's recognising the pattern, knowing the appropriate algorithm, and have some brains and creativity maybe on top. That's all it comes down to
Any of these questions should have an obvious solution for someone experienced in coding. I personally think they are a bad way to practice with little basis in the real world, I'm also not a fan of how they are used in interviews but you also can't expect them to watch you develop an entire application. From experience thy are usually relatively easy and even if you dont know the exact answer, sharing your thought process is very helpful.
@@rafaeldbx thanks for the insight. for me i just like having the comfort of knowing roughly the process of common questions that may be asked instead of being caught with my pants down
Interesting, when I got hired (about a year and a half ago) I was asked only general, highly conceptual systems design questions (full-stack engineer). Weird to see that there are so many companies out there grilling their interviewees with LeetCode questions -- especially if you're only working in JavaScript. What kind of position is it?
it's a frontend position. they also had general and conceptual systems design questions but they also included 2 easy to medium leetcode questions (i knew cause i had tried and failed interviewing for this company in the past)
