SQL is Agile
At a past job we had a really fun interview question.  What we did was laid out a concrete problem, and asked the interviewee to lay out a schema.  Since we know the problem well, for virtually any schema we'd be able to invent reasonable requirements that would force them to change their schema.  At the end we'd verify a basic knowledge of SQL itself by asking them to answer a couple of basic questions.(The actual problem we had them tackle was reports to use in making picks in a fantasy sports game.  But it could be anything simple to explain, fairly straightforward to solve.)The reason why the question worked so well is that this was, in fact, pretty much how we build CRUD applications.  We'd decide the schema, and once the schema was known, the CRUD application was fairly obvious and straightforward.  And a large part of the programming model would be immediately provided by your ORM once you had done so.