The engineering resources are not though. The work has to either be done by the Phds themselves or by student workers. Phds don't have enough time and student workers have very little time and no expertise.
There are some limited SWE positions in support roles, but as you can expect the pay is not competitive.
For some reason even in academic departments where we can build billion euro clusters the people are still paid utter crap.
Most comments note how the pay is less than FAANG; eg the top voted comments:
"Pay is pretty good by almost any standards except FAANG."
And elsewhere:
"The pay at a DOE lab is less than FAANG (PhD student interns might be around $80k/yr and starting staff scientists maybe $130k/yr), but the tradeoff for some people would be the research-flavor of the work, and the flexibility."
etc etc
I may not be a quality engineer, but I'd be interested. That's a long enough time frame for me.
But by what I hear from German academia the pay is bad, the environment is "meh" and the contracts have to be renewed in relatively short periods (yearly?). That makes an otherwise interesting field a hell of a lot harder to choose.
We are an academic group (sort of) that is looking to stand up a server or so for some public-facing apps and databases, but it's like no one has ever heard of such a thing. They keep giving me servers that are behind a firewall and only accessible on-campus.
We could maybe do AWS or Azure, but that is really expensive and not really covered by our (government) funding. Plus, any time you want to do something like that (particularly with a company the university doesn't have an existing contract with), you have to get several layers of bureaucracy (including lawyers sometimes) involved. We are a state school, so you can guess how fast that moves.
In general, it's easier to ask for a $500k instrument, or take $10k trips to conferences, than get $10/month subscription for some web hosting company. Academia can be really behind on this front.
(For me, academia is generally ok and fun in my current position, but this part is getting ridiculous)
Although to a lot of reviewers a server is a server. “You have a multi-million dollar compute cluster available, what do you need another server for?”
And tailscale can also give you a private access to any resources even if it's behind firewalls and all that (say you want to access the gpu cluster from your laptop at home).
And they can all run in user space without elevated privileges.
Had to fight to get paid most months; but the $2mil grant for a computing cluster went through and the Supervisor never had a problem getting their monthly trip to a conference through.
First, as you say the incentive structure is wrong: projects are led by researchers and the incentives for researchers are around publishing not around creating good software. There's virtually no credit for making software that is well-written, robust, has a great user interface etc.
Secondly, the funding structure for projects tends to be grant-based. It's extremely hard to get funding for general ongoing development. I saw lots of projects get initial funding for a couple of years, the funding stopped and then the project had no money even for the most basic support or server costs etc. Sometimes you could grant funding for new features and could funnel a bit of that into support but it did require a constant regular stream of grant applications, as often of course you don't get them.
My salary was certainly largely funded by grants - I had a permanent job and there was some allowance for gaps between funding to cover that and because of the type of work I was doing I could do some internal work too in those gaps. It's hard to manage funding that comes with short-term grants. You just can't recruit good people to short-term contracts that quickly before they are supposed to start, especially for what universities can pay (in the UK there are set pay scales, so if you don't manage anybody you basically can't be paid more than a certain amount, plus there are strict processes about recruiting, for good reasons, so it's hard to do quickly).
> The reality is that building systems is really hard. It requires a lot of resources, and a lot of engineering. I think the incentive structures in academia aren't very suited for this kind of costly, risky systems-building research.
I think this is the key point. I've heard similar from friends in industry and academic positions.