FB job reqs are drafted in collaboration with engineering, not imposed by HR (but really they are often copy-pasted and slightly modified from existing). If yo

FB job reqs are drafted in collaboration with engineering, not imposed by HR (but really they are often copy-pasted and slightly modified from existing). If you look at FB job reqs in prod network engineering (network in title, infrastructure is area of work), the qualifications should be reasonable. This covers most roles that are not pure SWE or rack and stack (SWE and "deployment and support" cover those roles). ~3-4 years ago a director shared a req and asked that we pass it on to our friends / anyone that might be interested. Some of us asked why specific items were in the req since they didn't reflect the team or our work. We also noted how it reinforced bias (women tend not to apply if they do not meet _all_ quals. men tend to apply if they meet _any_ quals). Response was "good point, we'll remove them" and our reqs got a lot shorter and less exclusionary. You might note that we tend to not have any education requirements. At one point the req listed university degrees. This was funny because we had a bimodal distribution of uni drop-out (maybe no high school diploma) on one side and MS or Ph.D on the other. e.g. zero education requirements section in job reqs for my team: https://www.facebook.com/careers/v2/jobs/468265564478223/ https://www.facebook.com/careers/v2/jobs/468265564478223/ https://www.facebook.com/careers/v2/jobs/190442889615860/ https://www.facebook.com/careers/v2/jobs/190442889615860/