Thanks for posting this video! I'm a long-time developer and I stayed at my first programming job for about 19 years. :) So, I'm an "old man", so to speak. :) Anyway, I have a question about your "leveling up" approach. This is the ONLY video I've seen, so I don't know anything else about the series. My question: why would I prepare for an on-site interview, in the manner you describe? My most difficult on-site interview involved a whiteboard and a "Sharpie". :) Given the "shell" of a C function, I was tasked with writing a compression algorithm that functioned in the manner described to me. I'm not sure how I would have prepared for that and I'm not sure I would even want to. I worked through the task as best as I could and completely botched it. I had never written a compression algorithm before, let alone access individual bytes in a 32-bit integer that was one of the parameters of the function "shell". I think it was actually a pointer to a list of 32-bit integers and I was to look at 3 bytes of an integer and use that data as part of the compression algorithm. Anyway, after I completed botched it, I was actually called back for a third round of interviews. I ended up not getting the job and I wasn't upset I didn't, despite being _very_ interested in the low-level nature of the development. I can understand programming tests to see if I can program, i.e. do I know the syntax, can I actually write code that makes sense, etc. What I can't understand is a programming test that sees if I can complete some esoteric task, off the top of my head. I mean in reality, that's something I would actually research and work through, not implement "off the top of my head" in some given job position or function. Sorry for making this such a long comment and I thank you, if you've made it thus far. :)
I agree that a lot of questions that are asked in interviews don't directly relate to the actual work that is done in the position, though since leetcode style questions are the norm it makes sense to prepare/learn the common patterns of those questions. not ideal ,I know, but thats the way the market is sadly
come join the community on discord: discord.gg/hqm6Uf8g
Thanks for posting this video! I'm a long-time developer and I stayed at my first programming job for about 19 years. :) So, I'm an "old man", so to speak. :) Anyway, I have a question about your "leveling up" approach. This is the ONLY video I've seen, so I don't know anything else about the series. My question: why would I prepare for an on-site interview, in the manner you describe? My most difficult on-site interview involved a whiteboard and a "Sharpie". :) Given the "shell" of a C function, I was tasked with writing a compression algorithm that functioned in the manner described to me. I'm not sure how I would have prepared for that and I'm not sure I would even want to. I worked through the task as best as I could and completely botched it. I had never written a compression algorithm before, let alone access individual bytes in a 32-bit integer that was one of the parameters of the function "shell". I think it was actually a pointer to a list of 32-bit integers and I was to look at 3 bytes of an integer and use that data as part of the compression algorithm. Anyway, after I completed botched it, I was actually called back for a third round of interviews. I ended up not getting the job and I wasn't upset I didn't, despite being _very_ interested in the low-level nature of the development. I can understand programming tests to see if I can program, i.e. do I know the syntax, can I actually write code that makes sense, etc. What I can't understand is a programming test that sees if I can complete some esoteric task, off the top of my head. I mean in reality, that's something I would actually research and work through, not implement "off the top of my head" in some given job position or function. Sorry for making this such a long comment and I thank you, if you've made it thus far. :)
I agree that a lot of questions that are asked in interviews don't directly relate to the actual work that is done in the position, though since leetcode style questions are the norm it makes sense to prepare/learn the common patterns of those questions. not ideal ,I know, but thats the way the market is sadly