Well "DEI vetos it" is obviously a problem. There's a discussion to be had around expanding candidate pools, expanding the pipeline, however you want to phrase it. These are good and noble goals but we're not talking about the pipeline we're talking about the candidates for a given role that we're hiring for right now.

No department should be vetoing any hire in a different department. Having an engineer veto a hire in the DEI department is ludicrous on its face, but no more ludicrous than having a DEI department tell the engineering team they're not "allowed" to hire a qualified applicant because of their race or gender.

Why is breadth of candidates defined by race and gender instead of experience and expertise. If the DEI department improves breadth of experience and expertise, by looking into alternative hiring streams, thats great, but people who defend DEI always approach it from the race and gender first which is a tell tale sign that race and gender are the primary objectives. And in my experience, when race and gender are the goals, formal and informal quotas appear.

It is odd that the expected inclusion was so specific, though. What about a 14 year old white male? Do they not satisfy: "consider more candidates who might not fit your preconceived notion of what you thought a person in that role should look like."?

I get it. I don't think a 14 year old looks suitable for a senior role either, but looking past that is the point. You never know what someone can offer.