@kfield: I can't see the downside of going out into the working world and getting some real, hands-on experience.
I think it's true that having some real-world, hands-on experiance benefits everyone -- it woudl give the person in question a richer perspective if he/she subsequently decided to return to academia. The big downside is that once you are out in the world earning a wage, it's really difficult to return to an academic environment (unless you are independently wealthy)
@Frank: I agree, it depends on the company and product type. If you step away from the EDA businesses, there are many examples where PhDs are engaged in product development including hands-on coding. Google & Yahoo are great examples where you find an abundance of PhD's doing handson work!
Unless the student is pursuing a career in academia, I can't see the downside of going out into the working world and getting some real, hands-on experience. He will get a better understanding of what it is to be an engineer and what it is he likes and doesn't like about doing the work. It would be a pity to rush into a graudate degree only to find out that isn't at all what you really want to do.
Let's differentiate "working in industry" from "developing products." At the risk of over-generalizing, I would say ask a member of a U.S. IC design and/or verification team how many PhDs were involved in their last project and the answer will mostly likely be zero. Go to the EDA companies whose tools they used to design & verfiy that IC and ask them how many PhDs were involved in writing & testing that software and again the answer will most likely be zero. But ask them who developed the algorithms that those tools use for logic synthesis, timing analysis, power analysis and automated place & route, and the answer will most likely be "a bunch of PhDs."
Frank, I appreciate your points. I think even in the US, perhaps more in Silicon Valley, there are more PhD's working in the industry than in other places.
I spent three years of my life in academia and I do miss it. Working in the industry that too in startups has been more rewarding though not financially!
Max, is the student's name Razi or Ravi? You very well know there's many a slip 'twixt the cup and the lip! Nonetheless, it is that proverbial fork in the road that one comes to in their life time. My generic advice would be to make a choice that gives you the most flexibility to go either way at any stage in one's life!
Each person should assess his or her own career goals when considering this decision. If one's goals include conducting research and publishing in academic journals, then by all means go for the PhD. If one's goals include someday returning to academia as a lecturer and/or researcher, a PhD will be an essential qualification.
But if one's goals are to obtain employment in the private sector as a working engineer, involved in the design, development, testing and/or manufacturing of for-profit products, the value of the PhD is less clear, and there could even be some negatives associated with it -- pricing onself out of the market for certain jobs, or giving the impression of being too specialized.
My thoughts on this are from a U.S. perspective and the situation may be quite different in other countries. The degrees themselves are, I think, perceived differently in different countries. It is my impression that it is more common in Europe, for example, to find PhDs working in product development than it is in the U.S.
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. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.