I had a recruiter suggest I do TDD during my coding interviews. When I was in the interviews, I started using TDD. It seemed like the actual interviewer was indifferent about me using TDD. He even seemed surprised, but I did it anyway because the recruiter suggested it.
Using TDD takes longer during an interview, so I didn't get as far into the problem as what I think the interviewer was expecting. I assume people that didn't use TDD performed better because they were able to get farther in the problem.
I didn't get an offer. I'm not sure if it's because of the TDD issue, but I can't think of anything else that could have contributed to the outcome. I sent my feedback to the recruiter after I was notified I didn't get an offer, and I asked for any feedback, but never heard anything.
I have to agree with the OP on this one. I recently have been looking at some different home security hardware to add to my home. In particular, trying to find a video/intercom doorbell that I can hookup to my self-hosted Home Assistant server without it reaching out to the internet is a very difficult task.
Even if you know what you want, and you know it's possible, it's difficult or impossible sometimes (without building it yourself) to find hardware that doesn't rely on internet connectivity and some user account.
Using TDD takes longer during an interview, so I didn't get as far into the problem as what I think the interviewer was expecting. I assume people that didn't use TDD performed better because they were able to get farther in the problem.
I didn't get an offer. I'm not sure if it's because of the TDD issue, but I can't think of anything else that could have contributed to the outcome. I sent my feedback to the recruiter after I was notified I didn't get an offer, and I asked for any feedback, but never heard anything.