I'm an interviewer (and SDE) at Amazon and (at least in my division) we won't do a hire loop for a non-entry level engineer that doesn't include a design interview. It can make or break a candidate, but if you've been in the industry for a few years we expect you have some ideas beyond "Get a bigger database server" when we ask how you'd scale a solution.
Once you get outside the bubble where development process is a dirty word and/or meme cargo culted from a blog, they often do. Especially companies with immutable external quality standards to design and test towards.
One of the best series of questions I've ever gotten in an interview. We probably spent close to an hour just on one major aspect of the service.
Not true in my experience, and the company that did ask such questions turned out to be a great place to learn a lot in a hurry. It also turned out not to be a good long-term fit, but I'm a much better dev for the experience, and I don't regret it at all.
No company will ever ask such questions, which is mind boggling. They will all ask minute questions about sorting algorithms which you will never code instead of asking questions related what you will be doing day to day or stuff that is actually critically important.
No one asks design questions, perhaps because it is an open-ended question. But aren't those the best question for a role that often requires coming up with new solutions?
EDIT: perhaps I was too harsh by saying "never". In my experience, companies have occasionally asked about design, but very few and very little in terms of the ratio with algorithm questions. Part of the problem is the "new interviewer every 45/60 minutes" style of interviewing. They all come in and start off with an algorithm question. Each and every one (at least the technical ones).