Thread regarding Qualcomm Inc. layoffs

Don't settle for less; and if you take contract positions, insist on 150% of the reasonable hourly wage for full time. You'll have to pay your own health and disability insurance, which is expensive. From my own job hunt, I can tell you that the most in-demand skills are Java, Linux, C/C++, C#, SQL, and knowledge of cloud based software with Linux/Windows interface. Even if you don't want to spend a year or more learning the SW side of the business, you can easily make six figures in Silicon Valley doing cloud based system set-up, or even website design! I learned basic web design for my own amusement from from a technical book I picked up on Amazon. There's also a lot of information available online. If you're motivated, you could probably learn w/o the $11,000+ cost of a programming boot camp. One advantage to the boot camps is their (--allegedly--) high placement rate upon completion.

If I had a choice to made 240k in the bay area versus 80k in san diego, I'd go to the Bay Area. It's simple economics.

Good idea on learning connectivity. Probably some classes you can take. Where is QC's API connectivity group located?

If shifting careers into web based software I would recommend adding Javascript to that list. And try a development bootcamp for skill acquisition instead of going back to school for a expensive Masters in CS. Of course the pay in those careers are not at qcomm level but maybe it can help salvage your career, also afterwards if you are entrepreneurial you can start your own company and not have to work for anybody (ideal goal for financial independence). http://www.hackreactor.com/ ; http://codingcamp.us/ ; http://www.skilledup.com/articles/online-alternatives-coding-bootcamp ; http://www.makersquare.com/ ; https://www.bloc.io/ ; http://www.devleague.com/

Most not all of the qcom engineers in qcom cant even find a job in commensurate with their current salary level

All are smart but staying in qcom for long time their skill set vanished and they aged as well

It is difficult for a middle-aged engineer to break into new field which prefers young people that too on visa

I am just being realistic about starting out in another field....that's why I said $80K. I would certainly hope that down the road that would increase.

I make more than 3X that now, but realistically that won't be replicated in San Diego soon. Many of us need to face this reality and downsize. I really don't mind doing that...its just the right and logical thing to do.

I have a good nest egg and could make it 20 years at this point, but not quite enough to guarantee a full retirement of 30-35 years.

Thanks for the comments, they are actually quite helpful.

For you hardware types, the best thing is to ease into a hardware+software time of job and the, over time, transition into pure application software and/or enterprise software if you want to do that. I'd start with brushing up on embedded software so that you can market yourself as someone that can design both hardware and embedded software for IOT devices. (That would require you to brush up on your C and C++).....When you get a chance to work on IOT devices, I'd take the opportunity to learn how to write mobile app software on both Android and iOS with specific emphasis on the connectivity APIs and any sort of APIs to integrate to raw hardware outside of the phone. While there are many people that can write iOS and Android apps, there aren't many people that can write apps that integrate with hardware or know what they are doing wrto writing software that uses those connectivity APIs. Connectivity API's include wifi, wifidirect, bluetooth classic, bluetooth low energy, USB/HID accessory, and any sort of proprietary apis such as apple HomeKit, apple HealthKit, iBeacon, etc. If you have a basic understanding of hardware, and can write embedded C software and also have android and ios app development (with connectivity experience) in your bag of tricks, you should not have any problems finding any job. I didn't have any issues finding opportunities down here in SD, and I'm sure if I seriously considered the bay area, I wouldn't have any issues there too.

EE in software is priceless. I would concentrate on low level drivers in linux kernel. I am at the same position as you are. When there is a need to put a scope on i2c line, all pure sw guys have no idea

80K? Are you serious? New grads make 100K. Why would you settle, I don't get it.