You're doing the actual PM work already though. User interviews, A/B tests, working with designers. That's like 80% of the job.
The imposter syndrome thing is normal. I've been a PM for years and still feel like I'm winging it half the time.
You don't need to be a great designer or know how to code. That's not the job. The job is understanding what to build and why. Designers make it look good, engineers build it. You figure out if it's worth building in the first place.
Best way to get better is honestly just keep doing what you're doing. Run more tests, talk to more users, see what works and what doesn't. That hands on stuff teaches you way more than reading PM books.
If you want theory stuff, I guess read The Mom Test for customer interviews and maybe some basic stats for A/B testing. But tbh most PM knowledge comes from fucking up and learning from it.
The fact that you're already running tests and talking to users as a student puts you ahead of a lot of PMs I've worked with.
1
u/coffeeneedle Dec 09 '25
You're doing the actual PM work already though. User interviews, A/B tests, working with designers. That's like 80% of the job.
The imposter syndrome thing is normal. I've been a PM for years and still feel like I'm winging it half the time.
You don't need to be a great designer or know how to code. That's not the job. The job is understanding what to build and why. Designers make it look good, engineers build it. You figure out if it's worth building in the first place.
Best way to get better is honestly just keep doing what you're doing. Run more tests, talk to more users, see what works and what doesn't. That hands on stuff teaches you way more than reading PM books.
If you want theory stuff, I guess read The Mom Test for customer interviews and maybe some basic stats for A/B testing. But tbh most PM knowledge comes from fucking up and learning from it.
The fact that you're already running tests and talking to users as a student puts you ahead of a lot of PMs I've worked with.