Electrical Engineering New Graduate | New York, NY
IMEG · Broad Street–Water Street Historic District, New York, United States · 4 wk ago
Consulting$79k–$83k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading only if content exists.
We must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Keep substantive info.
Let's parse content:
- Intro: "100% Employee-Owned | Big-firm resources, local-team relationships, ONE IMEG culture This posting is for Summer 2027 New Graduate opportunities. IMEG is hiring an Electrical Engineering New Graduate in New York, NY, to support the analysis, design, and implementation oversight of electrical systems in buildings. This entry-level role offers hands-on design, analysis, and project execution experience, with mentorship, training, and opportunities to grow your expertise from day one. You will work closely with experienced engineers and consultants to help develop practical engineering solutions for clients. In this role, you will support project planning and scheduling, document design decisions and client instructions, participate in quality control processes, and collaborate with multidisciplinary teams to meet project goals and client expectations across government/municipal and science and technology work, advancing high-performance, energy-efficient design aligned with MEP2050 and AIA2030."
That's about the role. Could be "About the role" section.
- "At a Glance" bullet list: Location: New York, NY; Discipline: Electrical; Markets: Government/Municipal and Science & Technology; Ownership: 100% employee-owned (ESOP); Travel: Up to 5%; Work Schedule: Full-time hybrid; Sponsorship: Not available.
We need to include Pay and Schedule sections only if stated. Pay: later we have "State of New York Salary Range: $79,000 – $83,000 per year". So Pay section exists. Schedule: "Work Schedule: Full-time hybrid" is in At a Glance; also maybe mention schedule elsewhere. So we can have Schedule section.
Benefits: later they list benefits: "Medical, dental, and vision coverage starting day one, with preventive care at 100%, a $50/month wellness credit, and a Calm subscription", "Generous time off, including 6 paid holidays and 3 additional floating holidays", "PE, SE, and other license exam prep, with a clear path from EIT to PE", "Dress for Your Day flexibility (wear what fits your day)", "Employee ownership (ESOP): fully vested at all times, with a 3% to 6% company contribution, plus year-end profit sharing", "IDEA Program: a firm-wide innovation accelerator where employees across every discipline develop and scale new tools, from VR and AI to carbon-reduction technology", "MEG, our in-house AI platform, helps employees find information and build agents that streamline project workflows and calculations", "Consultancy 101: our structured development program that builds your consulting and technical foundation from day one", "An assigned mentor to guide your growth from day one", "Other rewards may include annual bonuses and stock ownership options." Also "In addition, IMEG provides a variety of benefits to employees, including health insurance coverage, an employee wellness program, life and disability insurance, a retirement savings plan, paid holidays, and paid time off (PTO)." So we have benefits.
Responsibilities: "What You'll Do" bullet list.
Requirements: "Required What You'll Bring" includes Education And Experience, Skills And Abilities, Preferred, Physical Requirements.
Qualifications: maybe combine Education and Experience as qualifications. But we have separate sections: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have content for:
- About the role: intro paragraph.
- Responsibilities: "What You'll Do" list.
- Requirements: Education And Experience (Bachelor of Science, EIT required) maybe also Preferred? Actually Preferred is separate but could be under Requirements or Qualifications. We'll treat Requirements as mandatory: Education And Experience (BS, EIT). Also maybe "Engineering in Training (EIT) or equivalent required". Also "Prior internship experience ... preferred" is preferred, not required. So we can put that under Requirements? Might be better to put under Qualifications? But we have both Requirements and Qualifications headings. We need to decide distribution.
We could put:
- Requirements: Education And Experience (BS, EIT required). Also maybe "Physical Requirements" could be under Requirements? But physical requirements are more like job demands; could be under Requirements.
- Qualifications: Skills And Abilities (knowledge of design techniques, technical skills, software, communication, etc.) plus Preferred (internship experience, EIT license preferred). Actually EIT license is same as required? They said EIT required, then Preferred: EIT License preferred (maybe redundant). We'll include.
- Skills: maybe separate technical skills? But we already have Skills And Abilities. Could treat that as Skills section. Then Qualifications could be education and experience. However the instruction list includes both Requirements and Qualifications; we need to use them if we have content.
Let's map:
About the role: intro paragraph.
Responsibilities: What You'll Do list.
Requirements: Education And Experience (BS, EIT required) + Physical Requirements (regularly required to sit, walk, etc.) maybe also Travel up to 5%? Travel is in At a Glance but could be under Requirements? Might be better to put Travel under Schedule? Actually schedule is work schedule; travel is separate. There's no heading for Travel. Could include in About the role or Requirements. We'll keep Travel in About the role? But we have At a Glance separate; maybe we can incorporate At a Glance into a short paragraph under About the role? However we should not invent headings not listed. At a Glance is not a listed heading; we could fold its content into appropriate sections: Location maybe not needed; Discipline maybe not needed; Markets maybe not needed; Ownership maybe part of Benefits? Travel maybe part of Schedule? Work Schedule is Schedule. Sponsorship: Not available - we can drop as boilerplate? It's not required to keep; it's minor metadata; we can drop.
Thus we can produce sections:
- About the role: paragraph summarizing role, location, discipline, markets, ownership, etc.
- Responsibilities: ul list of duties.
- Requirements: ul list of education/experience, physical requirements.
- Qualifications: ul list of skills and abilities (knowledge, communication, teamwork, detail, eager to learn, BIM, MS Office).
- Skills: maybe we could combine with Qualifications? But we need to decide. Could treat Qualifications as education/experience, Skills as technical skills. Let's do:
Qualifications: Education And Experience (BS, EIT required) plus Preferred (internship experience, EIT license preferred). Actually EIT license preferred is same as required? We'll just list preferred.
Skills: Knowledge of design techniques, tools, concepts; strong technical and analytical skills; knowledge of industry standard software; excellent communication; ability to work collaboratively; attention to detail; problem-solving; eagerness to learn; basic BIM; proficient MS Office.
But we already used education in Qualifications; maybe better: Requirements: Education And Experience (BS, EIT required). Qualifications: Skills And Abilities (technical, communication, etc.). Skills: maybe we could list specific software knowledge? But that's already in Skills And Abilities. Could split: Qualifications: Education And Experience; Skills: Technical and soft skills. Let's do that.
Thus:
- About the role: paragraph.
- Responsibilities: ul.
- Requirements: ul (Education And Experience).
- Qualifications: ul (Skills And Abilities).
- Skills: maybe we could list specific software: lighting photometric calculation software, energy compliance software, Adobe/Bluebeam, BIM, MS Office. But that's overlapping. Might be redundant. Perhaps better to not have Skills section if content overlaps; but we need to follow instruction: only include section when posting has real specific content for it. If we already covered skills in Qualifications, we could still have Skills section with more detailed software list. Let's extract specific software: lighting photometric calculation software such as AGI, Elum Tools, Visual Lighting, or other; energy compliance software such as ComCheck; familiar use of Adobe or Bluebeam Revu; basic knowledge in the use of Building Information Modeling (BIM) software; Proficient with MS Office Suite including but not limited to Word, Excel, and Outlook. That's specific enough for Skills section.
Thus:
Qualifications: maybe we list education and experience? But we already have Requirements for education. Let's decide:
Requirements: Education And Experience (BS, EIT required). Also maybe Physical Requirements? Could be under Requirements.
Qualifications: Skills And Abilities (knowledge of design techniques, technical and analytical skills, communication, teamwork, attention to detail, problem-solving, eagerness to learn). That seems like qualifications.
Skills: Specific software/tools: lighting photometric calculation software, energy compliance software, Adobe/Bluebeam Revu, BIM, MS Office.
Benefits: list benefits.
Pay: Salary range.
Schedule: Work schedule (Full-time hybrid). Also maybe mention travel up to 5%? Travel could be under Schedule? But schedule is work schedule; travel is separate but we can include travel in Schedule section as note.
We must not include placeholder text like "commensurate with experience". We have actual numbers.
Now produce HTML.
We need to wrap each section:
for each heading only if content exists.
We must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Keep substantive info.
Let's parse content:
- Intro: "100% Employee-Owned | Big-firm resources, local-team relationships, ONE IMEG culture This posting is for Summer 2027 New Graduate opportunities. IMEG is hiring an Electrical Engineering New Graduate in New York, NY, to support the analysis, design, and implementation oversight of electrical systems in buildings. This entry-level role offers hands-on design, analysis, and project execution experience, with mentorship, training, and opportunities to grow your expertise from day one. You will work closely with experienced engineers and consultants to help develop practical engineering solutions for clients. In this role, you will support project planning and scheduling, document design decisions and client instructions, participate in quality control processes, and collaborate with multidisciplinary teams to meet project goals and client expectations across government/municipal and science and technology work, advancing high-performance, energy-efficient design aligned with MEP2050 and AIA2030."
That's about the role. Could be "About the role" section.
- "At a Glance" bullet list: Location: New York, NY; Discipline: Electrical; Markets: Government/Municipal and Science & Technology; Ownership: 100% employee-owned (ESOP); Travel: Up to 5%; Work Schedule: Full-time hybrid; Sponsorship: Not available.
We need to include Pay and Schedule sections only if stated. Pay: later we have "State of New York Salary Range: $79,000 – $83,000 per year". So Pay section exists. Schedule: "Work Schedule: Full-time hybrid" is in At a Glance; also maybe mention schedule elsewhere. So we can have Schedule section.
Benefits: later they list benefits: "Medical, dental, and vision coverage starting day one, with preventive care at 100%, a $50/month wellness credit, and a Calm subscription", "Generous time off, including 6 paid holidays and 3 additional floating holidays", "PE, SE, and other license exam prep, with a clear path from EIT to PE", "Dress for Your Day flexibility (wear what fits your day)", "Employee ownership (ESOP): fully vested at all times, with a 3% to 6% company contribution, plus year-end profit sharing", "IDEA Program: a firm-wide innovation accelerator where employees across every discipline develop and scale new tools, from VR and AI to carbon-reduction technology", "MEG, our in-house AI platform, helps employees find information and build agents that streamline project workflows and calculations", "Consultancy 101: our structured development program that builds your consulting and technical foundation from day one", "An assigned mentor to guide your growth from day one", "Other rewards may include annual bonuses and stock ownership options." Also "In addition, IMEG provides a variety of benefits to employees, including health insurance coverage, an employee wellness program, life and disability insurance, a retirement savings plan, paid holidays, and paid time off (PTO)." So we have benefits.
Responsibilities: "What You'll Do" bullet list.
Requirements: "Required What You'll Bring" includes Education And Experience, Skills And Abilities, Preferred, Physical Requirements.
Qualifications: maybe combine Education and Experience as qualifications. But we have separate sections: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have content for:
- About the role: intro paragraph.
- Responsibilities: "What You'll Do" list.
- Requirements: Education And Experience (Bachelor of Science, EIT required) maybe also Preferred? Actually Preferred is separate but could be under Requirements or Qualifications. We'll treat Requirements as mandatory: Education And Experience (BS, EIT). Also maybe "Engineering in Training (EIT) or equivalent required". Also "Prior internship experience ... preferred" is preferred, not required. So we can put that under Requirements? Might be better to put under Qualifications? But we have both Requirements and Qualifications headings. We need to decide distribution.
We could put:
- Requirements: Education And Experience (BS, EIT required). Also maybe "Physical Requirements" could be under Requirements? But physical requirements are more like job demands; could be under Requirements.
- Qualifications: Skills And Abilities (knowledge of design techniques, technical skills, software, communication, etc.) plus Preferred (internship experience, EIT license preferred). Actually EIT license is same as required? They said EIT required, then Preferred: EIT License preferred (maybe redundant). We'll include.
- Skills: maybe separate technical skills? But we already have Skills And Abilities. Could treat that as Skills section. Then Qualifications could be education and experience. However the instruction list includes both Requirements and Qualifications; we need to use them if we have content.
Let's map:
About the role: intro paragraph.
Responsibilities: What You'll Do list.
Requirements: Education And Experience (BS, EIT required) + Physical Requirements (regularly required to sit, walk, etc.) maybe also Travel up to 5%? Travel is in At a Glance but could be under Requirements? Might be better to put Travel under Schedule? Actually schedule is work schedule; travel is separate. There's no heading for Travel. Could include in About the role or Requirements. We'll keep Travel in About the role? But we have At a Glance separate; maybe we can incorporate At a Glance into a short paragraph under About the role? However we should not invent headings not listed. At a Glance is not a listed heading; we could fold its content into appropriate sections: Location maybe not needed; Discipline maybe not needed; Markets maybe not needed; Ownership maybe part of Benefits? Travel maybe part of Schedule? Work Schedule is Schedule. Sponsorship: Not available - we can drop as boilerplate? It's not required to keep; it's minor metadata; we can drop.
Thus we can produce sections:
- About the role: paragraph summarizing role, location, discipline, markets, ownership, etc.
- Responsibilities: ul list of duties.
- Requirements: ul list of education/experience, physical requirements.
- Qualifications: ul list of skills and abilities (knowledge, communication, teamwork, detail, eager to learn, BIM, MS Office).
- Skills: maybe we could combine with Qualifications? But we need to decide. Could treat Qualifications as education/experience, Skills as technical skills. Let's do:
Qualifications: Education And Experience (BS, EIT required) plus Preferred (internship experience, EIT license preferred). Actually EIT license preferred is same as required? We'll just list preferred.
Skills: Knowledge of design techniques, tools, concepts; strong technical and analytical skills; knowledge of industry standard software; excellent communication; ability to work collaboratively; attention to detail; problem-solving; eagerness to learn; basic BIM; proficient MS Office.
But we already used education in Qualifications; maybe better: Requirements: Education And Experience (BS, EIT required). Qualifications: Skills And Abilities (technical, communication, etc.). Skills: maybe we could list specific software knowledge? But that's already in Skills And Abilities. Could split: Qualifications: Education And Experience; Skills: Technical and soft skills. Let's do that.
Thus:
- About the role: paragraph.
- Responsibilities: ul.
- Requirements: ul (Education And Experience).
- Qualifications: ul (Skills And Abilities).
- Skills: maybe we could list specific software: lighting photometric calculation software, energy compliance software, Adobe/Bluebeam, BIM, MS Office. But that's overlapping. Might be redundant. Perhaps better to not have Skills section if content overlaps; but we need to follow instruction: only include section when posting has real specific content for it. If we already covered skills in Qualifications, we could still have Skills section with more detailed software list. Let's extract specific software: lighting photometric calculation software such as AGI, Elum Tools, Visual Lighting, or other; energy compliance software such as ComCheck; familiar use of Adobe or Bluebeam Revu; basic knowledge in the use of Building Information Modeling (BIM) software; Proficient with MS Office Suite including but not limited to Word, Excel, and Outlook. That's specific enough for Skills section.
Thus:
Qualifications: maybe we list education and experience? But we already have Requirements for education. Let's decide:
Requirements: Education And Experience (BS, EIT required). Also maybe Physical Requirements? Could be under Requirements.
Qualifications: Skills And Abilities (knowledge of design techniques, technical and analytical skills, communication, teamwork, attention to detail, problem-solving, eagerness to learn). That seems like qualifications.
Skills: Specific software/tools: lighting photometric calculation software, energy compliance software, Adobe/Bluebeam Revu, BIM, MS Office.
Benefits: list benefits.
Pay: Salary range.
Schedule: Work schedule (Full-time hybrid). Also maybe mention travel up to 5%? Travel could be under Schedule? But schedule is work schedule; travel is separate but we can include travel in Schedule section as note.
We must not include placeholder text like "commensurate with experience". We have actual numbers.
Now produce HTML.
We need to wrap each section: About the role
...
etc. For lists:- ...