Plant Controller

We need to output HTML fragment with sections: About the role (but we already have heading "About The Role" in source; we need to use

for section headings. The page already shows job title, so we should not repeat job title as heading. We need to include sections only when posting has real specific content. We need to extract content: The posting includes: - About The Role (some bullet lines: U.S. Person Required Travel Percentage Is Relocation Available Yes 0% No). This seems like metadata: U.S. Person Required, Travel Percentage, Relocation Available Yes 0% No. We need to fold minor metadata into a short

or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph with that metadata. - What You’ll Do (Job Purpose, Job Duties & Responsibilities with subpoints). We need to produce sections: maybe "About the role" (the description) and "Responsibilities". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits (if present). Also maybe "Working Conditions" but not in list; we can ignore if not requested. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, ITAR details, etc. But we need to keep substantive content like job purpose, duties, qualifications, skills, benefits, working conditions maybe. We need to decide which sections to include based on content. Let's parse the posting: **About The Role** (maybe heading) - U.S. Person Required - Travel Percentage - Is Relocation Available Yes 0% No That seems like metadata: U.S. Person Required (yes/no?), Travel Percentage (maybe 0%?), Relocation Available Yes 0% No (confusing). We'll just put a short paragraph: "U.S. Person required; travel percentage 0%; relocation not available." But we must not invent; we need to preserve exactly what is there. The text: "U.S. Person Required Travel Percentage Is Relocation Available Yes 0% No". It seems like a garbled line. Could be: "U.S. Person Required", "Travel Percentage", "Is Relocation Available", "Yes", "0%", "No". Probably they meant: U.S. Person Required: Yes; Travel Percentage: 0%; Relocation Available: No. We'll capture as is? Might be better to just include the line as a paragraph without interpretation. But we should not invent. We'll output exactly that line as a paragraph? However we need to fold minor metadata into a short

. So we can put:

U.S. Person Required Travel Percentage Is Relocation Available Yes 0% No

. That preserves the exact text. But maybe we should split? The instruction: "fold minor metadata into a short

or drop it." So we can keep it as a short paragraph. Now "What You’ll Do" includes: - Job Purpose: Provides financial leadership and analysis for assigned plant operations, ensuring accurate financial reporting, effective internal controls, and meaningful financial insight to support business performance. Partners with operations leadership to interpret financial results, evaluate business performance, develop forecasts and cost plans, and identify opportunities to improve financial and operational outcomes. - Job Duties & Responsibilities with subpoints: Plant Financial Reporting & Controls (30%) ... (details) Cost Accounting & Performance Analysis (25%) ... Financial Planning & Forecasting (20%) ... Business Partnership & Decision Support (15%) ... Inventory Financial Controls (10%) ... We need to output these as a list under Responsibilities. Use

• . Should we include the percentages? Yes, preserve all substantive information. So each duty as a list item, maybe include the heading and percentage inside the li. Now "Who You Are" includes: - Required Qualifications: Bachelor’s degree ...; MBA or other relevant advanced degree preferred. Five or more years ... Experience with manufacturing cost accounting, financial reporting, forecasting, and financial analysis. Experience working with ERP systems and Microsoft Office applications, including advanced use of Excel. - Knowledge, Skills, And Abilities: list of items. We need sections: Requirements, Qualifications, Skills. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide what to put where. "Required Qualifications" could go under Qualifications. "Knowledge, Skills, And Abilities" could go under Skills. Possibly also Requirements (maybe same as Qualifications). But we should not create thin sections. We have substantive content for both Qualifications and Skills. So we can have:

  Qualifications

  with the required qualifications paragraph.

  Skills

  with the knowledge, skills, abilities list as
  . We might also have a "Requirements" section but could be redundant. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Required Qualifications and Knowledge, Skills, And Abilities into one "Requirements" section? But they'd be separate concepts. However we have both; we could make a "Requirements" section that includes both the qualifications and the skills. But the instruction list includes Requirements, Qualifications, Skills as separate possible headings. We need to decide based on content. We have: - Required Qualifications (education, experience, ERP, Excel) - Knowledge, Skills, And Abilities (list of abilities) Thus we could have:

  Qualifications

  for the education/experience.

  Skills

  for the abilities list. We could omit a separate Requirements section. Now "WORKING CONDITIONS": description. Not in the list of headings but we could include as a paragraph under maybe a generic section? The instruction only mentions those headings; we could omit if not requested. But we should preserve all substantive information. However we could include it as a paragraph under a generic section like "Working Conditions" but not in the allowed headings 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 said "include a section ONLY when the posting has real, specific content for it". So we could add a section for Working Conditions if we want. However they didn't list it as an example; but it's not prohibited. Safer to include it as a paragraph maybe under a generic section? But we could add a

  Working Conditions

  with the paragraph. It's substantive. Now "Why Join Hitchiner?" includes bullet points: Mission-critical manufacturing, Internal mobility, We win together, Beautiful location. This is like benefits/perks. Then "Employee Benefits" section with details: medical, dental, vision, FSA, 401(k), company-paid short-term, long-term, basic life/AD&D, education/tuition reimbursement, wellness rewards, EAP, free onsite fitness center. Thus we have benefits content. So we should include a Benefits section. Also "About Hitchiner" company description; maybe not needed but could be included as a paragraph under maybe "About the company". Not in list but could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About Hitchiner description. However it's not a standard heading; we could add a section "About the Company". But they didn't list that as example; but we could still include. However they said "Prefer a few substantive sections over many thin ones." Adding many sections may be thin. But we could incorporate the About Hitchiner description into the "About the role" section? Not appropriate. Maybe we can add a

  About the Company

  paragraph. But the instruction about headings gave examples; not strict. I'd include a section for About the Company. Now "Additional Information": includes posting duration, equal opportunity, ITAR/ear, visa sponsorship not available, E-Verify. This is boilerplate legal/EEO etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO statement, ITAR details, visa sponsorship, E-Verify. Also the line about posting duration maybe not boilerplate? It's administrative; could be considered minor metadata; we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could drop the Additional Information entirely (since it's mostly legal boilerplate). However we need to preserve substantive information; the ITAR/ear and visa sponsorship might be substantive for eligibility. But they said remove EEO/equal-opportunity/scam-warning boilerplate. The ITAR/ear and visa sponsorship might be considered legal but maybe substantive for the role (U.S. Person required). However we already have U.S. Person Required in the metadata. The ITAR/ear details might be considered legal boilerplate; but it's about export control eligibility. Might be considered substantive. However the instruction says remove EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It didn't explicitly say to remove ITAR/ear. But it's legal. I'd err on side of removing legal boilerplate unless it's directly about eligibility. The posting already says "U.S. Person Required". The ITAR/ear details are extra. I'd drop them to keep concise. Thus we will keep: - About the role metadata paragraph. - About the role purpose paragraph (Job Purpose). - Responsibilities section with list of duties. - Qualifications section with required qualifications paragraph. - Skills section with knowledge, skills, abilities list. - Benefits section with employee benefits list. - Working Conditions section with paragraph. - About the Company section with paragraph (Hitchiner description). Maybe also include "Why Join Hitchiner?" as part of Benefits? Actually those are perks; we could incorporate them into Benefits section as well. But we have separate Employee Benefits details. The "Why Join Hitchiner?" includes mission-critical manufacturing, internal mobility, profit-sharing bonus, beautiful location. Those are also benefits/perks. We could include them in Benefits section as list items. Thus Benefits section could combine both. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  U.S. Person Required Travel Percentage Is Relocation Available Yes 0% No

  Provides financial leadership and analysis for assigned plant operations, ensuring accurate financial reporting, effective internal controls, and meaningful financial insight to support business performance. Partners with operations leadership to interpret financial results, evaluate business performance, develop forecasts and cost plans, and identify opportunities to improve financial and operational outcomes.

  Responsibilities

  • Plant Financial Reporting & Controls (30%) - Oversees the accuracy and integrity of plant financial reporting in accordance with Generally Accepted Accounting Principles (GAAP) and Company requirements, including period-end close activities, balance sheet reconciliations, audit support, and maintenance of effective internal controls.
  • Cost Accounting & Performance Analysis (25%) - Develops and maintains plant standard costing and related financial models, including work center rates, inventory valuation, and product costing. Analyzes actual performance against standards and plans, identifies significant variances and underlying drivers, and provides recommendations to improve financial and operational performance.
  • Financial Planning & Forecasting (20%) - Leads plant financial planning activities, including quarterly forecasts and annual cost planning. Evaluates operating assumptions, trends, risks, and business requirements to develop accurate financial projections that support plant and organizational objectives.
  • Business Partnership