Jobs · Engineering · Minnesota

Engineering Design Lead

ArchKey Solutions · Minneapolis, MN · 1 mo ago
On-siteEngineering$108k–$151k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About ArchKey", "About The Position", "Our Ideal Candidate", "Day in the life", "Minimum Qualifications", "Travel Days and hours of work", "Salary Range", "Benefits". Also "Additional information is available at Archkey.com." That's minor metadata. We must use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content appropriately. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings if we have content. But we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those headings where appropriate. We need to decide which sections we have content for. We have: - About ArchKey (company overview) maybe not needed as heading? Could be "About the role"? Actually "About the role" is typical heading for role description. We have "About The Position". That matches "About the role". So we can use

About the role

and put the paragraph(s) from "About The Position". - Responsibilities: we have "Day in the life" which lists duties. Could map to Responsibilities. Also there are many bullet-like sentences. We'll put them in
  • . - Requirements / Qualifications: we have "Minimum Qualifications". Could be Requirements or Qualifications. We'll use

    Qualifications

    maybe. Or Requirements. We need to decide. The instruction says we can use those headings; we can include both Requirements and Qualifications if we have content. But we should avoid thin sections. Probably combine into one Qualifications section. - Skills: we have many skill mentions within qualifications; maybe we can put under Skills. - Benefits: we have Benefits section. - Pay: we have Salary Range. - Schedule: we have Travel Days and hours of work (Monday-Friday, occasional evening/weekend, occasional travel). That's schedule. Thus we will output sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, legal, fraud disclaimer. Also remove "Additional information is available at Archkey.com." maybe minor metadata; we can drop or fold into short p. Probably drop. We must preserve all substantive information. So we need to include all details from sections. Let's extract content. About The Position paragraph: "As the Engineering Design Lead, you will provide technical and people leadership to a team of engineers and designers delivering high-quality electrical engineering drawings, 3D models, and construction documents that support complex and challenging electrical installations, in alignment with all Company policies, procedures, key objectives and regulations. This role combines advanced engineering expertise, team leadership, and construction-focused problem solving to ensure designs are safe, code-compliant, fully constructible, and aligned with project goals. The Engineering Design Lead supports projects ranging from Design/Build efforts to some of the largest hyper-scale projects in the country. In addition to leading design execution, this role reviews internal and external engineering documents to identify constructability risks and value engineering opportunities, performs advanced engineering studies, and provides hands-on field support and troubleshooting. The ideal candidate brings deep technical knowledge, strong leadership capability, and a commitment to engineering excellence and continuous improvement." We'll put that in

    . Responsibilities: from "Day in the life" list. Let's extract each sentence as bullet. List: - Leads and manages a small team of engineers and designers, overseeing the development of detailed electrical engineering permit drawings, 3D models, and construction installation documents to support field execution. - Develops, reviews, and approves engineering calculations, studies, and reports including arc flash, short circuit, overcurrent protective device coordination, duct bank ampacity, load, lighting, and power factor correction. - Serves as the primary engineering authority for project teams, providing technical direction, constructability guidance, and risk mitigation strategies. - Reviews and approves designs prepared by Electrical Engineers and Designers to ensure compliance with codes, standards, and company best practices. - Leads technical review of outside engineering documents and supports value engineering, scope development, and constructability planning. - Participates in electrical construction and design-related training. - Enforces company engineering standards and maintains strict QA/QC procedures for all deliverables. - Recommend improvements to design standards, workflows, and procedures. - Responds to design questions, resolve issues, and issue plan revisions as required. - Stays current with new electrical and safety codes, materials, technologies, and industry best practices. - Coordinates with field electricians to support data collection and implementation as needed. - Leads any size project from an engineering perspective, supporting estimating, scheduling, forecasting, and budget alignment. - Monitors and guides the design activities of engineers and designers to achieve high performance in quality, productivity, and schedule adherence. - Provides ongoing coaching, training, mentoring, and performance feedback. - Coordinates and balances team workload across multiple projects to ensure design deliverables are completed on schedule and within scope. - Demonstrates knowledge of local building energy codes and standards (e.g., IECC, ASHRAE 90.1, California Title 24), including developing, reviewing, and coordinating drawings for energy code compliance, evaluating lighting fixtures and control systems for compliance, utilizing energy compliance software and processes, and advising project managers on compliance strategies and solutions. - Mentors and develops Electrical Engineers and Designers; supports licensure development and knowledge sharing across the organization. - Builds trusted relationships with customers, inspectors, vendors, and trade partners while representing the Company’s technical leadership and core values. - Consistently make decisions in an attentive and safe manner to ensure the safety and health of self and others. - Utilizes LEAN concepts or other continuous improvement methodologies to ensure the most efficient operations, processes, and activities. - Promotes and models the Company mission, vision and values through exercising sound and ethical business practices, championing all elements of diversity, equity, and inclusion (DEI) and providing high quality services and programs as they relate to clients, subcontractors, co-workers, suppliers, and the public. That's many bullets. We'll put them in

    • . Qualifications: Minimum Qualifications bullet list. Extract: - Bachelor's Degree in Electrical Engineering or equivalent work experience in engineering, electrical design, or a related field. - Minimum of 12 years of applicable design engineering experience or 8 years with an electrical engineering degree and Professional Engineer (PE) license and demonstrated success leading engineering teams on small to mid-size projects. - Extensive experience in facilities power design, including lighting, receptacle layouts, circuiting, panelboard schedules, load calculations, and equipment sizing. - Experience in healthcare, heavy industrial, and/or data center projects is highly desirable. - Controls experience is a plus. - Advanced ability to read, interpret, and apply electrical contracts, plans, drawings, and specifications, with extensive knowledge of the National Electrical Code (NEC) and applicable building codes. - High proficiency in Revit, Autodesk tools, Bluebeam, and Microsoft Office. - Experience performing engineering studies using SKM or ETAP is preferred. - Strong commitment to electrical construction, engineering excellence, and team leadership, with a collaborative and solution-oriented mindset. - Proven experience supporting field electricians through all phases of construction, including troubleshooting and design clarification. - Demonstrated experience proposing, scoping, and estimating engineering and design efforts. - Ability to work independently in a fast-paced environment while managing competing priorities with strong organizational and time management skills. - Strong mathematical, analytical, and systems-level problem-solving skills. - Demonstrated sound judgment, customer focus, and effective decision-making under pressure. - Excellent written, verbal, and interpersonal communication skills with the ability to lead teams and collaborate across disciplines. We'll put those in
      • under Qualifications. Skills: Could extract skill-specific items like knowledge of NEC, Revit, etc. But many are already in qualifications. To avoid duplication, maybe we can put Skills separate highlighting technical skills: NEC, Revit, Autodesk, Bluebeam, MS Office, SKM/ETAP, energy codes, LEAN, etc. But we risk duplication. The instruction says preserve ALL substantive information; we can duplicate if needed but better to avoid redundancy. However we need to include all info; if we put everything under Qualifications, we still have all info. Skills section could be omitted if we think it's thin. But we have skill details; we could create Skills section highlighting specific technical skills: NEC, Revit, Autodesk tools, Bluebeam, MS Office, SKM/ETAP, energy codes (IECC, ASHRAE 90.1, Title 24), LEAN, etc. But then we would be repeating some info. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Qualifications and Skills into one section called Qualifications (or Requirements). But they gave examples of headings; we can still use Qualifications heading and include both qualifications and skills. That's fine. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't create empty sections. Now Benefits paragraph: "At ArchKey Solutions, our benefits package includes competitive health insurance options (medical, dental, and vision), a robust 401(k) retirement savings plan with employer match, paid time off and holidays, and access to wellness programs. Additionally, we offer professional development opportunities, tuition reimbursement, and employee assistance programs to support your growth and well-being. We ensure that our benefits are designed to promote the health, security, and work-life balance of our employees." We'll put that in

        . Pay: Salary Range: "$107,600 - $150,600 annually, based on experience and qualifications". We'll put in

        . Schedule: Travel Days and hours of work: "Monday through Friday. Occasional evening and weekend work may be required as job duties demand. Occasional travel to job sites is required." We'll put in

        . Now we need to output only HTML fragment, no /, no markdown. We'll structure:

        About the role

        ...

        Responsibilities

        • ...
        • ...

        Qualifications

        • ...
        • ...

        Benefits

        ...

        Pay

        ...

        Schedule

        ...

        Make sure to preserve all substantive information. Let's double-check we didn't miss any details from About ArchKey (company overview). That is not required as a heading; we could fold into About the role? The About ArchKey paragraph is about company; maybe we could include it in About the role section as additional context. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." About ArchKey is not minor metadata; it's substantive about company. Could be included in About the role section as a paragraph before the role description. That would preserve it. Thus About the role section will have two paragraphs: first about ArchKey, second about the position. Let's extract About ArchKey paragraph: "ArchKey is one of the nation’s largest privately held specialty trade installation and integrated facility service companies. We are a leader in designing, building and maintaining electrical, technologies and specialty systems. We’re the POWER behind making the improbable possible. We’re electrifying the nation, energizing the future and bringing communities to life like never before. What we do today shapes the vision of tomorrow.

Similar jobs

Engineering Design Lead

ArchKey SolutionsSan Jose, CA· 3 mo ago
Engineering$128k–$154k/yrapply on careers.archkey.com

Engineering Design Lead

ArchKey SolutionsPlymouth, MN· 3 mo ago
Engineering$107k–$129k/yrapply on careers.archkey.com

Engineering Design Lead

ArchKey SolutionsSan Francisco, CA· 1 wk ago
Engineering$108k–$151k/yrapply on careers.archkey.com

Engineering Design Lead

ArchKey SolutionsUpper Marlboro, MD· 1 mo ago
Engineering$108k–$151k/yrapply on careers.archkey.com