(For those things related to programmers, please star it)
A few days ago, we received a private message from a student on our public account, seeking everyone’s opinions.
I am studying Internet of Things Engineering, and I have learned programming and embedded systems at school. Recently, I found that I am quite interested in embedded systems during concentrated practice, but there are almost no seniors around me engaged in hardware, and I don’t know where to get reliable information from those who have been there. So I want to ask what the daily work of embedded engineers is like? What is the current employment situation, salary, and how does it differ from software development?
Selected enthusiastic replies from our readers:
@HexagonLove: Graduated in 2011 working with STM32, mainly in the industrial sector. Microcontrollers are used in industry, while PLCs are used in general applications. The market is very mature and saturated, so we can only do customized integration and R&D. The inherent conditions are not good, and companies are reluctant to invest in instruments, leading to a narrow employment scope…
@StillMeHaiRui: If you want to work in embedded systems, you need to be familiar with various microprocessors (like ARM, DSP, etc.), peripheral chips (like various sensors), and upper computer development (like VC++, Qt). This path is very long, and without several years of accumulation, it is hard to master. If it were ten years ago, I would strongly recommend you to learn, as the demand in the embedded industry was quite high. Now, if you have a passion to pursue this path, I do not oppose you working in embedded systems.
@theWDJ_Drzzm32: It depends on whether you are leaning towards automation, computer science, or electromechanics. One focuses on control, another on networking, and another on measurement. The difficulty in embedded systems lies in system architecture. As you progress, you will be proposing solutions rather than doing detailed work. The income can be quite substantial, but it requires a broad knowledge base. These chips are just tools; what matters is what you intend to do with them.
For example, if you study embedded systems and then go to DJI to work on flight control development, that is a great path. Or you could work in agricultural IoT, smart logistics, smart home applications, etc. If you have the capability, do not limit yourself to just writing programs and drawing boards.
@sem2-_-: Don’t get into embedded systems (microcontrollers); in manufacturing, the pay is low and the work is plenty. The average level of microcontroller practitioners is not high.
@NotPublishingSciNotChangingName: Embedded systems should be differentiated… FPGA development in certain companies is still very promising… If you are only dealing with microcontrollers or DSPs, the threshold is a bit low…
@LittleAntOnWildRice: Embedded technology is difficult, and the salary is low… But if you switch to software, you will find the threshold is even lower. When you enter an internet company, you will see various professionals from different fields, such as law, economics, biology, and history, all switching to software.
@JustWantToBeQuiet: Embedded software… does not necessarily mean working with microcontrollers. You can develop gateway devices, etc. The salary is not low.
@OldZhangSmiles: Someone above mentioned “difficult technology, low salary”; just think carefully about why that is. For example, if you are doing smart cloud control (only doing switches and states), such a program, if you have rich experience, you could complete it in a day. Later, your work might just be fixing and patching, and you will be working on just a few products. Your replaceability is very low, but you will not bring more value to the company. However, if you want to create a product yourself, you will be more proactive.
@HeQiongInTheWind: It’s very difficult; without someone to guide you, how do you learn? Just follow videos? Can you see the operations clearly? Do you have the equipment? Can you afford to burn money? Is the lab available for use? This requires hands-on work; without good conditions, I do not recommend learning it.
@PangNi: Come, see our embedded engineers’ daily work, which includes both “hardware and software”.
[Fan Letter Guidelines]
0. No need to ask if I am here; please clearly state the matter in one go;
1. Don’t be lazy; please use punctuation to break sentences when leaving a message;
2. If you want to seek help or advice from everyone, please describe your basic situation in detail;
3. If you want to discuss a topic with everyone, please first attach your personal opinion;
Recommended Reading
(Click the title to jump to read)
Programmers trained in the industry grab work, working overtime every day and being laughed at by colleagues
Discussion: How to cope with programming burnout?
Follow “Things Related to Programmers” and star it, so you won’t miss out on industry news.
