mjhjmtu

My real love is scientific computing, but I'm generally interested in nearly every academic field — through undergrad I've had research computing positions in social psychology, electrical engineering, volcanology, and pharmaceutical sciences. Now I've graduated, and I'm at a different university doing data analysis in cognitive science. I like it, but I have a long list of places I'd like to live and fields I'd like to learn more about, and my "career plan" is to move every 3–4 years and work at a different university in a different field, always doing scientific computing/data science though. I'm not too concerned about getting a huge list of academic accolades or getting a PhD right now; I'd rather just be doing interesting work.

I've mentioned this to several professors and graduate students who have asked about my plans, and they always react as if I've said I want to run off and join the circus. Is there some truth to how they react? Am I hurting my career this way?

I'd like to clarify that I just want to be doing data analysis. It seems like nearly every lab needs people to do this, so I don't see how I'm a funding leech.

As a data scientist myself, I have found it rather difficult to be a journeyman data scientist in academia. Yes, people need their data analysed; no, they do not want to pay for your full salary, benefits, and office space. Nor are they necessarily going to hire an outsider to analyse their data. They can get their postdocs/grad students to do it.

I have met repeated resistance to being taken onto projects as an outside data analyst. Certain STEM disciplines are especially bad with this. Because I have a PhD, I can find full time positions that allow me to be housed in a department, teach classes in that department, and then take on outside projects as I find them. These outside projects are never enough in and of themselves to provide enough work for me to retain my job. The fact that I can do independent research and teach classes is what allows me to do what I do.

I just think being a journeyman data analyst in academia can be a rather tough life, and you may not have much freedom to actually decide what type of subjects you are exploring. In my experience, you may rank below even the master's students and will possibly be paid subsistence level pay.

I think the other answers have mis-understood the OP's goal. He explicitly says that he wants to be a scientific programmer assisting other folks' research programs, not pursuing his own. Such positions do exist at every major research university. How common they are varies by subfield. In my experience physics departments generally leave all the programming to their students and post-docs, while life sciences department will hire quite a few software developers and data analysts, just as they hire a lot of wet-lab technicians. There is a lot of computational work to be done these days that requires fairly mature engineering skills, but is not novel research. Having your chemistry Ph.D. student set up a secure and robust web application is probably not a good use of their time.

To respond to the OPs question: what you want is not impossible, but you'll have to be lucky to pull it off. While there are scientific programmer positions at every major research university, there are not a lot of them compared to the non-academic world, and they generally don't pay nearly as well. I think PIs find hiring for these positions difficult and time-consuming, so they prefer folks looking for long term positions. Sometimes, one of the functions of these positions is to provide some overlap in institutional memory. Bit rot sets in rapidly each time a student graduates. If you aren't even going to stick around as long as your average Ph.D. student, your utility to the PI is diminished.

On the other hand, many of the grants that fund these positions are time limited. Projects that only last two to three years seem to be pretty common. That would seem to match pretty well with your goals. Unfortunately, at least in large departments, there seems to be a small cadre of programmers that get shuffled around projects as funding comes and goes. You'll be competing with those folks, and as they have a known local track record, it puts you at a disadvantage. For the same reason, constantly switching fields, would also put you at a disadvantage. Software skills are highly portable, but there is always some domain knowledge that's crucial as well.

I think your chances of success will be better if you stick to one field, say the life sciences. It will also help if, early on, you can find work on a high profile project, with a prominent PI.

I'm pretty sure that the funny looks are because people are making the assumption, probably warranted, that you will be fairly shallow in the work you do. Normally academic research is narrow and deep, so this plan seems too unlike what they expect. Some fields take a long time to learn and even more time to be able to deal effectively at the frontier of knowledge. Someone who wants to do a lot of relatively simple (in their view) things has less value, by far, then another who is a well known expert in a specialized field.

Along with this worry is that you wouldn't be a lot of help in leading students to a research (narrow, deep) career as you are a sort of "dabbler" in things.

I don't criticize your plan. Being a polymath (even a shallow one) can be a rewarding life. But deep and narrow is what is more valued in academia.

At non-research institutions (primarily small undergraduate colleges) you might find a better reception. But even there, not having a doctorate is usually a deal-breaker.

Core Facilities

One opportunity you may consider is seeking employment in some kind of core facility. At least in the United States, research intensive universities often have centralized organizations available to assist research from any discipline needing their services.

Often these are organized around specific equipment (such as specialized genomic sequencing) or other resources (such as animal care). However, I have definitely seen examples that are dedicated to providing computing services, including programming and statistical analysis.

Being employed at a research core facility would likely offer you the opportunity to focus on the tasks that you love, without needing to develop your own research agenda or teaching. However, the pool for these jobs is significantly smaller.

An example of such an organization is the University of Kansas's Center for Research Methods and Data Analysis.

Non-Academic Positions

A second opportunity could be leaving academia. I've made a career as a data analyst and I've switched industries reliably every 3-5 years. Currently I work in a university analyzing their research and grant performance data, but I've also worked in both private firms and other governmental agencies. Outside of academia it is far more common to see people leave for greener pastures on a regular basis.

Have you considered working on the supercomputing side? My university frequently makes hires in that area, and not only in engineering — some are for positions that assist faculty with supercomputing facilities, and the like. These facilities are usually funded centrally from the university, and/or with large external grants, and so can hire a lot more freely than departments or units with one-off data analysis needs.

To offer a different perspective: the behavior you're describing would be very welcomed by most companies. At most places that are hiring data scientists, 3-4 years of tenure is more than they get from many/most people they hire. Intellectual curiosity like you're describing can easily be seen as a good thing in interviews.

There's certainly no shortage of companies with data in all kinds of different domains who are desperate to hire experienced and interested data scientists to analyze and make sense of their data. Heck, even staying within the same company, you could pretty easily switch the field you're working in. My last job, I analyzed fraud data, mapping data, weather data, product recommendation data, server log data, all kinds of location data, food data, and marketing data, all in under two years.

Many companies publish their results publicly. Some do this through peer-reviewed journal articles, but many more publish through blogs and conference talks. So if you're looking to advance the state of public knowledge in a given field, I think you can do that at a company- in fact, most would be pretty excited to hear that you want to help them get publicity by making findings public.

My current job is actually somewhat similar to what you are looking for. (A software developer / analyst that assists various research groups on a short term, 6-18 month, basis.)

It is entirely possible to do this sort of work long term, but there are at least in my experience several things that you will want to keep in mind. (To simplify, I will refer to the group or groups you would potentially be interacting with as 'the clients').

• One of the core values that you will be able to provide the clients is a bridge between them and their universities greater IT sector. This means that you will not only likely be the one doing analytical / development work, but also interfacing with people that are setting up and maintaining the infrastructure, are in security and governance, etc. For this reason, you will be far better off finding a large university that does a wide variety of research, rather than moving universities constantly.




• The pay for such positions, in comparison to their workload is far below that of industry. (In my area, about 50-60% of what similar work would make in industry). Working at a university does have a variety of other benefits, but if pay is an issue for you, you may want to look elsewhere.



• 
  

  Even with having a lower pay than industry, developers and analysts are expensive. (Expect roughly after benefits that you are going to cost your employer twice your salary.) If you are going to want to have a position working solely on client problems, and not general IT/university systems, your likely going to need to be funded mostly/exclusively by the client's grants. While this seems reasonable on the surface, depending on the university's culture and environment there are several caveats:

  
  
  

  1. Your mainly going to be working on medium sized projects. (Multi million, decade long projects tend to have their own full time, long term staff members. These are common if fields like physics.) Smaller short term projects (<100K) are not likely to have the money to support a separate analyst, and even less likely to have that money put aside for IT/Analyst work.

  
  

  2. While I understand you are wanting to just do the analytics, expect to be doing a lot of software development. In general most of their analytics are going to be done by PhD students. (Far cheaper, and learning how to analyze and conduct research is why they are there.) However, depending on the field, they may be far less likely to be capable/interested in doing development work.

  
  

  3. I mentioned this briefly before, but depending on your university's culture, researchers might not even be thinking about including funding for a position like yours in their grants. You will likely need to be very proactive to find funding for yourself.

  
  

  4. You are going to likely be working directly with clients, This can be both a positive and a negative. (The benefits and woes of this have been more than adequately described elsewhere, but I would definitely make sure to read up on it before finalizing any plans.)

  
  

If you have any questions about this type of system, I would be happy to try and answer them.