You and every other recruiter are looking for experienced female engineers. There are no magical shortcuts here, very few companies have figured out how to do so consistently. It's extra hard if you have no women onboard already.
Here are some things you can try:
1. Don't focus on experienced candidates. Really. Your pool will increase a LOT when you start looking at new grads as well as bootcamp grads (see HackBright). Consider interns as well - it's a legitimate way to impress and retain young talent. Experience is nice, but if you can figure out how to grow your engineers, the sky's the limit.
2. I'm hardly an expert here, but neither the job posting nor the leadership principles strike me as particularly women-friendly. The former seems pretty neutral (and rather dry), the latter has language like "disagree and commit" and "vocally self critical" that may project a culture of conflict. Conflict is not bad, mind you (some conflict, anyways) and I know you're coming from the right place, but that's the kind of language you might want to think about. I haven't used it, but https://textio.com/ might be something to consider. Compare to this job posting: https://www.etsy.com/careers/job/d6f56ba8-f2f5-45fd-b7ae-949... (Etsy is one of the few companies that have figured this out, BTW, IMO).
3. Explain concretely what the opportunities for growth and learning are.
4. Volunteer as a mentor at HackBright Academy (or something similar, since you're not SF-based).
Honestly, #1 will give you the best results. But as far as I can tell this is still a very early hire, so might be hard for you to make that decision. Do your best and set yourself up for future success, even if your next hire is not a woman. These things take time. Gender is also not the only way to increase diversity ;)
I completely agree it's extra hard if you have no women onboard already--that's why I'm trying to source female engineers now, while the team has only one full-time engineer. The Etsy example of turning around a non-diverse culture is great, but waiting that long will cost 10x as much. Unfortunately, it seems that how it needs to be done, since sourcing at such an early stage is so difficult.
re: 1 -- I agree. I've found I won't have trouble sourcing entry level. The code schools and bootcamps seem to be making a lot of progress on gender diversity. I think in the long run when my company can afford to focus more on growth and leadership development I will pursue this route. Right now, however, I have a very solid pipeline of diverse and experienced engineers willing to join the team--just no experienced women.
In case anybody has stumbled on this short thread while experiencing similar issues: I've had pretty good success with LinkedIn connection requests. I think it helps that I'm crafting the invite to be personal and that I'm a founder and not a recruiter.
The biggest struggle was finding the candidates in the first place. LinkedIn limited the number of search results you can get for free and "premium" subscriptions didn't seem worthwhile.
Instead, I used Google-fu "site:linkedin.com/in" and some boolean search around the technology I was looking for and my location. The key that got female candidates was including "Grace Hopper" or "Anita Borg". Nearly 100% of the search results were experienced women.
Comments
You and every other recruiter are looking for experienced female engineers. There are no magical shortcuts here, very few companies have figured out how to do so consistently. It's extra hard if you have no women onboard already.
Here are some things you can try:
1. Don't focus on experienced candidates. Really. Your pool will increase a LOT when you start looking at new grads as well as bootcamp grads (see HackBright). Consider interns as well - it's a legitimate way to impress and retain young talent. Experience is nice, but if you can figure out how to grow your engineers, the sky's the limit.
2. I'm hardly an expert here, but neither the job posting nor the leadership principles strike me as particularly women-friendly. The former seems pretty neutral (and rather dry), the latter has language like "disagree and commit" and "vocally self critical" that may project a culture of conflict. Conflict is not bad, mind you (some conflict, anyways) and I know you're coming from the right place, but that's the kind of language you might want to think about. I haven't used it, but https://textio.com/ might be something to consider. Compare to this job posting: https://www.etsy.com/careers/job/d6f56ba8-f2f5-45fd-b7ae-949... (Etsy is one of the few companies that have figured this out, BTW, IMO).
3. Explain concretely what the opportunities for growth and learning are.
4. Volunteer as a mentor at HackBright Academy (or something similar, since you're not SF-based).
5. Speaking of Etsy, read this: http://firstround.com/review/How-Etsy-Grew-their-Number-of-F...
Honestly, #1 will give you the best results. But as far as I can tell this is still a very early hire, so might be hard for you to make that decision. Do your best and set yourself up for future success, even if your next hire is not a woman. These things take time. Gender is also not the only way to increase diversity ;)
I completely agree it's extra hard if you have no women onboard already--that's why I'm trying to source female engineers now, while the team has only one full-time engineer. The Etsy example of turning around a non-diverse culture is great, but waiting that long will cost 10x as much. Unfortunately, it seems that how it needs to be done, since sourcing at such an early stage is so difficult.
re: 1 -- I agree. I've found I won't have trouble sourcing entry level. The code schools and bootcamps seem to be making a lot of progress on gender diversity. I think in the long run when my company can afford to focus more on growth and leadership development I will pursue this route. Right now, however, I have a very solid pipeline of diverse and experienced engineers willing to join the team--just no experienced women.
In case anybody has stumbled on this short thread while experiencing similar issues: I've had pretty good success with LinkedIn connection requests. I think it helps that I'm crafting the invite to be personal and that I'm a founder and not a recruiter.
The biggest struggle was finding the candidates in the first place. LinkedIn limited the number of search results you can get for free and "premium" subscriptions didn't seem worthwhile.
Instead, I used Google-fu "site:linkedin.com/in" and some boolean search around the technology I was looking for and my location. The key that got female candidates was including "Grace Hopper" or "Anita Borg". Nearly 100% of the search results were experienced women.