mal4mac said:
What's even more scary is that you might do it "right" and still screw the world economy!
By definition if you do it right, the world economy is fine.
It wasn't bad programming that caused the sub-prime problem.
It was bad mathematical modelling. One thing about working as a "financial scientist" is that you aren't a mere coder. You are responsible for developing mathematical models, and your responsibilities include non-technical aspects including thinking about the broader implications of what you are doing (which is why banks hire people that think about the universe in the first place).
There are a ton of jobs in finance which are "shut up and code what we tell you to". But those jobs are extremely unappealing to Ph.D.'s.
This incidentally means learning a fair amount of securities law, since the details of the law in fact can change the mathematical model in lots of ways (i.e. when modelling North Elbonian bonds we have to include this term to take into account the fact that North Elbonian handles default in a different way than South Elbonian,)
Now if you did spot a problem and you raise the issue and are told to go to hell, then at that point you could have resigned since you've done everything you could (i.e. theoretically you could go to the regulators but before the crash they would have ignored you) and then when it falls apart, you have clean hands. I know of people that were in that situation pre-crash. Fortunately, the situation is different now, and one thing that the regulators did was to create mechanisms so that you can raise critical issues before the world blows up. But that means that "they wouldn't listen to me" is no longer an excuse.
On the other hand, if you push the panic button for everything then that doesn't work either. If you push the panic button for everything then that can kill new modelling which can also blow up the world because it means that you are running models which are obsolete and wrong because you can't get the new ones in.
I suppose the one good thing about financial programming is that "it's only money" you can bankrupt someone and destroy the world economy, but you won't directly kill anyone. Now the people that I know that design hydrogen bombs on the other hand...
Most of my programming involved creating educational software - that wasn't very scary. If the package crashes, just go back to chalk & talk, no real harm done...
A lot of my programming ended up being "emergency room" programming. Production is down or failing, and it's like bringing in a patient into the ER. It's really awful, and a lot of programming involves making life easy for yourself when the system gets into the emergency room. A lot of it involves managing emotions, both your own and others. You want to focus at stabilizing the system, and calm down the half a dozen people that are frantically screaming at you so that you can get the information that helps you resolve the issue.
Getting back to the original poster. Before you bite into the apple you really need to know what you are getting into. The thing about scientists is that you are dealing with the elemental forces of the universe, and those can be quite dangerous. There is the initial thrill of discovery, but that passes very quickly, and a lot of what happens next depends on what's left afterwards.