Mechanical Project Manager - Healthcare
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings; we should stick to those. So we should not add other headings like "About the company". Could incorporate company info into About the role or maybe omit if not fitting. But we need to preserve ALL substantive information; we cannot drop company description if it's substantive. However we could embed it within About the role or maybe a separate paragraph without heading? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for sections. Safer to include only those headings that have content. We could put company description under About the role as part of role description. Or we could add a paragraph without heading after the sections? The instruction says output ONLY the HTML fragment; we can include paragraphs not under headings. So we can include company description as a
after sections, not under a heading. That preserves info. Now we need to avoid boilerplate: EEO, legal, application instructions, "Check out the RQ Careers page for more information on life at GTMO." That's maybe not boilerplate but could be considered navigation? It's a reference to careers page; maybe we keep? It's not substantive about job; but it's not boilerplate. Might be okay to keep. However it's like a call to action; could be considered application instruction? It's not exactly instruction to apply. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "Check out the RQ Careers page for more information on life at GTMO." is navigation-ish; maybe remove. Also "Join RQ, apply today!" is application instruction; remove. Also "Since its founding in 1996..." is company description; keep. Now let's extract content: About the role: Could combine first sentences: "Take the lead on impactful healthcare construction projects by joining our team as a Mechanical Project Manager supporting the development of a large ambulatory care center and dental clinic. This opportunity is based in Guantanamo Bay, Cuba. This role offers a competitive salary ranging from $130,000 to $150,000, along with a comprehensive benefits package." But salary and benefits maybe better placed in Pay and Benefits sections. So About the role could focus on role description and location. Let's craft:
Take the lead on impactful healthcare construction projects by joining our team as a Mechanical Project Manager supporting the development of a large ambulatory care center and dental clinic. This opportunity is based in Guantanamo Bay, Cuba.
Responsibilities: the paragraph about overseeing mechanical construction operations. Requirements: maybe the minimum education? But they have Qualifications heading. We could treat Requirements as the mandatory items: high school diploma or GED minimum, 5+ years experience, etc. Qualifications could be preferred items. But the posting lumps them together under "Qualifications". To follow instruction, we can have both Requirements and Qualifications sections if we can split content meaningfully. Let's see: From the text: "Qualifications A 4-year degree in Mechanical Engineering or Construction Management is preferred. A high school diploma or GED is the minimum formal education required for this position.Courses in project management, construction management, mechanical trade school, BIM and CADD, etc. preferred.Five or more years work experience as a Mechanical Project Manager responsible for numerous projects and sizes (of the mechanical scope) of at least $5,000,000 (commercial/government) required.Government, military, or large commercial construction experience preferred. Work in the design-build industry is highly desirable.Demonstrated track record of managing projects in medical centers, dental facilities, or other healthcare environments preferred.Computer literacy (Outlook, Word, Excel, and Primavera P6) preferred. Training can be provided.Specific software literacy (BIM) preferred. Training can be provided" We can separate: - Requirements (mandatory): high school diploma or GED minimum; 5+ years experience as Mechanical Project Manager managing projects >= $5M; maybe relocation required? That's also a requirement. - Qualifications (preferred): 4-year degree in Mechanical Engineering or Construction Management; courses in PM, CM, mechanical trade school, BIM, CADD; government/military/large commercial experience; design-build industry; healthcare environment experience; computer literacy; BIM literacy. Skills: could be computer literacy, BIM, etc. But we already have those in qualifications. Could make Skills section for software literacy etc. But to avoid thin sections, maybe combine. Given instruction: "Prefer a few substantive sections over many thin ones." So we might just have Qualifications section covering both required and preferred, and maybe Skills not needed. But we need to include sections only when posting has real specific content. It does have qualifications content. So we can have Qualifications. Pay: salary range. Benefits: list of perks. Schedule: none -> omit. Now we need to format lists using- for any list of duties/requirements/benefits.
Thus:
- Responsibilities: could be a
- with each duty as
- . The paragraph contains multiple sentences; we can split into list items.
- Benefits: list items.
- Qualifications: maybe list items for each qualification.
- Requirements: maybe list items.
But we need to decide if we want Requirements section. Since we have Qualifications, maybe we can omit Requirements to avoid thin sections. However the posting includes both required and preferred; we could combine them into Qualifications but separate required vs preferred? Might be okay to have just Qualifications.
But the instruction says use headings for e.g. Requirements, Qualifications. It doesn't forbid having both. But we should avoid thin sections. If we put all qualifications in one section, it's substantive.
Let's craft:
About the role
Take the lead on impactful healthcare construction projects by joining our team as a Mechanical Project Manager supporting the development of a large ambulatory care center and dental clinic. This opportunity is based in Guantanamo Bay, Cuba.
Responsibilities
- Oversee and manage all mechanical construction operations on-site, ensuring work is executed safely, efficiently, and in compliance with project specifications.
- Work closely with mechanical superintendents, subcontractors, and internal team members to coordinate daily activities and maintain alignment with project goals.
- From early design coordination through project completion, play a key role in delivering high-quality results that meet government standards, budget expectations, and project timelines.
- Contribute to meaningful healthcare infrastructure projects while working in a dynamic and mission-driven environment.
Qualifications
- High school diploma or GED is the minimum formal education required.
- Five or more years work experience as a Mechanical Project Manager responsible for numerous projects with mechanical scope of at least $5,000,000 (commercial/government).
- Relocation to Guantanamo Bay is required.
- Preferred: 4-year degree in Mechanical Engineering or Construction Management.
- Preferred: Courses in project management, construction management, mechanical trade school, BIM and CADD.
- Preferred: Government, military, or large commercial construction experience.
- Preferred: Work in the design-build industry.
- Preferred: Demonstrated track record of managing projects in medical centers, dental facilities, or other healthcare environments.
- Preferred: Computer literacy (Outlook, Word, Excel, and Primavera P6). Training can be provided.
- Preferred: Specific software literacy (BIM). Training can be provided.
Benefits
- . The paragraph contains multiple sentences; we can split into list items.
- Benefits: list items.
- Qualifications: maybe list items for each qualification.
- Requirements: maybe list items.
But we need to decide if we want Requirements section. Since we have Qualifications, maybe we can omit Requirements to avoid thin sections. However the posting includes both required and preferred; we could combine them into Qualifications but separate required vs preferred? Might be okay to have just Qualifications.
But the instruction says use headings for e.g. Requirements, Qualifications. It doesn't forbid having both. But we should avoid thin sections. If we put all qualifications in one section, it's substantive.
Let's craft: