Although I work for an "engineering" company (in Canada), and most of our product is in the area of embedded comms, I have an even split between engineering and computer science grads in my group. I've found that there is no real difference between the two groups in terms of ability or creativity. Both types are also very capable in terms of understanding the H/W and the intricacies of driver level code. In terms of salary, both types are treated equally. The firmware architects in my group are comp sci types and there is an even split between engineers and comp sci types in the team lead and developer positions. I also have technologists who can run rings around an average engineer (or comp sci) type.
Perhaps we need to expand the definition to include others who are more than capable of doing the work traditionally described as engineering.
In our company we class all of the above as "engineers" although not all have graduated from an engineering program.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.