In the ethereal melody of a once thriving reef, we perceive a poignant echo of profound loss, reminiscent of hearing the tender voice of a dearly departed beloved. Drawn inexorably towards it, like a moth entranced by the siren call of a flame, we seek the comforting symphony of life that once flourished. Yet, akin to the cruel illusion of pursuing the ghostly whispers of our past, we know the vibrant chorus we seek has danced away into oblivion. Akin to the article's title, the pain of this elusive quest is a melancholic symphony, a mournful reminder of the vibrant life that once was, and the silent void that has come to be.
You can't create the take home yourself because you're drawing on your own personal domain experience.
For example I'm an expert on real time video streaming in embedded systems. It's trivial to me to program a real time system that will stream video at a lower resolution in real time from scratch. I pass that problem to your average backend web developer they're going to take 100x longer then me.
The issue is, while it may seem obvious to you that the domain is too specialized, when you yourself spend to much time in a specific domain you become biased and you start to think such knowledge is basic because you get too good at it. It's invisible to you.
Time shouldn't be the factor measured here because people have such varied backgrounds.
It's not BS in the sense they are lying. It's BS because they're wrong.
The reason they end up getting it wrong is usually because they pick something domain related to what the company does. So these guys literally work in that domain every single day of course they know it in and out.
When they throw it at someone completely foreign to the domain it's going to take a longer time to figure it out. Most interviewers just lack the ability to see this.