Project Manager - Engineering

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, etc). Must not create sections with placeholder like "commensurate with experience". Must not invent. We need to parse the posting. Let's extract sections: Overview: Who We Are, Why We Are Different, What You Will Get. This is about company culture, benefits. Could be "About the role"? Actually "Overview" includes company description and benefits. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings accordingly. We have: - Overview: Who We Are, Why We Are Different, What You Will Get. This could be "About the role"? Actually "About the role" is more about the job itself. But we have "Summary/Objective" describing the role. So we can put that under "About the role". Also "What You Will Get" includes benefits: comprehensive benefit offerings, fair compensation, career development, holiday etc. That could go under Benefits (and maybe Pay). But we need to only create sections if there is real specific content. Let's list content: Summary/Objective: description of Project Manager responsibilities (leading portfolio, communication, etc). This is about the role. Duties And Responsibilities: list of duties. Working Conditions: description. Qualifications: bullet list. Competencies: list. Supervisory Responsibility: statement. Physical Demands: description. Position Type/Expected Hours Of Work: full-time, 40 hrs/week, etc. Travel: local/minimal out of state. Work Authorization/Security Clearance: must be legally authorized. Other Duties: note about job description not comprehensive. Pay Group: not specific pay. EEO statement: remove. We need to decide which sections to include: - About the role: could combine Overview (Who we are, Why we are different, What you will get) and Summary/Objective? But "About the role" likely about the job itself, not company. However we have Summary/Objective describing role. We'll put that under About the role. - Responsibilities: Duties And Responsibilities. - Requirements: maybe Qualifications? But we have Qualifications and Competencies separate. Could combine Qualifications and Competencies under Requirements? But instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. We have Qualifications: Bachelor's degree, 5+ years experience, multiple reps successfully leading projects, PMP Certification, communication proficiency, etc. We have Competencies: list of skills like triple constraint, risk management, communications management, stakeholder management, leadership, decision making, financial literacy, business acumen, basic understanding of mechanical engineering, makes things happen. We could put Qualifications under "Qualifications" heading, Competencies under "Skills" heading. That seems appropriate. Benefits: What You Will Get includes: unique inclusive culture, comprehensive benefit offerings including medical, dental, vision, 401k with employer match, vacation, and more! Fair and competitive compensation. Career development, mentoring and opportunities to grow. Holiday, personal and vacation days. Thus we have benefits content. Also Pay: "Fair and competitive compensation." Not specific numbers. Should we create Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Fair and competitive compensation." That's a statement about pay but not specific. Is that enough? It says "Fair and competitive compensation." That's a statement about pay but not a specific number or range. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Fair and competitive compensation" is somewhat vague but it's a statement about pay. Is that considered filler? It's not a specific number but it's a statement. The examples of filler include "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Fair and competitive compensation" is similar to "commensurate with experience" in vagueness. I'd argue it's filler and we should not create a Pay section unless there is actual numbers or range. So we should not create Pay section. Schedule: Position Type/Expected Hours Of Work: full-time, minimum 40 hours per week Monday-Friday; weekend and overnight work could also become necessary. That's specific schedule info. So we can create Schedule section. Benefits: we have specific benefits: medical, dental, vision, 401k with employer match, vacation, career development, mentoring, holiday, personal and vacation days. That's specific enough. So Benefits section. Now About the role: we have Summary/Objective plus maybe Who we are/Why we are different/What you will get? But we already used What you will get for Benefits. Who we are/Why we are different is company description; could be part of About the role? Might be okay but maybe better to put under About the role as company overview. However the instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview and role summary under About the role. We must not repeat job title as heading. So we won't. We need to remove boilerplate: EEO statement, legal, etc. Also remove "Work Authorization/Security Clearance" maybe? That's substantive: must be legally authorized to work in US. That's a requirement. Could be part of Requirements or Qualifications. We'll include under Requirements maybe. Also "Other Duties" note about job description not comprehensive: that's boilerplate? It's a disclaimer but maybe we can keep as part of Responsibilities? It's not a duty. Might be considered boilerplate; we can drop. "Physical Demands": we could include under Requirements? Or maybe a separate section? Not in the list of headings; we could omit if not fitting. But we could include under Requirements as "Physical Demands". However the instruction only lists certain headings but doesn't forbid others? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. It doesn't say we cannot add other headings, but better to stick to those. Physical Demands could be part of Requirements or Qualifications. We'll include under Requirements. Position Type/Expected Hours Of Work: we have Schedule. Travel: could be part of Schedule or maybe a separate section? Not in list; we could include under Schedule as "Travel: Local and/or minimal out of state travel expected." Working Conditions: could be part of Requirements or maybe omitted. Could be under Requirements as "Working Conditions". We'll include. Supervisory Responsibility: statement that position does not have direct supervisory responsibility. Could be under Requirements or maybe under Qualifications? We'll include under Requirements. Now we need to preserve all substantive information. Let's extract each piece. Let's parse the text: Overview: - Who We Are: Lippert is a leading, global manufacturer and supplier of highly engineered products and customized solutions, dedicated to shaping, growing and bettering the RV, marine, automotive, commercial vehicle and building products industries. We combine our strategic manufacturing capabilities with the power of our winning team culture to deliver unrivaled customer service, award-winning innovation and premium products to all of our customers. - Why We Are Different: At Lippert, Everyone Matters. This is not just a tagline or empty promise; it is who we are. We have intentionally created a culture that values and celebrates our team members’ unique and varied backgrounds, perspectives, and experiences. We strive to give our team members a deeper sense of purpose at work, and we continue to build a better work environment by aligning our cultural and business strategies with the needs of our team members. - What You Will Get: A unique, inclusive and supportive company culture.Comprehensive benefit offerings including medical, dental, vision, 401k with employer match, vacation, and more! Fair and competitive compensation. Career development, mentoring and opportunities to grow.Holiday, personal and vacation days. Summary/Objective: The Project Manager is responsible for leading and managing the portfolio of projects for the organization's engineering team from project intake and scoping through production. This leader must be able to effectively communicate cross-functionally and to all levels of the organization, including face-to-face updates to senior leaders. They should be able to lead their project teams to accomplish challenging goals. This leader must be passionate, hardworking and have a sense of urgency. In addition to leading projects, the Project Manager will work closely with the corporate PMO to define and implement project management process continuous improvement initiatives. Duties And Responsibilities: - Manage multiple projects simultaneously - Understand business objectives and opportunities - Manage new project intake process - Lead cross functional project scoping - Assess and communicate resource constraints - Develop project charters to align project scope, schedule, budget, and KPI's (quality, cost, ROI, etc.) with project sponsors and stakeholders. - Establishes and manages the project schedule. Assigns clear tasks to specific team members and ensures project deliverables are completed as planned and documented in PLM system. - Leads project core team to ensure cross functional coordination of all project activities. - Supports the preparation for and ensures the completion of design reviews. - Leads preparation for and conducts project gate reviews. - Manage project scope through disciplined use of change management process - Manage Risk Register and Issues List. Transparently communicate issues and action plans. Effective and timely escalation of issues not able to be addressed within project team or established timing. - Own project status reporting. Communicates project updates to senior leadership and stakeholders in monthly reviews. - Role model for project management best practices. Responsible for defining, teaching, and enforcing the use of good project management practices. - Work with PMO team to continuously improve project management processes Working Conditions: - Primarily indoors in an office environment. - May sit for several hours at a time - May experience periods of prolonged exposure to computer screens. - May require use of hands to operate computers, printers, and copiers. Qualifications: - Bachelor's degree in engineering, project management, business, or similar field - 5+ years experience leading new product development projects - Multiple reps successfully leading projects from initiation through launch - PMP Certification - Written and spoken communication proficiency, coaching, organizational skills, initiative, team player, decision making, time management, and thoroughness - Able to effectively engage, manage, and communicate to stakeholders including senior leadership - Ability to manage multiple projects simultaneously Competencies: - Understands and able to manage the project management “triple constraint” of scope, time, and cost. - Risk management - able to effectively identify, analyze, communicate, and respond to project risks - Communications management - effectively manages and tailors project reporting and communications based on the needs of stakeholders - Stakeholder management - able to identify and engage stakeholders effectively - Leadership - able to build, guide, and motivate project teams - Decision making - able to make informed and timely decisions that are well documented, and “sticky” i.e. not second guessed or overturned. Able to recognize what decisions can and should be made within the project team vs. those that require escalation. - Financial literacy - working knowledge of project related financial analysis including management of inputs (resources, expenses, capital) and the calculation of project financial metrics (Payback, NPV, Revenue, DCM, etc.) - Strong business acumen - understands the many dimensions of a growing company, their importance, and new product development relationships within each. - Basic understanding of mechanical engineering concepts and manufacturing processes (metal cutting, forming, welding, assembly, etc.); can effectively interact