G. Mark’s Answer
I like Irida's answer. As the saying goes, "Do for a job what you'd do for fun and never work another day in your life." I was extremely lucky to have been recruited a long time ago by a famous research company. They expected me to study what I would do anyway. But bear in mind that a "computer engineer" can end up doing a lot of different things. In my case, the company I worked for sent me for my MS degree, and there I learned electronics, robotics, coding, architecture, and on and on. A blast. The company I worked at had a philosophy of engineers being "general purpose" -- you would just do what's necessary to get the project done. I had a lot of latitude in design and architecture and working with customers and solving problems. We were expected to work a project from the original problem statement to a proposed solution, requirements, design, coding or building hardware all the way to working with the customers and teaching how to use it. After awhile I specialized in architecture and then in Systems Engineering. So you might end up doing all of these things or you might specialize in, say, "solutions engineering", where you would be responsible for communicating to various engineers and customer organizations. So the answer to your question is that it can vary quite a bit. But a really nice thing is that a lot of companies are aware of the fact that a happy engineer is a good engineer. Sure, there are times when you'll be expected to do something tough to get the problem solved. In my case, I had a great relationship with our legal department, so I got a lot of odd-ball, interesting problems to solve and inventions to come up with. Or you might find that you like doing what I've done in some companies, and that's assemble the entire system from scratch and get it running. You'll find your niche. It's quite a satisfying career.