RMN Embedded Software Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. First part: "ROSENBAUER STATEMENT At Rosenbauer we pride ourselves on providing top-of-the-line fire apparatus, created with state-of-the-art technology, for more than 150 years. When lives are at stake anything less is unacceptable. As the world’s largest manufacturer of fire equipment, we make sure our vehicles, production teams, and service personnel are ready to do what is necessary to keep communities safe." That's about the company. Could be "About the role"? Actually "About the role" is about the position. The company statement could be considered "About the role"? Might be better as "About the role" includes description of role? The posting includes "Position Summary". So we can have "About the role" heading with the Position Summary and maybe the Rosenbauer statement? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include sections that have content. We need to extract: - Position Summary: "The Embedded Software Engineer develops software for fire truck electrical systems and supports product development, production, and issue resolution through cross-functional collaboration." - Essential Functions: list of duties. - Qualifications: Required Experience, Preferred Experience, Language Skills, Mathematical Skills, Reasoning Ability, Decision Making, Software Skills, Preferred Software Skills. - Working Conditions: description. - Physical Demands: description. - EEO statement etc to remove. - Application instructions: "Please specify which position you are seeking to apply for employment. Email Human Resources at info@rosenbaueramerica.com." plus the statement about reading etc. Remove. We must not include Pay, Schedule, Benefits unless present. None present. So we omit those sections. We need to decide which headings to use: About the role (maybe includes Position Summary and company statement?), Responsibilities (essential functions), Qualifications (maybe combine required and preferred?), Skills (maybe software skills?), Working Conditions, Physical Demands. But the instruction list includes sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Working Conditions or Physical Demands as possible headings. However we must preserve all substantive information; we cannot omit Working Conditions and Physical Demands. But we can only use those headings from the list? The instruction says: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they say "include a section ONLY when the posting has real, specific content for it". So we can create other headings if needed, but better to stick to those examples? However they didn't list Working Conditions or Physical Demands as examples, but we could still use them as headings if needed. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those types of content. For Working Conditions and Physical Demands, maybe we can put under "Requirements"? Or maybe we can create a "Working Conditions" heading even if not in examples, but they didn't forbid. The instruction says "Use

for section headings (e.g. ...)" meaning we should use h3 for headings, and the examples are typical ones. It doesn't say we cannot use other headings. So we can add Working Conditions and Physical Demands as headings. But to be safe, we could incorporate Working Conditions and Physical Demands under "Requirements" or "Qualifications"? However they are distinct. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Working Conditions and Physical Demands into a single "Working Conditions & Physical Demands" section. Let's think: The posting includes "WORKING CONDITIONS" and "PHYSICAL DEMANDS". We could combine them into a section titled "Working Conditions & Physical Demands". That would be substantive. Now, we need to decide sections: - About the role: could include the Rosenbauer statement and Position Summary. - Responsibilities: Essential Functions (list). - Qualifications: Could include Required Experience, Preferred Experience, Language Skills, Mathematical Skills, Reasoning Ability, Decision Making. - Skills: Could include Software Skills, Preferred Software Skills. - Working Conditions & Physical Demands: combine. We must not repeat job title. No mention of Pay/Benefits/Schedule. We must preserve all substantive information. Let's extract details. First, Rosenbauer statement: "At Rosenbauer we pride ourselves on providing top-of-the-line fire apparatus, created with state-of-the-art technology, for more than 150 years. When lives are at stake anything less is unacceptable. As the world’s largest manufacturer of fire equipment, we make sure our vehicles, production teams, and service personnel are ready to do what is necessary to keep communities safe." Position Summary: "The Embedded Software Engineer develops software for fire truck electrical systems and supports product development, production, and issue resolution through cross-functional collaboration." Essential Functions (list): - Develop and support embedded software for vehicle control systems. - Collaborate with global and cross-functional teams to deliver high-quality products. - Design, test, and validate software and system improvements. - Troubleshoot and resolve product issues through corrective actions and continuous improvement. - Provide technical support to internal teams and suppliers. Also note: "All employees are required to support Rosenbauer’s Mission, Vision, and Values." That's a generic statement; could be included under Responsibilities? Might be considered part of essential functions? It says "All employees are required to support Rosenbauer’s Mission, Vision, and Values." Could be included as a bullet under Responsibilities. Also: "The following are the essential duties of this position and do not include marginal functions that are incidental to the performance of fundamental job duties. The scope and duties of a given position may change or be temporarily altered based on the business needs of Rosenbauer." That's boilerplate; we can drop as it's not substantive detail? It's somewhat generic but maybe we can keep as part of Responsibilities? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those categories, but it's generic boilerplate about duties may change. Might be considered boilerplate; better to drop. Now Qualifications: Required Experience: - Bachelor’s degree in electrical engineering or computer science - 1 - 3 years of experience with embedded systems - Experience with low voltage electrical systems - Experience with signal processing Preferred Experience: - Knowledge of embedded C, C++, or Python - Experience utilizing software revision control systems. - Experience with requirements-based software engineering. - Experience in writing software for automotive control systems. - Experience with vehicle electric DC & AC generation and supply, multiplex wiring. - Knowledge of firefighting processes and equipment. Language Skills: - Read and interpret common scientific and technical journals and documents. - Excellent oral and written communication skills. Mathematical Skills: - Work with mathematical concepts such as probability and statistical inference. - Interpret an extensive variety of technical instructions in mathematical or diagram form and deal with several abstract and concrete variables. - Able to apply mathematical concepts to software solutions Reasoning Ability: - Emphasis will be placed on analytical and problem-solving skills. - Define problems, collect data, establish facts, and draw valid conclusions. - Prioritizes and manages multiple projects and objectives as well as handling unscheduled tasks. - Prepares and presents project status reports. Decision Making: - Responsibilities are guided by general company principles and objectives. - Decisions are made within these guidelines initially, and a supervisor is informed afterwards. - All decisions must be verified with the software manager and/or product manager Software Skills: - Implement code in software IDE’s (i.e. Eclipse, Microsoft Visual Studio, etc.) - Microsoft Office Products - Knowledge with embedded C and C++ Preferred Software Skills: - Strong fundamental knowledge of C++ - Able to work in Agile SDLC - Test software using various processes such as Unit and Regression testing - Microsoft Visio experience - Knowledgeable in SAE J1939 and CANopen protocol - Familiar with Peak tools such as PCAN Explorer - Knowledgeable in QML and QtCreator Now Working Conditions: - This position works in an office environment. - It is a quiet environment that is temperature controlled, ventilated, and well-lit. - Working Conditions will include a desk space where most of the shift will be spent, and it provides open space to work in. - This office space is routinely cleaned by Rosenbauer Cleaning Services. - It has access to all welfare facilities. - This position requires traveling to different departments, test environments and manufacturing environments exposing you to varying working conditions when out of the office. - This can cause exposure to cold or heat depending on the season. - Working conditions may include humidity, wet floors, and loud noises. - Most of the hazards come from machines but following proper procedures minimize risk. - There is also sometimes dust and airborne particles due to the machines being used in all the different shops. Physical Demands: - This position requires standing, walking, sitting, and the use of hands. - It can become very loud in certain shops. - Some projects require the use of feet, legs, hands, and fingers for over 60 minutes at a time, while the use of knees, back, shoulders, and arms can reach up to 60 minutes. - Specific vision abilities required by this job include close vision, distance vision, color vision, peripheral vision, ability to adjust focus, and good depth perception. - This position may require reaching, climbing, balancing, stooping, kneeling, crouching, or crawling. - All positions require the ability to lift 50 pounds, but this position rarely involves lifting heavy objects. EEO statement etc to remove. Now we need to output HTML fragment with

headings and appropriate

• for lists,

  for prose. We need to decide which content goes into which section. About the role: Could combine Rosenbauer statement and Position Summary as prose (

  ). Possibly also mention that it's Embedded Software Engineer role? But we shouldn't repeat job title. The Rosenbauer statement is about company; Position Summary is about role. We'll put both in

  maybe separate paragraphs. Responsibilities: Essential Functions list (including support mission vision values?). We'll make a

  with each bullet. Qualifications: Could include Required Experience, Preferred Experience, Language Skills, Mathematical Skills, Reasoning Ability, Decision Making. Might be too many sub-sections; but we can keep as a single Qualifications section with subheadings? The instruction only mentions using

  for section headings; we could use

  for subheadings? Not prohibited but they didn't mention. Safer to keep as a single Qualifications section with

  paragraphs describing each category, or

  for each. We could break into sub-sections using

  but not required. However to preserve structure, we could use

  for each major category (Required Experience, Preferred Experience, etc.) but that would be many sections; they said prefer few substantive sections over many thin ones. So better to combine into one Qualifications section with multiple

  paragraphs each describing a category, maybe using for category names. Similarly Skills: Software Skills and Preferred Software Skills. Working Conditions & Physical Demands: combine into one section with

  maybe "Working Conditions & Physical Demands". Provide

  paragraphs. Now we must ensure we don't include boilerplate like "All employees are required to support Rosenbauer’s Mission, Vision, and Values." That's not boilerplate; it's a responsibility. We'll include as a bullet. Now let's craft HTML. Start