System design problems are much better and more realistic than leetcode style IMO. Let's be real, most developers don't need to have leetcode T9 solutions memorized because it with either never come up, or they can do some research when it does.
Knowing more about an entire system and architecting it requires a lot of variety of experience and it's just a more fun interview for everyone involved.
When I interview people, I also hope I'm assigned to conduct our architecture one because it really makes you learn a lot about an engineer.
Could someone post a good answer (outline) about how you would build out a GPS related feature for an application?
1. Agree on terms and accept your consulting offer
2. Listen to / read up on your requirements for what you're trying to accomplish
3. Build out gps related system according to requirements and future plans
I also at the same time, interviewed with the fastest growing startup in the area, who had way better comp, slightly better benefits, etc. They asked me to do a take home homework assignment that would've taken like 20 hours, so they could see how I work.
I ghosted the second contact, and after another round of interviews, accepted with the first company, and I'm by far happier with my work and the respect given to my input at this job than any previous one I've had. I'm certain that wouldn't have been the case at the latter company.
I truly believe that once you are beyond the junior level, interviews really are a two way street, and you should jump with the utmost caution unless you already dislike where you are.