Intern - Engineering Software
or drop it. So we could include a short p for Worker Type and Group. Now decide sections: - About the role: content from "ABOUT THE ROLE: As a Software Engineering Student..." (maybe also include the preceding "Job Responsibilities ABOUT THE ROLE:" but we can just use that paragraph.) - Responsibilities: list of duties from "Your Responsibilities ..." (multiple sentences). Could be turned into
- items.
- Requirements: from "WHO WE ARE LOOKING FOR:" (degree, GPA, knowledge, experience, fluent English). Could be list.
- Qualifications: from "YOUR PREFERRED QUALIFICATIONS:" (list). Could be Qualifications section.
- Skills: from "Special Knowledge / Skills" (Microsoft Office, Professional Communication skills) plus maybe also include some from preferred qualifications? But we already have Qualifications. Could also include technical skills there. But we can treat Skills as the "Special Knowledge / Skills" (Microsoft Office, Professional Communication). Could also include Physical Demands / Work Environment maybe as a separate section? Not required. Could include as part of Skills or separate? The instruction says only include sections when posting has real specific content. Physical Demands / Work Environment is specific content; we could make a section maybe "Work Environment". But not in the list of allowed headings; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put Physical Demands under Skills or maybe under Responsibilities? Better to put under Skills as "Physical Demands / Work Environment". But Skills heading is for skills; we could still include that content under Skills as a list.
- Benefits: from "What We Offer At Magna..." (engaging environment, invest in employees, exciting varied responsibilities, wide range of development prospects, career path unique). That's benefits.
- Pay: not specified; do not include.
- Schedule: not specified; do not include.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to use
for section headings. Use
- for any list of duties/requirements/benefits, and
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as given, but we can format into lists. We must not repeat job title. Not include boilerplate. Let's extract exact sentences. About the role paragraph: "As a Software Engineering Student at Magna Electronics, you will join a team of software professionals, implementing cutting edge technologies on both existing and new development products of Autonomous Driving." We could also include preceding "Job Responsibilities ABOUT THE ROLE:" but that's just label. We'll just use the sentence. Responsibilities: The bullet points: - Perform all phases of the Software Development Life Cycle; design, code, test, integration, verification, and integration support, facilitated by an Agile software development workflow. - Support scripting (Python/Batch) to automate the embedded development tasks and develop the tool documentation. - Support the team to debug the real time ADAS safety critical application. - Learn and become proficient with your skills in many different technical areas including object-oriented software development, real-time embedded development for multi-core and multi-processor systems, development for multiple operating systems (Linux, Windows). - As well as cyber security/product protections, image/signal processing, image/data fusion, application development, and other development to support test and verification. Note: The last bullet starts with "As well as". Could be separate bullet. We need to keep the exact phrasing. Requirements (WHO WE ARE LOOKING FOR): - Bachelor’s or Master’s degree in computer or Electrical or Computer Science - Excellent academics (cumulative GPA greater than or equal to 3.0 as a general rule) - Knowledge of SW Development Lifecycle - Software development experience in C/C++ - Fluent in English Note: The original: "Bachelor’s or Master’s degree in computer or Electrical or Computer Science Excellent academics (cumulative GPA greater than or equal to 3.0 as a general rule) Knowledge of SW Development Lifecycle Software development experience in C/C++ Fluent in English". There's missing punctuation but we keep as is. Qualifications (YOUR PREFERRED QUALIFICATIONS): - Experience with Software integration and debugging techniques. - Knowledge Of Scripting Languages Preferred (Python/Bash Scripting Experience) - Familiarity and understanding of differences between relevant C/C++ standards (i.e., C++98; C++11; C++17, etc.) - Experience with Software Continuous Integration (CI) toolchains/pipelines, Git/GitHub/ (configuration management, automated unit testing, static analysis, etc.). - Knowledge of hardware bus interfaces, such as USB, UART, I2C and SPI - Proficiency in use of basic electrical tools, i.e., oscilloscope, multimeter - Demonstrated success in resolving technical challenges by leveraging strong problem-solving skills. Note: The original had some line breaks; we keep. Skills (Special Knowledge / Skills): - Proficient Computer knowledge and skills, Microsoft Office (Word, Excel, PowerPoint) - Professional Communication skills (written and verbal) - Physical Demands / Work Environment Normal amount of sitting or standing, average mobility to move around an office environment, able to conduct normal amount of work at a computer. We could split Physical Demands as separate bullet. Benefits (What We Offer): - Engaging and dynamic environment where you can help to develop industry-leading automotive technologies. - We invest in our employees, providing them with the support and resources they need to succeed. - As a member of our global team, you can expect exciting, varied responsibilities as well as a wide range of development prospects. - Because we believe that your career path should be as unique as you are. We could also include Group Summary? That's more about company; maybe could be part of Benefits or About the role? But we already have About the role. The Group Summary is about Magna Electronics; could be considered Benefits? It's not exactly a benefit but could be part of "What We Offer". However the instruction says only include sections when posting has real specific content. The Group Summary is specific content about the company; but we don't have a heading for "Company Overview". Could we put it under Benefits? It's not a benefit per se. Could we create a separate section? Not allowed headings. Could we incorporate into About the role? Might be okay to add a paragraph under About the role describing the company. But the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we cannot have other headings, but the examples are those. Safer to stick to those headings. We could put Group Summary under About the role as additional prose. Thus About the role could include both the role description and the group summary. Let's craft About the role paragraph: combine the role description and group summary. We need to preserve all substantive information; we can't omit group summary. So we will include it as part of About the role. Thus About the role content: "As a Software Engineering Student at Magna Electronics, you will join a team of software professionals, implementing cutting edge technologies on both existing and new development products of Autonomous Driving. Transforming mobility. Making automotive technology that is smarter, cleaner, safer and lighter. That’s what we
- for any list of duties/requirements/benefits, and