Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Automattic, the company behind WordPress.com, is a primarily distributed company with more than 1,000 employees across 76 countries. I’m an engineering lead, currently working on the Developer Experience team. As Automattic has grown, we’ve learned a lot about working remotely and across time zones, and have shared insights on what we see as the future of work on the Distributed podcast, hosted by our CEO, Matt Mullenweg. 

This week, Nicole Sanchez, the founder of Vaya Consulting and an expert on workplace culture, and I had an opportunity to co-present a Crash Course in Remote Management, a free one-hour webinar hosted on Zoom. Nicole has previously held social impact and leadership roles at GitHub and the Kapor Center for Social Impact.

Nicole and I walked an engaged audience through proven practices and what they’ve learned about leading, communicating with, and measuring the success of remote teams. Participants offered insightful questions, leading to lively discussions around:

• Collaboration and relationship-building.
• The cost, benefit, and ideal frequency of bringing teams together for face-to-face interaction (in general, if not as commonly right now).
• Communicating and prioritizing messages across a variety of channels. 
• Encouraging people to go outside, exercise, spend time with family, or otherwise step away from the computer (also known as being “AFK,” or “Away From Keyboard”) without the fear of being judged or anxiety over being less productive.

Some companies are encouraging employees to experiment with working from home, which can feel very different from in-person and office work. If you’re interested in learning more, please check out the full video recording of the course:

Matt’s latest blog post, “Coronavirus and the Remote Work Experiment No One Asked For,” is also worth a read. For more information and advice on COVID-19, please visit resources from the CDC, World Health Organization, and other health authorities.

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring. 

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring. 

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring. 

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring. 

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring. 

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring. 

Our Developer Hiring Experience team analyzed this topic in a recent user-research study. The issue resonated with women engineers and a strong response enabled the team to gain deeper insight than is currently available from online research projects.

Seventy-one engineers who identified as women or non-binary responded to our request for feedback. Out of that pool, 24 answered a follow-up survey, and we carried out in-depth interviews with 14 people. This was a highly skilled group, with the majority having worked in software development for over 10 years. 

While some findings aligned with our expectations, we still uncovered a few surprises. 

The Job Hunt

In initial job hunts, respondents were found to rely heavily on their existing networks and on personal outreach from companies.

If they do not have a pre-existing connection with a company, they’ll likely scrutinize it for red flags before they submit an application. Job descriptions are searched for any discouraging language — for example, if parental leave descriptions only refer to mothers. Information — about the job, salary, team, and hiring process — is key for encouraging applications.

Stack Overflow is a popular resource for job hunting; whereas Glassdoor is viewed as less useful, and more as a venting forum for former employees or unsuccessful candidates. 

The Hiring Process

The most favorable hiring processes represent a growth opportunity, rather than being purely evaluative. Communication and responsiveness are important, as is the visibility of other women within the team. For some participants, interviewing is seen as a skill to maintain. These developers are continually keeping an eye on job listings to stay abreast of their options. However, the chance for growth was the most widespread reason for actually leaving a current position. 

Job Satisfaction 

Consistently being able to have an impact, including leadership opportunities, stood out as important; if this is lacking, experienced women engineers are likely to seek new employment. Dissatisfaction can also be caused by being pushed onto the management track and having to fight to continue to focus on technical work. 

The data showed women are looking for more communities focused on connecting to other senior-level women, and around more technical topics. Concerns around online harassment can put women off trying to build their network online. 

Changes at Automattic 

We are working on Automattic’s employment branding to reflect our findings. We are in the process of gathering resources to better describe work at Automattic, and we’re encouraging existing developers to increase their visibility outside of the company — whether through writing or engaging in their communities. 

In job postings, we have removed any gameplay or language that emphasizes hiring as a competitive process — for instance, we no longer mention application volume. Instead, job postings highlight learning and career opportunities for the candidate. Adding the term “Senior” to postings is also being tested. Although this implies a job ladder that does not necessarily exist here, the research clarified that its absence sent the message that all positions are mid-level roles, without the path to growth that women candidates tend to look for. 

We are also managing candidates’ expectations by making the whole hiring process more transparent, and have created a public page outlining the hiring process.

We’ve made it easier for interested applicants to have casual chats with other women at Automattic. We also offer candidates the opportunity for one-on-one calls with a member of the Developer Experience team during the final stages of hiring; this has started with under-indexed candidates but with a view to rolling it out to everyone. These chats take place outside of the formal hiring process to provide an opportunity for the applicant to ask any questions they have and for the company to better understand their career goals and motivation. 

We are tracking the progress made and are excited to be able to contribute data to the field of gender representation in engineering. If you’d like to take a more in-depth look at our study, please do read the more detailed write up on our developer blog, or download the PDF!

Interested to learn what positions are currently open at Automattic? We’re always hiring.