It's hard. Because everyone claims to be doing TDD, just asking in the interview "do you do TDD" is pointless.
Example. Last year I consulted at an IC company, building a huge "moon-shot" chip. You might expect TDD to be an absolute certainty in such an operation. Not so, individuals had all sorts of justifications for not doing TDD.
Here is one idea. In the technical interviews, when the inevitable "and do you have any questions for me?" moment comes up, ask them to talk about their best test.
If they have a good answer, it's likely you've found somewhere that genuinely values TDD.
I agree with this. I've interviewed a lot of people recently for a senior developer role. The difference in people's ideas of what TDD or testing in general, is quite marked.
I love it when people ask me about how we test. I can tell you the pains we've had with tying our tests too tightly with implementation. :D
Example. Last year I consulted at an IC company, building a huge "moon-shot" chip. You might expect TDD to be an absolute certainty in such an operation. Not so, individuals had all sorts of justifications for not doing TDD.
Here is one idea. In the technical interviews, when the inevitable "and do you have any questions for me?" moment comes up, ask them to talk about their best test.
If they have a good answer, it's likely you've found somewhere that genuinely values TDD.