 Hello, welcome. I'm going to be talking about inclusion and how it includes everyone. So first, I'm Alice Bevac. I work at Mozilla. I work in our developer relations, which is also called developer outreach. You can mostly find me on Twitter if you're looking to contact me. My DMs are open. So has anybody here ever felt like an outsider? Yeah, me. Did joining open source or learning to code or finding a developer community change that for you? It did for me. Somewhat? Maybe, kind of. There is a lot of mythology that somehow, magically, by joining in communities were all included and welcome. But that's not actually the case for everyone all the time. A lot of time, it's hard. It's hard to be accepted. It's hard to belong. It's hard to find your people or your community and the place where you fit in. And for some people, it's easier. And for some people, it's harder. And especially if you're not a member of a majority in any community, whether it's in tech, whether it's social, whether it's anything else. It's harder and harder if you're not part of the norm or part of the in group to join and be accepted and included. And if you find communities like that, so for example, if you're joining an open source project and you don't feel like you belong, how long are you going to stay there? How much time are you willing to put into it? It's sometimes for many people even more hostile in tech than it is in normal society. I was really, really lucky. My first job in tech was at a funny little educational software company called Computer Curriculum Corporation, doing quality assurance on their educational software. I was 19. I was also an awkward introverted pink haired goth kid who'd grown up in Silicon Valley with my dad who worked at Atari. So I played a lot of video games and I wrote a lot of basic. But CCC was really unique at the time and even today. The CEO of the company was African American. The head of my department was a woman. My boss was a woman and the department was incredibly diverse. We had people from the Vietnamese, Salvadorian, Venezuelan, Mexican, Filipino, Chinese, Russian, Indian, African American, gay and trans, young, old, almost half or more than half were women. So this was an extremely unusual experience and I didn't realize it at the time. And it's not the norm then. And it's certainly not the norm now. And how not the norm? We'll have some data. So this is talking specifically around gender. But basically women make up roughly half of the population if you're just looking broadly in numbers. Yet at best about 40% of company employees in some of the largest tech and at worst down in the 20s and some even worse. Now, this is actually broad numbers of people who work at these companies. This isn't saying these are the percentage of women in engineering roles. And that is even worse. In the U.S., the numbers for gender are similar and the numbers for ethnicity, which is how we track things in the United States, are even more grim. Only 1% of Facebook's engineers and coders are black and 3% are Hispanic. That figure hasn't actually changed in four years, even though they've put immense amount of effort into driving diversity in their hiring. At Google, only 20% of technical jobs are held by women. And last year, last summer, only 49 of Twitter's almost 3,000 employees were black. This is especially striking because Twitter is actually highly adopted by the African American population of the United States. So there's a whole bunch of people using this platform who aren't represented at all in the people who are building it. And if you think a bit on some of the issues that some of these platforms have had, if we had more diverse people having input in the way they're built, it might change the way that they interact with us broadly across our societies. Apple has been working really, really hard to improve their diversity, and I'm using them as an example, not that they're perfect. But in the year between July 2016 and July 2017, about half of their new hires in the United States were from underrepresented populations. So that is looking at women, different ethnic groups, Hawaiian, Pacific Islander, Native American, black, Latino, etc. So they've really put a ton of effort into recruiting from places that they traditionally had not recruited. So going to things like black colleges in the United States that have technical program, they're actually training people with computer science degrees, but that were not included in the standard outreach that they had been doing as far as looking for interns. Programs like Outreaching have been incredibly successful in bringing different people in into internships to get a chance at a lot of companies that the doors were closed before. Now usually when you start talking about things like diversity, people tend to get a little uncomfortable, because if you think about it, if you're focusing on diversity and saying, we're focusing efforts on hiring this group, there's an automatic assumption that somehow that group is being excluded. So if you were excluding some people before, now you must obviously be excluding others now. It's often called reverse discrimination or various other things like that. And it might feel like that, especially if you're someone who's traditionally been in a majority. But realistically, there's an assumption made here that there is a scarcity of jobs in tech and there's only a small amount of people available to fill them. The fact is there's actually a shortage of skilled technical workers worldwide. In 2016, there were 223,000 unfilled coding jobs just in the United States. In 2017, there were 10 times more coding jobs than computer science graduates. And it's projected that by 2022, 30% of worldwide coding jobs will be left unfilled because of lack of workers with the skills to fill them. This is especially true if you start looking at areas like AI, Internet of Things, blockchain, VR, like a lot of new technologies. Now, this feels a little weird because I'm sure as people have job-hunted, it can feel really hard to find jobs. But there's also, I think, a way to look at where are jobs located? Are they located near you? Are they in Europe, United States? Are they in Asia? So broadly thinking about where these jobs are. But globally, there's enough room for everyone. And we also need to really think about how we talk about or think about what qualified means. If you look at some of the surveys that Stack Overload has done year over year, even though they're slightly problematic in a few areas, 68% of the people who were surveyed said they're at least partially self-taught. And less than half have computer science degrees of the people who identify themselves as being professional developers, which means they're employed as a developer. Yet, pretty much 100% of jobs advertising developer roles list having a CS degree as a requirement. Now, this affects a lot of different groups. Some groups, if you're more comfortable in your place and being part of a sort of a majority, may just say like, well, I have enough experience that it overrides that qualification. It turns out that people in underrepresented groups tend to take these lists of requirements pretty much as the truth and are less inclined to apply. It also just affects the fact that only 20% of CS graduates, at least in the United States, are women. There's more in India, roughly about the same in Europe. So we don't have a lot of people who are emerging right now with CS degrees. And even if you're a woman who is in a computer science program getting a degree, your experience with recruiting can be really, really miserable. Stanford, which is a college in the United States, did a study of college recruiting where they sent observers to recruitment sessions at top colleges. And the recruiting team that were sent by some of these top companies were overwhelmingly male. They overwhelmingly talked in language that was very specifically male gendered. They talked a lot about things like beer, which, you know, is a great thing, but also is a little bit alienating if that's not one of the things you're looking for in your career. And when they did send women, the women were almost entirely in support roles. They were checking people in and directing them to the snack table. And when they did have female engineers, they pretty much would only get them up to talk about company culture and not about their engineering contributions. And this has a dampening effect on the willingness of women to participate. The observers in these sessions watched women asked almost no questions and a large percentage of them left partially through the session. In the reverse side, when they do, when male students have female professors or female recruiters, it has almost no negative impact on their ability to want to participate in a career. So we're thinking about diversity broadly, because my talk is not necessarily on diversity, it's on inclusion, but you could have set the stage. Diversity is not just these broad categories, gender, race, ethnic background, et cetera, et cetera. It's all the things that make us who we are. That is things like being an introvert or an extrovert, speaking the native language of the company that you work at, your communication style, your age. Inclusion is actually getting all that mix of things and people to work together. So everyone is included and belongs and respected and feels like they are part of the team or part of the company and respected for that. At my first job at CCC, I was really lucky to be both in a company that was diverse but also really, really inclusive. I worked there for six years. I felt incredibly appreciated. Everyone was really patient with my cranky little 19-year-old goth self. I was encouraged to grow. This is where I learned HTML on my own time as I was working full-time and putting myself through university. And when I graduated, I was actually offered a job as a web developer at the company because they appreciated me and what I brought enough that they wanted me to stay. And I realized that this was really not necessarily the norm. And I think a bit about inclusion, when I think about this time and sort of inclusion and understanding what that really meant, I think about potlucks. So a potluck in the United States is essentially a communal meal where people participating each bring a dish. It's usually homemade. We had amazing potlucks at CCC. So people would bring in dishes and because we had this immense variety of people from different national backgrounds, we would have immense amount of food. We learned to really understand and respect each other's cultures based on food which is probably one of the oldest traditions that humans have. I learned to love Vietnamese food at this job. One of my co-workers' moms took me home and taught me how to make proper Indian food. I rolled thousands and thousands of lumpia which are egg rolls in the Philippines. And all of these things brought me closer to the people that I worked with. And it formed a unit I felt accepted and I belonged and I hope that I brought the same to them as well. That job sort of set the stage for me where I discovered that the thing that I loved to do was web development and that sort of kick-started my career which actually led to me being here today on the stage talking to all of you. What I didn't realize at the time was that that was not going to be the experience I had everywhere. As I worked at more and more companies, I realized how extraordinary that first experience I had and how lucky I was to have it. It turns out that was really just luck. I worked at a lot of other companies. And for a long time I really thought that the price of admission to the career and the work that I loved was being patronized to. Being harassed, being talked down to, being talked over. That was my predominant experience. And this was at a lot of different companies including some that were more diverse including somewhere diversity was either a white guy or an Indian guy. It was at different roles where I was in senior management or an individual contributor. It was my lived experience. Now I'm not actually saying that everything was terrible because these were in truth more the exception than the norm. I worked with a lot of really fantastic amazing supportive people. The arc of my career has been incredibly positive. And the company I work for now is fantastic. But I think sometimes where would I be if I hadn't had to deal with these kind of experiences? And where would other people be if they didn't either? So if it wasn't so hard to be female, if it wasn't so hard to be black. And also where would people who are currently sort of in the majority be if they felt more comfortable with others as well? If you think about it, monoculture and agriculture isn't good, right? You're more susceptible to disease. You're more susceptible to all kinds of things. So broadly thinking about more diversity is helpful. In fact, there's a lot of science that shows that diversity makes us smarter and more innovative. What happens when you're exposed to people who aren't like you is you tend to put more effort into justifying your thinking because you don't make assumptions that the people around you all think the same way that you do. Now, it may make us smarter, but it also makes us more prone to conflict, which is why a lot of the best practices around inclusion are really important. So conflict management, learning to have good communication skills, those things are really important in managing, making diversity turn into inclusion. Sometimes people sort of come at us and say, well, that's your problem, right? That's not my experience. That's other people's problems. Or I'm not a jerk. I treat everybody great. You know, none of this is my problem. I'm not the problem. But I will say it actually is your problem. It goes well beyond things like gender, ethnicity, various other things. And I'm going to talk about a really specific example that's going to affect every single person in this room, and that's ageism, right? And this is so incredibly prevalent in tech. There's a huge bias against people who are old. There's a thought that people who are old are out of touch. They can't learn new things. They're stupid. And here's a quick question. When I say old, how old do you think someone is when they're old? Particularly for thinking tech. But like 70, 80, like really old grandparents, right? 50, 60. So in tech, old is 40. Worldwide, the average age of a developer is 28. It's a little older, about 31 in the United States. It's roughly that in Europe. It's younger, excuse younger in Asia Pacific. And this isn't just a problem in western or northern countries. Age discrimination is massive in China. Three quarters of Chinese developers are under 30. It is legal to discriminate based on age, and most jobs actually limit applicants to be under 35. And if you're thinking about starting your own company, do it now. Because there's a cut-off date. For most investors, it's 32. And that comes from Y Combinator, who's one of the biggest startup funders in the valley, in Silicon Valley. In fact, just in the United States, only restaurants and shoe stores have an average age younger than tech. And those are considered transitional jobs that you do while you're in university. These are the median age of some of the biggest tech companies. Facebook is 28. Google is 30. Microsoft's really old at 33. And when you think about median age, you're basically saying about half the company, half the employees are under and half are over. But if you think about the arc of your career, most people get out of university, say roughly 22. So half of these companies' employees, more or less, have eight years or less experience. And half have a span, if you say retirement is, say, 65, there's 35 years crammed into that. Upper half. That's a big skew. In fact, millennials, which are under 35, roughly, are 50% more likely to be hired than their representation broadly in the population. And Gen X, which is 35 to 55, roughly, is 33% less likely to be hired. And if you're over 60 years screwed, you have a one-third chance of getting hired. 26% of workers at tech companies are over 40. So here's a quick thought. If everyone in this room right now was 30 years old and you're all, say, employed in tech, only one quarter of you would still be working in tech in 10 years. That's one quarter. Oh, and your salary peaks somewhere between 40 and 43. So for those of you who got aged out before then, you actually miss on your peak earning potential. This is a little bit different for people in management, however. Managers tend to roughly stick around until they're around 47. It's less old than any other industry, but older than individual contributors in tech. This is a quote in 2007 from Mark Zuckerberg. You laugh, but he's the head of one of the biggest companies on earth employing a huge amount of people and actually driving the way that most people interact with technology across the world. Now, I wonder, he's 34 now. He's six years older than the median employees of his company. Does he still feel that way? Is he still going to feel that way in 10 years or 15 or 20? And this is a prevalent thinking in tech. And everybody laughed, but it's really there. There's a thought that at some point you're just too old to understand new things. Even now, there's tons of data that show that older workers actually have higher performance ratings relative to people in the same job. And while it's illegal to discriminate based on age, there's all sorts of ways that companies use to phase out older workers. There's layoffs, there's stagnation where you don't get promoted. There's a whole host of other things being shifted to less important jobs. And this is rampant across the entire industry. And more people report age discrimination in tech than gender and sexual orientation discrimination combined. There's been huge lawsuits against Google and a whole host of other companies for age discrimination. Anybody nervous yet? So the challenge here really is what can we do? How do you make this better? Is there some way that we can make this change? And this is broadly around all of inclusion but very specifically around ageism which seems to be the big elephant in the room that everybody doesn't really want to talk about. I think some of it is just the more attention that's being placed on diversity opens up us a chance to really think about all diversity and all inclusion. Examine your own biases. I find myself sometimes falling into the trap of thinking like, especially when my mom calls me and says, can you come over and fix my printers? Oh my God, you're old, you don't understand things. But realistically it's familiarity more than necessarily the lack of ability to comprehend something. If you do something all the time, you gain familiarity with it. If you're already working in tech, there's no reason. If you've had a career for 20 years in tech, you've obviously, nothing's static for 20 years, you've obviously readjusted multiple times in the way you're thinking. And many of our biases are really unconscious, whether it's things around gender, around ethnicity, around age. They're driven by media, they're driven by our social norms. I find it fascinating that this concept that young people are smarter actually goes against cultural norms pretty much everywhere in the world that we accept them in tech. And if you find yourself thinking that someone doesn't belong, ask yourself, why? Why do you think that? Why is that your immediate reaction to them? A lot of time it's driven by something like a stereotype or an assumption about them. That may or may not be true. And force positive thinking. This is an exercise I have been teaching myself to do that's incredibly effective. A lot of times when we're confronted by differences, we tend to react negatively. So forcing yourself to think positively is one way to do this and talk about it, take action, be more involved. If we do all of these things together, we can be the factors for change that means all of us can be included as long as we want to be. Thank you.