News for hackers. Stuff that matters.

throwawayjobsea

No, for two reasons:

1. The preference (note: not requirement) is quite explicit.

2. No one in CS (literally, even the upper echelon) has the applicant pool that provides them with the luxury of prioritizing on the basis of diversity.

> How's the market look for MS holders with experience in industry?

If you like teaching and can deal with the cut in pay, you should seriously consider applying to lower-ranked colleges/universities that have teaching positions. You will get an offer, and you will make those places so happy!

> but the pay tends to be 1/2 what I make in industry, with similar benefits.

It's both far worse than that and far better than that, depending on the place.

1. Half is pretty good for lower-tier places. My prototypical offer was around 29% of my best industry offer in terms of raw amounts. Maybe close to half after counting up benefits and doing the CoL adjustment?

2. My best academic offer was about 50% of my best industry offer in terms of what typically goes into comp calculations in industry (salary/stock). But after cost of living adjustment and counting the value of the tuition (divided over a 30 year career and multiplied by the number of children I'd like), the academic position was within 20%. Which is pretty good. So make sure you're counting everything (including tuition remission) and accounting for cost of living (college towns are often dirt cheap compared to hub cities).

3. Oh, and make sure you know what "9 month salary" means. At some places you really can disappear all summer. At other places you need to work all summer even if not teaching; the salary is only nominally for 9 months.

> The teaching positions might be different

They are very very very different. You have the normal "applications close on / for full consideration submit materials before [month] [day]" thing. But if you submit your application on that day (or anyways, pretend you did) then the typical schedule was something like:

  * phone interview the next week
  * onsite between one week and one month from phone interview
  * offer within a few days/weeks of onsite.
Actually, my teaching job process moved much faster than my industry job process.

Maybe at least in CS we need to move to a "rolling basis" style.

I actually agree with parent's point here, but for a different reason.

Many of these teaching positions are in the range where you will be dependent on social security / medicare in order to retire. I consider that dependence effectively poverty in this country. Demographics, budget, and political climate all suggest to me that these two safety nets won't be available in 30 years.

When you're working from 18 or 21 onwards and saving, mid 5 figures over your whole life translates into a survivable retirement.

However, if you don't start saving for retirement until after graduate school (late 20s) and at that point start off at mid 5 figures with terrible benefits, little upward pressure on your salary, and lots of student loans, you're basically dependent upon the government for any retirement. Especially if you care to reproduce.

So, some of these teaching jobs really are poverty wages, given the opportunity cost of graduate school. The poverty comes at 65, but it does come.

What these places need to do is pay well and reduce course loads. But many of them cannot afford to do either.

(Oh BTW google's shooting you emails every week or two.)

> But the biggest problem is this: academics are afraid of anyone who hasn't demonstrated commitment to their system by earning a Ph.D, writing a thesis, and accepting terrible wages and living conditions for a number of years as junior or adjunct faculty. So the number of 50 year old software engineers who decide to semi-retire and take up an academic position is effectively zero.

A few thoughts:

1. Many schools who are willing to give up on the "traditional" job candidate profile are still have a very hard time hiring. I know this from many, many conversations with department and search committee chairs and lower-ranked places.

2. Hiring non-phds isn't always an option for higher-ranked (and especially mid-ranked) institutions. It'd be great if Google only used the data they collect in ways that enhance their users' experience. But it's unreasonable to expect an ad company to not use their data assets to sell ads. There's something analogous going on with hiring non-phd faculty to teach -- institutions involved in a rankings war should only care about maximizing educational outcomes, but we live in the real world and metrics do matter.

3. Most importantly, maybe these places are right to be skeptical! Engineering isn't teaching, and many of those who can do, cannot teach. I've seen a lot of situations where semi-retired industry folks don't take teaching seriously. The permeated anecdotes from industry are valuable, but not valuable enough to compensate for poorly structured courses or failing to explain tree rotations in an intelligible way. It doesn't help that teaching loads demand a 40 hour week, but teaching salaries only pay for 15-20 hours of even semi-retired engineering time.

I'm a phd student currently on the job market for more teaching-oriented (but sometimes still tenure-track) positions.

Outside of R1, the article actually understates the shortage. It's definitely a seller's market, and many of the buyers are viscerally panicked about failed searches.

Look at CS enrollments over time. This is a unique point in history. The phds graduating now went through undergrad at a historic lowpoint in enrollment (the 200x post-dotcom-all-the-jobs-are-going-to-India era) and are graduating into the single largest upswing in undergraduate enrollment in the history of the field.