How Do We Mentor the Next Generation of IT Leaders?

  |  Compiler Team  
AI/ML
전문력 개발

Compiler • • How Do We Mentor the Next Generation of IT Leaders? | Compiler

How Do We Mentor the Next Generation of IT Leaders? | Compiler

About the episode

New tech graduates enter the workforce every year. What generational differences and unique challenges will these younger professionals face? Mentorship is essential to make the transition into enterprise IT, regardless of where a person worked before. But it’s not always clear what mentees need, or what would be most beneficial for them.

In this episode, we speak to people about what makes a good mentor, how learning can go both ways, and what is most meaningful in mentoring relationships.

Compiler team Red Hat original show

구독

Subscribe here:

Listen on Apple Podcasts Listen on Spotify Subscribe via RSS Feed

자막

Angela, do you have a mentor? So I have two official mentors, one that I talk to pretty frequently, the other one, not very much. And then I have a, I guess, unofficial mentor who I talk to at least once a week. How about you, Brent? I would actually consider my current boss a mentor, absolutely. I also have, I guess, a more official mentor and that is really wonderful because one, he's not my boss, but two, he works in a completely different area. So he's able to have a lot of good perspective on my career, on challenges that I'm facing. So I have lucked out with some really great mentors. What about you, Kim? I have not had a very good experience with mentorship. I'll be honest. Oh no. Yeah. I probably have quite a few people I look up to, but for me, mentorship is kind of nerve wracking. Why is it nerve wracking for you? Well, for me, it's like, I'm always in fear of people judging me. So it doesn't really matter if that person's my boss or not. I'm always fearful of being judged or critiqued for my performance and the things that I'm doing or not doing. I think we carry those insecurities when we expose ourselves to folks. Right. Yeah. And sometimes you have to worry, are they going to judge me by something that I just said? So I don't think that goes away just as a human being. I don't think that really goes away if you do or don't have a good mentor. I think in listening to all of our experiences with mentorship, it seems like there's a lot of variability: who your mentor is, how often you meet, what you talk about, and even whether it's valuable or not. And I don't know that I've ever really thought about what makes a good mentoring relationship. You know what Brent, I had the same question. So let's find out together. This is Compiler, an original podcast from Red Hat. We're your hosts. I'm Brent Simoneaux. And I'm Angela Andrews. We are here to break down questions from the tech industry; big, small, and sometimes strange. Each episode, we talk to people working in the tech industry, including Red Hatters like us. Today's question. How do we mentor the next generation of IT leaders? Producer Kim Huang dug into this topic. Here she is. I decided to speak to a couple of people about the topic of mentorship, people who have kind of been on both sides, right? Oh yeah. So I started off speaking to Hugh Brock. He helped craft the mentorship program that Red Hat has with Boston University. And he talked a little bit about how the program started. I had the opportunity to come over to Boston and open up the office there and also launch our first ever real research relationship with a university, which was with Boston University. On the one hand, dealing with professors and university research and developing an intern program more or less from scratch and all of the other things that go along with that, I was for sure making it up as I went along. Hugh talked a lot about the students that he works with in the program and how they view things like open source, for example. He says that while there is an attraction to open source, it's sometimes a really hard concept for people to grasp. When I talk to undergraduates, I talk to prospective Red Hat interns, or Red Hat employees. And I tell them, "We work in the open. Your work remains your own. We don't tell you which upstream projects you can contribute to." I think that really resonates with people, but at the same time, I think it's also hard for them to understand working in the open. What does that mean? Does that mean everybody's going to criticize, going to be able to critique everything that I do? And the answer is yes. So there's a large element of support that goes along with that. In some cases, meeting a mentor like Hugh might be their first exposure to technologists, to the way they work, to the way they think. Before this, a person may have been learning to code on their own, through videos or books. Angela, I'm curious about the moment in your career when you switched from learning from a book to learning from a person. Oh gosh. So that was the way you learned. Yeah. That transition to learning from people was very gradual. You usually learn from the people around you that are the closest, your colleagues, your boss, and that circle tends to get a little bit bigger. You go to conferences, you go to some sort of training, you learn from as many channels as you can. Yeah. Think about it. Back in the nineties, there was not this YouTube, there was not all of these online learning platforms. I think maybe one really great thing, but also really bad thing, about books and YouTube and other things like them is that they don't talk back. Yes. Yes. You have a point, you have a point there because feedback is really important in anyone's learning process and that's what's missing in those methodologies. I definitely agree with that. So going back to what Hugh was saying about his work at Boston University, one of the troubles that he pinpoints is that some students have trouble opening themselves up to critique. Is that right, Kim? That's right. Think about it. If you're learning how to code on your own, if you are mostly studying in a program, you're not necessarily working with other people. You're in a very solitary learning environment. And then for the first time you're opening yourself up to critique, doing like code reviews and code comments, and things of that nature. So that can be a little bit of a shift that a lot of these younger tech professionals are not accustomed to and have not encountered before. It's not necessarily a bad thing. It's just that it's something that's very new. Yeah. It's scary and also unpredictable. Yes. Especially when you're young and you're starting out. Feedback, if you're not used to receiving constructive feedback, it can feel like a criticism. Oh yeah. So the delivery in which that information is coming is so important. And of course the deliverer, the person delivering it is really important because otherwise you might not be able to hear it. I wanted to talk to someone who was on both sides of the mentorship spectrum. So I decided to have a chat with Oindrilla Chatterjee. She's a data scientist who works at the Red Hat AI Center of Excellence. Oindrilla was a mentee in the program at BU and since then she's become a mentor herself. I asked her about the role of mentors and a person's development. And she started out by talking about the unique position a mentor can have in being a safe space for a young tech professional to express their thoughts and concerns. The core duty of mentors is to create that safe environment for mentees to ask questions that they wouldn't necessarily ask their managers. And it gives an opportunity for those people who are coming into the tech industry to get support from someone apart from your direct team members who are analyzing you, grading you, or directly responsible for your performance. The pressure to perform, plus generational differences, can result in a mentee needing very different kinds of nuanced things from their mentors. Oindrilla says that today's mentees are no different than any generation and that they could benefit from that type of empathy. Checking in, having conversations about what the mentees are working on, or just empathizing with their situation, that they might be really struggling hard to prove themselves, or get a job done by themselves without asking for help. Getting a job done without asking for help. That was a really big thing that stuck out to me. Yeah. There's really no specific part in your journey that this doesn't apply to. Not for just the new students and new people just entering tech, but this is for anyone along their tech journey. You really do need that space where you can benefit from that type of empathy. Because again, not for your team, not your boss, not anyone in that chain, but someone outside of it that can just give you that space to be is really important. And it seems like Oindrilla is the perfect person to help us out here because she's been on both sides. She's been a mentee and a mentor. I'm curious, Kim, how does she create empathy in a mentorship relationship? I asked her exactly that. As a mentor myself, I like to set these 30 minute check-ins at the start of every week, a time where the mentees can come and talk about what they did over the past week and just discuss any of the challenges that they faced and just plan forward for the next week. And remember, this is very different from a general team's sprint planning or sprint demos. This is very conversational. This is a time where we can really talk about how could we have done something better, or what are some things which as a mentor I can help you with to accomplish your goals. So she's talking about the importance of having someone outside of your team, right? Yeah. And that person creating time and space for you. Yeah. That's not something that I think mentees are positioned to ask for directly. So it's really important that it's offered. Yeah. That's a hard ask, right? I mean, we can ask for someone to mentor us, but this little benefit that Oindrilla is providing, we wouldn't know how to ask for something like that. We wouldn't know that we could. Yeah. There's something I found really special about instead of the mentee scheduling time with the mentor, sometimes having the mentor schedule time with the mentee. Yes. That feels like a gift and it feels really special. At first I approached this story thinking about, all right, people that are coming to tech for the first time, they may be freshly graduated from a computer science program. I was thinking along the lines of what their identity is and what their concerns are. So I talked to Hema Veeradhi. She is a software engineer at Red Hat. And I wanted to know about her experience in the mentorship program at Boston University as well. I feel everybody who comes out of college, you're sort of confused. I don't know if it's everybody, but I can say that for a lot of people, because there's so much there. There's so much, you have opportunities to take and it is confusing. It can be overwhelming as well. You're trying to make the right choice because this is something that you want to pursue in the future. And this is, you have your own goals. So a little bit of background about Hema. She did go to Boston University, but she did her undergraduate study in her native Bangalore, India. So in order to go to the program at BU she had to leave her family behind in India. She came here alone, separated from her family and that introduced a lot of different concerns and worries and obviously a lot of stress, right? You're separated from your family, everybody that you know, trying to transition into a different world basically. I think coming from that to an industry where you have a diverse bunch of people with tons of experience, there are super senior people in the company, super talented people, but there are also a lot of your own peers as well, who may have been older or younger. So it does get intimidating. I think that's how I felt. There are so many people. There are so many great people that sometimes you wonder what you are able to offer. Angela, take us back to your early career. Does this resonate with your experience? I wasn't leaving my family and my home place. But from where I grew up, moving into this space of higher ed and then moving into this space of corporate America, it was really a culture shift. It was a different type of diversity than I was used to. Everybody didn't look like me. So it went from being very comfortable to now having to stretch yourself because you have to make sure that you can communicate with folks that aren't like you. You know what I mean? They don't speak your language. And to her point, probably very literally they don't speak your language. And you get the people who've been around longer than you. So you still have on your training wheels, they don't. So you, there's that little bit of intimidation. Is this right for me? Am I doing this right? I'm not really sure. And in your defense, as someone in this space, you have to believe very strongly that you belong there and you have a place. So that's what gets you to the next hurdle, that gets you to the next project, that gets you through to the next assignment. Imposter syndrome is real and it can be couched in so many different things. But knowing you belong there really does take you where you need to go. I think for me, it actually took someone saying, "You belong here." Okay. Quite explicitly. I think it's like, there are so many opportunities it's kind of scary, but then also you look around and I work with a lot of really talented people. Yeah, like you said, imposter syndrome is real. I feel it. I bet you, it didn't end there. No, Uh-huh (affirmative), I bet you, you probably had that thought once, twice, a couple more times. You have to keep reassuring yourself, always, that you belong. So it's a struggle. The value of having a mentor, right, especially someone who's been around longer and maybe someone who is really successful or someone that you can see yourself being in some ways, saying that back to you, it's almost like a future self saying it back your current self that you belong here and you can do this. Man, that goes a long way. That means so much. Yes. Thank you for saying that. It means so much. Yeah. Both Oindrilla and Hema came from a really heavy computer science background. They both studied. They both had people and their family and their friends that were already in the tech industry. So they were kind of assured a little bit, at least in their, I guess, belonging. But what if someone doesn't have that? Oh yeah. What are their needs? Especially in a mentorship program, do their needs change? And what are some of the things that they could teach, maybe, the mentors themselves about how to approach young people who are trying to get into tech for the first time? So we heard from Hugh who created a mentorship program. We heard from Oindrilla and Hema who have kind of seen both sides of mentorship in both roles. Let me introduce you to Cali Dolfi. She's a data scientist at Red Hat. And I spoke to her about some of the needs and the wants that both mentors and mentees have. She says, one of the needs is the need to be vulnerable about what a person knows and what they don't know. I think a huge portion of breaking down that barrier as well is pretty much just being straight up, being like, you know what? I don't really know what I'm doing completely either. I think it's really a sense of vulnerability as well, necessary on both sides. And I think it's a responsibility of the mentor to show a little bit of vulnerability for the mentee can feel comfortable doing that as well. Here's the thing about Cali. She didn't have as much experience as all of her classmates in her computer science degree program. So she said it was a concern that she had to feel comfortable to share things with her mentor who gave her the support that she needed at the time. I can say that it can be really intimidating. And I would say that my technical expertise was actually something that I was very insecure about going into my internship at the beginning and I had a really great mentor in Oindrilla who was constantly like, "Oh, you don't understand this. Let's get on a call and let's figure this out together." Oh yeah, that's right. Her mentor was Oindrilla Chatterjee. Wow. Who we heard from earlier in the episode. I see what you did there, Kim. Yeah. So remember when Oindrilla was talking about generational differences? Yeah. Cali says that those differences can present in more than just a frustrating kind of way. They can also present unique opportunities. When people can start to break down their walls and figure out that they can learn from both directions is when you actually start to get somewhere. I found with all of my mentors at Red Hat, their excitement towards talking with me and hearing what I have to say. And just something that I was constantly hearing about is the energy that the newer people bring in and the new ideas. You need both sides of it. Oh, okay. I see what she's saying. Yeah. So she's saying that it's not just about the mentee, the person who is mentored learning from this is getting very confusing. I need to... We need a cheat sheet. I need a cheat sheet. She's saying that a mentor can learn just as much from their mentee. Oh for sure. Right. I agree. I mean, in that relationship, it definitely goes both ways. The mentee is definitely learning from the mentor, but think about how much the mentor is learning from this person. So in Cali's case, think about it. She came from a non-tech background, maybe different than some of her counterparts. She didn't have that technical foundation and curriculum before she got to college. So she was learning on the fly. So having a mentor that could listen to her and empathize with her in that relationship, it probably made for such a great symbiotic relationship between the two of them. And I think she mentions that, that was a really good relationship. So both ways, for sure. It seems like a less valuable mentorship relationship is where the mentor is like I have all of this knowledge and experience. Let me bequeath that to you. Yes, exactly. And that's not how it works. Or let me make you into a miniature version of me. Oh, wow. I would put that on the bad side. Yes. Yeah. That's definitely not a win-win in the mentor-mentee relationship. I think that a lot of people approach mentorship from the dominant side being the mentor, the seasoned professional. Just as you said, Brent, kind of like, "I'm going to pass on my experience to you," kind of like passing some kind of ancient kind of knowledge or something. I think that's the prevailing, maybe it's a prevailing belief, but the ideal mentorship experience is insightful for both the person who's being mentored and also the person who's doing the mentoring. And what a gift too. I feel like that's another way of saying you belong here. It's another way of saying you have something to offer because you have just taught me something. Cali walked into a program like this with less of a foundation than the other people in her program. So it was important to see her for who she was and the things that she cared about. I had a lot of people who took chances on me because they knew I was passionate about my work and passionate just as a human being. And so I just think that's why I enjoy working in open source because it's so much about the people and that's the same that you can kind of get with mentorship. And your personal impact can go so much farther if you choose to invest in others. Kim, you have talked to a lot of people for this episode. What I want to know now is what you have learned. I think that mentorship should not be a kind of copy paste situation. I think that mentors should approach mentorship as a very nuanced kind of relationship with the person that they choose to interact with or they choose to mentor. Not all mentorships look alike and they shouldn't. All right. Can we try a challenge? Yeah. Sure. What's that? Here's what I want us to do: I want the three of us, and I'm also going to challenge the rest of the audience to do this as well, but we're going to start it, the three of us, we're going to try to find some new mentors. So here's my question, Angela. If you could have any mentor in the world, who would you want to be your mentor? Oh my gosh. If I could pick a mentor, it would have to be Cree Summer. Who is Cree Summer? She is a voice actress and I've been following her since she was on A Different World, a TV show many, many years ago. And she pivoted into voice acting. I would love to be a voice actor. That's my secret thing that I have going on in my head. So, I would love if I could be mentored by Cree Summer. That would be insane. What about you, Kim? I think that my dream mentor would be Missy Elliot, the hip hop artist and producer. Okay. Yes. Yes. She came from a very similar background as me. She's from the same state as me. And she has always been kind of irreverent to whatever is contemporary or in style. She kind of set so many different kind of standards and so many different trends. And I think that that's so strong and so cool. And she always puts out amazing work because of it. And that's who I would pick in a heartbeat. That's a good one. That is a good one. I love it. All right. So here's what we're going to do. We are going to shoot our shots. Are we going to do this? Are we making a pact? Yes we are. Yes we are. Wait, you didn't tell us; who would be your mentor? Oh. So I think that I want Jad Abumrad to be my mentor. He hosts this show and created a show called Radiolab. And I think that he is brilliant. Nice. All right. All right. That's awesome. Let's do this. So we're going to make a pact and listeners, we want you to do this as well. Even if you don't even think it's possible, tag them on Twitter. Shoot your shot. Let's make this happen. Yes. I love it. That's fantastic. I'm so excited. I know. And that does it for this episode of Compiler. Today's episode was produced by Kim Huang and Caroline Creaghead. Victoria Lawton is the mentor of our dreams. Our audio engineer is Kristie Chan. She was helped on this episode by Elisabeth Hart. Special thanks to Shawn Cole. Our theme song was composed by Mary Ancheta. A big thank you to our guests: Hugh Brock, Oindrilla Chatterjee, Hema Veeradhi and Cali Dolfi. Another big thanks to Boston University for their help with this episode. If you want to know more about how Red Hat works with universities, check out research.redhat.com. Our audio team includes Leigh Day, Laura Barnes, Claire Allison, Nick Burns, Aaron Williamson, Karen King, Boo Boo Howse, Rachel Ertel, Mike Compton, Ocean Matthews, and Laura Walters. If you like the show, please follow for future episodes and tell your friends about it. That is the best way to help our show. Angela, you said you wanted to be a voice actor one day. Would you read the last line in your best cartoon voice? Sure. Why not? Until next time, see you soon! Angela, hats off. You can't see me, but I am standing and I'm applauding. Yes. Wow. That was funny.

More about professional development

Keeping up with changes in technology requires training and and engagement with learning opportunities—either in a traditional setting, or individually.

블로그 게시물

Friday Five — August 15, 2025 | Red Hat

2025년 8월 15일  |  Red Hat Corporate Communications

...

블로그 게시물

Developing a standard AI OS: Unlocking production-grade AI at enterprise scale

2025년 8월 14일  |  Brian Stevens

...

AI inference

About the show

Compiler

Do you want to stay on top of tech, but find you’re short on time? Compiler presents perspectives, topics, and insights from the industry—free from jargon and judgment. We want to discover where technology is headed beyond the headlines, and create a place for new IT professionals to learn, grow, and thrive. If you are enjoying the show, let us know, and use #CompilerPodcast to share our episodes.