The Peterman Pod - 28 Year Old Staff Engineer @ Google

Episode Date: November 22, 2024

Ricky (@findingricky) went from Junior (IC3) to Staff (IC6) at Google by 28. He doesn’t consider himself the best engineer, instead crediting his blend of technical and soft skills for his ability to land promotions quickly. In our conversation, we discuss:• Managing your manager• Finding good projects (and rejecting bad ones)• Imposter syndrome• Switching from IC to engineering management• Work-life balance—Where to find Ricky:• Instagram: https://instagram.com/@findingricky • YouTube: https://youtube.com/@findingrickyWhere to find Ryan:• Newsletter: https://www.developing.dev/• X: https://x.com/ryanlpeterman• LinkedIn: https://linkedin.com/in/ryanlpeterman• Threads: https://www.threads.net/@ryanlpeterman• Instagram: https://instagram.com/@ryanlpetermanIn this episode, we cover:00:00 – Intro01:08 – Promotion timeline02:34 – Junior to Mid-level04:24 – Finding independence10:39 – Mid-level to Senior11:20 – Learning how to say no17:26 – Senior to Staff20:18 – Finding next-level work23:42 – Transitioning to management33:46 – Reflections To hear more, visit www.developing.dev

Numbers don't lie, right? For me, it's just revenue. At the end of the day, if my idea makes the most money, no one's going to say anything to me. I don't know. I thought I was like a personality hire or something. Hey, everyone, it's Ryan Peterman here with another episode of the podcast. Today, we have a guest who went from a new grad at Google all the way to staff by the age of 28. He did it very fast. He has a lot to say about how to get promoted in Google's culture and how to work with your manager. But I think the thing that was most interesting to me about him was that he's the first person. Whoever told me that he wishes the opportunities for promotion to staff came later in his career. And he explains why that's the case. If that sounds interesting to you, let's get into the conversation. Ricky, welcome to the pod. So today I wanted to go over a bit about your career. I know you were at Google pretty much your entire time. So you did an internship at Google.

You committed full time. And you went from junior all the way to staff in your 20s. and I just felt like there's a lot to learn from that. So I want to lay that all out today. Yeah, I'm so excited to be here, and I hope that this podcast is very helpful to everyone else. Can you walk me through the overall arc of your career? Can you just lay it all out?

I'm kind of curious about the compensation and also how fast you got all the promos at Google. I started as a new grad in 2017, and around then I was making $180K, and I had some sign-on bonus, and I think that's pretty normal for a new grad offer from Google. And then after that, I got promoted in a year and a half to level four, or what we call like a mid-level engineer.

And at that point, my compensation was around 250K, which is, again, about average for an L4. And a year and a half after that, I got promoted to L5. So I made it from three to five in three years. That's very fast. I got very lucky, very fortunate with my team. On average, I would say it would take maybe like four or five years to get that done. So I did it maybe a year and a half or two years faster than average. So at level five, my compensation was 350K, which is again about average.

It was a little bit higher because of my initial stock grant. And then three years after that, I got promoted from five to six, so from senior to staff level. And at the staff level, my compensation was around 500, or it currently is around 520, maybe more, but it's around there. And again, that's also pretty average. I think these numbers really align with what you see on Levels.frii, so hopefully it's no surprise to anyone. So let's go into the first one, that junior to mid-level promo. You said you did it a year and a half at Google. What did you learn along the way? Can you tell us more about the ratings that you got and also a little bit more about the process? Maybe we can start with the ratings. Yeah, Google does ratings on a six-month cycle.

So the very first half, I got a meet's expectation, which is pretty normal for anyone who's only worked there for six months. And then after that, I exceeded expectations. And then after that, I got the promo with the level higher than that. I was really nervous about going for this promotion just because it was like really ahead of schedule. So I was really unsure at the time if I was going to get it. I definitely had all the attributes I felt like for the next level in terms of my impact. and how well I was doing at work. But I just wasn't sure if my tenure would support that,

and I was a little bit worried being docked about that. But luckily, my manager was supportive. Help put me up for promotion, and I ended up getting it. It sounded like you knew about it. Is it initiated by the employee or the manager at Google? At Google, it should be definitely initiated by the employee. I would say, though, more than anything, it should be an ongoing conversation between you and your manager.

Just making sure expectations are set of when you plan on, going for promotion, what projects you're working on, and what's going to move you to the next level. I was asking my manager, hey, do you feel like these projects that I'm currently doing are the next level and making sure my own expectations were set, making sure the projects that were doing were indeed for the next level. I see. So you were fully aware that the problem was happening and you were managing up throughout the whole process.

Yeah, definitely. I fully support managing your manager. I think it's something that you have to do if you want an accelerate. promotion timeline. What was it that you did that actually made the difference at this level? I think just being able to have independence and finish projects on your own is really the hallmark of what people are looking for when you're getting promoted from three to four or junior to mid-level that you just don't need that much hand-holding. You can unblock yourself on your own. Is there anything that you did that helped you unblock yourself? Anything you'd recommend for someone

that is junior to become more independent on the project. I would say what helped me the most was just asking a lot of questions. I think a lot of people when they first start, because the imposter syndrome, they don't want to seem dumb, and I didn't want to either. But I kept telling myself, and I kept reminding myself, hey, I'd rather ask questions and look dumb and learn something, and maybe I'll get fired because people think I'm dumb than to do nothing, not learn anything, not ask any questions, and get fired. I really tried to overcome my imposter syndrome with that mindset.

And I think that's what helped me learn a lot from others. Because in general, a lot of people are really willing to help, really wanting you to succeed and grow. So through that, I was able to learn how to do things on my own and move my projects forward by asking people questions rather than asking my manager to figure it out for me. You don't want to ask too quick because then you don't learn anything and someone just gives you the answer. Yeah. But you also don't want to block for too long. long because you're just going to be sitting there and not learning anything and it's not productive, especially when I had interns or people who are new in the industry, I feel like you

should reach out if you spend more than half a day on something. If you spend four hours or something and you make no progress, nothing's going to change. You might even want to reach out sooner than that, but of course you want to give it a good try before you ask the question. Yeah, 100%. And I think definitely if you're asking the same question multiple times, then it's maybe a red flag. You get stuck after working a while and you ask the question, that's totally fine. It's normal and expected. Definitely. Yeah, there's got to be this upward trajectory. If your

diffs, they constantly get tons of feedback and that doesn't change after months of work on the same code base, something's off there. But it's totally okay if the iterations are coming down. There's a lot of questions, but it's getting better over time. That's the ideal growth. So you got that promo, Pretty straightforward. Honestly, in the industry, that promo is just a matter of churning out code and just doing it more independently. So it makes sense. That just aligns with what I think as well. Let's talk about the senior promo.

I think, you know, on this promo, there's a little bit more change in your behaviors, and it's not just shipping more code. So I want to dig into that. For you, what did you feel was the biggest shift and how you were going about your work that helped you get promoted to senior at Google? I think the biggest shift is probably just taking more and more. ownership and getting to a point where I could confidently say I owned a certain scope or a certain area and the buzzword is the go-to person for a school of area. So I was able to get to that point by really understanding a portion of the code base and pushing out a lot of projects that had a lot

of impact in that special area. Was that something that you explicitly planned? Like you maybe with your manager you thought, okay, that area, there's not a good owner. or yet I'm going to go into that area? Or how did you become the go-to person? I think I got pretty lucky on this. So I work in ads and the scope of area that I chose to invest more time in, the ads just didn't look that pretty. And I wanted to make it better.

And by making it better, I was able to also have a lot of impact. So I just picked kind of the most interesting scope of area that I kind of did my toes a little bit into and I just kept working on it and I continued to find it interesting and slowly became more of an owner by doing more and more projects and taking my time to explore that area. I think some people, depending on the team structure, they have to compete for scope or they worry about that. So in your case, you didn't run into anything like that. Is that right? Yes. My team is a little bit special because we usually pick our own projects. Of course, you can still have projects handed down by your manager or your manager can help you pick

projects, but I really made an effort to find my own projects, making sure that they had reasonable impact because I feel like the best projects that you can find are the ones you find yourself because your manager might not always give you a project that's at the next level. So I really looked for projects that were at the next level, had big impact, push my boundaries and put me outside of my comfort zone so I had to learn and improve my technical skills. too. One of the most important parts of getting promoted is getting some next level scope to actually execute on. How did you know that the things you were looking at were at the next levels? How did you find those? Was there some tech lead that you were discussing things with or did you do it more by yourself?

I think what I did is I looked around my team and looked at how other people might have gotten promoted to senior and tried to understand, oh, this is what exactly a senior level or L5 project look like and thinking about how I could create something or find something of that same scope or complexity. And then after that, I took my ideas to my manager and asked him for feedback, asking him, hey, do you feel like this is a next level of complexity? Do you feel like this is a reasonable place that I can push the boundary on? And that's also kind of how I set myself up for success to get a promotion really early

because a year before I actually got promoted, I went to my manager and I said, you know, said, hey, these are all the things that I think are interesting that I'm kind of working on. And here's a roadmap for the next year of what I'm planning on doing. Do you feel like this is enough for the next level? So already a year before my promotion, I did my best to set expectations with him in terms of what I'm doing. And if it's at the next level or not. So that was after, so right after you got your promo tier to the mid-level, you put together that roadmap and you showed it to him.

Is that right? So after I got promoted from three to four, I had about six months where I was just like trying out different projects, seeing what was interesting to me, and slowly like figuring out what my L5 scope looked like. And then I put together that one year roadmap by myself and then showed it to my manager and got my managers buy it. Got it. Okay. And so as you were going along and executed on this roadmap, I mean, inevitably at work, like things come up. people might want to give you work that is not on that roadmap or I don't know there's some partner asks that come in what did you do in that case how did you handle it when work was not at the next level but someone was asking you to do it I think you just have to learn how to say no obviously if it's a bug that you caused and someone's bringing it to you you better fix it because you know it's your

bug or like if it's your scope of area and someone finds a bug you should still fix it but if it's a whole new project that someone else wants to take you on. Maybe it is like the next level scope and you do think that is a good project and you work on it. But most of the time I feel like people will just kind of like see who might want a project or who's interested in a project. And you have to decide for yourself, hey, is this at the next level or not? Do I have time for this? And I said no to a lot of products that I felt like were not at the next level. I'm sure they might have impact, but they weren't going to help me grow. Do you have any tips for people say no?

Because I think a lot of people, they don't feel comfortable, especially if the work's coming from their manager. What's the right way to say no without causing issues? If it's someone else giving you work and you don't want to do it, I would escalate to your manager immediately and being like, hey, this person's giving me work. I don't want to do it. Like, why is it being handed to me and trying to understand like, oh, maybe it is just like a bug that you cause so you do have to fix it. And if it's work given to you by your manager,

I think I would just try to push them and be like, hey, is this something I have to do? I have my own projects here that I feel like would have more impact and also help me grow more. Can I just do these projects instead? And I think a manager's job, and this is coming from someone who is a manager, is to find projects that help you grow and succeed and projects that you actually want to do because otherwise people might give you a project and you're forced to do it, you're just going to do a crappy job on it. So it's better for a manager to find a project that the reports actually want to do. So hopefully your manager's not giving you a project that you don't want to do. Makes sense. So it sounds like you had pretty good managers throughout this process.

It seems like they were pretty receptive to what you were saying. Yeah, I think I just built up like very early on this ability to find my own projects and have impact. My manager, I felt, was not too worried about the projects I was doing and just trusted that I'd find my own projects to push on. Obviously, he still gave me a lot of feedback to help guide me and help me understand, oh, these type of projects might be good or bad for me. But for the most part, my ideas were bottom up rather than top down. and I think that's one of the ways that I was able to succeed and get promoted really quickly. That makes sense.

You talked about knowing which ideas are impactful and which ones aren't. How did you develop that skill? I think maybe the first thing you have to do is figure out what exactly impact means within your org. For me, as an ad, so it just meant like, how much money is this going to make? Does it actually help the user, help the advertiser, help the publisher? sure. But if you were on a different team, maybe it's like increasing the number of daily active users or interactions with a certain product. So really thinking about what exactly that impact number meant. So again, for me, it was revenue and I was able to find projects by running a lot of

experiments to figure out, oh, here there's a gap where I can probably have a lot of impact and drive a lot of revenue. Here's another gap that I found where I can probably drive a lot of revenue here too. And I think the best part about this is that numbers don't lie, right? For me, it's just revenue. Other people might have ideas, but at the end of the day, if my idea makes the most money, no one's going to say anything to me. Yeah, yeah, for sure. There are metrics and there are projects with well-known milestones that the whole org knows is valuable. So when you move those metrics, obviously revenue and ads, yeah, no one can argue. If you have the biggest metric movement, let's say you're a junior engineer that moves it more than the whole team, like, okay,

obviously that's going to be something something huge. Okay, so when I actually got to the senior promo, what was that like? I would say that from three to four, it was a little bit scary, but they've been four to five. It was even scarier because I knew I was really going against the grain. Like, I was getting promoted really fast. It's a really expedited timeline. I heard that, like, the average time that it takes to get promoted can be like 2.5 years,

three years, three point five years. So doing it 1.5 years was really, really aggressive. And I was just worried that I'd be docked points for not showing that I was performing at the next level for an extended amount of time. So I knew it was a pretty big stretch. Luckily, my manager still supported me and said that we can go for promotion. Though, you know, like he said my expectations. He was like, I'm not sure. Like, we'll really have to see.

Again, you might be docked. but, you know, let's just try to go for it and see what happens. So I did end up going for it. I was able to make it. It was a really big surprise to me. Very fortunate that my manager supported me, even though it was a very aggressive timeline. One last thing on this level is for senior promo,

you need to lead a bit more than in the past levels. Is there anything that you did that some people, there's like growing pains to like becoming like a leader on your team? Like, how is that experience for you? Did you have imposter syndrome at any, points. It definitely was a little bit scary and as you said growing pains it takes some time to get used to almost being confident in yourself. For example, like I had some project ideas that I ultimately handed off to more junior engineers but I was pretty anxious that they wouldn't pan out or that the

experiments that I gave them wouldn't do so well and honestly some of them didn't but I think my batting average was still higher than than most people and that definitely helped. But you definitely have to get used to leading and just being comfortable mentoring people. And I think in buzzwords, you would say you'd have influence on others and their projects. Let's go into the staff promo. I think it's natural for promos to take longer later in your career. Did you feel stuck at any point? Honestly, I wish I could have stayed at the senior level a little bit longer.

I feel like being a senior engineer, you, of course, don't make as much as if you're a staff or a higher level engineer, but you have great work-life balance. Like, I really miss taking a nap at like 2 p.m. or going to the gym at 3 p.m. when there's no one there. And I think as you become more senior, you're just involved in a lot of bigger projects that require more meetings and your structure. The structure of your schedule just becomes more and more rigid. So I think for people that do want to go to staff, really think about is this something you actually want? Like looking at how other staff engineers are on your team or on adjacent teams and looking at what they are doing. And at Google, do they have an up or out policy? So you can stay at senior as long as you want.

Is that right? Yes. I think maybe you can even stay at mid-level as long as you want, but I'm not 100% sure. There's no expectation for people to stay as long as you want. people to go to staff, I think becoming a staff engineer is very much a choice that to, you know, go past senior, go to staff, because it is a lot more responsibility and a lot more work. And I think some people just don't want to make that trade off. If you were to take you at the senior level versus you at the staff level, what's the

biggest difference in your mind? I feel like at level five or as I as a senior, I definitely started owning a space. I had a scope that I was well versed in and I did a lot of projects and had impact there. And I think what helped me go from senior to staff is now that I really knew a scope of area, how can I push the boundaries of that scope of area, challenge the status quo, and have a larger influence over that scope of area. I think I got a lot of points for leading and pushing the boundary of that area. And through that, I was able to have a lot of impact and just like being a leader,

in that space rather than someone that just knows the space. I see. So you were creating scope and influencing across teams. Yeah, definitely just like both cross-functionally across org. Like it involved a lot of at some points like very high leadership buy-in. So I think once you start being the one to kind of like make those decisions and like push those decisions up, I think that starts to show very clearly staff level influence. One of the things to getting a staff is that you need to find that staff level project. And in a lot of cases, the manager can't just hand that to you.

That's something that you need to find yourself. How did you find your anchor project that got you promoted to staff? I think what helped me find my staff project is just working in a space and then being like, why are we doing things this way? This doesn't make sense to me. And then starting to challenge how we've been doing things for a while. So there's definitely a status quo. And like one specific example is we had a lot of support backed by user research that showed, you know, this one thing to be true.

But then when we actually ran the experiments, it conflicted with user research. And I was able to push that and show that, you know, despite what user research shows, we can do this instead to have a lot of impact. So I would say what really helped me have that staff level project is knowing a space so well that I can. start to challenge the boundaries or the rules that may have been set up and pushing it towards almost like this new frontier for a specific scope. And I think we talked a little bit about influence and how important it is for staff. How do you usually go about influencing other people? I think at work, I just kind of already established a brand of being someone who was able to find impactful projects or just find impact in general. And then I would kind of pitch my ideas to other

people. You know, obviously not trying to step on anyone's toes, but just giving ideas and collaborating with others. And I think a lot of people trusted my ideas at that point, and they also panned out really well, fortunately. So I think that's how I kind of established influence with other teams or cross-functional partners, just building a relationship, cross-pollinating ideas with other people, and ultimately getting those ideas. to become projects and ultimately succeed in launch. You had been at the company for a while and you had already evidence of past results that gave you credibility.

And so that made it that it made it so that you could influence people a lot more easily. Is that right? Yeah, I'd definitely say so. If your projects keep flunking, then, you know, people might not be as willing to try out your projects or trust your word as much. That makes sense. I think that's one thing that is unique about your career compared to a lot of our friends, is that you have been at Google since we graduated.

You've been in the same org the entire time. So all those people know you. They've seen you as this rising star that has been having a lot of success on all these projects. And so it's just natural that you're probably going to be more influential than if you got hired at the senior level on this team. You have to build all of that credibility from scratch. Yeah, I don't want to say Rising Star, but I definitely, you know, had some successful projects that I think we're able to showcase that, you know, my word had some value or some truth behind it. Yeah, yeah, yeah, the Rising Star would be just like that you've had past success.

Yeah. You've had past success. Yeah. You're believable. You're credible. Yes, exactly. They see your name and they're like, okay, this project's probably a good idea. For the staff level, like you also, like you were TLM for some time as well. Can you talk a little bit about, you know, why did you want to try management in the first place?

I think that's like a common thing that everyone's thinking is I see. They want to make that decision for themselves at some point. So how did you make that decision? Why did you want to try and manage? I wanted to try management just because I think I already have. had a lot of fulfillment in helping people grow, finding projects. Even though I wasn't directly managing people, there are definitely mentees I had at work. I also mentored interns at times, and it was just a really fun time watching them succeed, and it's almost like having a kid

and watching them grow, and I really enjoyed that. So that's ultimately why I wanted to try out being a manager. Luckily, my team was also very supportive of that idea, I started managing around two years ago. That makes sense. Did your manager really vet your motivations for wanting to become a manager before you became one? How did that process go? I don't know. Honestly.

I pitched the idea to my manager. I think even once I was at the senior level for a while, I think I kind of said, hey, like, eventually one day I'd like to become a manager. and I think just the right opportunity came up. I do feel like becoming a manager really early on was a little bit awkward just because at times felt like I wasn't mature enough to be a manager. When you say not mature enough, what does that mean?

I think I felt a little bit awkward at times. One example is like being in a meeting of a bunch of managers and I think a lot of the managers in our org skewed to be a little bit older, just naturally because some of them were even like higher level of managers and have been managers for a while. So there's, it felt a little bit awkward there. Another time it felt awkward is like when I'm out at a music festival and I'm really drunk and then I see my reports out there.

I think at the end of the day is probably fine, but I think I just didn't really think that that would happen until it actually happened. That makes sense. And before you came, had you done interns or any, did you have any management experience or did you just kind of ask your manager and he was like, okay, maybe one day and it just happened? Yeah, I did not have like any special managing experience.

I never had an intern. I was a little bit surprised. For some reason, I thought that there'd be more of like a textbook on how to be a great manager, but I feel like a lot of people just kind of get thrown in and then, you know, they do their best. I'm not saying that Google doesn't have resources. Google has tons of resources, but I don't know, I thought there'd be a little bit more structure, but it seems like in general people just become a manager. When you became a manager, what do you feel was the biggest difference between being an IC and manager? I think what a lot of people told me.

before I became a manager and I agree with their advice even today is that when you're just like a TL you have all the fun parts you get to help them grow you get to help them succeed and then all the harder parts is like giving difficult feedback when people are not performing so well and a lot of almost the busy work of writing reviews and like going to calibration session So there's just a lot more, I guess, overhead when you're a manager as opposed to being an IC. But I do feel like at the same time, it's a little bit more rewarding when you actually get to see your reports get promoted because you are their manager, right? You help them get promoted as opposed to just being a TL and helping someone get promoted. Definitely.

So now that you've tried it, do you think that you regret becoming a manager? I would say that I just wish I became a manager later. I think at the time my team just we had like a really odd scenario where we had 20 new hires and I felt like I was helping them all and I wanted a more formal role just so that I would only be responsible for the people that actually managed, which was four people rather than 20 people. So in that sense, like I feel like I was able to have. have more time back because I only had to really help for people. But if I had the choice, I probably would have been a senior engineer,

maybe a couple more years, just because I think they're less responsibility and it's less stress. And I think in your, I don't know, early or mid-20s when you wanna just relax a little bit more, it's just better to be a senior engineer than to be a staff level engineer or higher. that's fair yeah and there's a lot more meetings at the staff level especially as a manager

I feel like it's all meetings that sometimes yeah it's definitely a skill that I feel like you have to learn or get used to just powering through six hours of eight hours of back-to-back meetings or one-on-ones some managers I think have all of their meetings in one day some of them have it like sprinkled out throughout the week but in general as you become more senior whether or not you Are a manager or not a manager at the levels of 6, 7, 8, you're going to have a lot of meetings no matter what because the influence you have is always going to be through other people, and it's going to be less code that you actually write yourself, whether or not you're an ICER or a manager. So for me, at least, I think when I first graduated from college, I was like, oh, my God,

I want to be a director one day. It's going to be so fun. But I think as I become closer and closer to these high levels, I'm understanding what it actually means and it means no more random naps at 2 or 3 p.m. whenever I want. It means no going to the gym at, you know, 11 a.m. Obviously, to a certain extent, you can still have doctor appointments in the middle of day if you have to, but there's definitely less flexibility. And I think if you look at the calendars at work of any of these more senior people, you'll also see, sure, they still only work 9 to 5, but they are working 9 to 5. They are definitely working. I feel that. This is definitely

a lot more meetings. I think when I got promoted to staff, I remember my schedule. It was basically a large chunk meetings nine to five. Not entirely nine to five, but meetings kind of just fragment your focus time. Yeah. So then every day I would have

you know, fragmented meetings for most of nine to five. And then I would start working on my stuff at five until like I went to vet. So yeah, I totally agree. It can become a lot. Yeah.

So I guess last thing, you actually go for the promo, of course. Were there any differences between the past promos, or was it pretty straightforward? I already said that. I was unsure from 3 to 4 and 4 to 5. I was also very unsure for 5 to 6, honestly. I definitely had really good ratings. So that was definitely a signal. I had like, you know, the highest ratings possible for a while already.

but I was kind of just unsure just because I think people have said that going from five to six is notoriously hard. Three to four, four to five, obviously it still takes work, but it's a little bit more straightforward. And people say that going from five to six is almost like a complete job change in some aspects. So I was pretty worried about it just because even if you're a superstar, senior engineer, and you're having tons of impact. it doesn't necessarily mean that you are going to be a great staff engineer. Though I did end up going for a promo. Again, I feel very fortunate, very lucky that my manager was supportive and I was able to get promoted and only took me one try, which I'm also pretty thankful for.

So all of your promos, there was never a miss and try again, miss and try again. It just landed every time. Yes. But I was very lucky. I was very lucky. So, yeah, looking at the whole career, do you think you could do it again,

or was it a large part of this luck? I think you definitely have to be a little bit lucky just because sometimes you might not enjoy the team that you're on or maybe your manager is just out on paternity or a maternity leave, so they can't help you as much or they can't support your promotion as well. I think where I got lucky was that my team, team was a product area that I ended up really liking, even though I didn't pick that. I didn't pick my team, but they just matched me there.

And I've been on that team for seven years now. Clearly, I like it to some capacity. And I think my team was also relatively stable. My manager, although I had some like manager shifts, ultimately it was still under the same broader and larger team. So nothing crazy in terms of reorgs or restructuring that might have hindered. my career progress. But I will say that luck is like two parts. One of them is the chance of an opportunity actually coming along, right? Sometimes you just have to wait for that. It might take

longer, it might not take as long. I think the second part is being prepared for when that chance actually comes. So just making sure that you're doing your best and doing the right things so that when an opportunity does come along, you can actually take advantage and seize the opportunity. What percent of your career do you think has been due to your abilities, and what percent do you think was luck? I would say maybe like half-half. Like, I'm pretty confident that eventually I would get to senior, and I think that most people will eventually get to senior as long as they are like making sure to grow and putting work in. But maybe if I was on a different team or I just really did not like the stuff I was working on, it might have taken. taking me longer because I don't have to switch teams and then get ramped up in their code

stack. So I think I was just really fortunate that things worked out the way they did. But I definitely made sure to put in the effort and was very conscious about the next level and what I had to do to get there. That makes sense. Yeah, luck is a huge part of it. There could be an engineer that's better than you, but they're, I don't know, the team they're on is like literally just the worst. It's reorging every six months, they have no consistent project. And so in that case, of course you couldn't do it. And on flip side, it sounds like you had a lot of things around it, like a good manager and like the scope to continue to grow,

your product was like impactful and all of that. So that makes sense. One of the last things I want to talk about is, you know, I think we kind of mentioned that out of all of our friends, I think it's a little bit unusual to be at the same company for seven years, especially in this industry. People are kind of job hopping to try out new things or, you know, get more compensation or whatever.

And so what kept you at Google for so long? Yeah, I think it's really important to ask yourself, I don't know, maybe every three months, just ask yourself, hey, am I still enjoying the work I'm working on? Do I still feel like this team has whatever I want? for me it was like I really wanted some career growth. I also really wanted to travel a lot. I didn't care as much about what I was working on as long as it wasn't like too boring. So my team, I felt always had those opportunities for me and that's why I didn't leave. But I think what I often tell people is I just kept asking myself, is the grass greener here or elsewhere?

And it was greener on my side of the lawn. So I ended up staying. That doesn't mean that I wasn't thinking about leaving or if I should change teams every so often to make sure that the job was doing as much it was for me. Of course, there's survivorship bias, right? I'm sure people that did not get promoted as quickly, maybe they just didn't really enjoy the team or didn't enjoy the work, whereas I just had a good match. That makes sense. Yeah. And I think there's pros and cons to staying at the same team. there's this momentum that you get by staying on the same team and the same company,

you're like this snowball of organizational context and like the code-based know-how. And after four years in the same area, you're not just the go-to person in one area. You're like go-to person in like many areas. And you just become this person that just knows how to do, get everything done. You have all the relationships. So if you can get lucky with a good, you know, org setup and all of that, there is this, this, uh, benefit to, to having all that context that can give you unusually fast career growth. You know, on the flip side, of course,

you can job hop and try to get promos too. So that it's not, uh, black and white one is better than the other. I guess it's like a counterpoint to, I feel like the, the common opinion is like you should jump and you should switch and there is actually some value to sting, as long as your situation is good. Yeah. Okay. And the last thing I want to know is if you were to talk to that Ricky at the beginning of your career, junior and junior and junior Ricky, just under the industry, what advice would you give yourself and why? Hmm. I think to my younger self, I would just tell him to trust himself a little bit more because I think for a very long time, I just had so much impulsive syndrome. I was so anxious that, you know, I wasn't going to do so well. And over time, I, like,

built up that confidence, like, through projects, my projects succeeding and working well with others and getting good feedback. But I think I was, like, really unsure of myself. And I actually feel like I could have done more if I was willing to trust my judgment a little bit more, or have more of almost, like, audacity to push the boundary and try new things. because I had a lot of ideas that I felt like I maybe waited a little bit too long because, you know, I felt like, oh, am I going to rock the boat too much? But I ended up doing a lot of those projects that did rock the boat, and they were very successful. And I wish I just, you know, trust myself a little bit more to do it earlier.

So I'd be less anxious and stress all the time and be fretting less over imposter syndrome in the beginning of my career. When you say imposter syndrome, was that mostly, about your technical skills or something that you learned that made you have less imposter syndrome? I don't know. I thought I was like a personality high or something. And over time I realized, you know, obviously like Google's not going to do that. But I think I was always just a little bit worried because I think during my interviews too for Google, I think I like did okay. I don't feel like I like hit a home run and the same thing. with my internship. I didn't feel like I hit a home run. And also think at the lower levels,

I wasn't really sure how to kind of gauge my performance. And even though I would like bother my manager a lot and be like, am I doing okay? Like, are things going well? And he'd tell me like, oh, yeah, you're doing fine, you know. I would still like kind of be anxious, like, oh, but like, is it enough? Is it just okay? Or is it like, am I doing like, am I passing? Is this like a seat? I'm doing, am I like doing an A plus? Like, what's the vibe, you know? I was just stressing out about that. Yeah, that makes sense.

That's super natural. Awesome. All right. Well, yeah, I think that's everything. Ricky, is there anything that you want to plug or, you know, where can the audience find you? Yeah. So on social media, I'm finding Ricky.

If you want to watch my content. It's not really tech related. I have to warn you. I feel like I'm in a very different niche than Ryan here, but if you don't want to follow me or check out my socials, it's Finding Ricky. And I hope that this podcast would helpful to everyone, and I'm so happy that I could be here today. Awesome. All right. Thanks so much for your time, Ricky. All right. Thanks everyone. Bye. Hey, Ryan here. Thanks so much for listening to the podcast. I hope that it was helpful. And if you want to hear more from

Ricky, you can go and check him out on YouTube at Finding Ricky. He recently posted a video about a day the life as a staff engineer at Google. I know it sounds sensational, but actually I think he did a good job in capturing what the day-to-day is like. It's not just flexing big tech perks. It's more about the daily work of a staff engineer and how things kind of become much more different as you have more and more responsibilities. So you can take a look at that. And then two other things that I want to add is one. Thank you so much for the feedback on the first video. I hope that you can see that I took it to heart and the production quality is a little bit better. Still has a long way to go, but look at the background here. I bought a backdrop to make it a little bit nicer,

and I'll be using that for future videos. And then the other thing, too, that I got a lot of feedback on is the jump cuts. And so I tried to get rid of as many of those as possible, while still removing filler words and things like that. So you can see that I'm playing with the camera angles. I really appreciate the feedback. And if you have any more, feel free to drop comments on YouTube. I will take a look there and try to make every episode incorporate the feedback that I get. Thanks so much for your time. Thank you.