Location>code7788 >text

Embedded software enterprises written examination questions article summary post

Popularity:902 ℃/2024-10-27 20:41:42

1. Preamble

Welcome to my column, the author of the 25th fresh graduates, posting positions for embedded software development engineer related positions, in the fall recruitment process with the intention of recording the real written test questions of the major companies, is now recorded in the form of a blog, interested parties can view their own!

2. Agreements

Each article in the author's column will use a uniform habit/step-by-step approach to make it easier for readers to find, with the following main points to keep in mind:

  1. Articles in the column begin with "Written Exam Time + Company Name" Naming
  2. The blurb at the bottom of the column reads "Job Posting + Exam Questions", while positions and question types are also indicated at the bottom of the table of contents at the beginning of the corresponding article
  3. Most topics will have under them "solution (a math equation)", which the reader may regard as a paraphrase of the question
  4. Below some of the topics will be "Solution (doubtful)", indicating that the reader has a question about the question (there may be a problem with the question itself, or the author may be debating his answer)
  5. Below some of the topics will be "Answers (throwaway, non-standard answers)", indicating a non-standard answer, commonly found in short answer questions
  6. Some of the multiple choice options are "X", indicating that the author does not know the question - _ -

Please note:

  1. Major companies may change the written test questions each year, each year, each job seeker's questions may not be the same, but the examination questions and topics related to the general direction of knowledge may change less, the column is for readers' reference only!
  2. The column all written questions are embedded software development engineer related positions written questions (of course, there may be some companies do not have related positions or related positions but the written questions for the software development of a unified class, so this type of enterprise written questions involving embedded knowledge may be relatively small)
  3. Some of the questions are not parsed (common in logic questions, line test questions and some difficult algorithmic programming questions)

3. Catalog of columns

  1. 20240712 TCL Huaxing-Electronic Design (Advance Batch) Written Exam
  2. 20240719 CVTE Embedded Software Development Engineer (Linux Direction) Written Exam
  3. 20240720 KDDI Embedded Development Engineer Written Exam
  4. 20240726 itc Embedded Engineer Written Exam
  5. 20240727 Shadowstone Headend Embedded Engineer-2025 School Recruitment Written Exam
  6. 20240730 MediaTek Software Development Engineer (Embedded Software Direction) Written Exam
  7. 20240803 CoreMotion Embedded Software Engineer(25current session of the college recruiting class)(J12042) Written Exam
  8. 20240805 Ulai School Recruitment - Embedded Software Engineer Written Exam
  9. 20240811 DJI Embedded Engineer (Shanghai) Written Exam
  10. 20240812 Novartis Nebula 25th Early Batch - Embedded Engineer (Xi'an) Written Exam
  11. 20240817 Allwinner NO2510 Embedded Software Design Engineer (Zhuhai/Guangzhou/Xi'an/Shenzhen) Written Exam
  12. 20240818 ByteDance BSP Driver Development Engineer-OS Written Exam
  13. 20240826 Stewart Embedded Software Engineer [25th School Recruitment] Written Exam
  14. ...

4. Checking for deficiencies and remedies

In view of the author's limited ability, and enterprise written test questions often no reference answers, most job seekers also just know over no pass, and do not know the specific score and the correct answer, so although the author spent a lot of time to answer some of the questions in the written test, but in the way of limited knowledge, some of the topics in the article I can not be sure of the correct answer, or there may be a mistake, I hope that readers will be able to read! I hope that readers can read in the process of finding errors, can be boldly pointed out in the comments section or private letter to the author's mistakes, thank you!