> our tech workforces was 23% female as compared to the 19% cited in the policy announcement
> So we actually had an overrepresentation of women at the time, yet we still instituted explicitly discriminatory policies favoring them.
I think you and I have different definitions of what would constitute "overrepresentation" of women in a workforce. (Again, keeping in mind that at many/most tech companies, the majority of jobs are not held by engineers.)
This is explicitly spelled out in the policies I sent you: the opportunistic hiring bucket is exclusive for women and URM. If you want to use the opportunistic hiring bucket, the candidate has to be either a woman or URM. What is hard to understand here?
> I think you and I have different definitions of what would constitute "overrepresentation" of women in a workforce. (Again, keeping in mind that at many/most tech companies, the majority of jobs are not held by engineers.)
The "opportunistic hiring" was exclusively for engineers. Also what do you mean by "overrepresentation"? Representation relative to the workforce is what's relevant. In a field that's 80% women and 20% men, having 50/50 representation would mean that women are one quarter as likely to be hired as men. This would require vastly disadvantaging women relative to men.
What I said:
> how did it handle that case?
You haven't said a) whether this hypothetical actually happened or b) how it was handled. That leaves all this in the realm of rage-bait hypotheticals.
> Representation relative to the workforce is what's relevant.
You're defining "workforce" narrowly to exclude people who do not currently work in the "field." This is unnecessarily narrow because e.g. there are people who work in tech who do not work at pure-play tech companies in Silicon Valley (this is where the policy pulls its stats). So setting a low bar and barely clearing it.
There's also likely the possibility that they are conflating "engineering" and "tech" roles. Female CS majors are indeed ~19% in the US, but "tech" jobs often include lots of people on product teams who are not engineers: QA, UX, etc. I don't know whether Dropbox counts a UX person as "tech" or not tech. I also don't have good stats on e.g. gender balance in UX, but I would wager that it is not the same as for CS grads.
Incidentally, Dropbox non-tech is only managing 43% women. This includes roles like marketing, sales, finance, HR, etc. where the excuse of the college pipeline is not operant. (For example -- women are the majority of accountants in the US.)
> There's also likely the possibility that they are conflating "engineering" and "tech" roles. Female CS majors are indeed ~19% in the US, but "tech" jobs often include lots of people on product teams who are not engineers: QA, UX, etc.
It's for engineers.
> You're defining "workforce" narrowly to exclude people who do not currently work in the "field." This is unnecessarily narrow because e.g. there are people who work in tech who do not work at pure-play tech companies in Silicon Valley (this is where the policy pulls its stats). So setting a low bar and barely clearing it.
The figure of 20% comes from the number of people who put "software developer" on their tax returns: https://www.bls.gov/cps/cpsaat11.htm it's not just counting the "pure play tech companies" whatever that's supposed to mean.
If you put up a job for a software developer, count the number of men and women who would potentially be interested in the job the former is going to be about 4 times bigger than the latter. If you have a different way of measuring this proportion, you can make that argument.
> Incidentally, Dropbox non-tech is only managing 43% women. This includes roles like marketing, sales, finance, HR, etc. where the excuse of the college pipeline is not operant. (For example -- women are the majority of accountants in the US.
HR is 70-75% women according to Google. So if a company is hiring 70-75 women in HR it's not evidence of any discrimination. Same with all the other roles you listed. We'd have to inspect each role one by one, and comparing Dropbox's representation. Furthermore, the discriminatory policies were specific to engineering. So I'm not sure why these other roles are relevant. Did Dropbox discriminate against female accountants? I have no idea. But how does discrimination against male coders somehow make up for potential discrimination in other fields?
You clearly have a lot of privileged background information you have not shared yet (for which I do not blame you). So it's going to be very difficult to pre-but some of this. For example, the BLS report you linked also shows women "computer system analysts" at close to 40%, and this is a job title often given to programmers. But you know that the appropriate compare is the row that's 19%, presumably because you have the inside background knowledge I mentioned.
In any case, the debate is stale because the folks who want to keep tech extremely male have won and these types of efforts are being relegated to history. So tech has gone back to broadly not considering qualified women and URM and this debate is mostly historical.
> The Problem Statement
> Based on 177 like tech companies in Silicon Valley (market research and EOO-1 Diversity Statistics data), the percentage of diverse engineering talent is sparse. In short, 4.7% are latino, 2.1% are African American, and 19.2% are female. These candidates are being targeted with all of our top competitors with white gloves tactics, strategic outreach, and engagement strategies, while Dropbox has yet to systematically establish any of these practices to compete for this top talent and showcase our uniquely inclusive, dynamic, and thoughtful culture.
> Opportunity to market DBX [Dropbox] more broadly:
> Moreover, diverse engineers are the most sought after group of individuals on the market today. While the average response rate to engage is high (37%) the rate at which they are interested in moving forwards is quite low (11%). We interpret this in two ways:
> First, due to the small pool and scarcity of diverse talent, companies are motivated to keep their diverse talent happy, well-compensated, and engaged; prospects are rarely on the market, and when they are, it is a highly calculated and careful search based on existing relationships.
> Second, traditional sourcing engagement methods (email, LinkedIn) do not adequately showcase what makes Dropbox special, and because these candidates are so highly sought-after, it would serve us to highlight our culture early on, and to take a more long term approach to courting them.
> Opportunistic Hiring
> As the business needs shift and open roles become more narrow, it will become difficult to find a home for diverse candidates that we're able to engage and who pass our bar. We feel like it would be a disservice to use in the long-term if we miss out on hiring critical talent for Dropbox because of current headcount constraints. To this end, we propose that Eng VP's withhold 20 heads to hire opportunistically.
> When a diverse/URM candidate is interested in interviewing, regardless of headcount, we will put them through the process. If they pass the TPS [technical phone screen] we will bring them onsite and evaluate based on their skillset.
>If the candidate goes to HC [hiring committee], we will proactively find a sponsor/team home for the candidate, and that team would receive a preciously withheld headcount for that hire.
As you can see, this really is a needlessly verbose way of saying "we're setting aside 20 headcount off-limits to white and Asian men". The fact that these set-aside headcount doesn't count towards the team's initial headcount does not change this fact: we had 20 headcount that were explicitly off-limits to white and Asian men.
What's even more interesting is that as per the company's diversity report, our tech workforces was 23% female as compared to the 19% cited in the policy announcement. So we actually had an overrepresentation of women at the time, yet we still instituted explicitly discriminatory policies favoring them.