How do you interview for "chaos tolerance" instead of just raw coding skills?

There is a massive difference between a developer who can write clean algorithms in an interview and one who actually knows how to build something from absolute zero with no product manager or QA team around. Our biggest hiring mistake was optimizing for resume prestige instead of looking for someone comfortable with ambiguity and broken infrastructure.

If you're building a tiny early stage team right now what kind of practical test do you give candidates to see if they can handle startup chaos?