Jobs · Engineering · Minnesota

Project Engineer

Horwitz · New Hope, MN · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about company, then description of role. We need headings:

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive info. Let's parse content: Intro: "At Horwitz, we don’t just offer jobs—we build careers. For over 100 years, we’ve been a leader in HVAC, plumbing, electrical services, delivering exceptional service while fostering a supportive and innovative workplace. Joining our team means working with passionate professionals in a culture built on safety, accountability, professionalism, motivation, curiosity, and a can-do attitude. We’re committed to your growth with training, mentorship, and advancement opportunities. Along with competitive benefits—you’ll be part of a company that values its employees and makes a positive impact in the community. Join Horwitz and become part of a legacy of excellence and opportunity." That's about company and role intro. 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. So we can put an

About the role

and then paragraph(s) containing that intro and maybe role description. Then "The Project Engineer at Horwitz plays a critical role..." That's also role description. Could be part of About the role. Then "At Horwitz, we are guided by our core values..." That's also part of role. Then "Key Responsibilities" heading in source. We'll create

Responsibilities

and list responsibilities as
  • . The responsibilities include many bullet-like items but they are in paragraphs with line breaks. Need to extract each responsibility as list items. Let's list responsibilities from the text: - Core Values (list each value with description) Actually they list core values with description. Might be considered responsibilities? Could be separate but we can include under Responsibilities. - Documentation & Contract Management: * Create and manage submittals * Review Horwitz Way "Contract Review" Document * Understand the layout of project folders in Box and manage documents (ref PE L2) * Complete receipt inspections for project equipment deliveries * Apply for permits from the city or DOLI with assistance from the project managers. * Ability to gather required closeout documents with assistance from a PM (IOMs, warranty, startup forms, owner training, As-builts, punchlist) - Cost Management: * Send out equipment and material pricing requests using schedules, specifications, and material lists from Design * Understand the concept of project change orders and proposals. * Begin to understand forecasting in construction projects * Get familiar with estimating tools (estimate spreadsheet, QuoteSoft, PriceDuct, MCAA-WEBLEM) - Technical Skills & Knowledge: * Familiarize yourself with the different types of materials used in mechanical construction * Begin to understand ductwork, hydronic, plumbing construction methods. * Begin to understand HVAC, hydronic, plumbing system operation and design. * Understand ductwork, hydronic, plumbing construction methods (duplicate? maybe keep) * Begin to understand electrical requirements relevant to mechanical construction. * Begin to understand temperature controls requirements relevant to mechanical construction. * Begin to understand mechanical/plumbing code requirements, ASHRAE, IECC, etc. * Know who to talk to or where to find information regarding these codes. * Understand the prefabrication process and concepts * Understand the various roles and scope of work of Horwitz subcontractors * Complete receipt inspections for project equipment deliveries (duplicate) * Understand commodity (hardware, pipe, fittings, hangers, ductwork, etc.) material buyout pricing * Understanding roles of Foreman, Journeyman, Apprentices; and their labor rates - Communication & Leadership: * Attend meetings with customers/ownership/general contractor. * Adheres to guidance from the Project Manager and field team; demonstrates a strong motivation to learn, assume greater responsibilities, and advance professionally. * Learn how project managers develop relationships with customers, trade partners, and general contractors. * Attend internal meetings such as weekly foreman meetings, prefab meetings, constraint meetings, lessons learned, WIP, project handoff meetings. * Understand the concept and process of different types of billings (GMP, simple, T&M, lump sump) - Schedule, Project Planning & Coordination: * Understand project schedules * Learn the basics of our labor force and requirements based on project scope & timeline. * Attend and listen to weekly labor meetings. * Attend pull plan meetings. - Safety & Compliance: * Learn the basics of our labor force and requirements based on project scope & timeline. * Attend and listen to weekly labor meetings. (duplicate) - Other: * Cultivate a fun and productive work environment. * Be an encouraging leader and mentor. * Perform other duties as assigned. * Get better every day. We need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep duplicates if they appear in source. But we could combine duplicates? Might be considered summarizing away detail. Safer to keep as they appear, but we could note duplicates as separate items; but that may be redundant. However the instruction says preserve ALL substantive information; does not forbid removing exact duplicates? It says do NOT invent or summarize away detail. Removing duplicate lines could be summarizing away detail (though it's same detail). Might be okay to keep one instance. I'd keep one instance for each unique responsibility; duplicates may be considered noise but not invented. I'd keep them but could combine? I'd keep unique items to avoid redundancy but still preserve info. I'd note that duplicates appear but we can keep one. Now Requirements/Education: "Education Bachelor’s degree in Mechanical Engineering, Construction Management, or a related field is preferred." That's a requirement/qualification. Could be under Requirements or Qualifications. We'll put

    Requirements

    with

    or

      . Since it's a single line, we can use

      . Skills: The "Technical Skills & Knowledge" etc could be under Skills. But we already have many skill items under Responsibilities. Might be better to separate: Responsibilities for duties, Skills for technical skills. However the posting lumps them. We could create a Skills section for the technical skills list. But we need to avoid thin sections. Perhaps combine under Responsibilities is fine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we keep only About the role, Responsibilities, Requirements (education), Benefits (since they mention competitive benefits). Benefits: They mention "Along with competitive benefits—you’ll be part of a company that values its employees..." and later "What Sets Us Apart? Industry Leadership... Competitive Benefits: We provide a comprehensive benefits package, including health insurance, retirement plans, supplemental insurance and competitive PTO." So we have benefits details. So we can create Benefits section. Pay and Schedule: Not mentioned specifically. So we omit those sections. Thus sections: About the role, Responsibilities, Requirements, Benefits. Now we need to output only HTML fragment, no /. Use

      for headings. Use
      • for lists. Use

        for prose. We need to ensure we don't include boilerplate like EEO etc. Not present. Now craft content. About the role paragraph(s): Combine intro and role description. Let's write:

        At Horwitz, we don’t just offer jobs—we build careers. For over 100 years, we’ve been a leader in HVAC, plumbing, electrical services, delivering exceptional service while fostering a supportive and innovative workplace. Joining our team means working with passionate professionals in a culture built on safety, accountability, professionalism, motivation, curiosity, and a can-do attitude. We’re committed to your growth with training, mentorship, and advancement opportunities. Along with competitive benefits—you’ll be part of a company that values its employees and makes a positive impact in the community. Join Horwitz and become part of a legacy of excellence and opportunity.

        The Project Engineer at Horwitz plays a critical role in supporting Project Managers across all divisions, including Construction, Service, Electrical, Temperature Controls, Industrial Ventilation, Mechanical Insulation, and Millwrights. The Project Engineer will assist in coordinating project activities to ensure that cost, schedule, document control, and quality standards are consistently met. This position offers exposure to every aspect of the construction process, providing a solid foundation for a future career as a Project Manager.

        At Horwitz, we are guided by our core values: Safe, Accountable, Professional, Motivated, Curious, and Can-Do. These values are integral to the role and will shape your approach to all tasks and interactions as you contribute to the success of our projects and company.

        That's About the role. Now Responsibilities: We'll list as
        • items. We'll need to capture all responsibilities from the sections. Let's compile unique items: From Core Values (maybe we treat as responsibilities but we already mentioned core values in About; but we could still list them under Responsibilities as items). However to avoid duplication, maybe we keep core values in About only. But the instruction says preserve ALL substantive information; core values are substantive. If we omit them from Responsibilities, we still have them in About, so preserved. Good. Now list responsibilities: Documentation & Contract Management: - Create and manage submittals - Review Horwitz Way "Contract Review" Document - Understand the layout of project folders in Box and manage documents (ref PE L2) - Complete receipt inspections for project equipment deliveries - Apply for permits from the city or DOLI with assistance from the project managers. - Ability to gather required closeout documents with assistance from a PM (IOMs, warranty, startup forms, owner training, As-builts, punchlist) Cost Management: - Send out equipment and material pricing requests using schedules, specifications, and material lists from Design - Understand the concept of project change orders and proposals. - Begin to understand forecasting in construction projects - Get familiar with estimating tools (estimate spreadsheet, QuoteSoft, PriceDuct, MCAA-WEBLEM) Technical Skills & Knowledge: - Familiarize yourself with the different types of materials used in mechanical construction - Begin to understand ductwork, hydronic, plumbing construction methods. - Begin to understand HVAC, hydronic, plumbing system operation and design. - Understand ductwork, hydronic, plumbing construction methods (duplicate of earlier? keep) - Begin to understand electrical requirements relevant to mechanical construction. - Begin to understand temperature controls requirements relevant to mechanical construction. - Begin to understand mechanical/plumbing code requirements, ASHRAE, IECC, etc. - Know who to talk to or where to find information regarding these codes. - Understand the prefabrication process and concepts - Understand the various roles and scope of work of Horwitz subcontractors - Complete receipt inspections for project equipment deliveries (duplicate) - Understand commodity (hardware, pipe, fittings, hangers, ductwork, etc.) material buyout pricing - Understanding roles of Foreman, Journeyman, Apprentices; and their labor rates Communication & Leadership: - Attend meetings with customers/ownership/general contractor. - Adheres to guidance from the Project Manager and field team; demonstrates a strong motivation to learn, assume greater responsibilities, and advance professionally. - Learn how project managers develop relationships with customers, trade partners, and general contractors. - Attend internal meetings such as weekly foreman meetings, prefab meetings, constraint meetings, lessons learned, WIP, project handoff meetings. - Understand the concept and process of different types of billings (GMP, simple, T&M, lump sump) Schedule, Project Planning & Coordination

Similar jobs

Project Engineer

DPR ConstructionSan Francisco, CA· 1 mo ago
Information Technology$70k–$99k/yrapply on mydpr.wd5.myworkdayjobs.com

Project Engineer

ArcadisBuffalo, NY· 1 mo ago
OTHR$88k–$147k/yrapply on jobs.arcadis.com

Project Engineer

Samet CorporationSavannah, GA· 1 mo ago
Engineeringapply on recruiting.ultipro.com

Project Engineer

The Walsh Group - Walsh Construction & Archer WesternGoodyear, AZ· 1 mo ago
Information Technologyapply on rr.jobsyn.org

Project Engineer

TerraconGreensboro, NC· 5 mo ago
Engineeringapply on careers.terracon.com

Project Engineer

Liles ConstructionSpartanburg, SC· 6 mo ago
Engineeringapply on de.jobsyn.org