In fairness, Agile software teams do a lot of Whiteboarding.
Any Wilmotters into Agile, what?
Wrong domain!! It's a burn-down chart and very useful. It avoids the 90% complete syndromw in software i.e. leave the difficult 10% to the end when the budgte has becomne depleted. It's basic good project managemert that Agile has hyjackedlook at that stock chart top-left!
https://en.wikipedia.org/wiki/Burn_down_chart
Even more useful is the S curve I once automated this for Comprimo Engineers on an Apple II. It's real information!
My favourite speaker on the subject, Mark Horstman, says, "good candidates never complain about the process."There is no silver bullet here IMHO. Interview process always sucks. The only way to make less painful is to have it done by intelligent, open-minded people. But how do you recruit them in the first place?
Personally, I think a candidate for a programming job should be required to write code during the interview. They may be allowed to access reference materials, but if you're hiring a C++ developer than you should expect a certain level of familiarity with C++ syntax, STL, etc. Otherwise they'll be painfully inefficient on the job.