Just curious, what do you think a better interview for a software engineer should look like? People hate overly abstract/CS-focused whiteboard problems (mostly

Just curious, what do you think a better interview for a software engineer should look like? People hate overly abstract/CS-focused whiteboard problems (mostly for good reason), isn't practical coding the obvious better alternative?