Lol you guys are funny, everyone has to throw a jab in and make an assumption. More curious than anything to see if anyone else has experienced this.

In a word: "no".

But the controllers do know which company's are more likely to be troublesome than others...

No, because my FO's read back the runway assignment like they are supposed to

Fair enough guys, not trying to start a battle, and not saying that the intent is to blatently not read back a runway assignment. New to the forums and was trying to have a conversation without being jumped on.

Respectively...

Dude...

IN.

Even more recent than this incident was an incident about 4 years ago involving a NW DC-9. They taxied from 1 North and were told to plan on 22R but they thought 22L which is the usual departure runway. They were told to taxi U then LEFT on K, but they turned RIGHT on K and crossed 27R while an RJ was landing.
Nobody was hurt, in fact the crew didn't know they had done anything wrong until they landed at their destination.

Why do you need to read back the runway assignment in DTW?

The question should be "when is a runway readback not required?"

Seriously though, you always read back a runway assignment. Yesterday @ JFK, I heard somebody (Comair or Pinnacle) arguing with GND over the runway assignment. I guess he didn't realize how silly he sounded.

...really??? company's?

...and yes, it's a required readback. The OP is correct, though. Unlike other airports, DTW is particularly anal about it.