Senior Mechanical Engineer

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must not include Job ID etc. Remove boilerplate: EEO, equal opportunity, scam warning, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's parse the posting. Content: "Why You’ll Love Working Here" bullet points: culture values integrity, teamwork, professional growth; opportunities to lead and contribute to game-changing projects; ownership mindset—ESOP; competitive compensation & benefits; emphasis on work-life balance and flexibility; leadership team that listens and supports ambitions. Then "At Guernsey, we’re more than engineers..." paragraph. Then "What You’ll Be Doing" with subheadings: Design Leadership, Team & Project Leadership, Client & Business Engagement, Technical Focus Areas. Then "What You Bring To The Team" list: Bachelor’s degree in Mechanical Engineering or related field; Licensed Professional Engineer (PE) required; 15+ years of experience in mechanical building systems design; Strong proficiency in AutoCAD, Revit, and Microsoft Office Suite; Excellent communication, leadership, and mentoring skills; Proven ability to manage complex projects and deliver high-quality outcomes; Familiarity with energy modeling software (e.g., Trane TRACE, EnergyPlus) is a plus. Then "Essential Physical Functions" list: Sit/stand at a desk or computer; Walk, stoop, stand and move around job sites; Travel and occasional site visits requiring stooping, standing, and lifting up to 30 lbs.; Frequent communication via phone, video, or in-person meetings; Ability to focus on digital and paper-based information for extended periods; Some project-based travel may be required. Then "Let’s Build the Future Together!" motivational paragraph. Then "We Are an Equal Opportunity Employer" etc (boilerplate to remove). Then "Education Required Bachelors or better in Mechanical Engineering or related field" (duplicate of earlier). "Skills Required AutoCAD Revit" (duplicate). Then more EEO. We need to decide sections. We have content for "About the role" maybe the introductory paragraphs about company culture and mission. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. - About the role: could include the "Why You’ll Love Working Here" and the introductory paragraph about Guernsey. - Responsibilities: the "What You’ll Be Doing" sections (Design Leadership, Team & Project Leadership, Client & Business Engagement, Technical Focus Areas). Could be a list. - Requirements: maybe the "What You Bring To The Team" (degree, PE, years experience). Also "Education Required" etc. - Qualifications: maybe overlapping with Requirements; but we should avoid duplication. Could combine. - Skills: list of technical skills: AutoCAD, Revit, Microsoft Office Suite, energy modeling software (plus maybe communication, leadership). Could be separate. - Benefits: we have "competitive compensation & benefits", "emphasis on work-life balance and flexibility", "ownership mindset—our ESOP structure". Also maybe "competitive compensation & benefits" is vague but we have something. Should we create Benefits section? The instruction: only include a section when posting has real, specific content for it — 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. We have "competitive compensation & benefits" (specific? It's generic but states benefits). Also "emphasis on work-life balance and flexibility". Also "ownership mindset—our ESOP structure". That's specific enough? It mentions ESOP. So we can include Benefits section with those points. - Pay: not specified beyond "competitive compensation". That's vague; maybe we should not create Pay section because it's not specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation & benefits". That's a statement about compensation, but not specific. Might be considered too vague? The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is somewhat vague but still a statement. I'd lean to include Benefits but not Pay, as Pay would be redundant. - Schedule: not mentioned; no schedule info. So omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to avoid duplication. Let's extract unique content. About the role: - "Why You’ll Love Working Here" bullet points: culture values integrity, teamwork, professional growth; opportunities to lead and contribute to game-changing projects; ownership mindset—our ESOP structure means your success is our success; competitive compensation & benefits; emphasis on work-life balance and flexibility; a leadership team that listens and supports your ambitions. - Then paragraph: "At Guernsey, we’re more than engineers, architects, and consultants—we’re changemakers with a shared purpose. We’re driven by curiosity, united by collaboration, and committed to building a better future—together. We’re redefining what it means to work in the AEC industry, blending innovation with integrity and giving every employee a real stake in the outcome. Here, your ideas matter, your growth is prioritized, and your career has limitless potential." We can combine into a few

paragraphs or a

for bullet points. The bullet points are list items; we can put them in
• . The paragraph after can be

  . Responsibilities: We have headings under "What You’ll Be Doing": Design Leadership, Team & Project Leadership, Client & Business Engagement, Technical Focus Areas. Each has bullet points. We can create a

  for responsibilities, each item maybe a sentence. Could also group under subheadings but instruction only allows

  for section headings, not subheadings. So we can just list all responsibilities as

  items. Let's extract: Design Leadership: - Lead the execution of complex HVAC system designs using advanced engineering techniques and technologies. - Conduct energy modeling, life cycle cost analysis, and feasibility studies for proposed systems. - Drive innovation in system selection, integration, and sustainability strategies. - Oversee the production of construction documents and specifications. Team & Project Leadership: - Provide mentorship and technical guidance to junior and mid-level engineers. - Coordinate cross-discipline design efforts and lead internal quality reviews. - Manage scope, schedule, and deliverables on key projects. - Support proposal development and pursuit strategy, including go/no-go planning. Client & Business Engagement: - Build and maintain strong relationships with clients and industry partners. - Attend client meetings and lead technical discussions. - Support business development efforts through project interviews, client presentations, and marketing activities. Technical Focus Areas: - HVAC load calculations and energy analysis - Equipment selection and system layout - Ductwork and hydronic piping system design - Controls and automation system design - Plumbing and domestic water systems - Code compliance, LEED integration, and sustainable design best practices We'll put each as

  . Requirements: From "What You Bring To The Team": Bachelor’s degree in Mechanical Engineering or related field; Licensed Professional Engineer (PE) required; 15+ years of experience in mechanical building systems design. Also "Education Required Bachelors or better in Mechanical Engineering or related field" duplicate. Thus Requirements: Bachelor’s degree in Mechanical Engineering or related field; Licensed Professional Engineer (PE) required; 15+ years of experience in mechanical building systems design. Qualifications: Maybe we can include "Strong proficiency in AutoCAD, Revit, and Microsoft Office Suite; Excellent communication, leadership, and mentoring skills; Proven ability to manage complex projects and deliver high-quality outcomes; Familiarity with energy modeling software (e.g., Trane TRACE, EnergyPlus) is a plus". These could be qualifications or skills. The instruction separates Skills and Qualifications. Usually Qualifications are things like degree, certifications, experience; Skills are technical abilities. But we already put degree, PE, experience in Requirements. Could move those to Qualifications and keep Requirements for something else? However we need to avoid duplication. Let's think: The posting has "What You Bring To The Team" which includes both qualifications and skills. We could split: Requirements: Bachelor’s degree, PE license, 15+ years experience. Qualifications: Strong proficiency in AutoCAD, Revit, Microsoft Office Suite; Excellent communication, leadership, mentoring skills; Proven ability to manage complex projects and deliver high-quality outcomes; Familiarity with energy modeling software (e.g., Trane TRACE, EnergyPlus) is a plus. Skills: maybe list specific software: AutoCAD, Revit, Microsoft Office Suite, energy modeling software. But that would duplicate. Better: Use Requirements for education/experience/license. Use Skills for technical and soft skills. Qualifications maybe not needed if we already covered. But we need to output only sections with real content; we can omit Qualifications if content overlaps. However we have content for Qualifications (like "Proven ability to manage complex projects...") which is not strictly a skill but a qualification. Could put under Qualifications. Let's decide: - About the role: as described. - Responsibilities: list. - Requirements: Bachelor’s degree in Mechanical Engineering or related field; Licensed Professional Engineer (PE) required; 15+ years of experience in mechanical building systems design. - Qualifications: Strong proficiency in AutoCAD, Revit, and Microsoft Office Suite; Excellent communication, leadership, and mentoring skills; Proven ability to manage complex projects and deliver high-quality outcomes; Familiarity with energy modeling software (e.g., Trane TRACE, EnergyPlus) is a plus. - Skills: maybe we can list specific tools: AutoCAD, Revit, Microsoft Office Suite, energy modeling software (Trane TRACE, EnergyPlus). But that duplicates Qualifications. Could instead put Skills as the same list but maybe we should not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Skills into one section called "Qualifications & Skills" but headings are fixed. We could just have Qualifications and omit Skills, or have Skills and omit Qualifications. Which is more appropriate? The posting includes both technical proficiencies and soft skills. The heading "Skills" seems fitting for both technical and soft skills. "Qualifications" often refers to degree, certifications, experience. Since we already placed those in Requirements, we can put all remaining under Skills. Thus: - Requirements: degree, PE, years experience. - Skills: Strong proficiency in AutoCAD, Revit, and Microsoft Office Suite; Excellent communication, leadership, and mentoring skills; Proven ability to manage complex projects and deliver high-quality outcomes; Familiarity with energy modeling software (e.g., Trane TRACE, EnergyPlus) is a plus. - Benefits: competitive compensation & benefits; emphasis on work-life balance and flexibility; ownership mindset—our ESOP structure means your success is our success; leadership team that listens and supports your ambitions (maybe that's more about culture but could be benefits). Also "opportunities to lead and contribute to game-changing projects" maybe more about role. But we can include benefits: competitive compensation & benefits; work-life balance/flexibility; ESOP ownership; leadership support. We should not duplicate content already in About the role. The About the role already includes those bullet points. So Benefits section could just highlight those same points? That would duplicate. Better to keep About the role for culture and mission, and Benefits for tangible benefits: competitive compensation & benefits, work-life balance/flexibility, ESOP ownership. The leadership team listening could be part of culture. Thus Benefits: competitive compensation & benefits; emphasis on work-life balance and flexibility; ownership mindset—our ESOP structure means your success is our success. We could also include "op