I think the better alternative since it won’t kill application flows, is have a field somewhere saying that they need to mention the title of the job in a field that doesn’t make sense what it actually is,
such as have a duplicate middle name field, but specify in the job description that the second middle name field should be what the jobs listed title is.
To someone who didn’t read the job description, they would think that an error was made creating the job posting, but to anyone who bothered to read it they would know the second field is intended to be the verification process.
Anyone who doesn’t supply the job title (case insensitive all special chars like trailing whitespace and ’ removed) as the second field just gets auto rejected
I think the better alternative since it won’t kill application flows, is have a field somewhere saying that they need to mention the title of the job in a field that doesn’t make sense what it actually is,
such as have a duplicate middle name field, but specify in the job description that the second middle name field should be what the jobs listed title is.
To someone who didn’t read the job description, they would think that an error was made creating the job posting, but to anyone who bothered to read it they would know the second field is intended to be the verification process.
Anyone who doesn’t supply the job title (case insensitive all special chars like trailing whitespace and ’ removed) as the second field just gets auto rejected