I was looking into getting more coding based role. I got an offer at Siemens as a systems test engineer. Seems very hardware based but there’s some coding involved. Mostly embedded and automation testing. Seems like a decent bridge between my semiconductor engineer role to software engineering in the future. Been learning to code on my own so any role with some coding gets me in the right direction. The other Offer is a Samsung process engineer role with data engineering elements. The manager said they use Python to work with the data thats in the cloud. Was sent a whole course I was going to learn which involved Python R and machine learning at the end. Both roles seem to have some elements of coding on the job which would open up a path to being a software engineer later down the line. All that’s the con is that I’ve heard very bad things about the wlb at Samsung. But I’d be on shift schedule 8-5pm so not expected to clock in any time after that. So that may not be a factor. Locations Samsung: Austin at their fab. TC: 100k Siemens: Atlanta. TC:104k YOE: 1.4 Goal is to be there for 1-2 years and then leave for a full dev role externally. I’ll be targeting FANG companies and will work on LC the whole time. #tech #google
If you are really planning to be for 1-2 yrs then go for Siemens. You’ll make lot of contact to other companies or get exposure to broader application area that may include Samsung if they’re using siemens products. Tc is painfully lowest across the industry but you’ll get your wlb
It’s also a great place to weather the recession and hiring freezes. Better have a job than be laid off.
Siemens - so Mentor Graphics arm? I used to work as legal at semi, so not the most knowledgeable on SW but any junior level work relating to EDA seems too semi-specific and/or hardware based. With Samsung foundry at least you get to meddle with R and Python.
It’s with their EV charging division. So a new division. And it does seem like that at Siemens. But will that skillet be transferable into tech or just Siemens specific ?
From Google search embedded testing doesn't look like too much coding involved.