It depends on which area of the business you're in.

The quants (people who do the analysis to give buy/sell signals, basically, typically using programming for the analysis) will generally need a strong grasp of statistics and finance.

The developers that build the trading platform will need a strong grasp of exchanges and the mechanics of trading, but not really of statistics or "how the market works/reacts".

The developers that work on the reporting side don't really need a strong grasp of either. The math is relatively simple, the difficult part is handling stuff like cross trades. I.e. internally trading stocks between portfolio managers without having to hit the actual exchange (i.e. PM A wants to sell Intel, and PM B wants to buy, so you just transfer ownership instead of actual buy/sell orders). You have to attribute a profit/loss to PM A even though there wasn't a "real" profit or loss.

The SRE/ops side often doesn't require much knowledge of finance or math. The apps aren't particularly unique, and the portions of the trading flow you're expected to know aren't hard to pick up in a month or two. You aren't typically expected to have an in-depth understanding of trading strategy, or a highly detailed understanding of how trading works mechanically. Knowing that stuff probably lets you command a higher salary and title, but it isn't a prerequisite.

Math and theory would be more important for a dev job, parent commentor is doing SRE.

What exactly does an SRE do (Software Reliability Engineer, right?)? I've heard the title before but don't quite understand it.

Site Reliability Engineering (SRE) is a term coined by Google.

The goal of the job is keeping large systems online and operational.

Think: systems engineering, DevOps, and sysadmin at scale - leveraging automation.

Lots of other shops still call it DevOps Engineering, Production Engineering, etc.

I wanted to joke that some still call it sysadmin so they can pay you like one, but it is probably not as funny as I thought.

Site Reliability Engineer - I’m one too lol. Most of what you do is work with dev teams to make sure their service is reliable, then slap an SLO (service level objective) to make sure their service meets a certain threshold of reliability.

Can I ask what your day to day looks like? Are you configuring services? Writing code and tests? Like what are the things you do for reliability?

(I've never been in a company big enough to have one of these, so I'm just trying to understand)

It's going to vary based on the company you're with but a typical day for me includes reviewing/writing code, attending some meetings for projects, and answering pager duty when something goes boom. Occasional post-mortems and active maintenance of systems. I was up until last week an SRE at a firm maintaining an industrial information system and related services.

More tooling, infrastructure management, high-availability, ... work.

Rather than focusing on making the software do X, it makes software that already does X more resilient to failure.

I work at a fintech company as a software developer for 2+ years, and I've not needed any maths in my job really.

I think it strongly depends on exactly what you end up developing.

yeh, you do and most will want a degree at at least 2.1 even if you have a decades experience... unless you have the hallmarks of being rich e.g. went to some fancy school OR have a network that extends into a hedge fund