Iraq didn't have them.
The reason they didn't have them was because Saddam got rid of them
The reason he got rid of them wasn't because he was a good guy. He simply thought the easiest way out of sanctions was to get rid of them but keep the ability and knowledge to build them. Then inspectors would find nothing and sign off on getting rid of the sanctions. Once that happen restart his programs and start making his fun stuff again. I am also under the impression you're supposed to replace your chemical weapons every so often anyway because being caustic also means you can't store them forever.
What does your test actually measure? Do you know what it measures? How do you know what it measures?
What are you actually looking for? How do you know what you need? Are your tests actually set up to help you look for the things you're interested in? Does what you're looking for actually match the position you're trying to fill?
What I've found is a lot of companies don't really know what their tests really measure, are testing for things that they don't need or don't match what they hiring for. Just as an example on one interview I did every test was pretty much a software architecture test(Design plans that could be given out to other engineers in rational rose, etc) and yet I had applied for a software engineer position. My guess is they wanted to pay for a SE but wanted a SA which when I applied was very unrealistic to be blunt. If they understand the position and the tests they can use to rate candidates, my impression is that they often don't understand the test or the position or what they want so they get a shit show.
Elliptic paraboloids for sale.