It sounds like the kind of job you really want is going to be a bit of a unicorn. That means those kinds of jobs don't get advertised in job boards and have professional recruiters running around looking for candidates that fit. That in turn means that finding such a job is going to be a lot of networking and shoeleather. You'll probably have to go to a bunch of conferences, talk to people, and make contacts, and hope you can discover a place where your unique skills are a greater value to somebody's project than anyone with expertise in only one of those fields could be.
Well put. The standard practice is to hire a scientist and a developer, both with deep expertise, and have them work together. For a successful collaboration, it's obviously desirable for them to have some cross-disciplinary skills or experience. Ultimately, you're still primarily doing either development or research.
You are special. There are lots and lots of "software engineers" in the world. Very very few can bring scientific experience and knowledge to the job. I might look for a developer role in a large university project where they need programming skills and scientific rigor. Or a R&D person in a large software company or the government . These kinds of jobs aren't listed on Indeed or Monster. Attend conferences related to your field (don't attend the talks, hang around in the lobby and chat with people). Reach out to professors in your university or your field.
Make a list of the most interesting companies / areas you want to work in from a scientific perspective
Cold call or get introductions to their R&D leaders (principal researcher /director / VP). While connecting to something they or their company did, ask for a coffee meeting or phone call to learn more about their company and how it works.
Use this to Network network network. At some point a job will appear with interviews. Chances are good it’s with a good manager as they’re the ones taking time to build good teams and talent.
I did move from physics to becoming a SWE. I could put the knowledge I gained doing 3D rendering and GPU compute used for visualization and simulations in my academic jobs on my CV, and get a job as a SWE that way. Later I moved to another job where I could use my physics background to help develop a new sensor.
As for how to market yourself: first you should convert your academic CV to one that is suited for the type of companies you are applying for. Unless you wrote something that ended up in Nature or some other super high profile journal, companies typically don't care about your publications. What they do care about is things like: can you communicate well? How well can you organize things on your own? Do you handle stress well? You did a PhD, so the answer to those things is yes, you just need to write that in your CV in a way a company recruiter/interviewer understands, even if they themselves are not from academia. So you don't have two halves that belong to different resumes, you are just one person and you just translate your resume to the "language" that your prospective job provider speaks.
Finally, your list of skills does not need to be a perfect match for what a company is looking for. Of course, there needs to be some overlap, but as long as it means you can pick up new things quickly, it will be fine. That and being a good fit for the company's culture are the most important things.
I did not start out with a unicorn role, but in I found ways to apply my physics background in my current job.
Top-tier hedge funds are always looking for PhDs with engineering background, it’s a great combo of doing original research and being able to productionalize it
I was a studio recording engineer for about 7 years. I switched to software, and now I work in industrial global logistics. Job attributes I optimized for over the years: insulated from manufactured stress, autonomy, control over working hours, good relationships with my boss and coworkers.
A PhD means you can do novel research. As a full stack developer what novel subject(s) did you explore? That is the middle you are missing.
A big part of the problem is that you were spending time with tech stacks and frameworks. These have almost no practical utility value aside from attaining employment in a low skill area of software. I am saying that as a former 15 year JavaScript developer. Instead use your research background to solve real problems faced by businesses and users that you can measure.
I haven't done it myself but know a few people who did. They were all on the academic track and just made it happen and supporting their respective labs as postdocs. With an allowing or aligned professor I think it's very relistic in academia. From there you might find overlapping industry opportunities down the line. And I guess you have to be OK with pushing the envelope yourself.
I don't think it's at all as rare as I see other commenters say. I don't know earth sciences specifically but I'd be surprised if there is a STEM field where a strong SWE expertise isn't an asset you can put to regular use in research.
Not easy, but I have a friend who did this by reaching back out to his old professors and colleagues, figuring out what they needed, and ended up doing a swe project in his old lab and built that into a consultancy which does tech partnering for science.
Some examples: machine learning scientists and engineers; quants and (quant) developers.
In either case, you're primarily either a developer or a scientist/researcher. Unless you're at an early stage startup or in a principal/managerial role, chances are your time is better spent deeply focusing on one area rather than both. Either putting the system to production or doing research. A lot of the time, these tasks can be carried out in parallel -- while one person is carrying out research, the other can be improving the system.
I'm in much the same boat - however my SWE pivot was when I attempted to commercialize my PhD research along with my advisor. We had a startup for a few years and then got acquired by a global company. I now manage a team of SWEs and coordinate with SMEs in technical fields to make sure that our scientific software products are great in both areas. These roles exist, but probably not commonly as a straight hybrid - may have to lean into one and use the other as a differentiator/value-add. For me, I think I got here by caring about the customer experience first - which takes "whatever it takes" - software and science both. I have to be an evangelist for both of these things but only as a means to a common end, which is to help the end users expand their understanding and abilities with applied knowledge.
Maybe try finding a software engineering job at a place that also uses your scientific expertise. You may be able to find or create opportunities there. The position might not exist, but you can maximize your chances of something coming your way that needs both skill sets.
Allow me to suggest Research Software Engineering - https://society-rse.org/careers/rse-stories/
US Organisation - https://us-rse.org/ UK (but also worldwide) - https://society-rse.org/
There are RSEs who specialise in Earth Science, e.g. https://socrse.github.io/geoscience-sig/
It sounds like the kind of job you really want is going to be a bit of a unicorn. That means those kinds of jobs don't get advertised in job boards and have professional recruiters running around looking for candidates that fit. That in turn means that finding such a job is going to be a lot of networking and shoeleather. You'll probably have to go to a bunch of conferences, talk to people, and make contacts, and hope you can discover a place where your unique skills are a greater value to somebody's project than anyone with expertise in only one of those fields could be.
Well put. The standard practice is to hire a scientist and a developer, both with deep expertise, and have them work together. For a successful collaboration, it's obviously desirable for them to have some cross-disciplinary skills or experience. Ultimately, you're still primarily doing either development or research.
You are special. There are lots and lots of "software engineers" in the world. Very very few can bring scientific experience and knowledge to the job. I might look for a developer role in a large university project where they need programming skills and scientific rigor. Or a R&D person in a large software company or the government . These kinds of jobs aren't listed on Indeed or Monster. Attend conferences related to your field (don't attend the talks, hang around in the lobby and chat with people). Reach out to professors in your university or your field.
All the Best!
Make a list of the most interesting companies / areas you want to work in from a scientific perspective
Cold call or get introductions to their R&D leaders (principal researcher /director / VP). While connecting to something they or their company did, ask for a coffee meeting or phone call to learn more about their company and how it works.
Use this to Network network network. At some point a job will appear with interviews. Chances are good it’s with a good manager as they’re the ones taking time to build good teams and talent.
I did move from physics to becoming a SWE. I could put the knowledge I gained doing 3D rendering and GPU compute used for visualization and simulations in my academic jobs on my CV, and get a job as a SWE that way. Later I moved to another job where I could use my physics background to help develop a new sensor.
As for how to market yourself: first you should convert your academic CV to one that is suited for the type of companies you are applying for. Unless you wrote something that ended up in Nature or some other super high profile journal, companies typically don't care about your publications. What they do care about is things like: can you communicate well? How well can you organize things on your own? Do you handle stress well? You did a PhD, so the answer to those things is yes, you just need to write that in your CV in a way a company recruiter/interviewer understands, even if they themselves are not from academia. So you don't have two halves that belong to different resumes, you are just one person and you just translate your resume to the "language" that your prospective job provider speaks.
Finally, your list of skills does not need to be a perfect match for what a company is looking for. Of course, there needs to be some overlap, but as long as it means you can pick up new things quickly, it will be fine. That and being a good fit for the company's culture are the most important things.
I did not start out with a unicorn role, but in I found ways to apply my physics background in my current job.
Top-tier hedge funds are always looking for PhDs with engineering background, it’s a great combo of doing original research and being able to productionalize it
I keep the two halves separate.
I was a studio recording engineer for about 7 years. I switched to software, and now I work in industrial global logistics. Job attributes I optimized for over the years: insulated from manufactured stress, autonomy, control over working hours, good relationships with my boss and coworkers.
A PhD means you can do novel research. As a full stack developer what novel subject(s) did you explore? That is the middle you are missing.
A big part of the problem is that you were spending time with tech stacks and frameworks. These have almost no practical utility value aside from attaining employment in a low skill area of software. I am saying that as a former 15 year JavaScript developer. Instead use your research background to solve real problems faced by businesses and users that you can measure.
I haven't done it myself but know a few people who did. They were all on the academic track and just made it happen and supporting their respective labs as postdocs. With an allowing or aligned professor I think it's very relistic in academia. From there you might find overlapping industry opportunities down the line. And I guess you have to be OK with pushing the envelope yourself.
I don't think it's at all as rare as I see other commenters say. I don't know earth sciences specifically but I'd be surprised if there is a STEM field where a strong SWE expertise isn't an asset you can put to regular use in research.
Not easy, but I have a friend who did this by reaching back out to his old professors and colleagues, figuring out what they needed, and ended up doing a swe project in his old lab and built that into a consultancy which does tech partnering for science.
Apply to the research labs of the big tech companies. Both aspects will be valued.
It may be harder if you want to do only earth sciences, but if you're open to many areas of research, then the FAANGs will probably take you.
https://us-rse.org/jobs/
Some examples: machine learning scientists and engineers; quants and (quant) developers.
In either case, you're primarily either a developer or a scientist/researcher. Unless you're at an early stage startup or in a principal/managerial role, chances are your time is better spent deeply focusing on one area rather than both. Either putting the system to production or doing research. A lot of the time, these tasks can be carried out in parallel -- while one person is carrying out research, the other can be improving the system.
I feel like my scientific training is going to waste
Your training is a sunk cost.
It is also the source of soft skills.
I'm in much the same boat - however my SWE pivot was when I attempted to commercialize my PhD research along with my advisor. We had a startup for a few years and then got acquired by a global company. I now manage a team of SWEs and coordinate with SMEs in technical fields to make sure that our scientific software products are great in both areas. These roles exist, but probably not commonly as a straight hybrid - may have to lean into one and use the other as a differentiator/value-add. For me, I think I got here by caring about the customer experience first - which takes "whatever it takes" - software and science both. I have to be an evangelist for both of these things but only as a means to a common end, which is to help the end users expand their understanding and abilities with applied knowledge.
Maybe try finding a software engineering job at a place that also uses your scientific expertise. You may be able to find or create opportunities there. The position might not exist, but you can maximize your chances of something coming your way that needs both skill sets.
Do you have a CV for more context? Work in a more academic setting is always highly context dependent, as you know.
Chances are, there are a handful of labs, somewhere that could benefit from the overlap, but finding them is like finding the needle in the haystack.
Have you tried talking to someone at places like ESRI?