Ask HN: Moving into Academic CS from Industry?

If you can learn something for 5 years in your 20s, then it is going to be 10 years in 30s, 20 years in 40s and so on.

Do you have a friend in any of those field? Sometimes academia ask for the number of published papers and if you can collaborate with a friend to publish a few papers it may help. It's also useful to see if you enjoy the process when you know how the sausages are made.

Get on the speaking, lecture and conference tour on your topics of interest. If you have talks on youtube or online courses, that will help. Find people to publish some papers with and reach out to dept. heads with your CV. You don't need to show published papers if you're working in defense etc. In general though, get the research/papers conversation started with colleagues and start interviewing (and say you're working on publishing). Assistant/associate prof. bars are kinda lower at lower tier schools, but not by that much. In general, its better to apply to jobs that have listings as internally listed jobs often have a candidate in place for them. Good luck.

I think lots of European universities, where there is a high demand for CS/SE lecturers and engineers, may easily take someone with your profile for a lecturer (teaching-oriented) or (permanent) research engineer position (R&D-oriented). That is a good way to enter an academic career without a PhD, if you know where to find this kind of positions.

The UK and Scandinavian markets are quite straightforward and will not have any local language constraints. Hiring processes are also simpler, without requirements that are hard to meet for an outsider. The Netherlands and Ireland are also worth considering.

In the US, I think the market is a bit more competitive, especially at R1 institutions. Happy to provide more advice via email.

While it might be better if you better defined what you think the "academic career path" is, I'll throw out my experience . . .

I work as a programmer at an academic/research institution. But the job is just normal IT and light programming. I think finding a role similar to mine would be easy for you. Your MIT math undergrad will probably be more than enough credential signaling for that type of job to go along with your professional experience.

My path back to this environment for work goes roughly: earned MS in CS directly after BS in CS, two longer tenure jobs in industry (8-ish+ years total) after grad school, returned to academic/research institution because of personal network and also having skills needed for new role at institution. I have been here for 10+ years. Much of that time it seems like my earnings were at least 20% less than market rate for my region. But the pace of the job was easy and many people "settle in" to these jobs.

There is some autonomy here and a little room to stretch your day-to-day work to fit personal interests. But much less than you may expect. The work environment is not THAT different than industry and I personally have found that it is oddly more political here than expected with respect to who gets to do what work. I have been able to be involved more directly with researchers as a "side gig" when my day-to-day job responsibilities allowed. I probably would have left this role but personal+family responsibilities made the flexibility of the job hard to move on from. I am also in an unusual position wrt to funding - our group is heavily funded by hard money, so we are significantly less dependent on grants than even some research/teaching staff at my institution.

Your academic interests are probably going to be hard to fit in - those are "pure-ish" CS topics. I know some PhD applied math guys who do research computing support and their roles are often limited to helping with existing libraries with users of a research compute cluster. They aren't doing much applied math . . .

Are you willing to pull an extra stint of time in grad school for a MS or PhD? Joining a good research team and publishing with them could build up your CV for the academic job market. It isn't super critical unless you want to be research faculty somewhere . . . Some CS programs have a "professor of the practice" job role that could be attractive but it usually involves significant entry-level teaching requirements.

Not sure if any of this is helpful. Good luck figuring it out.

Not impossible, but very difficult. Reading between the lines it seems that you are underestimating the effort involved. You say that you are interested in type theory. Do you know everything about Hindley-Milner systems, lambda calculus, System F, etc? Great! That's the very basics and what you will learn in a CS master program at any reputable university. But to actually do research in this area, you need to know about all major results published in the field since the 1970s. Learning all that takes a lot of time. Then you need to learn the practicalities of research, how to write papers, how to write papers that gets accepted, etc. Phd programs aren't multi-year affairs because academia wants to prevent students from progressing, it's just that these things take time.

Then there is the financial side too. You're unlikely to ever earn as much in academia as you do now as a developer with 16 years experience. Phd and postdoc salary may be 1/2 or 1/3 of what you're making now. Then there is the age thing (16 years of experience implies you're 35+)... Your professors and supervisors might be younger than you.

But if you fed up of writing crud apps or bug fixing the shittiest t-sql code in the world then maybe it is worth it. If you've done something you didn't like for 16 years then it is time to stop and reconsider.

I'd say take a couple of courses first and see what happens.