PS

Ask Me Anything

Questions are answered publicly here, with your name anonymized. Want a private answer instead? Ask on ReachVIP. You can also host your own AMA.

I've worked as a senior leader at Microsoft, Meta, and OpenAI, and ran my own startup. Many people consult me over email and LinkedIn. Instead of answering them privately, one person at a time, I wanted those answers to benefit everyone… so I launched this: a public archive of anonymized answers, open to everyone.

Graceful Fern asked

answered Sep 30

Asking for Advice to an L4 at Google

Hi Philip,

I came across your interview on the Peterman podcast, and was drawn to your energy and insight. I was wondering if you could spare a few minutes to send some advice back.

I recently spent a year working on Gemini on Chrome iOS which was really fun from an innovation perspective, but I was moving so fast that my features and my performance started to decline as I was trying to meet deadlines and felt pressure from all the stakeholders that wanted the features completed.

It’s been a year since I’ve been switched to a different team due to this performance and I have a lot of pondering thoughts: “is this all I could do”, “was this my limit”, “am I even a good software engineer”.

My question to you is how can I shake these feelings of low performance and how can I have that unshakeable confidence I had before having a lower performance review?

Maybe I may never get that confidence back, but I’m having trouble finding my way towards a new profound and stronger confidence in myself.

Any help is appreciated.

Philip's answer

Your sentiments are something I have a lot of personal experience with. I've had several "doesn't meet expectations" performance reviews in my career, as well as long periods (e.g. 18+ months) of unemployment which contributed to self-doubt, not to mention being rejected after interviewing with several companies.

First, I think it's important not to imbue you with a glow of false or undeserved confidence. I'm not going to sit here and say you're great, that you can do anything you set your mind to, etc. I have no idea what you're capable of.

That said, you are obviously very highly capable, having secured a job at an amazing company. Google is extremely selective in its hiring. You have a job that most people would envy and find impossible to secure. These are all strong indicators of your potential.

I find the most helpful thing to rebuilding confidence is to start with small successes. These small successes, once achieved, give concrete reasons for confidence which aren't merely bluster. Start with areas and tasks you're strong at, and build up from there. Cycles of doubt can fuel increasing insecurity; but the opposite is also true. Build for yourself some cycles of success.

My sincere hope is that you regain your footing and can feel once again confident in your strengths.

Hardy Crane asked

answered Sep 20

Thanks a lot for your answer about leadership, Mr. Su. Speaking of which, what are the best resources or people (books to read, podcasts to listen to, people to follow) that you'd recommend so I can get to where you are at some point?

Glad Gazelle asked

answered Sep 20

Hi Philip! Thanks for being so engaging and responsive on this forum.

If someone wants to switch both their role and industry, which do you think is usually better to change first?

For example, if someone is a Data Scientist in Healthcare field and wants to transition to Product Manager in Entertainment, should they try to become a Health PM first or become an Entertainment DS first?

Roles/industries are hypothetical. But one can guess that the hop to the exact industry and role directly is very hard if no prior experience in both, so the likely options are becoming a PM at a less competitive company (and then switching industries later) or switching industries first in the same role (and then trying to role switch later).

Philip's answer

Changing both role and industry simultaneously is dangerous. Your premise is exactly right: you shouldn't change all the variables all at once. Even within the same company, I recommend people don't change role and team simultaneously. It's much better to change one before the other.

Changing fields is much more dramatic than changing teams in a company. I'm not sure if there's an exact right answer to this, but I'd recommend changing roles first:

  1. DS in Health → PM in Health → PM in Entertainment

The reasoning is around risk reduction. When you change from DS → PM within Health (and ideally within the same company / team, where you already have social capital and coworkers more likely to be patient with you based on your past contributions), you can flip back to DS if the transition to PM proves too difficult. But more importantly, it sets you up to go PM Health → PM Entertainment, which then gives you two outs if an industry transition proves difficult. You could:

  1. Go back into DS in your new industry (Entertainment)

  2. Go back to PM in your old industry (Health)

Whereas if you made the industry/field change first, you only have one option, which is to go back to your previous job (both role and industry).

The real answer for you will be highly dependent on situation and on your own abilities. What I'm recommending here is a theoretical framework with which to think about such a large transition.

Hardy Crane asked

answered Sep 19

Hi, Dr. Su,

Thanks a lot for your substack 'AI-Assisted Coding: Why a Distinguished Engineer Stopped Reading Code'. As AI is evolving at an unprecedented pace, what is your secret sauce on successful leadership in your field?

Philip's answer

I dropped out of Stanford's PhD program, so I'm not a "Dr." 😊 Thanks for your question!

I'm not sure there's a secret sauce, at least for me, TBH. At the highest level, success has three attributes:

  • Luck

  • Talent

  • Hard work

You can't control the first two, but you have to acknowledge they have in impact. Luck has played a huge role in my success. Talent has, as well. For instance, I learn things relatively quickly and tend to see things at higher levels of abstraction than many people. This makes it easier for me, compared with some people, to spot underlying causes and explanations for things.

That said, I also spend a lot more time working than most people. I'm not recommending that as a course of action; I'm merely stating that as a fact. For instance, why am I answering this question at all? Why did I build this AMA site so others can see previous responses I've sent to people? It's not because I think I'm going to get something out of it... but I do think it reflects my general initiative to try new things, to take everything another 10% higher than default.

When it comes to staying on top of things, I've often strived to join the strongest teams that'll accept me. This maximizes the chances I'll work with amazing people, which in turn is often the fastest way to learn.

Mighty Bluebird asked

answered Sep 11

Hey Philip,
I was looking for advice on navigating early software career struggles in this era of increasingly capable AI. I feel scared that the career ladder is being pulled away from people like me who are still in a phase where they are trying to learn and grow and instead be replaced by seniors whose contributions can be multiplied by AI.
I'd love your perspective on how to stand out as a strong candidate now. I'm trying to figure out how to signal good engineering judgment rather than just shipping code, since code output has become the easy part. I was wondering how you would try to show that if you were an early career candidate applying to jobs? Thanks!!

Philip's answer

A tough and highly relevant question.

First, the good news: when it comes to junior hiring, that's only fallen by ~19% since AI impacted the industry. 19% is from one perspective very high (e.g. the highest unemployment recorded in US history was the Great Depression, at 25%). But on the other, it means 4 out of every 5 junior people are getting jobs.

You can likely stand out within the top 80% of junior candidates. As you mentioned, things have gone way beyond code production as the main gauge of junior capabilities. I'd recommend spending a lot of time building with different AI approaches (models, harnesses, tools), and creating real projects (even side projects) which help hone your judgment about how best to use AI as a force multiplier. There is, in some senses, no way to speed up the type of learning you want other than to spend more hours doing highly-leveraged learning in those key areas (e.g. of better judgment around how to structure components or build the most impactful things).

Wishing you the best! It's a tough environment out there... but you only need to outrun 1 of every 5 people. You can do it!

Want a private 1:1 answer from Philip Su? Ask on ReachVIP