[spsful]

Not at all. Many of the people from Reddit are specifically applying using local zip codes, local addresses, and local area code phone numbers. Kellogg is going to have a massive headache trying to sort through these imo.

Edit: One thing I didn't think of was application source IP address. It's possible the ATS records that info when an app is submitted, so they could possibly delete bogus records that way but I'm no ATS expert and this is literally just my own conjecture.

[derivagral]

I've written systems that integrate with these. The old crop (bullhorn and similar) probably wouldn't be able to do what you're saying easily. The more modern ones out of the usual places could likely do it easily.

I base this opinion off of ~6 year old data and experiences. The "best" horror story was an ATS that used client-side browser datetime without timezone support as their official timestamp record for various events.

[TheNewsIsHere]

I’m sure that never, ever caused any problems for anyone, ever. /s

[egwynn]

Yes IP, and also User Agent doesn’t look like it’d be hard to filter against using the posted code.

[sumtechguy]

Also they could just pull the listing then go to some temp agencies (for example manpower, randstad) and say 'i would like to hire 10 people that have these qualifications'. I know a couple of people who do not even look at company websites and deal only with companies like this for these kind of jobs. They are perfectly fine being forever temp.

[tyingq]

A lot of applicant tracking systems will start to fall over at a certain level of items in the database.