I've been out in industry for exactly a decade. I know who they are laying off. I would bet heavily that these are the guys that like doing things the way they have always done things and are content on not improving it. They're the drafters that refused to learn "that CAD thing". You see it all over Slashdot. You guys sure like things the way you used to do them. "Why kids these days don't need to learn Assembly".
I spent a recent layoff learning Python 3.4. It's near impossible to get people off of 2.7 at work or Matlab. Why? Because that's what they learned during undegrad and grad school and that's where everything is written. And they do have a small point, I'm don't have time to go back and re-write 50 years of working software. Once we as a society figured out Linear Algebra in Fortran we stopped messing with it. Numpy, Matlab, et al are just pretty BLAS wrappers.
However at impedes a lot of progress. At this point I feel like I'm in Office Space half the time:
1st Bob: What you do at Initech is you take the specifications from the software engineer and bring them down to the hardware engineers?
Tom: Yes, yes that's right.
2nd Bob: Well then I just have to ask why can't the software engineers use the hardware engineer's API?
Tom: Well, I'll tell you why... because... software engineers are not good at dealing with APIs...
1st Bob: So you physically take the flash files from the software engineer?
Tom: Well... No. The project lead does that... or they're e-mailed....
If you're doing things the same way you did them even a year ago, then some lazier person that does your job is currently writing a script to do it that way. So in 50 years we can all look back and laugh at "Those idiots used to do it by hand". If you write a script to save you 1 minute a day, that's 4 hours a business year. If you write a script to save you and all of your co-workers 1 minute a day. That's an additional 4 hours per head per year. Start adding that up over a decade or two.
It's entertaining to watch you guys not wanting to use new tools, I just started writing new tools to use the old tools I wrote. I could reduce my manager's headcount by 3-4 and keep the same work level output with an improvement in quality. Software engineers have already done that, it's what continuous integration is for. Then they got tired of dealing with merges, so they wrote tools to automatically do merges if everything tests out.
CGP Grey's "Humans Need Not Apply" is a good video on the current state of automation. While I don't share quite his outlook his statements about what is going on right now is dead on. (Humans' will just start building warp drives instead of dicking around with what we do now). If TensorFlow can pick those images out that accurately they sure as heck can read the graphs I used to have to read much, much better. Give me the picture of a tachometer trace and I could tell you what's wrong it your car. I don't need to hear it, see it or know what's going on.
Last night on SharkTank there was a guy that had a mobile app that could take your measurements 20% better than a professional tailor, just by taking some photos and doing some math. If you were hoping to be a tailor and spend time measuring people, I have bad news.
Engineers these days use Simulink. Finding Engineers that can Code is hard. So we taught the engineers to play with block diagrams and taught the block diagrams to write C. And it writes better C than most humans. It easily meets ISO26262 (Automotive Safety) and DO 178b (Aerospace Safety) certifications. It's light years ahead of any open source project "Visual" coders available for Arduino. Some guys took the most boring parts of C and 'automated it'. Yet when "Visual coding" comes up on Slashdot you guys think 'it'll never work'. (Enjoy the unemployment line).
Jenkins is great for doing a lot of what I used to do 5 years ago. It doesn't need to replace everything but if it does 95% it's close enough and I can waste my days on Slashdot and then spend an hour a week on the other 5%. Scotty never did any work. He wrote a few AIs to handle the repetitive stuff so he could go on away missions.
The other half of what I have to do at work is 'TPS reports'. The fact that new software like Jupyter Notebooks exists means I can write my documentation, presentation and code in one place. I wrote a short script to kick out a company branded LaTeX document (for the engineers), PDF for the manager, Presentation for the Suits. It's win win for everyone. The suits can flip through it on their iPads and the Engineers can make pretty equations in LaTeX and everyone is happy and I just spent 10% of my time not copy and pasting crap into PowerPoint or Word.
I'm sure that you are all special unique snowflakes that have kept up with technology and that these guys will do exactly what you did, just for less. But I would put money on statistically, these are the Drafters that refused to learn CAD, the Engineers that refused to learn Simulink and the IT guys that refused to automate what ever they did every day.