 So what does a PM actually do? This is a common thing. I'm sure many of you have seen, I kind of hate this diagram, because it's kind of like saying, where is this, if somebody asked where the Statue of Liberty was, you wouldn't say it's between Manhattan, Jersey City, and Governor's Island. Like that's a very not helpful explanation. And so, but you've probably seen this a lot, so I wanted to put this out there. The way I think about it is that a PM owns the what and the why. Specifically, what problems are worth solving, and what features or products should we be building to solve those problems? Engineering and design often ends up honing the how. The boundaries are soft, so you'll often, you'll work across the two, but generally that's at a high level, at a principal level, what the PM role does in a software company.