Project Manager - MHE
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description about company and role (maybe About the role). Responsibilities listed. Required Qualifications and Preferred Qualifications (these could be Requirements/Qualifications). Skills maybe part of qualifications. Benefits listed. No explicit Pay or Schedule (though schedule mentioned: flexible work schedule, remote work location, unlimited PTO). That's schedule info? It mentions flexible work schedule, remote work location, unlimited PTO. That's schedule/benefits. Pay: "Generous compensation and bonuses based on individual and company achievement." That's pay info. So we can include Pay and Schedule sections.
We must not repeat job title as heading. No Job ID. Remove boilerplate like application instructions (email resume). That's application instruction; we should remove it. Also remove cookie/navigation/legal/EEO etc none present.
We need to preserve all substantive information. So include company description maybe under About the role. Provide responsibilities list. Provide qualifications (required and preferred) maybe under Requirements or Qualifications. Could combine. Use - for any list of duties/requirements/benefits. Use
for prose.
We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections with real content. Let's map:
- About the role: company description and role overview (first paragraph). Yes.
- Responsibilities: list of responsibilities.
- Requirements: maybe required qualifications.
- Qualifications: maybe preferred qualifications? Or we could treat Requirements as required qualifications and Qualifications as preferred? But we need to avoid duplication. Could combine required and preferred under Requirements and Qualifications? The instruction says use those headings if content exists. We have both required and preferred qualifications. So we can have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (maybe preferred). But better: Requirements = required qualifications; Qualifications = preferred qualifications; Skills maybe not needed if covered. However we could still include Skills if there are specific skills mentioned: proficiency with project scheduling and management tools, strong stakeholder management, communication, business acumen, leadership capability. Those are skills. Could put under Skills.
Thus we can have sections: About the role, Responsibilities, Requirements (required qualifications), Skills (key skills), Qualifications (preferred qualifications), Benefits, Pay, Schedule.
Check each for content:
About the role: company description and role overview paragraph.
Responsibilities: bullet list.
Requirements: list of required qualifications (Engineering/Construction Management degree, 8+ years PM experience, owning project financials, risk, P&L, stakeholder management, proficiency with scheduling tools, strong business acumen, leadership capability). That's a list.
Skills: maybe we can extract specific skills: "Strong stakeholder management and communication skills, both verbal and written.", "Proficiency with project scheduling and management tools", "Strong business acumen and project management skills.", "Demonstrated leadership capability to build and motivate cross-functional project teams." Those are similar to requirements but could be skills. However we might avoid duplication. The instruction says preserve ALL substantive information; we can keep them under Requirements and not duplicate under Skills. But we need to decide if we need Skills section. If we don't have distinct skill content beyond what's already in Requirements, we could omit Skills to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine required qualifications and skills into Requirements. Then we could have Qualifications for preferred qualifications (experience with automated material handling solutions and control systems). That's substantive.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule.
Check Pay: "Generous compensation and bonuses based on individual and company achievement." That's specific enough for Pay.
Schedule: "Flexible work schedule. Remote work location (within driving distance of an airport). Unlimited paid time off (must be approved by management and reconcile with project commitments)." That's schedule info.
Benefits list: "Generous compensation and bonuses based on individual and company achievement." Wait that's also pay; but benefits list includes: "Generous compensation and bonuses based on individual and company achievement." Actually that's under Benefits in the posting. But we already used that for Pay. However the posting lists under Benefits: "Generous compensation and bonuses based on individual and company achievement." Then "Flexible work schedule." etc. So we need to not duplicate. We should keep Pay separate maybe as "Compensation". But the instruction says use heading Pay if posting actually states them. The posting states compensation under Benefits. But we can still create a Pay section with that content. However we must not duplicate content. We could put compensation under Pay and not repeat under Benefits. But then Benefits would lose that line. However the posting's Benefits section includes that line; we could keep it under Benefits as well but that would duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication? It says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not inventing or summarizing away; it's repeating. Might be okay but better to avoid duplication. We could keep compensation under Pay and still mention it under Benefits? Might be considered duplication but not prohibited. However to be safe, we could keep compensation under Pay and not include it under Benefits, but then we lose that benefit line. But the benefit line is essentially compensation; it's still substantive. If we omit it, we lose info. So better to include it under Pay and also keep it under Benefits? Might be considered duplication but still preserving. The instruction didn't forbid duplication explicitly, only said do not invent or summarize away detail. Duplication is not summarizing away. I'd lean to include it under Pay and also keep it under Benefits? Might be seen as redundant but okay.
Alternatively, we could treat the compensation line as part of Benefits and not create a Pay section. But the instruction says create Pay section only if posting actually states them. It does state compensation, albeit under Benefits. So we could create Pay section with that line. Then Benefits section would have the rest: flexible schedule, remote work, unlimited PTO, health/dental/vision, 401k, life/AD&D. That seems reasonable.
Thus:
- About the role: prose paragraph(s) about company and role.
- Responsibilities: ul list.
- Requirements: ul list of required qualifications.
- Qualifications: ul list of preferred qualifications (experience with automated material handling solutions and control systems).
- Benefits: ul list (flexible work schedule, remote work location, unlimited PTO, health/dental/vision, employer-sponsored 401(k), life and AD&D insurance). Also maybe we could include "Generous compensation and bonuses based on individual and company achievement." but we moved to Pay.
- Pay:
Generous compensation and bonuses based on individual and company achievement.
- Schedule: maybe we already included flexible work schedule under Benefits; but we also have Schedule heading. The posting mentions flexible work schedule, remote work location, unlimited PTO. Those could be considered schedule. But we already put them under Benefits. To avoid duplication, we could move schedule items to Schedule section and keep Benefits for insurance etc. Let's think: The posting's Benefits bullet list includes: "Generous compensation and bonuses based on individual and company achievement. Flexible work schedule. Remote work location (within driving distance of an airport). Unlimited paid time off (must be approved by management and reconcile with project commitments). Health, dental, and vision insurance. Employer-sponsored 401(k). Life and AD&D insurance."
Thus we can split: Pay: compensation. Schedule: flexible work schedule, remote work location, unlimited PTO. Benefits: health/dental/vision, 401k, life/AD&D.
That seems logical and avoids duplication.
Thus sections:
About the role (prose)
Responsibilities (ul)
Requirements (ul) - required qualifications
Qualifications (ul) - preferred qualifications
Pay (p) - compensation
Schedule (ul) - flexible work schedule, remote work location, unlimited PTO
Benefits (ul) - health/dental/vision, employer-sponsored 401(k), life and AD&D insurance
We must not include headings with empty content. All have content.
Now format: Use for each heading. Use - for lists. Use
for prose.
We must output only HTML fragment, no /, no markdown.
Let's craft.
About the role: combine first paragraphs: "Maveneer is an engineering design firm that specializes in the design and implementation of distribution center and manufacturing operations, both new and retrofit. We are a rapidly growing startup founded by industry leaders in industrial automation, material handling systems, and operational leadership. We are looking for exceptionally talented, high-integrity people who want to be part of a team that does great work, supports one another, and strives to build a company at which we can all be proud and excited to work. Fueling this endeavor requires those who are multidimensional. As a Project Manager, you will lead our clients and a professional team through the full lifecycle of building the concepts we design – from detailed specifications of equipment and systems, bid and supplier selection, manufacturing and delivery, code development, system and equipment installation, testing, training, go-live, and stabilization. You will be the leader of the build effort, and you are ultimately responsible for all planning, execution, risk management, communications, and financial controls across a broad range of stakeholders. MOST IMPORTANTLY — YOU TAKE EXTREME OWNERSHIP IN EVERYTHING YOU DO. YOU MAKE IT HAPPEN. YOU PROACTIVELY ASK FOR HELP WHEN YOU NEED IT, BUT YOU DON’T WAIT FOR SOMEONE ELSE TO GET IT DONE."
That's a bit long but okay.
Responsibilities list: items from "Role Responsibilities:" after colon. Let's extract:
- Serve as the primary customer interface, maintaining strong relationships and clear, consistent communication throughout the project lifecycle.
- Lead multi-disciplinary teams and subcontractors, managing conflict, establishing priorities, and coordinating concurrent project activities.
- Assume full administrative, contractual, technical, and financial control of assigned projects, including P&L ownership.
- Manage project cash flow and deliverables maintaining overall responsibility for project profitability.
- Maintain system design integrity to meet performance and technical specification requirements across automated material handling systems, controls, and integrated equipment.
- Manage the project master schedule using various MS tools.
- Provide monthly project status reports to leadership and key stakeholders.
- Promote effective collaboration across departments and support the development of project team members.
- Identify, assess, and manage project risks and opportunities as they arise.
- Develop and oversee project-specific commissioning plans, schedules, and scopes of work.
Make each
- .
Requirements list (required qualifications):
- Engineering and/or Construction Management degree, or equivalent industry experience.
- 8+ years of project management experience, with a demonstrated record of successfully delivering large-scale industrial, construction, or manufacturing projects.
- Real experience owning project financials, risk, and P&L.
- Strong stakeholder management and communication skills, both verbal and written.
- Proficiency with project scheduling and management tools.
- Strong business acumen and project management skills.
- Demonstrated leadership capability to build and motivate cross-functional project teams.
Qualifications list (preferred):
- Experience with automated material handling solutions and control systems.
Pay:
Generous compensation and bonuses based on individual and company achievement.
Schedule list:
- Flexible work schedule.
- Remote work location (within driving distance of an airport).
- Unlimited paid time off (must be approved by management and reconcile with project commitments).
Benefits list:
- Health, dental, and vision insurance.
- Employer-sponsored 401(k).
- Life and AD&D insurance.
Check we didn't miss any: The posting also mentions "This position is based in the United States and requires up to 70%
for prose. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections with real content. Let's map: - About the role: company description and role overview (first paragraph). Yes. - Responsibilities: list of responsibilities. - Requirements: maybe required qualifications. - Qualifications: maybe preferred qualifications? Or we could treat Requirements as required qualifications and Qualifications as preferred? But we need to avoid duplication. Could combine required and preferred under Requirements and Qualifications? The instruction says use those headings if content exists. We have both required and preferred qualifications. So we can have Requirements (required) and Qualifications (preferred). Or we could have Requirements (required) and Skills (maybe preferred). But better: Requirements = required qualifications; Qualifications = preferred qualifications; Skills maybe not needed if covered. However we could still include Skills if there are specific skills mentioned: proficiency with project scheduling and management tools, strong stakeholder management, communication, business acumen, leadership capability. Those are skills. Could put under Skills. Thus we can have sections: About the role, Responsibilities, Requirements (required qualifications), Skills (key skills), Qualifications (preferred qualifications), Benefits, Pay, Schedule. Check each for content: About the role: company description and role overview paragraph. Responsibilities: bullet list. Requirements: list of required qualifications (Engineering/Construction Management degree, 8+ years PM experience, owning project financials, risk, P&L, stakeholder management, proficiency with scheduling tools, strong business acumen, leadership capability). That's a list. Skills: maybe we can extract specific skills: "Strong stakeholder management and communication skills, both verbal and written.", "Proficiency with project scheduling and management tools", "Strong business acumen and project management skills.", "Demonstrated leadership capability to build and motivate cross-functional project teams." Those are similar to requirements but could be skills. However we might avoid duplication. The instruction says preserve ALL substantive information; we can keep them under Requirements and not duplicate under Skills. But we need to decide if we need Skills section. If we don't have distinct skill content beyond what's already in Requirements, we could omit Skills to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine required qualifications and skills into Requirements. Then we could have Qualifications for preferred qualifications (experience with automated material handling solutions and control systems). That's substantive. Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule. Check Pay: "Generous compensation and bonuses based on individual and company achievement." That's specific enough for Pay. Schedule: "Flexible work schedule. Remote work location (within driving distance of an airport). Unlimited paid time off (must be approved by management and reconcile with project commitments)." That's schedule info. Benefits list: "Generous compensation and bonuses based on individual and company achievement." Wait that's also pay; but benefits list includes: "Generous compensation and bonuses based on individual and company achievement." Actually that's under Benefits in the posting. But we already used that for Pay. However the posting lists under Benefits: "Generous compensation and bonuses based on individual and company achievement." Then "Flexible work schedule." etc. So we need to not duplicate. We should keep Pay separate maybe as "Compensation". But the instruction says use heading Pay if posting actually states them. The posting states compensation under Benefits. But we can still create a Pay section with that content. However we must not duplicate content. We could put compensation under Pay and not repeat under Benefits. But then Benefits would lose that line. However the posting's Benefits section includes that line; we could keep it under Benefits as well but that would duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication? It says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not inventing or summarizing away; it's repeating. Might be okay but better to avoid duplication. We could keep compensation under Pay and still mention it under Benefits? Might be considered duplication but not prohibited. However to be safe, we could keep compensation under Pay and not include it under Benefits, but then we lose that benefit line. But the benefit line is essentially compensation; it's still substantive. If we omit it, we lose info. So better to include it under Pay and also keep it under Benefits? Might be considered duplication but still preserving. The instruction didn't forbid duplication explicitly, only said do not invent or summarize away detail. Duplication is not summarizing away. I'd lean to include it under Pay and also keep it under Benefits? Might be seen as redundant but okay. Alternatively, we could treat the compensation line as part of Benefits and not create a Pay section. But the instruction says create Pay section only if posting actually states them. It does state compensation, albeit under Benefits. So we could create Pay section with that line. Then Benefits section would have the rest: flexible schedule, remote work, unlimited PTO, health/dental/vision, 401k, life/AD&D. That seems reasonable. Thus: - About the role: prose paragraph(s) about company and role. - Responsibilities: ul list. - Requirements: ul list of required qualifications. - Qualifications: ul list of preferred qualifications (experience with automated material handling solutions and control systems). - Benefits: ul list (flexible work schedule, remote work location, unlimited PTO, health/dental/vision, employer-sponsored 401(k), life and AD&D insurance). Also maybe we could include "Generous compensation and bonuses based on individual and company achievement." but we moved to Pay. - Pay:
Generous compensation and bonuses based on individual and company achievement.
- Schedule: maybe we already included flexible work schedule under Benefits; but we also have Schedule heading. The posting mentions flexible work schedule, remote work location, unlimited PTO. Those could be considered schedule. But we already put them under Benefits. To avoid duplication, we could move schedule items to Schedule section and keep Benefits for insurance etc. Let's think: The posting's Benefits bullet list includes: "Generous compensation and bonuses based on individual and company achievement. Flexible work schedule. Remote work location (within driving distance of an airport). Unlimited paid time off (must be approved by management and reconcile with project commitments). Health, dental, and vision insurance. Employer-sponsored 401(k). Life and AD&D insurance." Thus we can split: Pay: compensation. Schedule: flexible work schedule, remote work location, unlimited PTO. Benefits: health/dental/vision, 401k, life/AD&D. That seems logical and avoids duplication. Thus sections: About the role (prose) Responsibilities (ul) Requirements (ul) - required qualifications Qualifications (ul) - preferred qualifications Pay (p) - compensation Schedule (ul) - flexible work schedule, remote work location, unlimited PTO Benefits (ul) - health/dental/vision, employer-sponsored 401(k), life and AD&D insurance We must not include headings with empty content. All have content. Now format: Use for each heading. Use - for lists. Use
for prose.
We must output only HTML fragment, no /, no markdown.
Let's craft.
About the role: combine first paragraphs: "Maveneer is an engineering design firm that specializes in the design and implementation of distribution center and manufacturing operations, both new and retrofit. We are a rapidly growing startup founded by industry leaders in industrial automation, material handling systems, and operational leadership. We are looking for exceptionally talented, high-integrity people who want to be part of a team that does great work, supports one another, and strives to build a company at which we can all be proud and excited to work. Fueling this endeavor requires those who are multidimensional. As a Project Manager, you will lead our clients and a professional team through the full lifecycle of building the concepts we design – from detailed specifications of equipment and systems, bid and supplier selection, manufacturing and delivery, code development, system and equipment installation, testing, training, go-live, and stabilization. You will be the leader of the build effort, and you are ultimately responsible for all planning, execution, risk management, communications, and financial controls across a broad range of stakeholders. MOST IMPORTANTLY — YOU TAKE EXTREME OWNERSHIP IN EVERYTHING YOU DO. YOU MAKE IT HAPPEN. YOU PROACTIVELY ASK FOR HELP WHEN YOU NEED IT, BUT YOU DON’T WAIT FOR SOMEONE ELSE TO GET IT DONE."
That's a bit long but okay.
Responsibilities list: items from "Role Responsibilities:" after colon. Let's extract:
- Serve as the primary customer interface, maintaining strong relationships and clear, consistent communication throughout the project lifecycle.
- Lead multi-disciplinary teams and subcontractors, managing conflict, establishing priorities, and coordinating concurrent project activities.
- Assume full administrative, contractual, technical, and financial control of assigned projects, including P&L ownership.
- Manage project cash flow and deliverables maintaining overall responsibility for project profitability.
- Maintain system design integrity to meet performance and technical specification requirements across automated material handling systems, controls, and integrated equipment.
- Manage the project master schedule using various MS tools.
- Provide monthly project status reports to leadership and key stakeholders.
- Promote effective collaboration across departments and support the development of project team members.
- Identify, assess, and manage project risks and opportunities as they arise.
- Develop and oversee project-specific commissioning plans, schedules, and scopes of work.
Make each
- .
Requirements list (required qualifications):
- Engineering and/or Construction Management degree, or equivalent industry experience.
- 8+ years of project management experience, with a demonstrated record of successfully delivering large-scale industrial, construction, or manufacturing projects.
- Real experience owning project financials, risk, and P&L.
- Strong stakeholder management and communication skills, both verbal and written.
- Proficiency with project scheduling and management tools.
- Strong business acumen and project management skills.
- Demonstrated leadership capability to build and motivate cross-functional project teams.
Qualifications list (preferred):
- Experience with automated material handling solutions and control systems.
Pay:
Generous compensation and bonuses based on individual and company achievement.
Schedule list:
- Flexible work schedule.
- Remote work location (within driving distance of an airport).
- Unlimited paid time off (must be approved by management and reconcile with project commitments).
Benefits list:
- Health, dental, and vision insurance.
- Employer-sponsored 401(k).
- Life and AD&D insurance.
Check we didn't miss any: The posting also mentions "This position is based in the United States and requires up to 70%
for prose. We must output only HTML fragment, no /, no markdown. Let's craft. About the role: combine first paragraphs: "Maveneer is an engineering design firm that specializes in the design and implementation of distribution center and manufacturing operations, both new and retrofit. We are a rapidly growing startup founded by industry leaders in industrial automation, material handling systems, and operational leadership. We are looking for exceptionally talented, high-integrity people who want to be part of a team that does great work, supports one another, and strives to build a company at which we can all be proud and excited to work. Fueling this endeavor requires those who are multidimensional. As a Project Manager, you will lead our clients and a professional team through the full lifecycle of building the concepts we design – from detailed specifications of equipment and systems, bid and supplier selection, manufacturing and delivery, code development, system and equipment installation, testing, training, go-live, and stabilization. You will be the leader of the build effort, and you are ultimately responsible for all planning, execution, risk management, communications, and financial controls across a broad range of stakeholders. MOST IMPORTANTLY — YOU TAKE EXTREME OWNERSHIP IN EVERYTHING YOU DO. YOU MAKE IT HAPPEN. YOU PROACTIVELY ASK FOR HELP WHEN YOU NEED IT, BUT YOU DON’T WAIT FOR SOMEONE ELSE TO GET IT DONE." That's a bit long but okay. Responsibilities list: items from "Role Responsibilities:" after colon. Let's extract: - Serve as the primary customer interface, maintaining strong relationships and clear, consistent communication throughout the project lifecycle. - Lead multi-disciplinary teams and subcontractors, managing conflict, establishing priorities, and coordinating concurrent project activities. - Assume full administrative, contractual, technical, and financial control of assigned projects, including P&L ownership. - Manage project cash flow and deliverables maintaining overall responsibility for project profitability. - Maintain system design integrity to meet performance and technical specification requirements across automated material handling systems, controls, and integrated equipment. - Manage the project master schedule using various MS tools. - Provide monthly project status reports to leadership and key stakeholders. - Promote effective collaboration across departments and support the development of project team members. - Identify, assess, and manage project risks and opportunities as they arise. - Develop and oversee project-specific commissioning plans, schedules, and scopes of work. Make each
Generous compensation and bonuses based on individual and company achievement.
Schedule list: - Flexible work schedule. - Remote work location (within driving distance of an airport). - Unlimited paid time off (must be approved by management and reconcile with project commitments). Benefits list: - Health, dental, and vision insurance. - Employer-sponsored 401(k). - Life and AD&D insurance. Check we didn't miss any: The posting also mentions "This position is based in the United States and requires up to 70%