Jobs · Information Technology · Virginia

Electrical Engineering Intern (Summer 2027)

Summer Consultants, Inc. · McLean, VA · Yesterday
Information TechnologyInternship
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes description, benefits, requirements, qualifications, skills. No pay or schedule mentioned, no schedule. So we should not include Pay or Schedule sections. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive information. Let's parse content: Job Type Internship Description: The description paragraphs. We can have sections: About the role (maybe description), Responsibilities (what you will do), Requirements (what you can do for summer? Actually "WHAT YOU CAN DO FOR SUMMER" is responsibilities), Qualifications (What you should bring with you), Skills (maybe tools and abilities), Benefits (Intern Benefits & Support). Also maybe "What Summer Can Do For You" could be considered Benefits or Learning outcomes. But we already have Benefits section for tangible benefits; we could treat "What Summer Can Do For You" as a section like "Learning & Development" but not in allowed headings list. The allowed headings are limited to those listed; we should only use those headings. So we need to map content to those headings. We have: - About the role: could be the introductory description: "When you walk into a building...". That's about the role. - Responsibilities: the bullet list under "WHAT YOU CAN DO FOR SUMMER" (the responsibilities). Also maybe the earlier paragraph about supporting real project work etc. Could be responsibilities. - Requirements: maybe the "What You Should Bring With You" list (education, interest, etc.) That's qualifications/requirements. - Qualifications: maybe overlapping; but we can treat "What You Should Bring With You" as Qualifications. Requirements could be the earlier bullet list? Actually the posting has "Requirements WHAT YOU CAN DO FOR SUMMER". That heading is "Requirements" but content is responsibilities. So we need to interpret: The posting uses "Requirements" as a heading but content is responsibilities. However we must follow instruction: use headings for sections only if posting has real specific content for that heading. The posting has a heading "Requirements" but the content under it is responsibilities. Should we treat that as Responsibilities? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should map the content to appropriate heading based on meaning, not necessarily the original heading. So we should create a Responsibilities section with the bullet list under "WHAT YOU CAN DO FOR SUMMER". Also maybe include earlier paragraph about supporting real project work etc. Could be part of responsibilities. Qualifications: The "What You Should Bring With You" list includes education, interest, etc. That's qualifications. Skills: Could be the tools and abilities: "Ability to learn from experienced engineers... Strong written and verbal communication skills. Strong Microsoft Word and Excel skills. AutoCAD and Revit experience preferred. Ability to support day-long field surveys..." That's skills. Benefits: The "Intern Benefits & Support" bullet list: Paid sick leave, parking and business travel. Also "What Summer Can Do For You" could be considered Benefits or Learning outcomes; but we already have Benefits. Could we add a section "About the role" includes that? The "What Summer Can Do For You" is more about what you'll gain. Could be part of About the role or Benefits. Since we already have Benefits for tangible benefits, we could incorporate the learning outcomes into About the role or maybe a separate section like "Learning & Development" but not allowed. So we can incorporate into About the role. Thus sections: About the role, Responsibilities, Requirements (maybe we don't need Requirements separate if we have Qualifications and Skills; but we could treat Requirements as the eligibility criteria like "At least two years completed toward a Bachelor's degree...". However that is more qualifications. The posting has a heading "Requirements" but content is responsibilities. To avoid duplication, we can skip Requirements section and put those under Responsibilities. But we need to ensure we don't miss any content. The "Requirements" heading content is responsibilities; we already have Responsibilities. So we can omit Requirements heading. Qualifications: education and interest. Skills: tools, communication, etc. Benefits: sick leave, parking. Now we need to output HTML fragment only. Structure:

    About the role

    ... (combined intro + what summer can do for you)

    Responsibilities

    • ... each bullet

    Qualifications

    • ... each bullet

    Skills

    • ... each bullet

    Benefits

    • ... each bullet
    We must not include empty sections. Now we need to extract precise bullet points. From posting: Responsibilities (under "WHAT YOU CAN DO FOR SUMMER"): - Support electrical design work on renovation and existing-building projects. - Participate in field surveys to observe and document existing building conditions and electrical systems. - Assist with lighting and power design, electrical calculations, lighting calculations, electrical distribution, and system layouts. - Help translate survey information, calculations, and existing constraints into project drawings and design documentation. - Use tools such as Revit and AutoCAD to support project work. - Coordinate with engineers and designers from other disciplines. - Ask questions, apply feedback, and take on increasing responsibility as your skills develop. - Help solve client problems with curiosity, precision, quality, and follow-through. Also earlier paragraph: "As an intern at Summer, you will support real project work alongside experienced engineers. You may assist with surveys, calculations, equipment selection, ductwork and piping layouts, drawings, and other project activities appropriate to your experience and the needs of the team." That's also responsibilities but similar. We could incorporate into responsibilities as additional bullet or prose. Since we must preserve all substantive information, we should include that as well. Could be a bullet: Assist with surveys, calculations, equipment selection, ductwork and piping layouts, drawings, and other project activities appropriate to experience and team needs. Also earlier: "Existing buildings do not give you a clean sheet of paper. Our engineers spend real time in the field walking buildings, surveying and documenting existing conditions, tracing systems, observing constraints, and figuring out how a new design can actually work within the building that is already there." That's more description, maybe part of About the role. Also: "Field surveys are also an important part of how our interns learn. You may help observe and document existing mechanical and plumbing systems, ask questions about what you are seeing, and learn how field conditions affect design decisions." That's also responsibilities. We need to capture all. Let's list all responsibility-like statements: From intro paragraph after description: "As an intern at Summer, you will support real project work alongside experienced engineers. You may assist with surveys, calculations, equipment selection, ductwork and piping layouts, drawings, and other project activities appropriate to your experience and the needs of the team." From "Existing buildings do not give you a clean sheet..." paragraph: This is more about the work environment; could be part of About the role. From "Field surveys are also an important part..." paragraph: responsibilities. From "WHAT YOU CAN DO FOR SUMMER" list: responsibilities. We should avoid duplication but include all distinct points. Let's extract distinct responsibilities: - Support real project work alongside experienced engineers. - Assist with surveys, calculations, equipment selection, ductwork and piping layouts, drawings, and other project activities appropriate to experience and team needs. - Participate in field surveys to observe and document existing building conditions and electrical systems. - Assist with lighting and power design, electrical calculations, lighting calculations, electrical distribution, and system layouts. - Help translate survey information, calculations, and existing constraints into project drawings and design documentation. - Use tools such as Revit and AutoCAD to support project work. - Coordinate with engineers and designers from other disciplines. - Ask questions, apply feedback, and take on increasing responsibility as skills develop. - Help solve client problems with curiosity, precision, quality, and follow-through. - Help observe and document existing mechanical and plumbing systems, ask questions about what you are seeing, and learn how field conditions affect design decisions. Note: Some overlap: surveys, calculations appear multiple times. We can keep distinct but may combine similar. Now Qualifications (What you should bring): - At least two years completed toward a Bachelor's degree in Electrical Engineering, Electrical Engineering Technology, or Architectural Engineering (Electrical/Lighting focus). - Genuine interest in power, lighting, electrical distribution, building systems, existing-building renovation, and learning how engineering works in practice. - Curiosity about how buildings are constructed, operated, maintained, and modified over time. - Willingness to spend meaningful time in the field surveying existing conditions. - Ability to learn from experienced engineers, ask questions, receive and apply feedback, and contribute as part of a project team. - Strong written and verbal communication skills. - Strong Microsoft Word and Excel skills. - AutoCAD and Revit experience preferred. - Ability to support day-long field surveys outdoors and indoors, including conditioned and unconditioned spaces, with or without reasonable accommodation. Field work may include walking 10,000 to 20,000 steps in a day, climbing up and down a 6-foot ladder, kneeling, squatting, and bending. - Ability to obtain site access at client locations, including federal facilities, as required by project assignments. Now Skills: Could be overlapping with qualifications; but we can separate: maybe Skills = tools and technical abilities: AutoCAD, Revit, lighting calculation software, applicable electrical analysis software, Microsoft Word/Excel, strong communication, ability to learn, etc. However qualifications already include many. To avoid duplication, we could treat Qualifications as education and interest, Skills as tools and abilities. But the posting lumps them together. However we need to follow instruction: include a section only when posting has real specific content for it. The posting does have content for Skills (tools, software). So we can create Skills section with those items. Let's extract Skills items: - Experience with tools such as Revit, AutoCAD, lighting calculation software, and applicable electrical analysis software (from "What Summer Can Do For You"). - Strong Microsoft Word and Excel skills. - AutoCAD and Revit experience preferred. - Strong written and verbal communication skills. - Ability to learn from experienced engineers, ask questions, receive and apply feedback. - Ability to support day-long field surveys outdoors and indoors, including conditioned and unconditioned spaces, with or without reasonable accommodation. Field work may include walking 10,000 to 20,000 steps in a day, climbing up and down a 6-foot ladder, kneeling, squatting, and bending. - Ability to obtain site access at client locations, including federal facilities, as required by project assignments. But some of these are also in qualifications. To avoid duplication, we could split: Qualifications = education and interest; Skills = tools, software, communication, physical ability, site access. However there is overlap; but we can still include both sections with distinct items, ensuring we don't repeat exact same sentences. We'll try to keep each bullet unique. Let's define: Qualifications: - At least two years completed toward a Bachelor's degree in Electrical Engineering, Electrical Engineering Technology, or Architectural Engineering (Electrical/Lighting focus). - Genuine interest in power, lighting, electrical distribution, building systems, existing-building renovation, and learning how engineering works in practice. - Curiosity about how buildings are constructed, operated, maintained, and modified over time. - Willingness to spend meaningful time in the field surveying existing conditions. Skills: - Ability to learn from experienced engineers, ask questions, receive and apply feedback, and contribute as part of a project team. - Strong written

Similar jobs