Hearted Youtube comments on A Life Engineered (@ALifeEngineered) channel.

  1. 4
  2. 4
  3. 4
  4. 4
  5. 4
  6. 4
  7. 4
  8. 4
  9. 4
  10. 4
  11. 4
  12. 4
  13. 4
  14. 4
  15. 4
  16. 4
  17. 4
  18. 4
  19. 4
  20. 4
  21. 4
  22. 4
  23. Sorry I think this video is out of touch with the current state of hiring in software engineering. In my experience getting an interview is not the bottleneck, the key is doing better at the technical interviews and behavioral interviews than every other person who applied for the position. With the sheer number of people on the job market, the threshold for passing has to be absurdly high in order to filter out candidates. Unfortunately, the way to differentiate yourself today is by learning (or memorizing) leetcode solutions, and practicing enough that you can perform them live within 30 minutes. It’s a charade, where the interviewer and interviewee both pretend as if you’re seeing a novel problem and solving it in real time, when really you’re either recalling the solution or re-conjuring it based on practicing similar problems. If you haven’t seen the problem or a similar one before the interview, your chances of beating someone who already knows the solution drop exponentially. It really is that simple, the candidate who can perform the best at the interview performance will get the job. This means learning (or memorizing) solutions to enough leetcode problems / system design challenges / behavioral scenarios that you increase your chances of getting lucky and being asked one of the solutions that you know well enough to demonstrate your ‘competency’ and ‘expertise’ in the on-site interviews. So let’s be real, how to stand out in an insanely competitive tech market: keep grinding leetcode
    4
  24. 4
  25. 4
  26. 4
  27. 4
  28. 3
  29. 3
  30. 3
  31. 3
  32. 3
  33. 3
  34. 3
  35. 3
  36. 3
  37. 3
  38. 3
  39. 3
  40. 3
  41. 3
  42. 3
  43. 3
  44. 3
  45. 3
  46. 3
  47. 3
  48. 3
  49. 3
  50. 3