Enterprise Risk Management Program Manager
Crest Industries · Pineville, LA · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company and role. We need to use .
Requirements: The REQUIRED QUALIFICATIONS section includes bullet-like sentences. We'll list them.
Required qualifications list:
- Five or more years of progressively responsible experience in enterprise risk management or a closely related field, preferably in a complex, multi-business, regulated, publicly traded, industrial, or manufacturing environment.
- An equivalent combination of education and experience will be considered
- Demonstrated experience owning or managing an ERM program, enterprise governance process, or comparable cross-functional risk program with recurring executive deliverables
- Strong working knowledge of enterprise risk assessments, risk registers, risk taxonomy and scoring, controls, mitigation plans, issues management, key risk indicators, and management reporting
- Ability to manage multiple workstreams, deadlines, data requests, meetings, and recurring reporting cycles
- Experience preparing clear, concise materials for senior leadership, governance committees, boards, or board committees
- Strong organization, follow-through, and attention to detail
- Strong written and verbal communication skills. Ability to summarize complex information clearly and professionally
- Comfortable working with employees and leaders across multiple business units and functions, including ability to ask questions, clarify information, and challenge incomplete or inconsistent responses
- Strong judgment and comfort working through ambiguity
- Ownership mindset and ability to drive work forward with limited structure
- Ability to work independently and proactively, establish structure, manage competing priorities and deadlines, exercise sound judgment, think creatively, and take ownership of issues and matters through their successful conclusion
- Strong interpersonal skills, including a good sense of humor, patience and an ability to maintain an even keel
- Share the company’s purpose and values, including high ethical standards, teamwork, customer service mindset, and positive attitude
We'll put each as .
Preferred qualifications: list.
- Demonstrated ability to lead the evolution and maturity of an early-stage ERM program into a fully integrated business practice
- Experience working with Power BI, SharePoint, Microsoft Lists, Excel-based reporting tools, GRC systems, RMIS systems, or similar platforms
- Bachelor's degree in risk management, business administration, finance, accounting, or a related field, or equivalent relevant experience
- Professional certification or formal training in risk or project management, such as PMI-RMP, ISO 31000, CRMA, CRM, CERP, PMP, or a comparable credential
Location: Pineville, Louisiana (on-site). Could be included in About the role paragraph.
We also have "Essential Functions" sections with mental & cognitive etc. Those are substantive? They describe job demands. Should we include? The instruction: include a section ONLY when posting has real, specific content for it. Essential Functions is a section with details. Could be considered as "Requirements" maybe but we already have Required Qualifications. However essential functions are about mental/physical requirements. Could be considered as part of Requirements or maybe a separate section like "Requirements". But we already used Requirements for qualifications. Could we add a section "Requirements" that includes both qualifications and essential functions? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Requirements and Qualifications separate. Likely Requirements = mandatory qualifications, Qualifications = preferred qualifications. Essential Functions could be placed under Requirements as well, but we already have Required Qualifications. Might be better to include Essential Functions under Requirements as additional bullet points. However we must not invent sections; we can include Requirements with both qualification and essential functions. But we already have Required Qualifications heading; we could rename that to Requirements. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use exactly those headings. So we need a
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have content for About the role (intro), Responsibilities (KEY RESPONSIBILITIES), Requirements (maybe REQUIRED QUALIFICATIONS), Qualifications (PREFERRED QUALIFICATIONS), Skills maybe not separate but could be part of qualifications. Benefits, Pay, Schedule not present, so omit those sections. Also location maybe part of About the role? Could include as a paragraph. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove application instructions (none). Remove duplicated lines. We need to preserve all substantive information. So we need to include the intro paragraphs about Crest Industries and the role description before KEY RESPONSIBILITIES. That can go under About the role. Responsibilities: list bullet points from KEY RESPONSIBILITIES. Need to capture each bullet. The text is a long paragraph with many responsibilities separated by periods. We need to split into list items. We'll extract each responsibility sentence. Let's parse KEY RESPONSIBILITIES paragraph: "Lead Crest’s ERM program, including Risk Owner meetings, Risk Liaison communications, data collection, follow-up, and status tracking. Coordinate with Risk Owners and Risk Liaisons to collect updates, clarify information, improve documentation quality, and reduce manual rework. Improve ERM processes to make update cycles more consistent, efficient, and less dependent on manual coordination Own and govern the enterprise risk register, including risk descriptions, risk owners, gross and net scores, current controls, planned actions, mitigation status, and supporting documentation. Identify incomplete updates, inconsistent data, documentation gaps, or items requiring escalation Prepare the ERM Steering Committee materials, executive summaries, dashboards, and enterprise risk profile updates, as well as the Board of Directors annual report Track mitigation plans, planned controls, action items, owners, due dates, and follow-up items across business units and functions. Lead risk workshops, Risk Owner meetings, scoring calibration discussions, control documentation review, and planned-action tracking. Develop and maintain key risk indicators, risk metrics, action-plan reporting, and other reporting enhancements as the ERM program matures Develop and maintain ERM tools, templates, process documentation, guidance materials, and training resources. Maintain Power BI inputs and support recurring dashboard updates, data validation, trend analysis, and risk reporting Own the recurring ERM program calendar, including risk update cycles, Risk Owner meetings, Risk Liaison coordination, Steering Committee preparation, action-item tracking, and follow-up reporting. Promote practical risk ownership by helping teams understand ERM expectations, timelines, and documentation requirements Lead continuous improvement of the ERM process, reduce administrative burden, clarify expectations, and improve consistency across business units. Escalate process gaps, incomplete updates, inconsistent information, or items requiring leadership attention" We'll make each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use exactly those headings. So we need a Requirements
containing the mandatory qualifications and essential functions. And a Qualifications
containing preferred qualifications.
Thus we need to move the REQUIRED QUALIFICATIONS content into Requirements section. Also include Essential Functions under Requirements as well (maybe as sublist). We'll combine.
We must not repeat job title as heading. Good.
We must not include boilerplate like EEO etc. Remove all that.
Now craft HTML.
Structure:
About the role
Intro paragraphs about Crest Industries and the role, plus location.
Responsibilities
- ... ...
Requirements
- Five or more years... ...
- Essential Functions: Mental & Cognitive Requirements: ... maybe break into sub-items? Could list each essential function as separate li. We'll list essential functions as separate li under Requirements. Thus Requirements list includes qualification items and essential function items.
- Preferred qualifications items ...