Coming from the financial services industry, I can say that this is a fairly typical job description for an entry level role, and as an analyst I did need most of these skills. The term "analyst" is usually the 'pay band title', while software engineer is the "functional title". Usually the progression there is something like: analyst -> associate -> vice president: equivalent to a FAANG-like progression of L3->L4->L5. This is of course complicated by the fact that 'analyst' is a title with a very different meaning if you're in, e.g. the investment banking.

These requirements are vague, but if I had to guess, this role is most likely heavy on data extracts and reporting (hence the SQL in point 1), and expects you to be able to work with your business counterparts to understand what's wrong/right with your reports. The charts and graphs point is probably more like 'basic Excel knowledge to manipulate the CSV you pulled from the sql database'. PM skills is probably a roundabout way of saying "can you estimate how long a feature might take to deliver". This role is most likely "big investment bank is required by regulation[1] to keep specific positions and send us their trades daily, write a query to make sure they're netting out to zero and send us a daily report".

Do you need a masters in comp sci to perform this role? No, probably not. I think it's more of a "well if you have the hard skills in programming, we can teach the other parts'. In my experience, a lot of the people from pure comp sci degrees left financial services fairly quickly out of boredom, whereas people with information systems degrees seemed to thrive based on the higher need for soft skills. [1] e.g. SEC's FIN41 https://dart.deloitte.com/USDART/pdf/793a25c7-3f31-11e6-95db...