Community

Summarized using AI

Keynote

Marco Rogers • April 25, 2017 • Phoenix, AZ

In the keynote address at RailsConf 2017, Marco Rogers discusses his experiences and insights on being a black person in the tech industry. He emphasizes the challenges and systemic issues faced by African Americans in tech, and shares what he has learned throughout his career. The talk is structured around several key points that highlight personal anecdotes and broader observations regarding diversity and inclusion in tech.

Key Points Discussed:

  • Introduction: Marco introduces himself and his background in tech, noting his work at Clover Health. He sets the stage for discussing race and diversity in tech.
  • The Importance of Representation: Marco mentions the rarity of black individuals in tech positions and how it significantly impacts the experiences of those who are there.
  • Networking and Connections: He emphasizes the necessity of forming connections with people, particularly in predominantly white spaces, to gain opportunities. His first job was secured through a friend who helped him get a foot in the door.
  • Survival Tips:
    • Know People: The importance of networking and forming relationships within the tech industry.
    • Avoid Showing Struggles: The survival mechanism of not openly asking for help to avoid being viewed as less competent.
    • Confidence and Attitude: Learning from colleagues, Marco contrasts his initial difficulties with the different experiences of other black individuals in tech.
  • Employee Retention: He discusses how black employees can often be overlooked or let go more easily, using examples of previous colleagues like Karl and Trey who were dismissed under vague pretenses.
  • Belief in Self-Worth: Marco stresses the need for constant perseverance and display of competence in order to maintain a position in the industry, suggesting that confidence is crucial for survival.
  • Conclusions and Hopes for Change: Marco concludes with a call for the tech community to improve diversity efforts and create a more inclusive environment where black individuals can thrive without feeling like their survival depends solely on proving their worth.

Overall, Marco Rogers' keynote addresses the emotional and social hurdles that black professionals face in the tech industry and the necessity for broader structural changes to foster an equitable environment.

Keynote
Marco Rogers • April 25, 2017 • Phoenix, AZ

RailsConf 2017: Keynote by Marco Rogers

RailsConf 2017

00:00:11.929 Good morning, everybody. Can you hear me okay? Thank you for that introduction, Sarah. I was listening to it, and at the end, I felt like it was talking about me in school. So, it's early, and I'm a bit nervous. I'm going to take a second.
00:00:29.730 My name is Marco Rogers. I'm going to move around a little bit, but I need my notes to remember what I want to say. I don't have any slides, so kick back and come along with me. It'll be fun.
00:00:52.350 Thank you for having me to keynote at RailsConf 2017. Let me get to the work stuff—I work at a company called Clover Health, and we are building a different kind of health insurance company. It's backed by technology, it's data-driven, and our goal is to focus on our members and their health, keeping them on a path to living well. This is a way for us to be successful as an insurance company. It's really cool, but I'm not here to talk about that today.
00:01:17.040 I’m not here to talk about Rails today either; I don’t actually know Rails, and they promised me that that was okay before I came.
00:01:23.250 So, I’m not here to talk about programming either. I’ve been a manager for several years now, so if I start talking about programming, you should probably check your email or push something to production. We are not here to pay attention to that.
00:01:53.280 What I am here to talk about today is how it feels to be Black in tech. I’m going to let that hang for a second so you can adjust. It’s going to happen, but don’t worry—we’ll get through this. I didn’t come here to start controversy on my first invitation to RailsConf.
00:02:11.400 This talk will be easy for you; it’ll be hard for me. I’ve spoken at conferences before, but this is my first keynote address. When Sara and the other organizers reached out to me to ask if I would give a talk, I asked them why they were interested in me.
00:02:29.610 They said they appreciated my voice on Twitter, blog posts I’ve written, and they had seen other talks of mine. They said they wanted me to come and talk about whatever is important to me and share that with them.
00:02:50.040 When I asked other people what they wanted to hear me talk about, many friends who are not Black said they wanted to hear me talk about being Black in tech. That’s a topic that people want to discuss. We’ve been talking about diversity and inclusion for a long time, but we need to start digging deeper into various aspects of it.
00:03:01.530 We’ve talked a lot about being a woman in tech—I think we’ve done a good job with that—but we don’t get to discuss being Black in tech very much. So, people said this is what they wanted to hear about. I thought about it for a second, and I was not brave enough to take on that topic initially.
00:03:14.370 I wrote a different talk; I wrote something I thought was good. My wife thought it was good, and other people told me it was good, but it was a regular talk. It did not pass my bar for keynote-worthy.
00:03:52.280 The keynote slot says there are no other activities planned right now; we need all of you to come in here and hear what this person has to say. That’s a lot of pressure. I asked myself what qualifications I have to come and ask you, hundreds of people, to listen to me for however long.
00:04:17.040 What makes me unique? I’ve done a lot of interesting things, but one thing stands out as unique: I’ve had a solid career in tech for over 12 years. I have been successful, and I’ve been Black that entire time. We’re laughing, right? Okay, I’m glad you’re awake.
00:05:03.760 But that’s uncommon; it’s not normal. And I mean, this is real talk today. I want to have a real conversation with you about it. We know that the diversity numbers in tech are not good for Black people.
00:05:20.380 Companies are releasing their diversity statistics, showing 2% or even 1% of African Americans and sometimes 0%. Sometimes, it's just a pie chart line with 0%. When it gets crazy, it’s like 4 or 5%—some people are high-fiving, but it’s not great.
00:05:35.680 It’s so uncommon that I often get asked, 'How did you do it?' People say, 'Marco, how did you make it?'. I don’t know if that question is the right question, but it seems to be something people want to talk about. So, I found some courage and thought okay, let’s talk a little bit about it.
00:06:04.919 So, what I’m here to discuss is how to survive as a Black person in tech when all the evidence seems to point to the fact that it’s really hard to do so.
00:06:11.590 As I was putting together the title of the talk, I thought it would be something like 'Survival Tips for Being Black in Tech,' with the parenthesis 'if you’re Marco' because I can only speak for myself. If I tried to speak for all Black people, they would probably revoke my membership.
00:06:23.110 But hopefully, we will learn something. A couple of years ago, I gave a talk at UltraComp called 'Conforming to Succeed.' That talk was about my formative years growing up and how I initially found my way toward a career in tech.
00:06:31.120 You can find that talk on the internet; you should check it out—it's good. This one basically picks up where that one left off: my graduation from college. I received a degree in computer science from Georgia Tech, originally from Atlanta.
00:06:42.790 Getting my career started was pretty rocky. Upon graduating, my situation was pretty dismal. I had no idea what I wanted to do and wasn’t a stellar student, which some people would be surprised by.
00:06:53.050 I was on a long journey to getting to a point where I knew how to show up and be good. I did not have many prospects; I didn’t have any internships.
00:07:05.790 I was just a recent grad trying to find a job while being Black. Things were not looking good. Searching around in Atlanta, I wasn’t getting any callbacks.
00:07:15.680 I didn't even know that Atlanta was not a good place to be searching for tech jobs. There wasn't much of a tech scene there at that time. I was spending a lot of money on this degree, and all I wanted was to get a job.
00:07:28.990 So, my first survival tip I picked up for surviving as a Black person in tech was quite simple: you gotta know some White people. Yeah.
00:07:38.990 What I really mean is that you can know some people already in tech so they can vouch for you, help you make connections, and get your foot in the door.
00:07:46.490 For me, it was a buddy of mine from school—a White guy and a really good friend—who called me up while working in the DC area.
00:07:54.230 He said he was working at a place where he could recommend me, and that worked out. But you might be thinking when is the part where it gets hard because I’m Black?
00:08:04.720 I mean, anybody can make the right connections and get their foot in the door, except, well, we know that’s not true.
00:08:14.480 If you’ve been paying attention to the diversity conversation, you know most people already in tech make connections with people like them.
00:08:20.350 We tend to cluster around our racial and ethnic identities. That’s why they're more likely to make connections with White people, and presumably, I can make connections with people who look like me.
00:08:28.440 Except I didn’t see any of those people in tech. I didn’t meet any other Black students in the College of Computing at Georgia Tech, nor did I have any Black professors.
00:08:38.440 I was kind of on my own, and I had to reach out to whoever was around me and try to make some connections, but I didn’t really know how to do that.
00:08:48.440 Most of the people around me were White, and that’s how it played out. If I wanted to get anywhere, I had to connect with some White people.
00:08:56.530 That's expected until we make more progress with this diversity problem. We should expect people to follow their networks.
00:09:05.150 So, networking for Black people in tech was really slim. What I’m saying to you is if you need to make connections and you’re Black, you might have to be the exception to the trend of only connecting with your own ethnic group.
00:09:11.790 Before you can do anything, you have to go against the statistics—it's going to be hard. I got lucky; my friend reached out to me.
00:09:19.990 He was also a recent grad, but he got his job because his dad knew a guy who owned a web shop.
00:09:29.100 They got me hooked up, and I have no problem with that. If you can pull strings, do it, as long as you can get in.
00:09:37.240 I had one friend who reached out to me, and it worked out. But I don’t know how many people never had any strings to pull.
00:09:47.280 They didn’t get to do anything because they weren’t able to buck the trends keeping them from finding the right network.
00:09:56.890 That worked for me. When I had my first phone interview—this is not that important, but it’s funny.
00:10:06.010 In that phone interview, I had to tell them about what I did in school, and I said I basically didn’t do much.
00:10:14.420 I told them we built some cruddy apps, but one key question got me the job: the interviewer asked,
00:10:23.150 ‘Oh, so you said you mostly used Java. Does that include JavaScript?’ I knew those weren't the same thing, though I hadn't done much JavaScript.
00:10:30.200 He said cool, you should come here and work. I had gone through so much trouble to get a call back, and I got a job because my friend referred me.
00:10:39.480 There was no barrier except for the social ones to reach me, that was my experience. I got my first job at a web consulting shop in DC.
00:10:50.300 I didn't know how well I was doing, but I kept getting paychecks, which for me was the only criteria for killing it.
00:10:58.230 I was making a lot of friends, but at the same time, I noticed I was the only Black person on my team.
00:11:06.350 This didn’t bother me necessarily, but I couldn’t help but notice. You know, when Black people walk into a room, we immediately scan for how many other Black people are in it.
00:11:15.180 One day, that changed when another Black person joined the team. Let’s call him Karl—names have been changed to protect the innocent.
00:11:24.160 Karl was similar to me in certain ways. He was a recent grad with a CS degree from a decent school, and he was Black.
00:11:32.679 That was enough of a similarity. There weren’t many Black people around, and having another Black person on the team really matters.
00:11:40.720 Diversity helps because it allows us to see ourselves reflected in people succeeding. That's a huge impact on your ability to succeed.
00:11:52.450 Suddenly, I had Karl, who could reflect back at me what was going on.
00:12:00.160 If you take nothing else away from this talk, let it be this: being Black always matters.
00:12:06.230 Whatever you're trying to do, I'm trying to do the same thing but while Black, which means the rules might be different.
00:12:19.450 I need to tread carefully, and it helps to see what happens to others who are trying to do the same thing.
00:12:27.240 But what I observed was that Karl was let go within six months. His performance wasn’t picking up fast enough; they said he didn’t have the right attitude.
00:12:34.620 To this day, I don’t know what the right attitude is.
00:12:41.320 But I had to put this together with what I was able to observe about him, and it was clear—Karl was always asking for help.
00:12:48.110 He was upfront about what he knew and what he didn’t. However, my next survival tip I picked up was the opposite.
00:12:55.390 Don't ask for help. Don’t admit you’re having a hard time; keep your head down and just make it work. This is not good life advice.
00:13:04.560 It took me a long time to unlearn it, but remember—these are tips for survival. I was trying to adapt to my environment.
00:13:13.230 I saw people like me dropping out of the workforce. The first Black engineer I ever worked with took a hit because he couldn’t prove he deserved to be there.
00:13:20.460 I tried to learn from that to ensure that wasn’t going to be me.
00:13:27.460 Long story short, I started doing well and began leading larger projects, interacting with clients. I built a reputation.
00:13:35.770 Years later, I was contracting with a big tech company, and another Black developer, let’s call him Trey, joined the team.
00:13:43.410 He was the fifth or sixth Black dev I had encountered in my four years. So, I didn’t even get excited anymore—it was almost standard.
00:13:51.040 Trey and I began working closely, and his work directly affected mine. I found he didn’t move fast enough, and it frustrated me.
00:13:58.880 I figured I needed to talk to higher-ups to express my concerns. I didn't single him out but said things weren’t materializing fast enough.
00:14:07.170 Next thing you know, though, Trey was gone within a week. That was a shocking reality check.
00:14:15.120 When you’re the only Black person left on a team, it hits you hard how easily folks can get rid of you.
00:14:21.800 This was not a situation I wanted to be a part of, so my next survival tip is: Never help them get rid of us.
00:14:27.600 The only reason I’m here and able to talk today is that I managed to stay on the right side of relationships. I was often lucky to be just awesome enough.
00:14:39.520 To this day, I find it incredibly difficult to give negative feedback to other Black people. It doesn’t feel right.
00:14:47.170 There are not that many of us who even get a chance to get hired.
00:14:54.730 I want to be clear that this isn't what you might expect when talking about being Black in tech.
00:15:04.190 I want to talk about how it feels for us in this industry. For the longest time, being Black in tech felt like walking a tightrope.
00:15:12.480 I had to concentrate because everyone else walked around freely while I attempted to get to the end of that tightrope.
00:15:22.150 When something went wrong, it felt like I couldn’t look away to help someone who might have fallen.
00:15:30.210 Carl slipped and fell one time, and I couldn’t do anything. And then Lester, who rode a unicycle, sped around me—showed me what could be.
00:15:39.150 But, as soon as I tried to boost my speed to play catch-up, Trey fell, too.
00:15:47.020 Watching people throughout this experience, that’s how it felt at times, being on that thin rope.
00:15:57.400 It can be difficult and daunting. In many ways, I still feel like I’m walking that tightrope—and let’s face it—the industry’s track record is far from ideal.
00:16:05.670 Being made aware of that history isn’t just a conversation starter; it’s reality for many of us.
00:16:13.200 I know many people, like me, want to build towards something better—where we can thrive without constantly fearing we're on the chopping block.
00:16:21.550 I wanted to spend more energy learning Rails and less on survival. It’s just that simple.
00:16:29.210 One of my younger cousins has just started college and told me he wants to do computer science. He said he wants to do what I do.
00:16:38.080 He thinks my life is great. So, I’ve begun introducing him and his brother to this world.
00:16:46.470 Every conversation is an opportunity to help them navigate better than I did.
00:16:53.670 And we should all want that. So thank you for letting me share today.
00:17:00.000 I’ll be around for the rest of the day, so feel free to come chat with me. Thanks!
Explore all talks recorded at RailsConf 2017
+109