The entire theoretical CS field yes. In the practical field of CS engineering, this is only a subset of the useful competences and a small one at that. Communication, working as part of team, reliability, ability to look up and learn things you don't currently know, caring about the state of the code you write, mentoring others, being able/willing to push for things you believe can be done better (not just in terms of algorithm, but processes affecting the entire business) etc. are all as important.
I would much rather hire someone that sucks in algos/data structure, but is fairly good on all those other points than the opposite.
So yes, whiteboarding can be useful to assess how a candidate is doing on one of the specific skills that are useful for a CS engineer, but if 50% to 90% of your hiring decision is based on that, just like it is in FANGs today, you have an inadequate hiring process IMHO.
For the average SDE job. If your job is to implement and optimize a compiler, then sure it's extremely important.
* A sample of one is not relevant
* You also used to have many other coworkers that weren't very good at whiteboarding, since even very good engineering teams in FANGS have many people like that, and that didn't have that problem since you specifically said you had one occurence of that.
So hear me out: maybe there isn't a single predictor that you can just automatically throw at interviewees, like a hard leet code problem, and hope that it will magically filter out the very best engineers for you to pick from. Maybe you should have an interview process that test the different areas I mentioned proportionally to what the actual job you are recruiting for requires.
It's not an easy thing to look for, I know, but it's what we should be striving towards IMHO and what I'm focusing on. So far it has had great results, with a few misses, but a better success rate than just handing out technical stuff.
I worked in a (good) CS department for 4.5 years. They did not teach programming skills to anyone. Most (not all, but most) of the jobs you might be hired to do require far more from the programming skills area than the "computer science" area. People coming out of that program (even at the PhD level) often didn't not even understand how to use a debugger!
Based on my experience, theory problems on white boards is about as useful as dropping a CUPs automation problem on unsuspecting interviewees.
Build me a CUPs driver that drops pdf into in folder in 15 minutes or less. Without documentation.
Bonus points if you can ask if you can skip that bullshit and install and configure an existing a package.
Note: I'm a senior developer with at least a decade of experience. I don't just slap two libraries together. If you want to have fun, dig into how macOS sandboxes CUPs. My bash scripts were not happy.
I capitalized it three different ways as I wrote it and picked the one that looked correct. :)
That said, I do understand why people complain about algorithm questions -- it's undeniably a good filter if you have a large pool of candidates (and a reasonable predictor of ability), but it's mostly irrelevant to most software jobs today since you can usually import textbook algorithms as OSS modules.
The "correct" but harder way to interview is to tailor the interview questions to your actual requirements. This is much more involved and it requires the interviewers to divert attention from whatever they're working on just to set the problems. Setting a problem that's at the right difficulty level and evaluates the right set of skills precisely tailored to the team's needs is hard. (I don't think most typical software engineers have the chops to do this, even experienced senior ones.)
So it's kinda understandable that everyone just randomly picks something from leetcode and use that instead. It's probably not so much a failure of the software industry on the recruiting side, but more of a symptom of how we have failed to come up with skills, tricks, standards and practices that everyone actually agrees on. (eg. it's mostly fruitless to determine whether a candidate is hire-worthy with a question like "would you use Javascript to implement a backend system?") At least the algorithm questions are objectively agreed to be true (even if possibly irrelevant) by everyone and is actually part of most CS cirricula...
It shows you've solved a similar problem recently and have gonads of steel, with a bit of overlap of how good an employee you'll be.
A short test contract after a bit of legwork is far more revealing imho.