Even among EEs, there is so much specialization, it would be easy to stump a "real" engineer with questions that are outside of his area of expertise.
Ask a digital EE, even a very talented one, to explain the difference between S11, S12, S21 and S22 and you may get a vague answer like "I learned about that in school a long time ago but I never had to use them."
Ask an RF guy, or a data converter designer to explain how a cache memory controller works and you may get a similar "huh?" kind of blank stare...
The question depends upon what type of engineer you are dealing with. EE should know EE things, SE should know softwre things, and CE should know civil engineering things. So you really have to put this question in context.
As a systems engineer, I could answer correctly on a wide range of engineerng topics that are not part of any particular engineering field.
Plus good engineers, are also knowledgable on any engineering discipline that interacts with their field.
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.