Job titles can be things pairing off terms like research/computational/computer/software/[domain] with analyst/engineer/scientist commonly. In my experience, most companies learn that it’s usually easier to turn an “x” into an “x programmer” than to turn a “programmer” into an “x programmer”, so it can be inaccessible to do interesting work in fields that you didn’t start in.
One of the most accessible fields for outsiders tends to be biology. Employers include the NIH and federal agencies, state research labs like http://labs.fhcrc.org/compbio/ and http://www.wadsworth.org/resnres/bioinfo/ , biotech firms like Amgen and Stryker, and university research labs. Many problems in biology are not that hard to pick up and the field is short on programmers.
Another field welcoming of outsiders is finance. Working conditions are terrible (high stress, long hours) but pay is good for people with skills. Every major investment firm, actuarial firm, insurance company, etc. is looking for programmers and will convert you to understand their domain well.
Other engineering and science disciplines are tougher to crack, but if you’re looking to earn a degree or commit excessive amounts of study, can be great homes. It’s hard to get by in fields that aren’t desperate for programmers without a really strong intuition for the topic and potentially a really strong background in the right methods and mathematics. Engineering stuff tends to be dominated by defense and energy contractors, from SAIC to Lockheed to the thousands and thousands of little suckerfish companies sucking at the military-industrial complex’s teet.
There is some commercial presence to this as well, where companies mostly make software for the above sorts of companies to use. Big firms such as Siemens and Ansys have well-defined roles for software development with domain expertise. Small companies like Enthought and Continuum Analytics need cross-disciplinary thinkers to survive.
It bears noting that if someone is like OP and just starting their career, opportunities such as academia and national labs are open to them if they pursue the right academic path. These can be very rewarding domain-centric programming careers, but are a lot harder to transition to from other careers.
I’m actually in a kinda similar position to the OP in terms of starting my career, I’m 21 and I have 3⁄4 of a computer science BA. My programming+web development resume is very good, but it’d be interesting to branch out in to other stuff (just lately I’ve been taking Coursera classes on machine learning and related stuff). On the other hand, money is really important to me (effective altruism FTW) so if a field doesn’t have the promise of offering Silicon Valley type salaries (150K-ish being reasonably typical) for a programmer like me, I’m probably not interested.
My understanding was that finance was in the process of contracting right now; can you say anything about that? Having an excuse to learn more economics would be cool though. For some reason the idea of working for a defense contractor doesn’t appeal to me.
I’ve never worked in finance and don’t know that area well, but I get a lot of cold contacts from the finance industry and occasionally meet people who work as analysts writing software who indicate there is a ton of demand. I cannot attest to salaries, but people seem to imply they’re very competitive compared to other fields.
I work in what is essentially mechanical engineering. Money isn’t very important to me, so I don’t have the highest salary, but I turned down a job offer doing similar stuff in NorCal where the offer was above that. I’m in my late 20s.
No matter what path you choose, I encourage you to squeeze out all the room in your degree you can for stuff involving other disciplines.
Formal training means little in software development, but means a lot in fields where autodidacts are unheard of—it would go in your list of qualifications and you’d actually know the topics. I’ve never met someone who has taught themselves heat transfer or solid mechanics from scratch who seemed actually to remotely know what they are talking about, let alone communicate lucidly about it.
Job titles can be things pairing off terms like research/computational/computer/software/[domain] with analyst/engineer/scientist commonly. In my experience, most companies learn that it’s usually easier to turn an “x” into an “x programmer” than to turn a “programmer” into an “x programmer”, so it can be inaccessible to do interesting work in fields that you didn’t start in.
One of the most accessible fields for outsiders tends to be biology. Employers include the NIH and federal agencies, state research labs like http://labs.fhcrc.org/compbio/ and http://www.wadsworth.org/resnres/bioinfo/ , biotech firms like Amgen and Stryker, and university research labs. Many problems in biology are not that hard to pick up and the field is short on programmers.
Another field welcoming of outsiders is finance. Working conditions are terrible (high stress, long hours) but pay is good for people with skills. Every major investment firm, actuarial firm, insurance company, etc. is looking for programmers and will convert you to understand their domain well.
Other engineering and science disciplines are tougher to crack, but if you’re looking to earn a degree or commit excessive amounts of study, can be great homes. It’s hard to get by in fields that aren’t desperate for programmers without a really strong intuition for the topic and potentially a really strong background in the right methods and mathematics. Engineering stuff tends to be dominated by defense and energy contractors, from SAIC to Lockheed to the thousands and thousands of little suckerfish companies sucking at the military-industrial complex’s teet.
There is some commercial presence to this as well, where companies mostly make software for the above sorts of companies to use. Big firms such as Siemens and Ansys have well-defined roles for software development with domain expertise. Small companies like Enthought and Continuum Analytics need cross-disciplinary thinkers to survive.
It bears noting that if someone is like OP and just starting their career, opportunities such as academia and national labs are open to them if they pursue the right academic path. These can be very rewarding domain-centric programming careers, but are a lot harder to transition to from other careers.
Thanks for your response!
I’m actually in a kinda similar position to the OP in terms of starting my career, I’m 21 and I have 3⁄4 of a computer science BA. My programming+web development resume is very good, but it’d be interesting to branch out in to other stuff (just lately I’ve been taking Coursera classes on machine learning and related stuff). On the other hand, money is really important to me (effective altruism FTW) so if a field doesn’t have the promise of offering Silicon Valley type salaries (150K-ish being reasonably typical) for a programmer like me, I’m probably not interested.
My understanding was that finance was in the process of contracting right now; can you say anything about that? Having an excuse to learn more economics would be cool though. For some reason the idea of working for a defense contractor doesn’t appeal to me.
I’ve never worked in finance and don’t know that area well, but I get a lot of cold contacts from the finance industry and occasionally meet people who work as analysts writing software who indicate there is a ton of demand. I cannot attest to salaries, but people seem to imply they’re very competitive compared to other fields.
I work in what is essentially mechanical engineering. Money isn’t very important to me, so I don’t have the highest salary, but I turned down a job offer doing similar stuff in NorCal where the offer was above that. I’m in my late 20s.
No matter what path you choose, I encourage you to squeeze out all the room in your degree you can for stuff involving other disciplines.
Any advantages to taking classes officially over just doing independent study?
Formal training means little in software development, but means a lot in fields where autodidacts are unheard of—it would go in your list of qualifications and you’d actually know the topics. I’ve never met someone who has taught themselves heat transfer or solid mechanics from scratch who seemed actually to remotely know what they are talking about, let alone communicate lucidly about it.