If a qualification for the role is "appreciation for certain less represented cultures/ideas/..." then sure. Otherwise, for a backend c++ engineer the benefits are significantly less obvious, to the point it's really hard to make a case for why DEI concerns should trump traditional evaluation metrics for skill.
The goal should be to hire the best team for the use case, regardless of gender/race/culture/background.
Appreciation isn't always enough, lived experience provides a lot of value as well.
See all the Falsehoods Programmers Believe About Names/Addresses/Birthdays/Phone Numbers/Time Zones/etc, for example. Do you want a backend engineer who designs a 64-character ascii text field for legal name and have everyone nod in agreement, or would you rather have one who knows that it isn't going to work for their cousin "Pablo Diego José Francisco de Paula Juan Nepomuceno María de los Remedios Cipriano de la Santísima Trinidad Ruiz y Picasso"?
> it's really hard to make a case for why DEI concerns should trump traditional evaluation metrics for skill
It doesn't. The goal of DEI has always been to attract a diversity of perspectives, all else being equal. Nobody ever proposed choosing a woefully unqualified diverse candidate over an obviously-qualified Generic White Guy. The only people who would oppose that would be the unqualified Generic White Guy who just happens to be the nephew of the CEO's golf buddy.
> why DEI concerns should trump traditional evaluation metrics for skill
It was never trumping skill. This is just a willful rewrite of history perpetuated for some political goal.
The goal was always to ensure that skill had adequate opportunity to be displayed without bias.