Transitioning from Software Development to Engineering

[Chubigans]

Hello.

I graduated 1.5 years ago with a major in Computer Engineering. I have been programming since I was a young child so it seemed very natural for me to go into software development. Throughout my undergrad I focused on the easiest path to me (computer science classes were a breeze) while doing decently well in my engineering classes (electronics, digital systems, dynamics, mechanics of materials.) The engineering classes seemed very difficult.

During my internships I worked at huge engineering organizations (NASA, Lockheed, my school robotics lab) but I was always doing mostly software (C++, Java/Android, and C#.NET). My current job is as a web developer at a startup where I am about as far from hardware as I can get.

I don't see myself as much of a true "engineer", but more of an embedded software developer. I programmed the microcontroller (an Atmel XMEGA) for senior design and had a lot of fun. I loved writing low level routines for electronic devices like motor controllers, sensors and LCD screens. But I felt like I was at such a "hobbyist" level that I wasn't qualified for a real "embedded job".

I've never had the title "embedded engineer" and all I know is how to program a few very simple microcontrollers. What do I need to learn to be a well rounded "embedded software engineer"? Would a second degree that teaches me more about hardware and mechanics be helpful? Do I need to improve my CAD skills? Or should I be compiling linux kernels and writing device drivers for that? I just don't really know WHAT skills I would need or how to get them.

 

[analogdesign]

Get an MS degree in EE. That's by far the easiest way to get where you want to go. Then you 1.5 years in Software will be included as your experience when you get a job out of grad school.

 

[JakeBrodskyPE]

analogdesign's advice is sound. Allow me to suggest that you look into taking the Fundamentals of Engineering (FE) test and then seek a PE in software engineering.

There are a whole lot of embedded critical safety applications and they'll go begging for people who are willing to put their name on their work. I speak as one who uses them.

 

[donpacino]

I agree with analog.
I know it seems like common sense, but make sure the EE program you look at has good computer engineering classes. If the school has separate EE and CE programs, I recommend going to computer engineering.

 

[Matrix0]

I understand your concerns about transitioning from software development to engineering. It can be daunting to feel like you may not have the necessary skills or experience to be considered a true engineer in your field. However, I believe that with your background in computer engineering and experience in software development, you have a strong foundation to build upon to become a successful embedded software engineer.

First and foremost, I would recommend focusing on gaining more experience and knowledge in the areas of hardware and electronics. This could include taking courses or workshops in microcontroller programming, circuit design, and analog and digital electronics. You could also consider seeking out projects or internships that involve working with hardware and embedded systems.

Additionally, it may be helpful to expand your knowledge in other areas related to embedded software engineering. This could include learning about real-time operating systems, firmware development, and device drivers. You could also consider gaining experience with different programming languages commonly used in embedded systems, such as assembly or C.

In terms of a second degree, it may not be necessary if you are able to gain the necessary skills and experience through other means. However, if you feel that a degree program would provide you with a more structured and comprehensive education, then it could be a valuable option to consider.

Lastly, I would also recommend networking and seeking out mentors or professionals in the field who can offer guidance and advice on how to become a well-rounded embedded software engineer. They may be able to provide insights on specific skills or experiences that would be beneficial in your career path.

In summary, transitioning from software development to engineering may require some additional learning and experience, but with your background and passion for embedded systems, I have no doubt that you can become a successful embedded software engineer. Keep seeking out opportunities to expand your knowledge and skills, and don't be afraid to ask for help and guidance along the way.