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.
Drones are, in essence, flying autonomous vehicles. Pros and cons surrounding drones today might well foreshadow the debate over the development of self-driving cars. In the context of a strongly regulated aviation industry, "self-flying" drones pose a fresh challenge. How safe is it to fly drones in different environments? Should drones be required for visual line of sight – as are piloted airplanes? Join EE Times' Junko Yoshida as she moderates a panel of drone experts.