I have been working in finance as a Quant, basically combining some aspects of data science with tool programming. In my free time I worked on side projects including with Flask, Django and Plotly Dash. Basically worked with Python with a pinch of React mixed in. I’m 38 now and seriously considering to move into a software company in the hopes that I can work on probects like my sideprojects. Although I am willing to learn a lot and invest time, I am afraid that I may not be good enough. Should I take a chance and quit my new job as a math and physics teacher (it just does not make me happy)at a high school to persue a position at a software company?
I am at a crossroad now and am happy for any hint if you have ever seen a similar move work out.
Thank you in advance for any reply!
I'm only slightly older than you. You do not want a Jira job. It will burn you out. It's not the same as indie development... you will probably work on tickets, adding features no one really cares about or fixing bugs that you didn't create. It's awful. If you were a real quant, you can probably use your CV to get something a lot better.
When I was working at the acquiring company, they didn’t really have a good place for me. I had more domain knowledge than anyone else at the company but I had less experience with even the basic etiquette of how software reviews work (I.e. GitHub pull requests).
Coding as a quant and software engineering are really quite different. As a quant, you have to optimize for getting stuff done quickly at all costs. In software engineering, there’s more focus on testing, maintainability, and readability.
Eventually I created my own role as a technical product manager and that worked out quite well.
Just as with dating: there’s always someone you are good enough for. And you can build up your career from there.
Aim for small companies or early stage startups where they're more impressed by your determination than by your background in the field.
Happy to chat more with you or anyone in a similar situation, email in profile.
Many people do not consider the actual job requirements and skills necessary for the work. It's like, they're just trying to find the best person possible. Some people are even hardcore about this; they test you and judge you quite aggressively. That's cool, and there is some truth to that; there is a bar that needs to be met. But, it's a rather shallow perspective. And, it can have negative consequences. E.g. people burn out, get bored, don't work well with others. There's overlooked value in getting to know a person and positioning them well in a role.
You might be surprised. Your experience from side projects may translate extremely well to a "real" job doing similar things. If you can stay humble, work well with others, and spend time on fundamentals, I think you'll do well in the right environment.
As an aside, within the past year I've sparked an interest and appreciation for biology. In the back of my mind, I sometimes think it would be very fulfilling to work on software/hardware for biotech at some point in the future. Maybe a "second career" type of deal. I have massive "imposter syndrome" about that, but who knows... maybe some day my path will lead me there.
I’m currently working with a friend who is transitioning from retail investing to software development and the bar for an entry-level role is quite attainable.
Your quant experience could also land you in specialized software dev roles that might have to do with finance or data analysis if that calls your attention.
As for the tech that you mentioned (Python, Flask, Django), roles using those things are alive and well but feel free to explore other languages frameworks to sort out what type of role you might like more (i.e. flask is usually backend while plotly is frontend). Nowadays at least some passing familiarity with JS is useful because of how it everywhere.
Take a look at the threads like “who’s hiring” but see if you can leverage network connections to talk with people instead of sending a hundred copies of your resume everywhere.
Do feel free to reach out (email on profile) if you’d like to chat further and good luck!
I started as a quant but preferred building software so I left finance to software / data science consulting for a bunch of years and now am co-founder/CTO of a software company that just finished YC (AiSupervision W22).
My advice is to put together a portfolio website with some demos of your projects and well-documented code on GitHub and then create a profile on workatastartup / apply for jobs.
Good luck!
If you think you will enjoy it, I don't see why not.
>Should I take a chance and quit my new job as a math and physics teacher (it just does not make me happy)at a high school to persue a position at a software company?
I think it's better if you quit your job after you already have found a job as a software developer.
My suggestion is that you get into data science or bioinformatics. You will be able to pick up the specifics easily, given your quant background, and there is a decent amount of software development involved as well.
Wait so you've already quit finance to be a math/physics teacher?
In my opinion, it is a great work very valuable for the society, and that allows to pass your passion for science to children (those who are receptive). It can even be a bridge to some academic career.
My wife&I are your age and have worked at 6 & 5 companies respectively in our careers. Never have we quit a job before having found a new one, gotten the offer, accepted, and gone through background checks.
Why create an exploding timeline for yourself?
1) Make decisions about things, and did the required research to make those decisions (and can talk about what you did and why).
2) Went through the entire deployment lifecycle. Its really easy to just do the interesting stuff then call it a day, but if you have actually gotten to production with something then you are forced to address a bunch of tiny paper cuts along the way which will round your skillset out significantly when trying to get your foot in the door.
One potential avenue would be to build a SAAS product for Quants with your existing domain knowledge. This would allow you to leverage your existing body of work and do the programming work you want to.
Good luck!
- Much of what you have acquired as a Quant is potentially going to be re-usable
- Becoming an actual SWE will potentially require you to learn a lots of new stuff (code review process, unit testing, large scale software architecture, code refactoring, OO, algorithms, code productionization, source control, debugging, etc... the list is very long) , and more importantly, you may have un-learn a lot of reflexes you might have acquired as a quant (of the "code, run once and throw away" persuasion)
I'd keep on money rolling as a quant, or enter academia, or doing consulting as a quant. Don't waste that knowledge, it's super difficult stuff
Don’t quit your day job until you have another one though, there’s no point in increasing risk