What does a typical engineering org chart look like for a SaaS company all the way from CTO down to engineers?

This would seem to be a 'spans and levels' type question, and will depend on whether you include / exclude product management and architecture from your model and whether you believe in the ratios and management science type approach or a much more self organising, dynamic organisation. Assuming a more traditional approach - I would expect that folks with management responsibility would typically have between 5 and 8 reports as an organisation matures, higher either if you have great process, or are early on in the lifecycle and growing fast or have a much more self-organising organisational culture. A typical model might be 1 (S)VP Engineering reporting to your CEO for this kind of scale, there is a lot of evolution that would normally happen between 30 and 80 engineers.

To provide great and timely product input for that number of engineers you would would expect 6-12 product managers (depending on the cycle time and technology you are using and enterprise/consumer bias - typically ... more.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.