3 ms·
I see something similar in my industry. I work on embedded systems for industrial automation and in my mid 30's I still tend to be one of the younger ones in an
by mreome 8y ago
I see something similar in my industry. I work on embedded systems for industrial automation and in my mid 30's I still tend to be one of the younger ones in any group of coworkers/clients. In my case don't think this is issue of "insulation" but rather a difference between technical fields. Industrial automation is a long-game. Development projects can last a year or more, and client support can stretch into the 10s of years. Also, there is a lot of value in deep domain knowledge that takes years to develop.
I think age of the companies themselves comes into play. If a company is only a year old, nobody has had time to age with the company, almost nobody is going to have had a kid, been through major medical issues, ect, while working there. Even if an individual may have that kind of life experience, the company itself doesn't. I think it shows in the kind of environments they create and the type of people they tend to attract/want.
- vips7L 8y agoHow did you get into embedded? Web work doesn't really interest me and I've been studying kernel programming for a few months.
- mreome 8y agoMy academic background was Computer and Systems Engineering, with a focus on computer science and machine vision. I started with project/application-level work at a company that specializes in industrial machine vision then moved into embedded Linux development on the devices I had been doing project-level work with.
- stuxnet79 8y agoTo echo the other commenter. How easy is it to transition to embedded if all the experience you have so far is web related? Is this possible?
- mreome 8y agoUnfortunately I couldn't really offer any useful advice here as it wasn't really a major transition for me. My academic background was Computer and Systems Engineering which includes embedded systems programming.