My Technical Mentorship Experience – Senior to Principal Path

Sharon Xie

Author: Sharon Xie – Principal Software Engineer

Impactful Engineer shares the stories and journeys of women and men who are making a significant impact in the software industry. The purpose of Impactful Engineer is to inspire young software engineers to see that there are many paths they can take to move forward in their careers and grow their impact wherever they work.

Technical mentorship usually means the mentoring relationship between two engineers – one engineer (mentee) receives advice, guidance, or learning from a more experienced engineer (mentor). This relationship is often informal/implicit. For example, when a buddy (mentor) is assigned to an engineer (mentee), who newly joins a team to help him/her on board. I also see code/design review as a form of informal technical mentorship. Formal/explicit technical mentorship is less common based on my experience. However, I’ve found it very useful for my career development as a mentee.  As a result of an explicit mentoring relationship, I was promoted from Senior Software Engineer to Principal Software Engineer. In this blog, I’d like to share how I set up my mentorship with Joey Echeverria,  previously a Senior Principal Software Engineer at Splunk. I hope my story can provide some ideas to start formal mentorships.

Seeking a Mentor

I started considering having a mentor when I switched from a front-end engineer to a platform engineer working on Data Stream Processor (DSP) at Splunk. My primary goal was to speed up my learning on the platform. The secondary goal is to get advice on how to get to the Principal level (P5) from the Senior level (P4).

To find the mentor, I searched my network to see who was doing well on the goals that I wanted to achieve. It was pretty easy for me to identify Joey to be the one at that time because

  • He was the architect of DSP. He was also an early engineer who worked on the platform. He knows the platform inside out.
  • He was at the Senior Principal (P6) level. He interacted with a big group of engineers at various levels daily. I think he should have some good ideas about what it takes a Senior Engineer to get to the Principal level.
  • Most importantly, I’ve seen him in action, and I wanted to become Joey.

Initiating the Mentorship

I talked to my manager Vidya at that time about having Joey mentor me. I asked her to talk to Joey about this idea first because I wasn’t sure if Joey is open to a formal mentorship. He was busy and important, and I didn’t want to add more workload to him if it’s hard for him to commit to the mentorship.

He said “yes!” and my journey started.

First 1 on 1

The first 1 on 1 is more or less like a two-way interview. Both of you should feel comfortable talking to each other and working on the goals together.

I used the first 1 on 1 to address my questions and concerns. For example, I asked Joey how he felt when my manager asked him to be my mentor. It was my way to figure out if he believes in mentorship. I further asked Joey to tell me his interpretations of engineers at different levels. It confirmed that he knew how promotion works. I was very nervous then as I was still new to the team and was afraid of judgment. I could see that Joey made extra effort to make me feel comfortable talking to him.

On the other hand, Joey asked about my short-term and long-term goals and what I thought was needed to achieve those goals. He asked me how he could help me too.

In this 1 on 1, we also agreed on the following structure for recurring meetings:

  • Weekly 30min 1-1s
  • Focus on: expanding my platform/system knowledge and technical leadership skills.
  • Adjust the schedule and structure if needed

Recurring Meetings

We adhered to the weekly 1 on 1s with very few exceptions. Joey always offered to reschedule if he couldn’t make it.

On my side, I was the one who set the topics for our 1 on 1s. As a mentee, I tried not to waste Joey’s time so I always go into the meeting prepared. This weekly meeting pushed me to review my work regularly, which was a pleasant side effect. Things we usually talk about:

  • Code / design reviews
  • Deep dive a specific part of the system or codebase
  • I talked through challenges (technical, communication, collaboration, etc) I was facing, and Joey shared his perspectives/suggestions.
  • I went over something I did (eg: an incident response) and got Joey’s advice on how I could have done better.

Joey did an awesome job being a mentor. He was very patient in listening and creating a safe space for me to talk. Gradually, I was very open to talking about my vulnerabilities and frustrations. He never criticized my work. Instead, he asked me why I did it my way and helped me discover the room for improvement myself. If he had different proposals, he always described how he approached the problem and why he approached it that way. The key to getting to the Principal level is technical leadership. However, it was very vague for me in the beginning. Joey guided me to discover what it means and how to achieve it in a very concrete way.

Beyond Mentorship

Joey actively used his influence to provide opportunities for me to push the boundary of my comfort zone and demonstrate my abilities. He nominated me to take on bigger projects; He mentioned my name in meetings I was not in; He pointed people to ask me questions, etc.

In other words, Joey became my sponsor.

Other Resources

 

Gunawan Herri, VP of Engineering @ DomainTools

Gunawan Herri Impactful Engineer

Gunawan Herri, VP of Engineering @ DomainTools

Gunawan HerriImpactful Engineer shares the stories and journeys of women and men who are making a significant impact in the software industry. The purpose of Impactful Engineer is to inspire young software engineers to see that there are many paths they can take to move forward in their careers and grow their impact wherever they work.

[beautifulquote align=”full” cite=””]1. Find a good mentor. Learn continuously.
2. Never give up and BE nice.
3. Wake up early and try to do more stuff in the morning.[/beautifulquote]

LinkedIn Profile: @gunawanherri

Interview By Tony Tam | Join impactfulengineer on Slack to connect w/engineers.

I remember Herri as a key connector for our team of 7 engineers in the 1996 to 1999 time frame when we worked at Silicon Graphics, Inc. (SGI).  We were building X11 Motif tools that shipped with every SGI machine to collect customer warranty information, diagnostic data, electronic call logging, patch tools and customer data management. 

During lunches with the team, he always pushed us to try out different ideas.  I remember him leading technical discussions, reaching out to the team to offer help and a very positive force to have on our team.  He showed genuine interest in knowing and caring about his teammates both in their personal lives and life at work.  I’m not surprised at all to see him in a leadership role now and his investment in mentoring.

Questions & Answers

Q: How do you know Tony?
A: I know Tony through our tenure together at Silicon Graphics, Inc. He and I are colleague as software engineers at that time.

Q: Where do you currently work and what your current role is within the company? What scope of impact do you have within your organization?

A: I just left my job as CIO and VP of Technology at a mid-size company. Before that, I was CTO and SVP of Technology.

In the last three jobs, I was a member of Executive Leadership Team. I managed the whole engineering team and full control of day-to-day operations from budget, architecture and hiring/firing decision.

Q: When did you get started with computers? Do you remember your first computer? Could you give us a history of how you got to where you are today?

A: I was always interested in the STEM (Science, Technology, Engineering, and Mathematics) subjects and computer since middle school. My home town in Indonesia happen to be the central place for oil and gas companies (Chevron-Texaco). They have computers and mainframes and I happened to know a mentor who was kind enough to teach me about computer related matter. I started my career as software engineer in Silicon Valley and follow the path of technical lead, engineering manager. I then took my MBA and pursue some product (program) management type of work at Microsoft before joining a few mid-size companies as their executives.

Q: What does a typical day at work look like for you and how do you stay on top of everything that is asked of you?

A: I try to keep a comprehensive to-do list for myself and encourage my direct reports to do the same thing for our 1-on-1. Much of my time is consumed either by fire-fighting, planning or strategizing with my fellow Engineer Leadership Team or direct-reports.

Q: What computer language have you used at work in the last 10 years, and which language do you use for personal projects? If they are different languages, could you explain why?

A: In the same last 10 years, I’d say Java, Ruby on Rails (RoR), PHP. Many developers and companies seem to enjoy RoR nowadays. There are other languages sprinkled in there such as Python for Machine Learning (ML) related deliverables.

Q: What website, tools, apps do you use on a daily basis help you be more productive and more informed?

A: Collaboration tools in general, such as Atlassian Jira/Confluence. Communication tools such as Flowdock, Slack, or Skype. I also use any tool to keep track of my personal to-do list.

Q: Who was the best manager you’ve ever had and why?

A: One of the best managers that I have had is Dirk Dougherty at Commerce One. He’s very down-to-earth, supportive, positive-reinforcement (rather than stick), ready to provide mentorship. I try to emulate this management style whenever I go, particularly on the mentorship.

Q: Who has helped / mentored you and has made the biggest impact on your career? What did you learn from this person that you still carry with you to this day?

Aside from Dirk Dougherty at Commerce One (in an earlier answer), I also had a great mentor named On Lee (he used to be a director at Microsoft). I learn to connect with each team member individually. Make each of them successful and mentor them (many times it’s not technical issue at all but personal, such as I’ve done engineering and I want to try management. Can you guide me how to get there?)

Another lesson is to keep up with knowledge and technology and honestly I’m not doing well on that front at all…

Q: Which team was the best team you were on and why?

A: I had a really good time with my team at Commerce One. We’re tight-knit team. We went through very good and very bad together but we also do it as a team. Team members just work together for a common purpose. Love it.

Q: Which project are you most proud of and why?

A: Again, at Commerce One where we needed to deliver enterprise-quality B2B platform. We went through tight deadlines and many distractions, but we did make it.

Q: How do you prepare for meetings and how do you successfully run meetings? What patterns of behavior do you wish junior engineers would do more of? Less of during, before and after meetings?

A: A few things I try to do for my meeting:

  • Make it short, 30 minutes if possible. Does it need a meeting or an e-mail will suffice?
  • Make sure the invitees are appropriate
  • Make sure that the agenda and goal are clear and set
  • Make sure we have some action items out of it

Q: If a software engineer came to you and asked for advice on increasing their impact and getting promoted, what would you say to them?

A: It’s all about solving business problems by providing values. Our values as engineers are to use technology to solve those business problems.

Q: What advice would you give to a smart, driven engineer zero to three years out of college? What advice should they ignore?

A: Learn about how to collaborate, learn how to understand business problems itself. Ignore advice that you MUST use technology x, y. z. Those technologies change all the time. Always use the right tools to solve the problems.

Q: What blogs, newsletters, GitHub repos, podcasts, conferences, and websites do you regularly read/attend in order to stay ahead of the changing landscape?

A: I personally use TechCrunch and Geekwire. I know my team used Stackoverflow quite a bit. I found Amazon ReInvent conference to be useful.

Q: Thinking back on your career, what do you think has helped you personally grow your impact in the various stages of your career?

[beautifulquote align=”full” cite=””]1. Find a good mentor. Learn continuously.[/beautifulquote]

Q: Do you have any advice on how to effectively mentor someone through their career? What does a successful mentor / mentee relationship look like?

A: Mentor should try to understand what motivates the mentee. Ask hard questions of what they really want. After identifying of what they need, connect them with someone who can help them or guide them of how to acquire those skillsets.

Q: Is there anything that hasn’t been mentioned that you think is relevant to helping other engineers increase their impact? If so, what?

A: The ability to work with other disciplines are very important. Always put customers need ahead of engineering complexity.

The following questions are from Tim Ferriss’ book Tribe Of Mentors.

Q: In the last 5 years, have you adopted any habits or rituals that make you more impactful?

A: I like to read and try to be curious.

Q: If you could have a gigantic billboard anywhere with anything on it — metaphorically speaking, getting a message out to millions or billions — what would it say and why? It could be a few words or a paragraph. (If helpful, it can be someone else’s quote: Are there any quotes you think of often or live your life by?)

[beautifulquote align=”full” cite=””]A: Never give up and BE nice.[/beautifulquote]

Q: What is one of the best or most worthwhile investments you’ve ever made? (Could be an investment of money, time, energy, etc.)

A: I always feel the time I invest for my mentees worth every single penny and second!

Q: In the last five years, what new belief, behavior, or habit has most improved your life?

[beautifulquote align=”full” cite=””]A: Wake up early and try to do more stuff in the morning.[/beautifulquote]

Q: In the last five years, what have you become better at saying no to (distractions, invitations, etc.)? What new realizations and/or approaches helped? Any other tips?

A: I try to separate needs from wants.

Q: When you feel overwhelmed or unfocused, or have lost your focus temporarily, what do you do? (If helpful: What questions do you ask yourself?)

A: Prioritize my work.  

Q:  What is the book (or books) you’ve given most as a gift, and why? Or what are one to three books that have greatly influenced your life?

A: My goodness. I always feel like my first C reference book is a classic. Short and sweet.  Also  Good to Great by Jim Collins.

Q: Who else should I interview?

A: Muljadi Sulistio and Pamela Chan and Sue Liu (Tony & Herri worked with them in SGI)

Q: And finally, the question I didn’t ask you. What lesson learned from your past experience that you either will emphasis/encourage or avoid?

A: For engineers who loves new shiny toys and new technology, make sure you understand how new approach solve business problems and don’t use new tech just because it’s “hot”. Open your mind about various technology stacks (both open source and proprietary such as Microsoft).

Get close to your customer base as close as possible. Ask your PM to join them during customer calls. Talk to customer support folks about common issues that real customers are facing. When you implement a feature, make sure you understand why (such as how the result from this module is going to be consumed? Which other module will consume it? What is the end-goal?).

Q: Was there any particular turning point or decision in your career that changed the trajectory of your career path? Tell us more about that.

A: I decided to take MBA and do some product management in addition to just engineering track. IMHO (In my humble opinion), the blend between business/strategy and technical skills help me in pursuing a C-level career. Doing some technical program management is a great litmus test that an engineer can do if they want to taste the business side.

—–

This interview was conducted with Gunawan Herri in January 2018.   The questions were answered via email and clarified via LinkedIn messenger and final editorial cleanup by Hunter S.

Raji Rajagopalan – Partner Software Engineering Manager at Microsoft

Raji Rajagopalan
Partner Software Engineering Manager at Microsoft

raji circle

Impactful Engineer shares the stories and journeys of women and men who are making significant impact in the software industry. The purpose of Impactful Engineer is to inspire young software engineers to see that there are many paths they can take to move forward in their careers and grow their impact wherever they work.

Profile: http://rajiraj.com/
https://www.linkedin.com/in/rajiraj/

Interviewed by Sharon Xie, Tony Tam,
Kristal Curtis
Editing by Robin Pille


[beautifulquote align=”full” cite=””]You should talk about your work in terms of the value that it is bringing to the people that you are serving.[/beautifulquote]

Tony: Can you briefly tell us about where you currently work and how your journey led you to where you are today?

Raji: I am a partner engineering manager at Microsoft. I have been working at Microsoft for 12 plus years now. Before then, I got my bachelor’s in computer science in India. I did my master’s in computer science in Canada. I then worked for a company called Schneider Electric for three years. So that’s sort of my journey going back. 

Tony: Can you tell us more about your scope of impact within your organization?

Raji: My team’s mission is to help our IT professional customers be the best at their jobs on Windows and Office Platforms. That’s we think about, what we obsess about day in and day out. What do I specifically do?

My role is a combination of a venture capitalist, a therapist or coach, and a culture curator. Here’s what I mean by that.

The first part of my role is like a venture capitalist.  I look for the best ideas possible, those great ideas that are going to be successful, and fund those ideas. And to me, in my day-to-day, I’m looking for ideas coming from my team, ideas coming from myself, ideas coming from my partners and from my customers. And I need to make the decision: is this a good idea for the business? Is it something that I want to fund with people? Is this something that I want to work on, something I want my team to deliver on? So, that is a big portion of what I do. Setting the strategy for the company, finding the best ideas, and grooming those best ideas.

The second part of my role is sort of like a coach. A lot of my time is spent on people: growing people, mentoring people, hiring the best people, making sure that these people are happy, retaining them and making them be the best at their jobs. So that’s like being a coach: I talk to them, I hear them. What are the challenges in their jobs? How can I make them better? Are they being the best human being they could possibly be, both from a personal perspective and a professional perspective.

The last part of my role is more the culture curator. I am looking for the cultural aspects, the values I want to nurture in my team, the culture I want to establish. Things about how we are inclusive, about how we’re all growing up to be emotional intelligent human beings and respectful of each other, providing each other an opportunity to grow and be supportive of each other so that we have the right kind of culture I want to set for my team. So that is my impact within the company.

raji-1.jpegTony: In this journey, where do you think you had the most significant growth and learning experience?

Raji: I learned different things in different stages in my career because at every single point in my career, I intentionally chose to accomplish something that I wanted to be known for. When I was an entry level IC, I wanted to be the champion of engineering excellence within my organization. I chose it because I was passionate about engineering excellence.I knew that there was a gap in my team and I intentionally chose to become the engineering excellence champion. I didn’t think of that at the time as branding. I just wanted to do this. And I grew in that respect, because it was not like I was born an engineering excellence champion. I only knew some things. But I learned a lot about how to drive and influence people towards culture changes, like doing test-driven development or unit tests, and code reviews.

But then, when I became a senior engineer I had this tendency to land myself projects that were screwed up or not on track. Either the code needed to be refactored or, you know, there was something messed up about the project and the people were like “Oh my God, this is the worst project ever.” And I would pick that project intentionally because at that time I wanted to change what I was known for. If a project was screwed up, I wanted people to say “Pick up the phone, call Raji.” So I kind of landed myself those projects and again there was a lot of learning there. It’s not just that I got to be associated with these projects. This was my brand, but it was more. I learned so much from working on these projects that other people had given up on because it was up to me to figure out how to go about fixing them.

Then I became a lead and there was a lot of learning there. My training was all in computer science. No one really teaches you people management and what motivates people, what makes people tick and how to communicate with people in a way where they understand what’s going on and get motivated. When I became a lead, there was a lot of learning in that regard. How to manage people, basic behavioral science, what drives people, and so on. And also how you work with people who are difficult to work with, including managing people out.

And then strategy was what I learned in the next stage of my career. Now I’m a development manager. I have to pick projects that have promise and that are going to make money for the company, right? Strategy was something that I didn’t know how to do before. It’s a journey of learning how to be more strategically savvy.

[beautifulquote align=”full” cite=””]When someone is interrupting me, I don’t think of it as, “Hey they interrupted me because I am a woman.” Instead, I internalize that and say “Oh I need to speak up more,” or “I need to make this point more clearly because it didn’t actually land.”[/beautifulquote]

Sharon: Can you tell us why you decided to make the move from the IC track to the manager track?

Raji: I’m always interested in trying new things. Before I started hiking and running marathons I did not know if I was going to be successful at it. But it interested me. It seemed like there was something that I could learn from that. Maybe I’ll be successful, maybe I’ll like it. In my career, I followed a similar logic. There was an opportunity that came up to lead people. I didn’t know if I was going like it or be good at it, but I thought, What’s the worst that can happen? Maybe I will not like it, maybe I’ll fail. I can always come back and be an IC.” I knew that my skills were not going to go away if I became a manager. So I took a leap and I raised my hand and I said, “I want this opportunity, can I become a lead?” and I ended up liking it. In another life, I’d probably be a behavioral scientist because I like learning about people. I like learning about why people do certain things and what causes people to not do things a certain way and so on. So I like that aspect of psychology and human behavior and being a leader of people gives you that opportunity.

Sharon: You say you like to try new things, but I see that you’ve been at Microsoft for quite a while. What keeps you there and what motivates you every day?

Raji: So there are a few things I consider to be important when I make a decision on whether to be in a team or not. Keep in mind that Microsoft is a huge company with lots of different varieties of technologies, different teams, a lot of people that you can work with. So, very often I have this decision point of changing my team.

For example, I want to go from working in Azure to working in Windows. Within Windows, I want to go from working on the client side writing kernel code to writing service code, Windows update code. Very often you have to make these decisions, so I give them a lot of thought. I like being intentional about my decisions.

What keeps me in a team or makes me want to change teams? I look for four things.

Number one: I want to have really good people that I work with. People that I love, managers above me that I really like and enjoy and respect. People that are working with me that I respect and love. People who work for me that I absolutely admire. So, people are a very important factor. I want to make my decision based on that.

Second, I want to work on interesting projects that have customer impact and business value. I think that also is important for your career growth. Obviously, there are lots of projects you can work on. You can work with interesting technologies and you can build cool tools, but, it’s important to pick things to work on that are going to have business value and customer value. At the end of the day, you want to have customers, humans that are going to use what you’re building. So that’s important.

The third thing is that I want to constantly be learning. I get excited every day if I come in and I get to learn something great. Every stage of my career has been an immense learning journey for me.

Lastly, I want to have career growth. I always want to feel like my career is not stagnant  and that it’s obvious that people are recognizing what I bring to the table.

Microsoft has given me all four of these factors. These are the biggest reasons I stayed within the company. The mission of the company is to “empower every single person and organization on the planet.” That really really resonates with my core value as an individual. At Microsoft, we do a lot of things around the world to make sure that we are empowering people. And the people that I’ve worked with, the ideas that I come across on a day-to-day basis, have made my life a lot richer. Every once a while I think if I didn’t work in technology, if I were at home doing something else like writing, because I love to write, then I would be at home by myself, and I would miss out on opportunities to meet and understand people that are so smart and have so many bright ideas.

[beautifulquote align=”full” cite=””]Even if you feel you might not be up to a particular opportunity, if you raise your hand and give yourself a chance, you might fumble but you will learn.[/beautifulquote]

Sharon: What has your experience been like as a woman in tech?

Raji: My experience has been somewhat unique, and I’m puzzled over that every once a while when I talk to people that I coach. See, I come from India and in India, I was never told that I was not good at math. I hear that here a lot of women enter into technology with that sort of social messaging already given to them, which was not the message for me. We have other problems in India, but that was not the problem that I faced. In fact, people were constantly encouraging me, “Hey, you know, you’re good at math” and so it never occurred to me that I could not be a computer science engineer. I mean I did not choose to be a computer engineer. That was not my first choice. I wanted to be a doctor. Once I chose my career, I did not think that I would not be a good tech person because I was a woman. Instead, I had challenges with communication.

English is not my first language, there was a point in my life that I was new in this country, I would not pick up the phone because I was worried that I wouldn’t understand what they are saying because my own English was so broken. This was 20 years ago. My English was so broken that when I first came  to California and the phone would ring, I would think “Oh my God, the phone is ringing and I cannot pick up the phone because they will speak English and they will speak so fast.” I wouldn’t understand what they were saying.

I had to work constantly to overcome that, but I never felt like the men that I was working with were deliberately disrespecting me because I was a woman. Perhaps I just had the good fortune of working with really awesome men in my career, but more likely, it is that I tend to reframe my problems. When someone is interrupting me, I don’t think of it as, “Hey they interrupted me because I am a woman.” Instead, I internalize that and say “Oh I need to speak up more,” or “I need to make this point more clearly because it didn’t actually land.” There are some unique aspects to my own experience as a woman in tech, and so I’m constantly aware of the fact that you cannot take an isolated experience and generalize it.

But I have the fortune of working with many women and many quiet people, and that’s where I derive my advice for folks that ask me for this kind of advice.

Sharon: What advice do you have for women in the tech industry?

Raji: I wrote a blog post about this topic after my conversation with the woman engineer whom I mentor. In my mind, the advice for a woman in tech is not very different than the advice that I give to men in tech. It’s more about personalities than even gender. I meet lots of men who are quiet and introverted and they don’t know how to get across their point, and they get interrupted all the time, which is also a challenge that I hear from a lot of the women engineers that I work with. “How do I work with people who are constantly cutting me off? Who don’t recognize even my presence in the room?”

My advice is, number one, like I said before, pick the project that is going to help you be successful. You have to be passionate about what you work on and you have to make sure that the project that you’re working on is not some grunt project, but it is going to deliver customer value and business value.

And when an opportunity comes, like it did for me with my switch from IC to a lead, take it and give yourself a chance. Remember, I actually did not know whether I was going to be a good lead.

I did not know if people would respect me. But I raised my hand still. I strongly believe in that. Even if you feel you might not be up to a particular opportunity, if you raise your hand and give yourself a chance, you might fumble but you will learn. For a lot of women, the first barrier in their career is confidence. This is true for some men as well. You have to have confidence in yourself. Granted, a lot of people placed confidence in me, starting with my own dad, and also my mentors and all the people that helped me grow in my career. But first and foremost you need to have confidence in yourself. You need to know that you’re going to figure it out. Things may not be so crystal clear right now, but you’ll learn and you’ll figure it out. So, I think the first thing is pick projects that you are passionate about and that have business value, and then raise your hand and volunteer for leadership roles on projects like that.

And the second thing is actually own it on your turf every single day. Do a very good job at what you are doing. You have to be thorough about it. You have to understand what you are doing and you have to really deliver successfully for your team. And lastly, which is a challenge for a lot of women and a lot of introverted quiet people, is to talk about what you’re doing. Talk about it, even if you’re shy. You don’t have to talk about “Sharon, me, I did this.” Talk about your work in terms of the value that it is bringing to the people that you are serving. The work that I do, like I said before, brings a lot of value to IT professionals. It helps them understand their own enterprises and it helps them be the best at their jobs. So I always focus on telling the customer’s story rather than my own story. But you have to tell the story of what you’re building, whether it’s from a customer’s perspective or something else. If you’re just quiet and don’t talk about your team, your people, and yourself, then no one is going to do that for you. So that’s my advice for how you can be successful as a woman in tech.

[beautifulquote align=”full” cite=””]I learned different things in different stages in my career because at every single point in my career I intentionally chose something that I wanted to be known for. [/beautifulquote]

Tony: Do you have any advice for talking about your work, whether it be an elevator pitch, hallway conversations, writing, or giving formal talks? What advice do you have for how to do this well?  

Raji: Yes. I think the key thing here is that whatever the medium of your message is, whether you’re writing, speaking, or just giving someone a hallway or elevator pitch, you have to be clear about what the core of your message is going to be. Because one of the challenges I see is that people ramble on and their message gets lost. So, you have to ask yourself “What is the core of the message that I want to convey to this person?” But then, it’s not just the message itself, you have to understand the person that you’re talking to. What is the currency of that person? Is this person a V.P., is this person a customer, is this person a reporter, is this person an engineer that you want to attract and recruit in your team, or is this a fellow engineer? For every single person you want to deliver that core message in a slightly different way, the angle will have to be different. It’s not about changing your message, it’s more about how to resonate with that person, because everybody sees the world through their own unique lens. And so you have to understand that a V.P. will look at your message from the business perspective, versus an engineer who is probably looking at it from a technical perspective. So how you’re conveying what you’re working on should resonate with the person that is your audience.

Tony: Do you have any advice for getting your message through when people are talking over each other in a meeting?

Raji: I saw someone do this recently in a big meeting that I attended. I’ll will give this example and then I’ll circle back to some of the concrete tips that I have. So, this was a big meeting, thirty people, or something like that. There was a mix of senior people and junior people, and people were talking over each other. At one point, this woman just stood up and everyone just looked at her. She stood and then she made a point and she made it very clearly, and then she said “Now we are going to listen to this person, and then we are going to move on.” So, she did two things there. She made her presence known just by the act of physically standing up. People noticed that. Wow, what is she doing? Why is she standing up? Once she had people’s attention she landed her point but she also did one more thing which I really appreciated. She said, this person wants to say something. Let’s hear him. Let’s hear what he’s trying to say and let’s move to the next topic. So she kind of set some of the ground rules there, that when someone is trying to talk you need to give them the chance to talk. I think the ground rules are so important. When you are driving a meeting or even if you are a participant in a meeting, I think it’s useful for you to set the ground rules. Like, we are meant to listen to each other. If someone feels that they are not being heard they are going to raise their hand or stand up or whatever. Raising your hands helps sometimes. But I think setting the ground rules is important because people are people. They don’t intend to be rude, just in the heat of things they run on, because they want to be heard themselves.

So it’s human nature. So at that point it makes sense to call it out. “It looks like things are getting heated. It looks like there’s lots of voices that are getting drowned out in the room. So let’s take a step back and reset this meeting.” So be aware of what’s going on in the room and see who is getting heated up and step in to calm the temperature down.

One thing to remember is projecting your voice. A lot of people have soft voices. Others are not even aware that a soft-spoken person is trying to say something. You might not even know you have a quiet voice. I spoke at a get-together recently. We were celebrating a milestone achieved by one of our directors. I spoke and didn’t have a mic. I always believe that my voice will carry through. I thought that I had a loud voice, but it turned out I did not. I was talking to the crowd and I was thanking this person for doing an amazing job. And then I see my friend standing in front of me motioning with her hands to say “Raise your voice, raise your voice.” And I was very thankful she gave me that cue because I did not know that people couldn’t hear me. So I think projecting your voice helps.

One of my colleagues gave me this advice recently: Even if you don’t say a lot in the meeting and you’re not the loudest voice in the room, how you say something matters. If you believe in what you’re saying, make sure that comes across. It’s important not to sound tentative, like “Maybe I know this, maybe I don’t know this.” This advice applies when you really believe something, obviously. If you don’t believe in it then you have to make that clear, because you don’t want people to take away the wrong message. When you believe something it’s important to sound authoritative and have conviction in what you say.

[beautifulquote align=”full” cite=””]When you pitch an idea to senior people, show them that you’ve thought it through and it’s going to make the business successful or make them as individuals successful. [/beautifulquote]

Tony: How can you best influence decisions when people ultimately making decisions are more senior than you are? For example, what if you are trying to come up with a new design direction and trying to influence somebody two levels above you?

Raji: Think about it from the senior person’s perspective. Put yourself in the shoes of the senior person. Obviously, most people working for companies want to be successful. And they can be successful if they make the best decisions possible. There are obvious biases and things that are screwed up every once in a while. Most of the time, people want to pick decisions, designs, and technologies that are going to make them successful as well. What they are looking for, a senior person, is some level of conviction and credibility in what you are proposing. When you pitch an idea to senior people, show them that you’ve thought it through and it’s going to make the business successful or make them as individuals successful.

So your challenge then is to prove or show that you have thought through this and that your idea is going to give this person the best chance of success. And you can do this in many ways. You can just have one-on-ones with people. Find the influencers of the person you need to convince and have one-on-ones with them to say “Hey, here is my idea and this is why I think it is going to be successful.” Or, have a one-on-one with the person you’re trying to influence. But prototyping, having a little bit of actual validation that something is working, also helps. You have a design idea, you’re thinking about how to use a cool tool, or whatever. If you do a little bit of a prototype and show it to that person, when someone can concretely see something in action there’s going to be more belief in the idea itself.

You can also write up a white paper or some kind of document to pitch your idea, and do prototypes, but ultimately you have to have talk about it.

[beautifulquote align=”full” cite=””]If you want to progress in your career, you have to make sure that people know you, and not just the people you work with on a day-to-day basis. [/beautifulquote]

Tony: Have you seen a situation where something that you were doing or that other people were doing was overshadowing your impact?

Raji: I think the one thing that people with an engineering background tend to overlook is making sure that people know you. This is actually true in my own experience. When I became a manager of managers, I walked into my manager’s office for my first one-on-one thinking we should talk about how I will run the team. Then he sits me down he tells me “Raji, I’ve heard so much about you. You were technically kickass. Every single person I’ve talked to talks about how you’ve run these difficult projects and you come across amazingly from an engineering point of view . But outside of this little world of our team, people don’t know you. If you want to progress in your career, you have to make sure that people know you, and not just the people you work with on a day-to-day basis. You have to be a known commodity inside Microsoft and externally as well.” I did not spend a lot of time early on in my career explicitly for relationship building. I would sit in my office, finish my features, finish my bug fixes, write my tests, and so on. I would work with my seven people that were on my team and we had a very good relationship. We knew each other. We were friends and all that. But then I did not spend a lot of time going out and seeking out people that were going to be influential. I realized, based on this conversation with my new manager, that this was not just for my career, because that’s in a way secondary, but if I wanted to advance my business in a certain way, I could not do it on my own. If I had an idea and I wanted to pitch the idea and I wanted the best backing for the idea, I wanted to make sure that there were people that know me and would trust me. And so then I started actually very intentionally and consciously figuring out who are the people I need to go and start understanding more. Have coffees, have lunches, and meetings and so on to understand what they’re doing, first of all. How can their organization help me and how can my team help them. How can I personally help them. So, figure out who are the people that you need to build relationships with. Even if you do an amazing job, at some point you want to know people that are not in your immediate sphere. Your close friends should not be the only ones who know about you and can speak well about you. You want more people to speak well of the work that you are doing.

It’s very uncomfortable. I know how uncomfortable it is. I’m by nature not a very extroverted person but I know a lot of times you just have to put yourself outside the comfort zone and go seek out these relationships. At the end of the day, I have come to enjoy these relationships that I’ve built over over time. I think that is one thing that we cannot neglect doing.

[beautifulquote align=”full” cite=””]For me now, in this stage of my career, my mission is making a difference in other people’s lives. [/beautifulquote]

Tony: What question did I not ask you I should have asked?

Raji: What do I want out of my career?

Raji: If you were a business, then you have to do a lot of planning. You sit down and think about as an organization, why do we exist? What is the vision? What is the mission for this organization? What are the cultural values you want this organization to have? We should do the same thing for ourselves. Ask yourself: “Why do I exist? What is my mission in life?” And it can be different things at different points in life. I have done this many times, and my answers have been different in different times. My mission ended up evolving. For me now, in this stage of my career, my mission is making a difference in other people’s lives. I think it’s not about just making a living anymore. I really, really, really want to make a difference in other people’s lives. I want to make sure that it’s not just me but I lift other people to the top as well. So I think that’s one thing that I really want to nail. Everybody should think what they want to do. What is it about at this stage in your life: is it about making a buck? Perhaps it is. You still haven’t paid off your student loans? You still have things you need to take care of? From that perspective, it’s okay in this stage of your life to want to make a buck. But then, over time, constantly think about what do you want in this stage of your life and have that answer ready for yourself.

Tony: How far out do you project that mission? Do you plan five years, ten years out?

Raji: I usually do only two years. Because every couple of years there’s some kind of inflection in my own life where I have to rethink this. Even if there is no major inflection, from a life perspective, it is a good idea to check in. “Is this still what is me? Are these my core values? Do I still value freedom and integrity and being able to help others? Are these my core values at this point in my life?” Perhaps it’s different in two years, but we don’t know. I plan for a timeline for two years, but more often than not, I end up planning every year.

Tony: Awesome, thank you so much for your time.

Raji: By the way, it was so much fun doing this interview, and thanks for launching the interviews on Impactful Engineer. I really appreciate what you are doing and I want to see what the end product looks like. You already said that you have four interviews already done. This is awesome. I think there is a lot of potential in here and you should keep working on it.

Tony: Thank you so much. I know you’re pushing me to think bigger. Thank you.


Join Our Pre-released Reader Program

Leave feedback specific to interviews you have read and you will receive an invite from Tony to join our Slack channel to be part of our beta readers group for pre-released interviews and engage with other software engineers.

We ask our beta readers to give us feedback.

  1. What 1-3 things did you learn from the interviews?
  2. What 1-3 things are you going to follow and change your own behavior because of the interviews?
  3. What 1-3 things did you find not helpful at all, or changes to the interview (longer shorter), questions that should be removed or added

Fill out this Google Form to send feedback and join our beta reader program.  Feedback will be consolidated and sent back to Raji.


Personal blog

Read more of Raji’s personal blog posts and her wonderful photographs at https://rajigopal.weebly.com/-me.html

More Background Questions

Tony: Could you explain what a partner manager is?

Raji: A partner engineering manager is the last level before the executive level at Microsoft. As a partner manager I am a manager of managers. So I have leads under me who have ICs under them. Twelve years ago, I started at Microsoft at level 59, which is the entry level. I got promoted to SDE2, and then a senior engineer, and then principal engineer. Between when I was a senior and principal engineer, I became a lead, which means managing other engineers. So that was both an expansion of my role, moving to managing people from being an IC, but also a promotion in levels. Very recently actually, just last month, I was promoted to the partner level. It’s one of the biggest things that has happened to me in my life from a career perspective. Out of 95,000 people here at Microsoft, there are 113 women who are partners.

Rick Hawes : Former Architect Fellow, Yahoo

Rick Hawes
Former Architect Fellow at Yahoo

rick-hawes

Impactful Engineer shares the stories and journeys of women and men who are making significant impact in the software industry. The purpose of Impactful Engineer is to inspire young software engineers to see that there are many paths they can take to move forward in their careers and grow their impact wherever they work.

Profile: https://www.linkedin.com/in/rickhawes/
Interviewed by Tony Tam
Editing by Robin Pille
Reading Time: 12 minutes


[beautifulquote align=”full”]It’s not really the task that’s interesting, because any task can be made interesting. It’s how you approach the task.[/beautifulquote]

Tony Tam: Your current LinkedIn profile says you are on hiatus. Could you tell me why you decided to take a break and how are things going for you?  

Rick Hawes:  It’s great. It’s fantastic! It really comes back to the thing that I’ve struggled with the most throughout my career, which is life and career balance. My career started to consume everything and I became conscious of that. I struggled against it, but I choose work that’s interesting to me, that absorbs me. It’s just a natural thing that I get deeply involved in a problem. For me, it has been important to take a step back, be conscious of the need for balance, realize when I’m tired, and take the time to go off and do the things I want to do.

There’s also a pull factor. We all accumulate these lists: the things you want to do, places you want to go. I love traveling, my wife loves traveling, so we had a long list of places we wanted to visit. By taking that time to travel, you get perspective on your life and where you are in it. You need do it when you’re healthy, when you’re vigorous. I don’t think I would be able to climb Machu-Picchu if I waited 10, or 15 years. So it’s good to be conscious of that and just go do it.

TT: Given that perspective, would you have done it earlier?

RH: In fact I did do it earlier. I think maybe twenty years ago, I took a year off as well. I really wanted to spend time with my kids when they were young. That was a great decision as well.

TT: A good friend of mine and I have talked about how as men and engineers, we never take a break, we never take time off between jobs. We tried to imagine what it would mean to take a year off and just not work. But there are opportunity costs.

RH:  There is a cost. I mean, there’s no doubt about that. The opportunity cost is that your career doesn’t progress as fast, and being away for a long time makes it harder to get back into things, and so forth. Still, for me personally, it was worth it. And you can do it in other ways. You don’t have to take a whole year. You can take off some two-month stretches, and I don’t think there is any cost in that. If I really needed to be career-conscious, I would do it in two-month stretches.

TT: Good to hear. I hope one day I can make that decision as well. Let’s go back to the career side of the balance. Can you describe your journey in tech and what positions have had the greatest impact on you?

RH:  Okay. We’ll start with the beginning. I’m an electrical engineer. I was really into computer signal processing, and so that’s what I studied as an undergraduate. I got my first job in the plotter and printer division at Hewlett Packard. We were doing control software for the print heads. Since all the top engineers were given the assignments of designing these things, they needed somebody to write code. That’s how I got into software. It wasn’t a conscious decision that I made, but writing software was always very easy and natural and simple for me. As a career path, it turned out to be a good choice to try to do the things that no one else wanted to do.

TT: As a young person, you may often find that you are asked to do something that is not your top choice. Do you remember your mindset when you accepted that assignment?

RH: Well, of course there was that little voice that said, “Darn, I wanted to design that circuit right there.” But I always tried to fit in and do the right thing for the team, so I had that mindset. It worked out really well because I was quickly able to establish a place of expertise on that team. They would say “Hey, the software’s not working, let’s go ask Rick.” So, doing what is needed is important. I have done that again in other parts of my career. For example, there was a time when I really focused on build systems. Instead of the big fancy features, I worked on making the build system better.

[beautifulquote align=”full”]You start thinking about engineering as a system. Instead of just programming a simple Makefile, you can turn it into something much bigger and look at the solution to solve systemic problems.[/beautifulquote]

TT: Did you choose that because that had the biggest impact on the biggest number of people?

RH: No, because no one wanted to do it!

But of course I could see the impact as well. One of my mentors had this advice: “It’s not really the task that’s interesting, because any task can be made interesting. It’s how you approach the task”. That really stuck with me. The task of making build systems work was, at the time, not considered interesting. But then when you really start thinking about it at a meta level, you realize it’s really about code quality. You want to make a system that improves the quality of the code that has come into the system. You start thinking about 100 engineers checking in code at the same time. How do you make that work and maintain productivity? You start thinking about engineering as a system. Instead of just programming a simple Makefile, you can turn it into something much bigger and look at the solution to solve systemic problems.

I think those less popular tasks are really great opportunities, and as an engineer you will come across many of these in your career.

TT: That’s great! So from printers to build systems, what was next?

RH: So I went to Stanford and got my master’s degree paid for by HP. Hewlett Packet was a great company. I expected to stay there for 20-25 years. I was working in the PC division at the time that we partnered with Microsoft. I wrote Windows drivers and did a joint venture with Microsoft, so I got to know that Windows team pretty well. Microsoft then opened a location near me, and I could see that was going to be a good jump for me.

So, that’s how I ended up being the fourth engineer working on what would become Microsoft PowerPoint for Windows. Microsoft at that time was in third or fourth place in the market. It had MS-DOS, but there was something called a graphical interface that was being developed. All these things were still just coming out.

The company started to double in size and went on this exponential growth path for the next 10 to 15 years.  It’s a great thing to be on a rocket like that.

[beautifulquote align=”full”]There is a maxim that you always overestimate what you can do in a year and underestimate what you can do in 5 years. If you can string together accomplishments that build on each other, it is always surprising what a person or a team can achieve.[/beautifulquote]

TT: So, I imagine that being on a rocketship, along with your skills and attitude, helped your impact grow faster than other engineers.

RH: Microsoft at that time was a very immature company, so I wasn’t really thinking about growth paths, mentorship, impact, or any of those things. It was very much like a startup. “Let’s hire the smartest people and make the greatest products” — that was their mantra. At that time, really what I was trying to do was make the best product. The opportunity was very much there: Do a good job and you’ll get recognized and get more responsibility.

TT: But there must be more to it than just doing a good job. Why did you get further along than your peers?

RH: Well, there was the work: we had a schedule and we had a list of tasks and all this stuff to get done. So one way you could approach that would be to just go through and punch out the tasks. I was productive. I was pretty fast doing most tasks, but that wouldn’t distinguish you or get you the recognition. So what I did was notice that there was recency bias in the review cycle. So I made sure that two to three months before the review cycle, I did something spectacular. I did some big thing, completely off the task, as an extra project. I used my creativity.

TT: Okay. That’s a new thing I’ve never heard of before. Recency bias, you call it?

RH: Yeah, that’s my one hack: plan it out! Do more, and choose when to do it. Make sure that you do something special before the review cycle. Then, in the self evaluation, you can write about this extra thing that you did. That can really help you get recognized.

[beautifulquote align=”full”]The values that matter are the ones you hold to when no one is looking.[/beautifulquote]

TT: So how did your journey then lead you to Yahoo?

RH: I had a manager that I really worked very well with, and I ended up following that manager to Yahoo to take an excellent opportunity there, though it was quite a different role than what I had done before.

TT: That’s a big statement. Tell me more about what makes a manager so great that you would be willing to follow them to a new company.

RH:  I think what makes a great manager is a core set of values: Doing the right thing both for the company and for the person. A company can put a lot of pressure on managers to ignore the individual situations and blindly apply policies. For example, they might force a bell curve on performance reviews. Many managers will just throw their hands up and not try to fight for their people. But the manager I followed to Yahoo was able to understand each person as a human and understand how to factor in a personal problem where someone had to take leave, rather than just fit the bell curve. The values that matter are the ones you hold to when no one is looking.

TT: It seems like you care about managers who have integrity and great values and care about people as humans.

RH: It’s so important, and I know from my own experience that being a manager requires a different set of skills and ways of thinking.

I was asked to be a manager for the first time at Microsoft. I didn’t choose that role, I was pulled into it because the team needed a manager and they asked me to do it. That’s actually happened to be about half a dozen times. Even though I didn’t ask for that role, I’m really grateful for that experience. I feel that getting that experience as a manager can really help you even if you go back to being an IC.

I am an example that proves that you can zig zag between leading teams of up to 100 people and then going back to being an IC on that team. Maybe some people are naturally attracted to one role or the other, but I’d encourage everyone to try out both sides. You will definitely gain perspective as an IC by going into the manager track. I think I was more successful at Yahoo because I could relate so well to the managers: I understood their pressures, what they have to think about, what is important to them. It also makes you a better influencer.

TT: So how did your career and your influence evolve while you were at Yahoo?

RH: So, I joined Yahoo as an IC6, Principal Architect, where I had the role of a thought leader for the technology behind Yahoo Mail. At Yahoo, I was part of a team who all were expected to think like architects. There was a Chief Architect who acted as a mentor and helped me to build a different set of skills. At Yahoo it was like the whole history of the Internet was kept there in their old legacy code, so it was a great place to learn from examples about systems and to think about how larger systems work together and how to do long-term technical planning.

TT: So being an architect is more convincing, planning, thought leadership, influencing as opposed to coding.

RH: Yeah, and you’ll find that you can only write so much code, right? Some code can be really impactful, so I could see sticking with the code. At Yahoo, they made it clear that you would have more impact by working to influence large teams. For example, most companies divide into independent product or feature teams for innovation and execution speed. Decentralization has many benefits, but one possible downside is the development of independent data warehouses. Data fragmentation leads to many ills and missed opportunities. It’s the job the architect to see where teams should work independently and where they shouldn’t.

[beautifulquote align=”full”]The people who had most influence on me as mentors are the ones that demonstrated through their values and their work that they were top engineers.[/beautifulquote]

TT: Who are the people who have had the biggest impact on your career?

RH: The people that really most influenced me are the ones who set an example. There was one engineer mentor in particular who asked me questions that I still ask others to this date. Overall, the people who had most influence are the ones that demonstrated through their values and their work that they were top engineers, and those were informal mentorships where I really just observed what they did.

TT: You mentioned that you have a few questions you picked up from one of these mentors that you now ask the people that you mentor. What questions are those?

RH: One of the questions that particular mentor asked me was, “What’s your brand?” Back then, I didn’t understand that question. What he was asking was “How do people perceive you? What do they know that you stand for as an engineer? What are your core values?” Honestly, I had not given any thought to that. He helped me to see that if you are self-reflective about who you are and what you trying to project, then you should be able to answer that. I said at the time, “I have a lot of values!” He said “That’s your problem. You have all these values and they are all good, but you have to choose three of those to start projecting them, and that becomes your brand.” I found that exercise really helpful and I thanked him for that.

I still think about it now and continue to ask myself these questions too. For me, this exercise helped me discover the importance of saying no. Sometimes you have to say no to projects that are attractive because you have a limit. I’ve figured out my priorities, and that means I’m definitely going to say no in order to stick to those. For example, I took this hiatus. I know my priorities now are that I want to travel to these places. So, even though I do like working, I have said no a lot more, and I think that’s a good thing.

TT: What aspects of your career have surprised you the most?

RH: I guess the biggest surprise is when projects fail and companies fail. I go in expecting success, because I have an optimistic point of view. Most of my mistakes are due to the fact that although we were working on good ideas, they weren’t strong enough in the context that we were in.

I remember in particular a project that I worked on in the middle of my career that was a really massive product failure. I had worked really hard on this product and I was so enthusiastic about it, but with the economic situation in the industry at that time, it failed. It was a classic case of over-engineering: it turned out we were building a skyscraper and we really should have been building a two-story building.

Experiences like that one have given me perspective. Perhaps, the most import is that project failures also provide opportunities. You can learn from your mistakes and become wiser. You also have a chance to clarify what is important to you or your team. This knowledge is very powerful for execution as you go forward. Finally, you usually have a chance to try again and succeed. Once you succeed, you have a compelling story that can shape the culture of your team.

RH: There is a maxim that you always overestimate what you can do in a year and underestimate what you can do in 5 years. If you can string together accomplishments that build on each other, it is always surprising what a person or a team can achieve. I’ve seen this adage play out multiple times. Early in my career, PowerPoint had zero market share, but over many years, the team was able to make it nearly ubiquitous. Yes, I’ve heard of “Death by PowerPoint,” but the idea that people would mock it like this is amazing given the obscurity where we started. Likewise, I’ve seen companies go from hobbies to the Fortune 100 companies. When you can make steady progress over many years, the results are always surprising.


Join Our Pre-released Reader Program

Leave feedback specific to interviews you have read and you will receive an invite from Tony to join our Slack channel to be part of our beta readers group for pre-released interviews and engage with other software engineers.

We ask our beta readers to give us feedback.

  1. What 1-3 things did you learn from the interviews?
  2. What 1-3 things are you going to follow and change your own behavior because of the interviews?
  3. What 1-3 things did you find not helpful at all, or changes to the interview (longer shorter), questions that should be removed or added

Fill out this Google Form to send feedback and read 2 more behind the scenes questions
(I’m experimenting on not using comments)

Lyn Campbell : Corporate VP, Global Operations at Proofpoint

Lyn Campbell
Corporate VP, Global Operations at Proofpoint

Impactful Engineer shares the stories and journeys of women and men who are making significant impact in the software industry. The purpose of Impactful Engineer is to inspire young software engineers to see that are many paths they can take to move forward in their careers and grow their impact wherever they work.

Profile: https://www.linkedin.com/in/lyncampbell
Interviewed by Tony Tam
Editing by Hunter Shen
Reading Time: 24 minutes
Artwork by Cate Tam


TT: Where do you currently work and what is your role within the company? Also what is the scope of impact that you have within your organization?

LC: I work for a cybersecurity company called Proofpoint, a leading provider of security solutions to our customers. I’m the Corporate Vice President of Global Operations. Proofpoint Operations includes our NOC (network operations), our network team, the data center, and data center technicians. We have engineers who are responsible for core infrastructure and then we have DevOps engineers who are responsible for product infrastructure—the applications that are running on our core infrastructure. Operations at Proofpoint also include the CapEx (Capital & Expenditures) responsibilities for the company. I’m also responsible for our compliance, both our own as well as the compliance guidelines of our customers. For example, we have a large number of financial institutions that use our products and they have compliance requirements that we need to meet as a vendor. I’m also responsible for our security team, our information security, and the application security for the company. I’ve been here for almost four years. I report to our CEO who is someone that I’ve worked with twice previously over my career. I have a phenomenal team and I work for a phenomenal company.

TT: That a fantastic summary. I looked through your profile and at your college degree. It was the first time I looked at it. Your college degree was actually in English. It’s the same major that my daughter actually hopes to major in.

LC: Good for her!

[beautifulquote align=”full”]You can look at someone’s technical skills and know that they are brilliant technically and maybe they’re even a good communicator. But when you start going up that vertical ladder for individual contributors and technology people, to be really good you have to be an influencer.[/beautifulquote]

TT: It was surprising to me how you got here. Could you talk about your journey, and how you got into this part of the industry.

LC: Sure. I originally wanted to be a film critic. My goal was to become the next Pauline Kael. And so I got my degree in English and also studied a lot of film and film literature. But when I graduated from college, as you might have guessed, Pauline Kael’s job wasn’t available. And so I started working in the reinsurance industry. There was a technology aspect that I sort of fell into through selling a computer version of the product to other companies. That kind of morphed into a QA (Quality Assurance) function, which then finally morphed into Tech Pubs (technical publications). And so I became a tech writer and a manager of tech writers, which opened a door to Sybase. Sybase was looking to expand their database technology and they needed someone to start up a new Tech Pubs team. And so I left the insurance industry and went to work at Sybase and my CEO now was my VP then. As I got more responsibility at Sybase for more and more documentation, I got to know him pretty well and when he left Sybase to become the CEO of an early SaaS company, he brought me over to run a small business unit of services for our target market as well as tech pubs and QA.

What I found through that period was how much I liked working with engineers. I like how engineers think. It is very different from my own way of thinking. But I was really kind of looking to expand all the experience that I was getting in the various companies beyond working closely with engineers, so I started working directly with customers by going to another SaaS company where I managed account managers and first and second level support. And at that company was an Operations engineer that I knew who left there and went to Yahoo. And while he was at Yahoo he found that Yahoo Media was looking to expand its service engineering function. They were hiring a lot of service engineers and they needed to hire a handful of managers and so he convinced me that what I didn’t know about technology I could learn well enough to be a good people manager at Yahoo.

After getting into Yahoo, what I found was that my liking for working with engineers was in part due to my strong communication skills. I like the challenge of understanding the context, if not the code, and I’m able to synthesize information and deliver it to different kinds of audiences. And so because I was able to speak and write articulately, I got more responsibility at Yahoo and had some really good mentors at Yahoo who helped me further develop.

And those years at Yahoo brought me all the way back to a former VP who was the CEO at Proofpoint. At Yahoo, there was a period where we had some stability issues for a time. I was having lunch with a longtime friend who worked for the CEO at Proofpoint and he was telling me about their outages and I was telling him about my Yahoo outages. And he said “hey, why don’t you come to Proofpoint and help us improve our infrastructure.” And he pitched the idea to the CEO—and here I am. So I think it was not so much the aptitude for technology as much as the aptitude for working with technologists that got me to this place. The seven years at Yahoo and the four in the Proofpoint have absolutely been the most rewarding of my career.

[beautifulquote align=”full”]There are two things that I tell people about meetings. First, I don’t care what your company culture is, shut your laptop, put your phone down and be present.[/beautifulquote]

TT: I have a follow up on that question. We connected on LinkedIn and you say you are a strong supporter of women in tech. Do you feel like you’re an industry insider or because of your background do you feel like you’re an outsider? Are you able to look at the industry from an outsider’s viewpoint?  

LC: It’s a really good question Tony. I think I have a foot in both worlds. I’ve been doing this now for more than 15 years if you aggregate the experience with working with tech companies. So I don’t feel like I’m an outsider. I’ve certainly had to develop my technical skills to be conversant as well as to understand a lot of the principles behind them. But I am still an outsider in the sense it’s not the technology; it’s that language and the words that we use—the way we express ourselves, the way that we write—is very very important to me. I’m always going to be an English major regardless of what I’m doing. My philosophy, which is a slight tangent from what you asked me, is if somebody hadn’t given me the job at Yahoo, I never would have found that I have affinity for operations and the kinds of things that we do in operations. And if I hadn’t had that opportunity, all of the things in my life that have happened over the last 15 years wouldn’t have happened. Because of that, I feel a tremendous amount of alignment to women in technology because I think a lot of times women have fewer opportunities. Whether or not there are reasons behind that, I don’t want to say.

But I literally also make opportunities for other people because I really do believe in paying it forward. So, to give you an example, the guy who was the project manager for remodeling my kitchen had a phenomenal customer-facing skill set. He also was able to balance about ten different subcontractors, deal with purchasing, deal with pricing, and deal with me as a customer—and I can be a little demanding. At the time, I was realizing that I needed to up-level the whole purchasing function within Proofpoint, from procurement all the way through to deployment into our data centers. And so I asked this guy who had been in construction his entire adult life, “Hey, do you want to give high tech a try?” He’s been with us now for almost three years. He gets recognized in quarterly meetings. All of the ops people and the engineers love him. He’s doing a phenomenal job and gets to spend more time with his family, and there’s zero physical labor. His whole life changed—and it wouldn’t have, if someone wasn’t willing to take a chance on him.

I brought another woman into the company who was one of my Account Managers and who took over the leadership for that team after I left my second SaaS company. I brought her in to first run the Operations program management office and then our Compliance team. She’s knocking it out of the park and utilizing all of her skills, but in a different function entirely. Everybody just needs a chance to show what they can do and trying to find those opportunities is my responsibility, whether for women specifically or people who want to further their career. That’s what I’m here for.

[beautifulquote align=”full”]The difference between feeling like you are controlling your day or your day is controlling you is to consciously decide what you’re NOT going to do today. Try something for me. Make your list and then take 20 percent off the list. Just decide that you are not going to do this, this, this, and this today. .[/beautifulquote]

TT: When I started the Impactful Engineer project, I wanted to interview an equal number of women and men. My original idea was to interview only individual contributors, not leaders in management. I thought I wanted to show the path forward for individual contributors. However, what I found was in our Senior Principal level, there were probably fewer women in IC roles than female VPs. It was incredible. I wonder if what you’re saying about opportunities is also true of our current senior level IC roles. Because senior ICs need peers to nominate and support them to get over an artificial wall, because we try to run pattern recognition to recognize if a person fits in a club.

LC: Right, for sure. I think some of it also has to do with the fact that to be a really good leader and to be a high performing individual contributor, you have to have pretty solid influencing skills. I think that because women at times may have fewer opportunities and potentially fewer mentors who are helping them develop some of those skills, they have the additional pressure of trying to grow their careers without the benefit of some of the coaching that men seem to get more directly.

You know, you can look at someone’s technical skills and know that they are brilliant technically and maybe they’re even a good communicator. But when you start going up that vertical ladder for individual contributors and technology people, to be really good you have to be an influencer. And so I think that it’s key for that skill set to be nurtured very early in both men and women.

But we may need to over-rotate a little bit on behalf of women so that we can catch up. While I think that Sheryl Sandberg sounds like a fantastic person, I think we’ve gone a little overboard on the whole Lean In movement; it’s become more of a catch phrase and now we’re all leaning in all the time. But there is more to it than that, and one of the things she said much earlier—it was quoted in her first New Yorker interview—was that if you offer an opportunity to a man that’s outside of his skill set, many men tend to say “sure, no problem,” even though they don’t know how to do whatever the thing is, whereas women tend more often to say “I don’t know how to do that” and hang back. From talking to people in my network, men and women, it seems to hold true very frequently.

If we were to spend more time with women early on, building awareness in how many of us think by default, and how to think differently, and how to develop our soft skills in addition to technical skills, we can do more. Because it seems for women that we need more than just influence; we also have to carve away at that notion that “I don’t know how to do that, therefore I can’t.”

[beautifulquote align=”full”]Everything that you say to your manager is going through a filter. So if you’re one of those people who constantly brings a lot of negatives or challenges, your manager will come to expect that of you and see you as more negative.[/beautifulquote]

TT: Do you have any tips about how you stay productive, how you protect your time while managing a large organization.

LC: I have one really good one that’s particularly relevant. The company that I was at prior to joining Yahoo was a small SaaS company and the CFO was a woman I admired greatly. My teams were all customer facing, and my entire day was interrupt-driven. Our customers were so sensitive to stability at the time that we had to over-communicate whenever the Ops team needed to apply patches or do anything in production that MIGHT be noticeable. And one of my responsibilities was to notify everybody every time we were going to make a change, which was just not a scalable way to run, and as a result, I was just constantly overwhelmed.  

The CFO came by my office one day and said “You know, you look frazzled. What’s going on?” By the way, that’s the biggest thing I’m still working on because I still don’t do a good job keeping my face impassive. Anyway, I was telling her how overwhelmed I was feeling. She said “What’s your normal process?” And I said “Well my normal processes is that I get in super early when it’s quiet, I make a list of everything that I need to do, and then I attack the list.” And she said “OK, so, how’s that working for you?” I replied that I was never able to get to everything. And she said, “The difference between feeling like you are controlling your day or your day is controlling you is to consciously decide what you’re NOT going to do today. Try something for me. Make your list and then take 20 percent off the list. Just decide that you are not going to do this, this, this, and this today. I don’t care when you do it in your workflow—just practice consciously choosing not to do certain ‘must do’ things.” And it was the single best piece of coaching on how to not feel overwhelmed by aspects of a demanding job that I’ve ever received, and I’ve relied on it for years. And I find that it works so well, if I occasionally don’t manage to grab a little bit of quiet time and decide what I’m not going to do, I really do feel like I’m flailing a bit and I can’t lead effectively if I seem scatterbrained or distraught. I always try to make sure that I’m controlling all of my inbound, even the stuff that comes to me on the fly, and just say “You know what? I’m not going to do that today.” Eventually, it became largely subconscious, and that’s how I’ve managed to keep my sanity over the years.

[beautifulquote align=”full”]A lot of the credit for mentoring has to go to people who cared enough about me to give me feedback in a way that I could absorb it.  Because it took me several years to be able to absorb feedback with gratitude as opposed to feeling “Ow, ow, ow, that hurts.[/beautifulquote]

TT: And do you have a process of ranking, even in your head?

LC: There are certainly buckets of ranking. Whoever my boss is at any given time is always number one.Then customers. Then the people who work for me, and there I try to be mindful of the balance between people who are growing in their careers and people who are struggling. I try to stick to some of the great teachings at Yahoo about facing forward and not overly investing in the strugglers and instead investing in people who are growing.

So those are kind of the three buckets that I tend to think in terms of. At my level, they wind up being interchangeable to some degree because I’ve found the higher I report in my career the more it’s easy to see the intertwining of all of those things. It’s not as stratified as people think—there are those three, and then most other stuff that can be punted when the day is overly busy.

TT: You talked about a mentor or several mentors. Could you please describe some things that you carry with you that you still practice from these mentors?

LC: A lot of the credit for mentoring has to go to people in my Yahoo career who cared enough about me to give me feedback in a way that I could absorb it. Because it took me several years to be able to absorb feedback with gratitude as opposed to feeling “Ow, ow, ow, that hurts.” Early on, when I got promoted to Director, I got pulled into a conference room one day by my VP at the time, and she said “You need to remember that you’re on a stage.” She knew I was a Disneyland person, so she said “Think about being a Disneyland cast member. The other cast members look to you. If Snow White is having a bad day, Mickey Mouse is going to freak out a little, as are the children. And so you really do need to remember that you’re on a stage whether it’s walking through the hallway or in a meeting.” As I said earlier, working on keeping my face “open” has probably been the hardest thing for me to do but it is something that I try to stay conscious of and whenever I’m in my office with my door shut, before I open it and walk out into what is basically a large open space, I try to remember to smile, or at the very least not frown.

There’s one other thing which is kind of odd but is very important. Because of my non-technical background, I had a lot of trouble with impostor syndrome for the first several years at Yahoo. I know impostor syndrome is something that often gets assigned to women in general, but I actually talk to a lot of guys about it and men feel it too. I struggled so much that at one point I even tried to resign, but a senior VP intervened and stopped me from leaving, and also gave me a raise to convince me to stay. That was this weird sort of validation for me—I couldn’t be an impostor because they were choosing to pay me more rather than lose me. I also talked to my boss at the time who told me, “You’re the only one in the world who has this job. There’s nobody else in the world who is responsible for this collection of things. You’re unique.” So those two people’s feedback and support helped me to finally put aside this notion that I’m an English major hanging out at tech companies and sooner or later somebody is going figure out that I don’t know what I’m doing. I had never managed a network team before I came to Proofpoint, as well as some other areas in what I’m responsible for now. But I don’t have that impostor syndrome pulling me back into a lack of confidence. Fortunately, I have more of the attitude of  “You know what? I’ll figure it out,” or “I’ll trust the people I work with to know, and we’ll do it together.”

So, I think those mentors all really had a tremendous influence on me.

[beautifulquote align=”full”]I think that because women at times may have fewer opportunities and potentially fewer mentors who are helping them develop influencing skills, they have the additional pressure of trying to grow their careers without the benefit of some of the coaching that men seem to get more directly.[/beautifulquote]

TT: When I mentor young engineers one of the first things I tell them is, your job as an engineer is to make your manager’s job super easy to promote you. They want to promote you. Some engineers don’t understand that. Your job is to make it super simple for them. And part of that is just do your job well and do more than they asked you to do. The second thing I tell especially women is, in meetings make sure to say something, ask a question, contribute something in the dialogue, never be silent, because that’s time you just lost, and that’s an opportunity lost, especially when your boss or your VP is in the same meeting. Besides those, is there other advice you would give to young engineers?

LC: There’s a very important component to the second suggestion that I have heard quite a bit, and honestly that advice predates both of us. But what I noticed from the really ambitious people is that they can be so interested in contributing and getting their spot in the conversation that sometimes what they’re adding isn’t always valuable. There are times when being silent, if done correctly, also forms a good impression.

There are two things that I tell people about meetings. First, I don’t care what your company culture is, shut your laptop, put your phone down and be present. I’m not the only person who evaluates others in meetings. People who are sitting there typing away are either are too busy, which is a problem for their manager, or they just don’t understand how important it is to be present, make eye contact, follow the people who are talking, and be 100 percent focused. We’re not as good at multitasking as we like to think we are. You miss things when you’re in your phone or laptop. Being present allows a person to contribute much more meaningfully because they are listening to what is said and they’re watching what’s going on in the room. Those things matter.

The second thing is about body language. I just I hired a guy in a remote office and we did an all-hands meeting to introduce him to everybody—video for multiple locations except for the office in which he is based. He was in a curious position; leaning backward, and slumped sideways in his chair. It was hard to separate the body language of—tired? Overly relaxed?—from his talk track about being super glad to be here. They just didn’t align. So, don’t just be present by shutting your laptop, be present by looking interested, sitting up straight, having body language that shows you want to be there. Because sometimes, when you’re competing with a bunch of other people, you have to also rely on non-verbal cues to stay noticed in a meeting.

Also, to complement your suggestions about making it easier for your manager to promote you: one of the things that also helps is to bear in mind is that everything that you say to your manager is going through a filter. So if you’re one of those people who constantly brings a lot of negatives or challenges, your manager will come to expect that of you and see you as more negative. That’s not to say you can’t vent. But tell your manager, “Hey, look, I’m frustrated. I need to vent for a minute before I tell you what I want to do about it.” Help your manager help you by cueing them that you know  you’re not at your best, and then moving on to a more positive place. You know, there’s a lot of communication and packaging that goes into all of these interactions that honestly matters.

TT: I’ll add a little bit to that. The advice I gave to this young engineer—and she might feel like I’m overdoing it—was this: Every meeting I go to, I prep ahead of time. Either the same amount of time or more than the meeting itself. So I go in there more prepared than anybody. And if somebody wants me to, I could probably control the agenda if I wanted. Besides what I said, is there any other tips on meetings that you would give to younger people?

LC: Absolutely. If you are going into a meeting and you know that you want to influence the outcome, whatever that is—you may be doing an architecture review and you’ve got a competing idea for the design or you’re going into a post mortem and you really believe that the root cause is wrong, then the place to begin your influence is pre-meeting. Go find another attendee in that meeting and run your idea past them. You don’t really want to surprise people in a meeting. You just don’t wind up getting A) buy-in, or B) the productivity that you want. Because if you throw a big thing out there that nobody’s expecting, the meeting takes three steps backward and then everybody has to get on the same page and then go forward.

And so, go to someone else who’s in the meeting and let them know what it is that you’re concerned about and let them know what it is you’re going to mention. Because again, it goes back to influence. You want to get people to join you in whatever that thought leadership is going to be. And the way that you do that are through multi-channels as opposed to just in that meeting space.

[beautifulquote align=”full”]For women, we need more than just influence; we also have to carve away at that notion that “I don’t know how to do that, therefore I can’t.”[/beautifulquote]

TT: So your advice does compliment my advice that you have to spend time before the meeting.

LC: I think we’re numb to meetings largely. And I think that people just kind of go from meeting to meeting to meeting and they don’t think about the value that their presence can add. The people that I’ve seen do well are the people like you who prep for the meetings or people who are present in the meetings or people who use the meeting for its intended purpose rather than to show people how bright they are. And I’ve been able to correlate those behaviors with people that I’ve watched rise. It’s the people who really do show up in all senses that tend to do well over time.

[beautifulquote align=”full”]So I think it was not so much the aptitude for technology as much as the aptitude for working with technologists that got me to this place. [/beautifulquote]

TT: What personal philosophy has contributed to you growing your impact over your long career? I have noticed that you are a “people person” and that groups of people tend to be very loyal to you.

LC:  The thing I have learned a long long time ago that has worked for me in every job that I’ve had pretty much since I started working at Sybase in 1993—so a really long time—is this: If you treat people well, and by that I mean you have empathy for them, you are genuinely interested in helping them grow, whether it’s growing a skill set or growing their career, and you are as fair as you can be and empathetic overall to the best of your ability, then they will do good work for you, regardless. And I think that putting people first and knowing—not hoping, really knowing—that good work comes from that, allows you to be able to help them balance their personal lives and their jobs. There’s a balance that comes by putting people first and trusting that they will deliver for you. I’ve never not found that to work. Each time you get to have that opportunity to prove that in action just makes it that much more of a core competency going forward. I’m not saying that putting people first means that you become some sort of nonprofit for making people feel good all the time, and I’ve certainly had to let people go many times in my career. But when you trust that from good comes more good, the philosophy itself doesn’t fail.

TT: Do you have any advice on being mentored, either formally or informally? For example, how do you ask for mentorship or even figure out who would be a good mentor for you?

LC: I’m going to talk about informal mentoring first because I think it’s super important. So, we’re all competing for time, right? We don’t have enough time, and each person that we deal with takes a little bit away. I think that there’s an implied notion that you need to have time to either be a mentor or seek mentorship. And one of the things that I tell people that I work with is that we all have slightly different viewpoints and we’re all in different places. Don’t ever miss an opportunity for informal mentorship. And by that I mean, in a meeting if you know going in that it’s going to be a tough meeting for you, go to someone whose opinion you value, not necessarily somebody you like or that you are a pattern match of, but someone to whom you can say, “Look, I want you to pay attention to me in this meeting because it’s going to be a bit of a struggle. Then afterwards would you be willing to give me feedback?” I do that in advance when I know that I want to get that feedback. I don’t want compliments. I don’t want criticisms. I just want to know how I came across. I want that person’s assessment as a benchmark for how effective I was.

TT: Do you have any advice for making the most of formal mentorship situations?

LC: I really admire my boss. I really admire our CFO. I will ask them after e-staff meetings when I had something important on the agenda, “Tell me what I could have done differently to be more effective.” Those organic moments are fantastic opportunities.

I also do some formal mentoring. I’ve got people who I meet with once a month who I tell that in order for me to work with them formally, they need to come prepared with an agenda. They need to have something in mind, not come to me with a random list of questions. Mentoring is not an interview, it is a series of conversations designed to make some progress. I think people think that if you don’t have a formal structure for feedback you can’t get the feedback, but that’s absolutely not true. There are formal and informal ways in which to gather data on how you’re coming across and to improve.

The other thing that I would say that goes along with that is you learn as much if not more from people that you don’t naturally click with. Some of the best feedback for me has come  from people that I really disliked working with or for. That lack of synergy or alignment doesn’t change the fact that you need to be effective with a broad spectrum of people, not just people you like working with. Getting a diverse view is very helpful. And I think that a combination of structured and organic mentoring helps you be the best you that you can be.

TT: What should I have asked you that I didn’t?

LC: What would you have done differently?

TT: OK, what would you have done differently?

LC: I would have thrown myself into my job at Yahoo earlier. In my first year, I got feedback that as a non-technical individual, my entry level was as far as I could go in technology. This was motivating in that I had a strong desire to prove this individual wrong. I was also supporting a VP whose respect I wanted to earn and both of these combined into a tremendous sense of focus, a crazy amount of work 7 days a week, and a drive to achieve that I had never felt before. If I had thrown myself into my work with that same amount of drive in my 20s as opposed to my 40s, I have no idea where I’d be today. I wish I had known what I was capable of earlier in career, because I think I would have done things differently. But I will tell you, on balance, I am satisfied with where I have ended up because of the people that I’ve met and worked with and the opportunities that I’ve been able to create for others. So it works out!

TT: Thank you so much Lyn! I hope this was useful for you as well to reflect back on your career.

LC: Absolutely. Anything I can do to help other people is just paying it forward. And you know, it was really interesting to think back on my career in this context. So it was enjoyable. I’m really glad to have done it.

TT: That’s great. Thank you Lyn!


Feedback from our beta readers!

Reader 1 (Senior Software Engineer)

Things are useful:

  • To grow in IC track, you need to be an influencer. Knowing that women are likely say “no” to opportunities because of uncertainty, we as women should consciously push us more out of the comfort zone.
  • Lyn’s story about how she came from an English major and grew her career is totally intriguing and impressive. It gives me a lot of confidence because she has come (maybe arguable) from an even more difficult route.
  • You need to work hard, throw yourself in!

Things that I will practice:

  • For meetings: Shut your laptop, put your phone down and be present
  • Ask for feedback from PM and my manager for important meetings

Reader 2 (Software Engineer):

For Lyn’s interview, points I find to be useful:

  • Do things you don’t know how to do
  •  Decide what not to do today to avoid feeling overwhelmed
  • Don’t try to multitask in a meeting

Things I will actually practice myself (in addition to the above):

  • Think about whether you want to influence the outcome of the meeting; if so, prepare, and talk to the other attendee(s) beforehand so you make sure they’re on the same page
  • Ask in advance for feedback on how you do in a tough meeting, or ask how you could have been more effective

Reader 3 (Senior  QASoftware Engineer):

1-3 things I learned from interviews:

  • When you start going up that vertical ladder for individual contributors and technology people, to be really good you have to be an influencer.
  • Each meeting should be an opportunity, make you valuable at presence.
  • Informal mentorship, ask diverse feedbacks, to make you be the best one you could be

1-3 things I going to follow and change

  • Changing the meeting habit, be present, be prepared and be valuable
  • Work less hard, make more impact
  • Carve away at the notion that “I don’t know how to do it, therefore I can’t”
  • keeping my face “open”, at the very least not frown

Join Our Pre-released Reader Program

Leave feedback specific to interviews you have read and you will receive an invite from Tony to join our Slack channel to be part of our beta readers group for pre-released interviews and engage with other software engineers.

We ask our beta readers to give us feedback.

  1. What 1-3 things did you learn from the interviews?
  2. What 1-3 things are you going to follow and change your own behavior because of the interviews?
  3. What 1-3 things did you find not helpful at all, or changes to the interview (longer shorter), questions that should be removed or added

Fill out this Google Form to send feedback
(I’m experimenting on not using comments)

The Non-Definitive Guide To Mentoring Software Engineers

Impactful Engineer

(This is the first blog post of Impactful Engineer, make sure to sign up for our monthly interviews with software engineering leaders)

You are someone who would like to mentor someone else in their professional career to help them grow their influence and impact.

More Comprehensive Reference Material

Benefits Of Mentoring

  • You develop a network of enabling and trusting relationships.
  • You give yourself  an opportunity to reflect on your own practice.
  • You get recognition for being a force multiplier.

How to Become a Mentor

  • Volunteer To Be A Mentor: If your organization offers a formal program and is looking for mentors, this is the easiest path toward becoming a mentor. Throw your hat in the ring and reach out to the organizer.
  • Offer To Mentor Someone: If you’ve already established a relationship with someone on your team or in your organization, you can reach out to them directly and their manager to offer yourself as a mentor.

Time Commitment

Being a mentor usually requires you to dedicate a minimum of 6 months to 2 years to your mentee. I’ve even seen 3 to 4 years of commitment. Weekly check-ins are usually a healthy way to see how each other is doing, handle any urgent questions and build up a level of trust and habit.

Start By Building Trust

The first meeting is crucial to the success of the ongoing mentoring relationship. For the mentor, it’s their job to be open to listening, come prepared, be honest, show commitment and most importantly build trust. At this point of the mentor/mentee relationship, the mentee has the most to lose and is the most vulnerable.

I can’t emphasize this enough: build trust first before moving forward on working on goals. If you don’t feel like there is enough commitment, keep on working on the personal relationship so that there is genuine care taken on both sides.

Emphasize Privacy

Keep everything confidential, even with the mentee’s manager. If you want to communicate and talk about the mentorship, take the time to ask for permission before disclosing any information to others. Do not even disclose the mentorship unless both parties are in agreement to do so.

Ask For Clarity Of Goals

Usually, a mentee wants to reach a career goal but is unsure about how they can get there. After trust has been built, ask them what they would like to get out of your time together.

Listen And Reflect On The Goals

Listen, don’t talk. Make no judgement on the goals themselves. Stop and listen. This is what I work on for myself. Then after the mentee is done talking, summarize back what you heard.

Your Job As A Mentor Is Simple But Difficult

  • Ask the hard questions for the mentee in order to get them to think about difficult subjects.  (future blog post coming)
  • Teach the framework to think about problems, instead of offering immediate solutions. (future blog post coming)

How To Mentor Software Engineers

With software engineers, start with explaining how the corporate game is played: there are players in the game (peers, product managers, managers, manager’s manager, VP, other more senior people), and there are rules of the game (HR policies on evaluation, software job family and level guides). You want your mentee to learn how the corporate game is played: what are the rules for evaluation? What are the rules for getting promoted. Who is in the room when they are evaluated?

Then, recommend a process of self-evaluation, where the engineer ranks themselves on how they are performing at their current level and at the next level. Software engineers are promoted when they operate at the next level. Have them print out their corporate job definition and spend 2-3 hours going through each of the skills and talk through why they rank themselves at that level.

I also recommend an exercise where they “project” into the future. Ask them to imagine themselves in two years: What are they doing more of, less of? Ask them about the people they are interacting with: How have those interactions shifted over the years? What are they spending their time doing? What will they enjoy doing in two years? What do they not want to be doing?

A Question Worth A Few Weeks Of Time: What Is Your Brand?

Ask this question to get them to explore how they want their co-workers to perceive them as at work. Ask: What do you want to be known for within your organization? Another way to approach this question is to ask them about the top three values they want to hold on to. Values are self-imposed rules that you follow even when nobody is watching.

Questions You Might Ask When Mentoring a Software Engineer

– Do you understand the corporate game?  The rules such as job leveling.  How the promotion process works?  How are in the room making recommendations and making decisions?

– What steps could you take to be a more effective communicator in meetings? For example, you could set goals like preparing ahead for all meetings, or speaking up or ask one question in every meeting. Don’t be afraid to take initiative in a meeting, take notes, or put ideas on the whiteboard.

– What could you do to focus on improving your own iteration speed? Then, how could you help others with theirs?

– How can you make your job obsolete? Can you automate, document, train someone else? This opens up opportunities for you to take on something bigger.

– How can you make your manager’s job super easy? What can you do so that your manager just can’t help but give you a raise, promote you to the next level, or give you a stretch assignment? 1:1’s can be quite productive if you are always asking thoughtful questions.

– What would it mean for you to take on 110% and stretch yourself? There are always breaks where you can work on multiple things at once.

– What can you do to heighten your love for your job? Can you look at it from different perspectives? Can you increase the quality of your work? Can you see your work as part of solving a bigger problem?

Feedback?

Email t@tonytam.org

See Also

Tony Tam’s Life’s Work: Sprint 1

tony tam life's mission

I believe computer science should be taught as a core skill, much like math and English. Not all children will grow up to pursue computer science, but I believe that all children should be exposed to computer programming because it is a skill that will help them increase their impact in whatever they career path they choose.

Impactful Engineer is the first step I’m taking towards my life’s work. After reading Amber Rae’s article on 8 signs you’ve found your life’s work to ensure that I am on the right path, I am more convinced than ever that this is the right first step towards being able to teach children computer science.

Software engineers like to refer to the “end state”. What does the end state look like for me? What is my endgame? Where is this all leading to?

Rather than answer the very difficult question of what my life will look like 20 to 30 years from now, I will borrow from my software engineering experience to validate this first step.

Software engineers like to experiment with different projects, learn from these projects, and create new iterations. We call this agile software development. Borrowing from agile software development, I’m calling Impactful Engineer “Sprint #1”.

In Sprint #1, this is what I plan to achieve in six months:

  • Acquire permission from my employer to work on Impactful Engineer in my personal time.
    • Working with Legal
  • Publish at least three interviews with software engineers who have made a significant impact on their industry
    • Herri Gunawan – done
    • Rick H. – done
    • Tenni
    • Lyn C.  – done
  • Talk to at least 20 people about Impactful Engineer in order to gather feedback for Sprint #2 and plan for the next six months
  • Figure out a gift I can send to the interviewees that is not priced (a stylized drawing of them that I can use for published articles)
  • DONE Build out an editorial team to help me with what my weaknesses are, with editing and proofreading. (Hunter, Cate, Robin)

Sprint #1 Progress

I will be recording my progress over the next six months on this page. For the sake of privacy, I will be using initials when referring to people.

  • I have talked with JC, KC, CT, KT, JH, RH, RB, HG, GD, RP, HS, BB, BB, AH, MT, Charu Sharma, ZY, CP, RH, AW, JC, CT, AW
  • I have sign up Cate T, Hunter S. and Robin P. on my editorial team
  • I have paid for the first iteration of the website content, $25 to Cate T., Editor at large
  • Herri G. has filled out answers to all the questions
  • I’m waiting for Tenni to schedule
  • Rick H has finish the audio interview
  • Lyn has finished the audio interview
  • I have reached out to 25 women in tech who are not my first connections on LinkedIn and gotten 4 new connections

Tools

I’m using Trello to track my status on a kanban board

See Also