Program Controller

We need to output only HTML fragment with sections for headings that have real content. The posting includes: "What We Offer" (maybe a section). Also "Group Summary". "Job Responsibilities". "Requirements And Qualifications". Also "Work Environment". Also maybe "Awareness, Unity, Empowerment" but that's EEO boilerplate, should be removed. Also "Magna Standards" etc maybe part of responsibilities? Actually "Magna Standards Practice and maintain integrity..." appears under Requirements? It's after "Requirements And Qualifications". It's more like company policies; could be considered part of Requirements? But it's generic boilerplate; but it's not EEO; it's about integrity, code of conduct, safety, etc. Might be considered part of Requirements? However guidelines: remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Magna Standards section is not EEO but it's about company policies; could be considered part of Requirements? It's not a list of duties/requirements but more like corporate values. Might be considered boilerplate? Not sure. Safer to keep as part of Requirements? But it's not a requirement per se; it's more about company expectations. However we can include it under Requirements as a list? It's prose. Could be included as a

under Requirements. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The posting has: "What We Offer" (maybe corresponds to Benefits? but not exactly). There's no explicit Benefits, Pay, Schedule. There's Work Environment (20% travel). That's schedule? Not exactly. There's no Pay info. So we should not create Benefits, Pay, Schedule sections unless posting actually states them. So we will not include those. We have sections: "What We Offer" (maybe we can treat as "About the role"? Actually "About the role" is a heading we can use for description of role. The posting includes "Group Summary" describing the team/mission. Could be "About the role". Also "Job Responsibilities". Also "Requirements And Qualifications". Also "Work Environment". Also maybe "Skills" (advanced Excel skills etc). But we can incorporate skills into Requirements. We need to avoid repeating job title as heading. No Job ID. We need to use

• for any list of duties/requirements/benefits. So we need to convert lists into
  • . The posting includes bullet-like lines but not explicit bullet characters; they are sentences separated by periods. We need to identify lists: Under "Job Responsibilities" there are multiple responsibilities each starting with a capital letter and ending with period. We can treat each as a list item. Similarly under "Requirements And Qualifications" there are bullet-like lines: Bachelor’s degree required..., Five (5) plus years’ experience..., Financial background favored..., Cost Accounting desired..., Willingness to travel..., Spanish and/or German language is an asset., Must have advanced Excel skills..., Must have the ability to balance multiple tasks. Also "Magna Standards..." maybe separate. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the text exactly as given (maybe minor punctuation). We'll output as

    for prose,

    • for list items. We need to decide which sections to emit. Potential sections: - About the role: could combine "What We Offer" and "Group Summary". But "What We Offer" is more about company offering; "Group Summary" about Magna Powertrain. Could be separate headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for the descriptive overview (What We Offer + Group Summary). Or we could split into two sections but only allowed headings are those; we cannot create custom headings like "What We Offer". So we must map content to allowed headings. So we can put the descriptive content under

      About the role

      . That seems appropriate. - Responsibilities:

      Responsibilities

      with list. - Requirements:

      Requirements

      with list (education, experience, etc). Could also have Qualifications separate but we can combine. - Skills: maybe separate

      Skills

      for advanced Excel, computer literate, Microsoft Office, ability to balance multiple tasks, language asset. But those are also qualifications. Could put under Requirements. - Work Environment: Not in allowed headings list; but we could put under Schedule? Not exactly. There's no heading for Work Environment. Could we omit? The instruction: "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 must only use those headings; it says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests those are examples; we can use other headings if needed? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those examples; likely they expect only those headings. Work Environment may not be needed; maybe we can incorporate into Responsibilities or About the role? But it's distinct. However we could treat it as part of "About the role" or maybe as a separate heading "Work Environment" but that's not in the list; risk of being considered not following instruction. Safer to omit Work Environment? But we must preserve ALL substantive information; omitting work environment would lose info. However maybe we can incorporate it into Responsibilities as a duty? Not really. Could we create a section "Schedule" for travel? The posting says "Work Environment Office environment: 20% travel required." That's about schedule/travel. Could fit under Schedule heading (though schedule usually about hours). But we could use Schedule to mention travel requirement. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state work environment and travel requirement, which could be considered schedule-related. So we could create a Schedule section with that info. Similarly, Benefits: The posting has "What We Offer" which describes benefits/engaging environment, development prospects, etc. That could be considered Benefits. So we could create a Benefits section with that content. However the instruction says "Prefer a few substantive sections over many thin ones." So we might combine What We Offer and Group Summary into About the role, and maybe Benefits separate? But we already have About the role for overview. Benefits could be separate but might be thin. However we have substantive content: "What We Offer At Magna, you can expect an 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." That's substantive. Could be Benefits. Group Summary: "Transforming mobility. Making automotive technology that is smarter, cleaner, safer and lighter. That’s what we’re passionate about at Magna Powertrain, and we do it by creating world-class powertrain systems. We are a premier supplier for the global automotive industry with full capabilities in design, development, testing and manufacturing of complex powertrain systems. Our name stands for quality, environmental consciousness, and safety. Innovation is what drives us and we drive innovation. Dream big and create the future of mobility at Magna Powertrain." That's also substantive about the group. Could be About the role. Thus we could have two sections: About the role (Group Summary) and Benefits (What We Offer). Or combine both into About the role. But we need to avoid thin sections. Combining yields a substantive About the role. Then Responsibilities, Requirements (including qualifications and skills), Schedule (work environment/travel). Possibly also Skills separate? But we can incorporate skills into Requirements. Thus final sections: About the role, Responsibilities, Requirements, Schedule. We must not include Benefits, Pay, etc unless posting states them. We have not used Benefits heading. Now we need to format. We'll output:

      About the role

      Transforming mobility. Making automotive technology that is smarter, cleaner, safer and lighter. That’s what we’re passionate about at Magna Powertrain, and we do it by creating world-class powertrain systems. We are a premier supplier for the global automotive industry with full capabilities in design, development, testing and manufacturing of complex powertrain systems. Our name stands for quality, environmental consciousness, and safety. Innovation is what drives us and we drive innovation. Dream big and create the future of mobility at Magna Powertrain.

      What We Offer At Magna, you can expect an 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.

      But we might want to keep them as separate paragraphs; that's fine. Next Responsibilities:

      Responsibilities

      • Mission of the Position: Supports sales management as well as program management to deliver accurate, on time quotes to the customer while satisfying financial key figures for each project.
      • Execute financial quoting activities and support the GPMS quote process.
      • Maintain and ensure accuracy of program financials (lifetime view) through regular program updates and reports.
      • Quoting process:Support the implementation of new processes, standards to support the Global Quoting Process from a financial perspective.Improve the quote cost models and other finance tools.Ensure all costs are accurate and included in the cost model.Support Sales with contracts regarding fixed cost clauses, financial terms, and conditions, etc.
      • Financial analysis and financial steering of projects:Generate financial analysis and sensitivity analysis of projects.Provide the project team with financial advice.Analysis of business cases.
      • Cost break-down & other financial information for customers:Support the program team in generating “Cost break downs” for the customer.Prepare financial information to support sales negotiation.
      • Preparation of data for the management:Generate monthly/quarterly reports for as needed by Management to enable right decisions. Support budget process
      • Preoperational cost tracking:Support pre-operational cost tracking and reporting.
      • Other duties as assigned.
      But note some items have no spaces after colons; we should keep as given. Might be okay. Next Requirements:

      Requirements

      • Bachelor’s degree required – Business / Finance and Related disciplines.
      • Five (5) plus years’ experience in automotive industry or equivalent.
      • Financial background favored.
      • Cost Accounting desired
      • Willingness to travel.
      • Spanish and/or German language is an asset.
      • Must have advanced Excel skills, be computer literate and have experience in Microsoft Office.
      • Must have the ability to balance multiple tasks.
      • Magna Standards Practice and maintain integrity while following Magna’s Charter and Constitution.
      • Follow Magna’s Code of Conduct and Ethics and related compliance policies.
      • Supports and adheres to policies, procedures, and operational guidelines related to established quality management system (IATF 16949).
      • Drive the development of new technologies to improve quality, efficiency and reduce cost.
      • Comply with safety policies and procedures to ensure duties of self are performed in a safe manner.
      • Health &