16 Comments

I love those podcasts. Great job Ryan! 💯

Expand full comment

great interview

Expand full comment

It taught us a lot.

Expand full comment

Thank you for your sharing this video.

This is really tons of help.

Expand full comment

Thank you for keeping this content for free. This is a goldmine.

Expand full comment

I can relate to the challenge of being a young manager. I became director by 28 (albeit in a small startup, which is much easier), and now manage people almost twice my age.

The worst thing I did is acknowledge it too much 😅

Expand full comment

I feel like this interview it talks about the same thing over and over after each question

Expand full comment

How do you find relevant projects when projects come from product teams?

Expand full comment

Hi Ryan,

Another amazing interview—I'm absolutely loving these! BTW, I think the production quality on this one was top-notch. It got me thinking—if you’re looking for other engineers to interview, I’d happily volunteer myself. I’m not a FAANG engineer per se, but I think my story is pretty compelling. Here are some highlights of my journey:

1. I spent 10 years in finance right out of college with 0 programming experience or classes.

2. Quit my full-time job to attend an iOS bootcamp.

3. Struggled to find a job for 6 months but finally landed one.

4. Worked in Indiana for a year at Sweetwater.

5. Moved to a smaller growth company, Life360.

6. Got promoted 3 times in 4 years at Life360.

7. Shipped a revolutionary fitness app that tracks runs, rides and walks comletely autonomously. Still struggling marketing the thing but it works like a beast. https://apps.apple.com/be/app/godiary-running-tracker/id6448186957

8. Ideated, evangelize, and developed the software for Flight Notifications at Life360, (which is now being patented). https://www.life360.com/blog/landing-notification-announcement/

9. About 1 years ago, I switched domains completely—from iOS Engineer to Cloud Engineer—where I’ve shipped code, reviewed cloud tech specs, and run on call shifts.

10. I've been a lead algorithm and data structure interviewer probably interviewing over 100 iOS engineers and also mentoring other interviewers.

Compensation Growth Through the Years at Life360:

2017: $55,000 (Sweetwater)

2018: $104,000 (Life360)

2019: $131,000 (Life360)

2020: $175,000 (Life360)

2021: $194,000 (Life360)

2022: $238,000 (Life360)

2023: $319,000 (Life360)

2024 (projected): $526,000 (Life360)

If this resonates with you, I’d love the opportunity to share my story in more detail! Let me know if you’d be interested. Feel free to hit me up on linkedin.

Best,

Chad Wiedemann

Expand full comment

I’m curious about the phrase 'saying no to projects.' What exactly does the term 'project' mean in this context?

I currently work as a Software Engineer and am part of an Engineering Team that is assigned to a specific project. In my organization, I can’t switch projects without also changing my Engineering Team. This has led me to wonder how project and team structures are organized at Google, as their approach seems to be significantly different from what I’m used to.

Expand full comment

Project in this context means some encapsulated piece of work. Your definition of "project" reminds me more of a workstream than just a piece of work.

Without switching teams, I'd say you should look for tasks or pieces of your workstream which have the most impact.

> This has led me to wonder how project and team structures are organized at Google, as their approach seems to be significantly different from what I’m used to.

Picking your work is much easier if planning is "bottoms up" (done by the engineers) compared to "top down" (done by leadership). This is team culture specific

Expand full comment

Thank you so much for clarifying that. In my organization, planning is definitely "top-down." We receive specific requirements from the business side, which must be implemented across all series of our devices before the deadline. Each team is responsible for one or two series of these devices. That said, I can certainly choose tasks that have the most significant impact.

Expand full comment

I’m curious about the phrase 'saying no to projects.' What exactly does the term 'project' mean in this context?

I currently work as a Software Engineer and am part of an Engineering Team that is assigned to a specific project. In my organization, I can’t switch projects without also changing my Engineering Team. This has led me to wonder how project and team structures are organized at Google, as their approach seems to be significantly different from what I’m used to.

Expand full comment

Metaa

Expand full comment

Too good. Too motivates. Sometimes I also feel imposter syndrome. Ahh 😅.. hard to come out of it. But sir, your every week article keeps me motivated and inspire me towards my goal.

Expand full comment

Imposter syndrome common in this field, even among high performers like Ricky! Glad the content it is helpful Komal, thanks for reading

Expand full comment