Lead Electrical Engineer (UAV/UAS)
Drone.vet · Rockville, MD · 4 wk ago
Engineering$140k–$190k/yrFull-time
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 when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info.
We need to parse the posting.
First paragraph: description of company, culture, benefits: "Enjoy competitive benefits, a supportive work environment, and every other Friday off to recharge." That's benefits and schedule info.
Then description of role: "The Lead Electrical Engineer will provide hands-on technical leadership..." That's about the role.
Then "Job Responsibilities" list.
Then "Qualification Requirements" list.
Then "Skill Requirements" list.
Then "Physical Requirements" (maybe we can include under Requirements? But we have a section for Requirements; we could include physical requirements under Requirements or maybe separate? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have to map content accordingly.
We have:
- About the role: could be the introductory description of the role (the paragraph after company description). Could also include the mission statement? Probably "About the role" includes the description of what the role does.
- Responsibilities: the list under "Job Responsibilities".
- Requirements: maybe includes Qualification Requirements? But we also have separate Qualifications and Skills headings. The instruction list includes both Qualifications and Skills as separate headings. So we need to decide: "Qualifications" heading for education/experience requirements; "Skills" heading for skill requirements. "Requirements" maybe for other requirements like physical requirements, travel, citizenship, driver's license, passport, etc. Or we could combine Qualification and Skills under Requirements? But they said prefer a few substantive sections over many thin ones. However they also gave list of possible headings. We should include sections only when there is real specific content. We have content for:
- About the role: yes.
- Responsibilities: yes.
- Qualifications: yes (Bachelor's degree, Master's preferred, 10+ years experience, etc.)
- Skills: yes (advanced knowledge, hands-on experience, etc.)
- Benefits: yes (competitive benefits, supportive work environment, every other Friday off, health/dental/vision, 401K with match, company-paid holidays, PTO). Also mention discretionary annual performance bonus.
- Pay: yes (Salary Range: $140,000-190,000 Annually, plus bonus info).
- Schedule: yes (every other Friday off). Could also mention flexible? Not needed.
- Requirements: maybe include physical requirements, travel, citizenship, driver's license, passport, ability to lift 45 lbs, etc. Also mention "Ability to travel (domestic and internationally). Must have valid driver’s license and ability to obtain a passport. Due to federal contract requirements applicable to this position, candidates must be U.S. citizens." Also physical requirements.
Thus we can have a Requirements section covering those.
We must not include boilerplate like EEO, equal opportunity, etc. Remove that.
We must not include duplicated lines. Ensure we preserve all substantive info.
We must not invent or summarize away detail. So we need to keep specifics: e.g., "Lead the design and development of UAV and USV electrical architectures, including power distribution, avionics, communications, controls, sensors, and payload integration." etc.
We need to format lists with
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info.
We need to parse the posting.
First paragraph: description of company, culture, benefits: "Enjoy competitive benefits, a supportive work environment, and every other Friday off to recharge." That's benefits and schedule info.
Then description of role: "The Lead Electrical Engineer will provide hands-on technical leadership..." That's about the role.
Then "Job Responsibilities" list.
Then "Qualification Requirements" list.
Then "Skill Requirements" list.
Then "Physical Requirements" (maybe we can include under Requirements? But we have a section for Requirements; we could include physical requirements under Requirements or maybe separate? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have to map content accordingly.
We have:
- About the role: could be the introductory description of the role (the paragraph after company description). Could also include the mission statement? Probably "About the role" includes the description of what the role does.
- Responsibilities: the list under "Job Responsibilities".
- Requirements: maybe includes Qualification Requirements? But we also have separate Qualifications and Skills headings. The instruction list includes both Qualifications and Skills as separate headings. So we need to decide: "Qualifications" heading for education/experience requirements; "Skills" heading for skill requirements. "Requirements" maybe for other requirements like physical requirements, travel, citizenship, driver's license, passport, etc. Or we could combine Qualification and Skills under Requirements? But they said prefer a few substantive sections over many thin ones. However they also gave list of possible headings. We should include sections only when there is real specific content. We have content for:
- About the role: yes.
- Responsibilities: yes.
- Qualifications: yes (Bachelor's degree, Master's preferred, 10+ years experience, etc.)
- Skills: yes (advanced knowledge, hands-on experience, etc.)
- Benefits: yes (competitive benefits, supportive work environment, every other Friday off, health/dental/vision, 401K with match, company-paid holidays, PTO). Also mention discretionary annual performance bonus.
- Pay: yes (Salary Range: $140,000-190,000 Annually, plus bonus info).
- Schedule: yes (every other Friday off). Could also mention flexible? Not needed.
- Requirements: maybe include physical requirements, travel, citizenship, driver's license, passport, ability to lift 45 lbs, etc. Also mention "Ability to travel (domestic and internationally). Must have valid driver’s license and ability to obtain a passport. Due to federal contract requirements applicable to this position, candidates must be U.S. citizens." Also physical requirements.
Thus we can have a Requirements section covering those.
We must not include boilerplate like EEO, equal opportunity, etc. Remove that.
We must not include duplicated lines. Ensure we preserve all substantive info.
We must not invent or summarize away detail. So we need to keep specifics: e.g., "Lead the design and development of UAV and USV electrical architectures, including power distribution, avionics, communications, controls, sensors, and payload integration." etc.
We need to format lists with - . For prose, use
.
We must not repeat job title as heading. So no
Lead Electrical Engineer
. Use About the role heading.
We must not put Job ID/requisition numbers as headings; none present.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
... (company description and role overview)
But we need to ensure we don't include boilerplate like "Ideal Aerosmith is a leading supplier..." That's company description; it's part of about the role? Might be okay. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include company description under About the role.
We should include the sentence: "Enjoy competitive benefits, a supportive work environment, and every other Friday off to recharge." That's benefits/schedule; maybe we put that under Benefits and Schedule sections.
But we can also include it in About the role? Better to separate.
Thus About the role: description of role and maybe company mission. Let's capture:
"Ideal Aerosmith is a leading supplier of precision inertial guidance test systems, flight motion simulators, innovative defense solutions in support of the warfighter, and a premier provider of aerospace test engineering services, ATE system engineering, and quality contract manufacturing services to the aerospace industry. We're experts and we earn that title everyday with our customers through innovative engineering, manufacturing, and sustainment of world-class motion and electric test solutions and services. Here, we don’t just solve complex problems - we redefine what’s possible. Every role at Ideal Aerosmith supports a lean culture through continuous improvement - ongoing, incremental enhancements to products, processes, or services aimed at reducing waste and boosting efficiency, customer service, and performance. With a team of skilled problem solvers and a culture that thrives on tackling challenges head-on, we are dedicated to our clients' success."
Then role-specific: "The Lead Electrical Engineer will provide hands-on technical leadership for the design, integration, and performance of complex electrical systems supporting Ideal Aerosmith’s unmanned platforms, including UAVs and USVs. We’re building the next generation of unmanned systems for the warfighter and are looking for an experienced electrical engineer who enjoys building things and still wants to work directly with hardware. This role will help guide the electrical team and make system-level technical decisions while remaining directly involved in design, build, integration, testing, and troubleshooting. You might spend one day working through a power-distribution architecture and the next tracking down a noisy CAN bus, reviewing a circuit board, building a test harness, or troubleshooting an aircraft before flight test. We value engineers who are naturally curious, work well across mechanical, software, manufacturing, supply chain, and flight-test teams, and can make sound decisions in a fast-moving development environment. If you want real technical ownership, interesting hardware, and the chance to see your work built, tested, and flown, this could be a great fit."
That seems good for About the role.
Now Responsibilities: list each bullet under - .
We need to capture all responsibilities listed after "Job Responsibilities". Let's extract them:
- Lead the design and development of UAV and USV electrical architectures, including power distribution, avionics, communications, controls, sensors, and payload integration.
- Own and guide end-to-end electrical system architecture, including power, data, RF, and control interfaces.
- Serve as a lead electrical system integrator across internal subsystems, external vendors, and program partners.
- Define and manage electrical interfaces and documentation, including ICDs, schematics, wiring diagrams, pinouts, BOMs, electrical specifications, test plans, and configuration-controlled design data.
- Lead system-level trade studies involving power budgets, bandwidth, thermal impacts, reliability, EMI/EMC, scalability, and cost.
- Design, review, debug, and redesign electrical circuits and printed circuit boards as needed to support development and integration.
- Support electrical systems involving BLDC motors and motor controllers, battery systems, chargers, battery management systems (BMS), cell-balancing circuits, DC/DC converters, MOSFET switching, power distribution, and protection circuits.
- Integrate and troubleshoot embedded systems and communications interfaces, including CAN, UART, SPI, Ethernet, microcontrollers, flight computers, radios, sensors, and payloads.
- Lead grounding, shielding, EMI/EMC, and transient-protection design and mitigation efforts, including resolution of issues identified during integration, pre-compliance testing, formal testing, and flight test.
- Perform hands-on electrical integration, system bring-up, checkout, and troubleshooting during prototype builds, ground testing, and flight testing using oscilloscopes, logic analyzers, current probes, and other electrical test equipment.
- Provide technical direction, design reviews, and mentoring to electrical engineers and other technical team members without direct people-management responsibility.
- Drive component-selection decisions with consideration for performance, reliability, availability, manufacturability, scalability, and cost.
- Partner cross-functionally with mechanical, software, manufacturing, supply chain, systems, and flight-test teams to resolve integration issues and support program execution.
- Support development and execution of verification and validation plans, including environmental and performance testing.
- Support transition from prototype to production, including design for manufacturability, cost optimization, documentation maturity, and resolution of production issues.
- Contribute to program reviews, risk assessments, technical decision-making, engineering standards, design practices, and continuous improvement efforts.
Now Qualifications: after "Qualification Requirements". Extract:
- Bachelor’s degree in Electrical Engineering, Electronics Engineering, or a related field.
- Master's degree preferred.
- 10+ years of electrical engineering experience involving complex electromechanical systems; aerospace, UAV, robotics, vehicle, or similar systems experience strongly preferred.
- Demonstrated experience serving as a technical lead or senior technical contributor on complex electrical development and integration efforts.
- Experience with avionics, power systems, communications, embedded systems, controls, and sensor integration.
- Experience working in a fast-paced R&D, prototyping, or new-product development environment
- Ability to travel (domestic and internationally).
- Must have valid driver’s license and ability to obtain a passport.
- Due to federal contract requirements applicable to this position, candidates must be U.S. citizens.
Note: Some of these (travel, driver license, passport, citizenship) could go under Requirements but they are listed under Qualification Requirements. We'll keep them under Qualifications for now, but we also have a separate Requirements section for physical requirements etc. Might be overlapping. To avoid duplication, we could put travel, driver license, passport, citizenship under Requirements (since they are not qualifications per se). But the instruction says we can have Requirements section for things like physical requirements, travel, etc. However we also have Qualifications and Skills sections. It's okay to have some overlap? Better to follow the posting: they labeled "Qualification Requirements" includes education, experience, travel, driver license, passport, citizenship. So we can put all that under Qualifications. Then we can have a separate Requirements section for physical requirements only. But we need to decide if we want a Requirements section at all. We have physical requirements: "Must have the ability to lift and/or carry 45 lbs. Ability to work for extended periods at computer workstation/keyboard. Ability to type accurately and efficiently. The position will require walking, standing, squatting, crouching, stooping, lifting, climbing, pulling, pushing, sitting, repetitive motion and kneeling." That's substantive. So we can have a Requirements section for physical requirements.
Thus:
Qualifications
- ... (education, experience, travel, driver license, passport, citizenship)
Skills
- ... (skill requirements list)
Requirements
- ... (physical requirements)
Now Benefits: we have "Enjoy competitive benefits, a supportive work environment, and every other Friday off to recharge." plus later: "Ideal Aerosmith additionally offers a comprehensive benefits program, which includes health, dental, vision, and voluntary benefits; 401K with company match; company-paid holidays; every other Friday off; and paid time off for vacation and personal time." Also discretionary annual performance bonus.
Thus Benefits section: list those.
Pay: Salary range and bonus info.
Schedule: every other Friday off (maybe also mention flexible? Not needed). Could also mention work schedule? Not given.
We should avoid duplication: Benefits already mentions
. We must not repeat job title as heading. So no
Lead Electrical Engineer
. Use About the role heading. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment, no /, no markdown fences. Let's craft. Structure:About the role
... (company description and role overview)
But we need to ensure we don't include boilerplate like "Ideal Aerosmith is a leading supplier..." That's company description; it's part of about the role? Might be okay. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include company description under About the role.
We should include the sentence: "Enjoy competitive benefits, a supportive work environment, and every other Friday off to recharge." That's benefits/schedule; maybe we put that under Benefits and Schedule sections.
But we can also include it in About the role? Better to separate.
Thus About the role: description of role and maybe company mission. Let's capture:
"Ideal Aerosmith is a leading supplier of precision inertial guidance test systems, flight motion simulators, innovative defense solutions in support of the warfighter, and a premier provider of aerospace test engineering services, ATE system engineering, and quality contract manufacturing services to the aerospace industry. We're experts and we earn that title everyday with our customers through innovative engineering, manufacturing, and sustainment of world-class motion and electric test solutions and services. Here, we don’t just solve complex problems - we redefine what’s possible. Every role at Ideal Aerosmith supports a lean culture through continuous improvement - ongoing, incremental enhancements to products, processes, or services aimed at reducing waste and boosting efficiency, customer service, and performance. With a team of skilled problem solvers and a culture that thrives on tackling challenges head-on, we are dedicated to our clients' success."
Then role-specific: "The Lead Electrical Engineer will provide hands-on technical leadership for the design, integration, and performance of complex electrical systems supporting Ideal Aerosmith’s unmanned platforms, including UAVs and USVs. We’re building the next generation of unmanned systems for the warfighter and are looking for an experienced electrical engineer who enjoys building things and still wants to work directly with hardware. This role will help guide the electrical team and make system-level technical decisions while remaining directly involved in design, build, integration, testing, and troubleshooting. You might spend one day working through a power-distribution architecture and the next tracking down a noisy CAN bus, reviewing a circuit board, building a test harness, or troubleshooting an aircraft before flight test. We value engineers who are naturally curious, work well across mechanical, software, manufacturing, supply chain, and flight-test teams, and can make sound decisions in a fast-moving development environment. If you want real technical ownership, interesting hardware, and the chance to see your work built, tested, and flown, this could be a great fit."
That seems good for About the role.
Now Responsibilities: list each bullet under - .
We need to capture all responsibilities listed after "Job Responsibilities". Let's extract them:
- Lead the design and development of UAV and USV electrical architectures, including power distribution, avionics, communications, controls, sensors, and payload integration.
- Own and guide end-to-end electrical system architecture, including power, data, RF, and control interfaces.
- Serve as a lead electrical system integrator across internal subsystems, external vendors, and program partners.
- Define and manage electrical interfaces and documentation, including ICDs, schematics, wiring diagrams, pinouts, BOMs, electrical specifications, test plans, and configuration-controlled design data.
- Lead system-level trade studies involving power budgets, bandwidth, thermal impacts, reliability, EMI/EMC, scalability, and cost.
- Design, review, debug, and redesign electrical circuits and printed circuit boards as needed to support development and integration.
- Support electrical systems involving BLDC motors and motor controllers, battery systems, chargers, battery management systems (BMS), cell-balancing circuits, DC/DC converters, MOSFET switching, power distribution, and protection circuits.
- Integrate and troubleshoot embedded systems and communications interfaces, including CAN, UART, SPI, Ethernet, microcontrollers, flight computers, radios, sensors, and payloads.
- Lead grounding, shielding, EMI/EMC, and transient-protection design and mitigation efforts, including resolution of issues identified during integration, pre-compliance testing, formal testing, and flight test.
- Perform hands-on electrical integration, system bring-up, checkout, and troubleshooting during prototype builds, ground testing, and flight testing using oscilloscopes, logic analyzers, current probes, and other electrical test equipment.
- Provide technical direction, design reviews, and mentoring to electrical engineers and other technical team members without direct people-management responsibility.
- Drive component-selection decisions with consideration for performance, reliability, availability, manufacturability, scalability, and cost.
- Partner cross-functionally with mechanical, software, manufacturing, supply chain, systems, and flight-test teams to resolve integration issues and support program execution.
- Support development and execution of verification and validation plans, including environmental and performance testing.
- Support transition from prototype to production, including design for manufacturability, cost optimization, documentation maturity, and resolution of production issues.
- Contribute to program reviews, risk assessments, technical decision-making, engineering standards, design practices, and continuous improvement efforts.
Now Qualifications: after "Qualification Requirements". Extract:
- Bachelor’s degree in Electrical Engineering, Electronics Engineering, or a related field.
- Master's degree preferred.
- 10+ years of electrical engineering experience involving complex electromechanical systems; aerospace, UAV, robotics, vehicle, or similar systems experience strongly preferred.
- Demonstrated experience serving as a technical lead or senior technical contributor on complex electrical development and integration efforts.
- Experience with avionics, power systems, communications, embedded systems, controls, and sensor integration.
- Experience working in a fast-paced R&D, prototyping, or new-product development environment
- Ability to travel (domestic and internationally).
- Must have valid driver’s license and ability to obtain a passport.
- Due to federal contract requirements applicable to this position, candidates must be U.S. citizens.
Note: Some of these (travel, driver license, passport, citizenship) could go under Requirements but they are listed under Qualification Requirements. We'll keep them under Qualifications for now, but we also have a separate Requirements section for physical requirements etc. Might be overlapping. To avoid duplication, we could put travel, driver license, passport, citizenship under Requirements (since they are not qualifications per se). But the instruction says we can have Requirements section for things like physical requirements, travel, etc. However we also have Qualifications and Skills sections. It's okay to have some overlap? Better to follow the posting: they labeled "Qualification Requirements" includes education, experience, travel, driver license, passport, citizenship. So we can put all that under Qualifications. Then we can have a separate Requirements section for physical requirements only. But we need to decide if we want a Requirements section at all. We have physical requirements: "Must have the ability to lift and/or carry 45 lbs. Ability to work for extended periods at computer workstation/keyboard. Ability to type accurately and efficiently. The position will require walking, standing, squatting, crouching, stooping, lifting, climbing, pulling, pushing, sitting, repetitive motion and kneeling." That's substantive. So we can have a Requirements section for physical requirements.
Thus:
Qualifications
- ... (education, experience, travel, driver license, passport, citizenship)
Skills
- ... (skill requirements list)
Requirements
- ... (physical requirements)
Now Benefits: we have "Enjoy competitive benefits, a supportive work environment, and every other Friday off to recharge." plus later: "Ideal Aerosmith additionally offers a comprehensive benefits program, which includes health, dental, vision, and voluntary benefits; 401K with company match; company-paid holidays; every other Friday off; and paid time off for vacation and personal time." Also discretionary annual performance bonus.
Thus Benefits section: list those.
Pay: Salary range and bonus info.
Schedule: every other Friday off (maybe also mention flexible? Not needed). Could also mention work schedule? Not given.
We should avoid duplication: Benefits already mentions
Qualifications
- ... (education, experience, travel, driver license, passport, citizenship)
Skills
- ... (skill requirements list)
Requirements
- ... (physical requirements)