Electrical Systems Engineer

• Power: batteries, battery management, DC power distribution, chargers, protection, fusing, converters, current sensing, thermal limits, and energy monitoring.
• Body: robot-wide electrical architecture, harness routing, connectors, grounding, shielding, cable strain relief, serviceability, and dense electromechanical packaging.
• Brain: compute hardware integration, edge AI hardware, storage, networking, high-speed interfaces, safety processors, and power budgeting for onboard intelligence.
• Eyes: camera, depth, lidar, IMU, microphone, tactile, force/torque, encoder, and sensor front-end electronics.
• Hands and legs: actuator electronics, motor drives, encoder interfaces, current sensing, thermal sensing, flex cables, and high-cycle connector reliability.
• Factory layer: PCBA bring-up, harness build quality, end-of-line tests, electrical fixtures, production diagnostics, compliance evidence, and sustaining engineering.
• Fleet layer: electrical telemetry, charging health, fault codes, power logs, field failure analysis, and design improvements based on deployed robots.

An electrical systems engineer turns robot requirements into working electrical hardware that can be built, tested, debugged, and scaled.

In a humanoid company, the work often includes:

• Defining electrical architecture for robot subsystems such as the head, torso, arms, hands, legs, battery pack, charging dock, compute stack, sensor suite, and actuator electronics.
• Designing, reviewing, or validating PCBAs for mixed-signal circuits, motor controllers, power distribution, sensor interfaces, compute carriers, audio/display systems, battery interfaces, and test fixtures.
• Selecting components such as microcontrollers, processors, power regulators, gate drivers, MOSFETs, current sensors, encoders, connectors, cable assemblies, fuses, protection devices, cameras, microphones, speakers, antennas, and thermal sensors.
• Designing or improving power distribution across batteries, chargers, DC-DC converters, motor drives, compute modules, sensors, and auxiliary electronics.
• Creating electrical block diagrams, schematics, layout constraints, interface-control documents, cable diagrams, harness drawings, connector pinouts, and assembly notes.
• Working with mechanical engineers on board placement, harness routing, connector access, strain relief, thermal paths, sealing, vibration, shock, and serviceability.
• Working with embedded engineers on board bring-up, firmware flashing, boot behavior, communication interfaces, diagnostics, watchdogs, sensor reads, and fault handling.
• Working with actuator and controls teams on motor drives, current sensing, encoder feedback, electrical bandwidth, noise, thermal limits, and safe shutdown behavior.
• Working with perception teams on sensor interfaces, camera synchronization, MIPI/USB/Ethernet/PCIe bandwidth, timestamping, power noise, and sensor calibration support.
• Debugging hardware with oscilloscopes, logic analyzers, multimeters, power analyzers, thermal cameras, DAQs, current probes, spectrum analyzers, and robot logs.
• Running electrical validation tests for power integrity, signal integrity, thermal behavior, EMI/EMC risk, connector reliability, battery/charging behavior, motor-drive performance, and system-level robustness.
• Supporting manufacturing by creating test fixtures, end-of-line procedures, rework instructions, inspection criteria, supplier documentation, and failure triage workflows.
• Supporting deployed robots by analyzing electrical faults, power logs, charging failures, intermittent cables, sensor dropouts, board damage, thermal issues, and field reliability data.

The role is deeply cross-functional. Electrical systems engineers sit between the physical body, the low-level firmware, the robot software, the controls stack, the factory, and the real deployment environment.

What the work feels like day to day

A normal week might include:

• Reviewing the robot's power tree to check whether a new compute module overloads a DC-DC rail during peak actuator motion.
• Debugging why a camera stream drops when the robot's arm motors accelerate.
• Updating a board layout because a high-current switching node is coupling noise into an encoder signal.
• Working with a mechanical engineer to reroute a harness that is failing after repeated elbow flexion.
• Bringing up a new PCBA with a bench supply, oscilloscope, current probe, thermal camera, and firmware engineer nearby.
• Creating a validation plan for a charging dock, including thermal, electrical, functional, and compliance-related tests.
• Investigating whether a sensor failure is caused by firmware, connector seating, cable strain, ESD damage, grounding, or a supplier issue.
• Writing a Python script to automate power-cycle testing and collect current, voltage, temperature, and fault-code data.
• Building a factory test fixture so technicians can validate a board or harness without needing engineering support.
• Reviewing fleet logs to identify whether a field failure is random, environmental, build-related, or tied to a specific robot revision.

The best electrical systems engineers are not only circuit designers. They are hands-on system debuggers who can move between schematics, boards, cables, firmware, mechanical packaging, robot logs, lab instruments, and production constraints.

Humanoid robots are electrical systems wrapped around a moving mechanical body. Power, sensing, compute, actuation, charging, and communication all have to work together under motion, heat, noise, impact, and safety constraints.

Electrical systems engineering matters because humanoids need:

1. Reliable power delivery
   A humanoid robot draws power from batteries, distributes it across compute, sensors, actuators, communication systems, cooling, displays, audio, and safety electronics. Poor power design creates brownouts, noise, overheating, shutdowns, and unexplained behavior.

2. Dense packaging
   Human-like proportions leave limited space for boards, connectors, cables, thermal paths, shields, batteries, fuses, antennas, and service access. Electrical design must work with the mechanical body, not fight it.

3. Clean sensing
   Perception, control, and safety depend on trustworthy sensor data. Encoder noise, camera dropouts, IMU timing errors, force-sensor drift, grounding mistakes, or cable failures can break higher-level robot behavior.

4. Safe energy control
   Robots carry batteries and powerful actuators. Electrical systems need protection, isolation where required, fusing, fault detection, thermal monitoring, safe charging behavior, and clear shutdown states.

5. Noise-aware design
   Motor drives, switching regulators, high-speed interfaces, radios, displays, audio systems, and sensor front ends can interfere with each other. EMI/EMC is not a paperwork problem at the end. It has to influence architecture, layout, shielding, grounding, and validation.

6. Manufacturing repeatability
   A hand-built prototype can hide fragile assumptions. A production robot needs boards, cables, and electrical assemblies that can be built, inspected, tested, repaired, and traced consistently.

7. Field reliability
   Deployed robots experience dust, vibration, repeated charging, cable flexing, connector wear, ESD, temperature changes, operator handling, and long duty cycles. Electrical systems engineers turn field failures into design improvements.

8. Whole-stack performance
   AI models, control loops, sensors, actuators, and fleet tooling depend on electrical foundations. If the electrical system is unstable, every higher layer becomes harder to debug.

A simple rule: when electrical systems are weak, robot failures look mysterious. When electrical systems are strong, the rest of the team can build on a stable platform.

This role fits people who like hands-on hardware, system debugging, detailed design work, and cross-functional trade-offs.

Electrical and electronics engineers

You already have useful skills: circuits, schematics, PCB design, lab instrumentation, component selection, board bring-up, debugging, and electrical validation.

You are probably missing: robot-specific power budgets, actuator noise, moving harnesses, sensor timing, firmware integration, robotics safety expectations, field reliability, and production robot test workflows.

Best entry angle: electrical hardware engineer, PCBA design engineer, electrical systems engineer, mixed-signal hardware engineer, electrical integration engineer, or electrical test engineer.

Robotics and mechatronics students

You may already understand motors, sensors, microcontrollers, CAD, ROS, controls, and basic robot integration.

You are probably missing: professional electrical design process, signal integrity, power integrity, EMI/EMC, design reviews, test documentation, DFM/DFA, supplier documentation, and production-quality validation.

Best entry angle: junior electrical engineer, robot hardware engineer, electrical test engineer, hardware integration engineer, or mechatronics engineer.

Power electronics engineers

You already understand converters, switching behavior, gate drivers, thermal behavior, efficiency, current sensing, protection, and high-power debugging.

You are probably missing: robot packaging, moving cables, actuator/sensor integration, field diagnostics, battery/charging constraints, and the cross-functional robot stack.

Best entry angle: power electronics engineer, motor drive engineer, charging systems engineer, battery systems engineer, actuator electronics engineer, or electrical systems integration engineer.

Battery, charging, and energy systems engineers

You already understand cells, packs, charging, safety, thermal behavior, test data, compliance constraints, and energy trade-offs.

You are probably missing: humanoid duty cycles, actuator peak loads, robot charging workflows, whole-body packaging, fleet telemetry, and integration with embedded diagnostics.

Best entry angle: battery systems engineer, BMS engineer, charging systems engineer, power systems integration engineer, or robot energy systems engineer.

Embedded systems engineers moving toward hardware

You already understand microcontrollers, buses, firmware bring-up, debugging, timing, real-time behavior, and hardware/software interfaces.

You are probably missing: deeper analog and power design, PCB layout constraints, component derating, EMI/EMC, power integrity, harness design, and manufacturing documentation.

Best entry angle: embedded hardware integration, board bring-up engineer, sensor electronics engineer, actuator electronics support, or electrical systems validation.

Automotive, aerospace, medical, or consumer hardware engineers

You already understand product reliability, test discipline, documentation, design reviews, suppliers, compliance, manufacturing, and quality systems.

You are probably missing: robotics-specific actuator loads, robot autonomy integration, sensor fusion needs, humanoid packaging, fleet operations, and fast prototype iteration.

Best entry angle: electrical systems engineer, electrical integration engineer, compliance-oriented hardware engineer, production electrical test engineer, or reliability-focused hardware engineer.

Think of this role in layers. Do not try to learn every specialty at once.

Electrical fundamentals

These are the base skills behind credible robot electrical work.

• Circuit analysis: voltage, current, resistance, impedance, capacitance, inductance, transients, grounding, and protection.
• Analog design: filtering, amplification, noise, ADC/DAC interfaces, sensor conditioning, references, biasing, and measurement accuracy.
• Digital design: logic levels, timing, buses, high-speed interfaces, clocking, resets, bootstrapping, and signal integrity.
• Power electronics: DC-DC conversion, switching regulators, gate drivers, MOSFETs, current sensing, thermal behavior, and protection.
• Batteries and charging: cell behavior, pack architecture, BMS concepts, charging profiles, protection, balancing, temperature monitoring, and fault handling.
• Electromagnetic compatibility: emissions, susceptibility, shielding, grounding, cable routing, filtering, and layout practices.
• Thermal awareness: component losses, heat paths, derating, enclosure effects, airflow, conduction, and thermal validation.

PCB and electronics design

Humanoid robots contain dense, high-consequence electronics.

Learn:

• Schematic capture and electrical design reviews.
• PCB layout for mixed-signal, power, high-speed, and dense assemblies.
• Design rules, clearances, creepage where relevant, controlled impedance, stackups, grounding, and return paths.
• Component selection, derating, lifecycle risk, supply chain constraints, and second sourcing.
• BOM management, design documentation, manufacturing outputs, and revision control.
• HDI, flex, rigid-flex, and compact board packaging where relevant.
• Bring-up planning: power rails first, clocks/resets, interfaces, sensors, firmware, and system tests.

Robot electrical architecture

Robots are not isolated boards. They are distributed electrical systems.

Learn:

• Robot power trees and current budgets.
• Safety power paths, e-stops, interlocks, watchdogs, and safe shutdown behavior.
• Sensor power and data interfaces.
• Motor drive and actuator feedback electronics.
• Harness routing, connector selection, shielding, strain relief, bend radius, and service loops.
• Communication buses such as CAN, CAN FD, EtherCAT, UART, SPI, I2C, USB, Ethernet, MIPI, PCIe, LVDS, and RS-485.
• Time synchronization and trigger signals for cameras, IMUs, and other sensors.
• Electrical interface-control documents so mechanical, firmware, software, and factory teams know what the hardware provides.

Hardware debugging and validation

This is where many candidates become credible.

Learn:

• Oscilloscope use: probing, grounding, bandwidth, triggering, rail ripple, switching nodes, and signal timing.
• Logic analyzer use: SPI, I2C, UART, CAN, and timing analysis.
• Power analysis: inrush current, peak current, brownouts, efficiency, rail sequencing, and thermal rise.
• Fault injection: power-cycle tests, connector disconnects, sensor dropouts, communication errors, temperature changes, and motor load changes.
• Root-cause analysis: reproduce, instrument, isolate, test hypotheses, document findings, and verify fixes.
• Test automation with Python, LabVIEW, MATLAB, or vendor APIs.
• Reliability testing: vibration, cable flex, connector cycling, temperature, charging cycles, and life-cycle testing.

Manufacturing and production readiness

Humanoid companies need hardware that can scale beyond prototypes.

Learn:

• DFM and DFA for PCBAs, cables, enclosures, and robot assemblies.
• IPC-style workmanship expectations for boards and harnesses.
• Factory test fixtures, bed-of-nails concepts, flying probe, functional test, calibration, and end-of-line test.
• Rework and failure-triage processes.
• Supplier documentation: drawings, fabrication notes, assembly notes, inspection criteria, and test requirements.
• Production data capture and traceability.
• Sustaining engineering: ECOs, design revisions, field failures, root-cause reports, and corrective actions.

Humanoid-specific skills

These separate humanoid electrical work from many other hardware roles.

• High-density board and cable packaging inside limbs, hands, torso, and head.
• Moving harness reliability through shoulders, elbows, wrists, hips, knees, ankles, neck, and fingers.
• Motor-drive noise and sensor integrity in the same compact system.
• Charging behavior for autonomous or semi-autonomous robot operation.
• Battery, thermal, and duty-cycle limits during locomotion and manipulation.
• Electrical telemetry for fleet health, field diagnostics, and predictive maintenance.
• Human-facing electronics such as displays, audio, lights, microphones, buttons, and status indicators.
• Safety around people: power limits, fault detection, safe shutdown, insulation, grounding, and compliance evidence.

Do not present this list as a syllabus where every tool is required. Different companies use different stacks. These are the common clusters to recognize.

ECAD and PCB design

• Altium Designer: widely used for schematic capture, PCB layout, design rules, manufacturing outputs, and professional hardware design reviews.
• KiCad: open-source schematic capture and PCB design; useful for portfolio projects and low-cost learning.
• Cadence OrCAD / Allegro: common in more advanced PCB and enterprise hardware workflows.
• Mentor / Siemens Xpedition: used in complex electronics organizations.
• EAGLE / Fusion electronics: sometimes used for simpler boards and quick prototypes.

Circuit simulation and analysis

• LTspice: practical SPICE simulation for analog, power, filtering, transients, and switching behavior.
• PSpice / SIMetrix / TINA-TI: alternative circuit simulation tools.
• MATLAB / Simulink: modeling, signal analysis, control/power analysis, and test-data processing.
• Python: automation, data analysis, instrument control, plotting, and report generation.
• Jupyter notebooks: useful for sharing validation analysis, but not a replacement for real hardware evidence.

Lab instruments

• Oscilloscope.
• Logic analyzer.
• Digital multimeter.
• Bench power supply.
• Electronic load.
• Current probe.
• Differential probe.
• Power analyzer.
• Function generator.
• Spectrum analyzer.
• Network analyzer where RF or high-speed work requires it.
• DAQ system.
• Thermal camera.
• Environmental chamber.
• Motor dyno or actuator test stand.

Robot electrical interfaces

• CAN / CAN FD: common for robust embedded communication in mobile robots, vehicles, motor controllers, and distributed electronics.
• EtherCAT: common in high-performance motion and industrial automation contexts.
• USB / Ethernet: compute, sensors, cameras, debugging, and robot networking.
• MIPI CSI / DSI: camera and display interfaces in compact embedded systems.
• PCIe: high-speed compute and accelerator interfaces.
• SPI / I2C / UART: microcontroller, sensors, and board-level interfaces.
• LVDS / RS-485: differential signaling for noisy or longer-distance links.
• GPIO / PWM / ADC / DAC: low-level control, sensing, and diagnostics.

Power and battery systems

• Battery packs and battery management systems.
• DC-DC converters.
• Load switches and ideal diodes.
• Protection circuits, fuses, TVS diodes, current limiting, and reverse-polarity protection.
• Gate drivers and motor-drive stages.
• Chargers and charging docks.
• Current, voltage, and temperature monitoring.
• Power sequencing and brownout handling.

Mechanical-electrical integration

• Harness design tools or CAD-integrated wiring tools.
• Connector supplier catalogs and datasheets.
• Cable bend-radius and flex-life data.
• 3D CAD reviews for board fit, connector access, cable routing, strain relief, serviceability, and thermal paths.
• Assembly drawings, cable diagrams, pinout tables, and interface-control documents.

Manufacturing, quality, and compliance

• IPC standards for soldered electrical assemblies and cable/wire harness assemblies.
• UL, IEC, CE, FCC, and regional compliance workflows where relevant.
• EMI/EMC test plans and pre-compliance testing.
• Functional safety concepts and hazard analysis support.
• PLM systems, ECO workflows, BOM tools, and supplier documentation.
• Jira, Linear, GitHub, or similar tools for tracking electrical bugs, validation work, and design changes.

Robotics integration tools

• Robot logs and telemetry dashboards.
• ROS 2 or internal robot middleware for hardware status, diagnostics, and sensor data.
• Foxglove, RViz, or internal visualization tools for correlating electrical data with robot behavior.
• HIL/SIL setups for testing boards, sensors, controllers, and robot subsystems before full-robot deployment.

A strong electrical systems portfolio should show real measurements, design trade-offs, and debugging evidence. Do not only show a render of a PCB. Show the board, the test setup, the data, the failure modes, and what you changed.

Use low-voltage, current-limited bench setups unless you are trained and supervised. Do not build mains chargers, high-voltage battery packs, or unsafe power systems as a solo portfolio project.

Project 1: Robot power distribution and diagnostics board

Build: a low-voltage power distribution board for a small robot or actuator test rig. Include input protection, fusing or resettable protection, multiple regulated rails, voltage/current/temperature monitoring, status LEDs, a microcontroller interface, and a simple communication interface such as CAN, UART, or USB.

What it proves:

• You can design a practical robot power subsystem.
• You understand protection, sequencing, current measurement, and telemetry.
• You can produce schematics, layout, BOM, and manufacturing files.
• You can bring up hardware and measure whether it behaves as expected.

Evidence to include:

• Block diagram and power tree.
• Schematic PDF and PCB screenshots.
• Photos of the assembled board.
• Bring-up checklist.
• Scope captures of rail startup and ripple.
• Load-test results.
• Fault-test results such as overcurrent or disconnect behavior.
• A short explanation of what you would improve in revision 2.

Project 2: Sensor and compute integration rig

Build: a small sensor integration platform with one compute board, one or more cameras or IMUs, a power subsystem, and a diagnostic harness. The goal is to show stable power, clean interfaces, synchronized data where possible, and clear documentation.

What it proves:

• You can integrate sensors and compute hardware like a robot subsystem.
• You understand cable routing, connectors, power budgets, and signal integrity risks.
• You can debug hardware/software interactions.
• You can produce clear interface documentation for other engineers.

Evidence to include:

• Interface-control document with pinouts, voltages, connectors, and data links.
• Photos of the wiring and mounting.
• Power budget table.
• Test procedure.
• Sensor data capture.
• Notes on timing, dropouts, and noise issues.
• Improvements you would make for a robot head or torso package.

Project 3: Motor-drive or actuator electronics validation setup

Build: a safe, low-voltage motor or actuator electronics test setup. This could use an off-the-shelf motor driver or a small custom driver board if you have the experience. Measure current, temperature, encoder feedback, PWM behavior, supply ripple, and fault states under different loads.

What it proves:

• You understand the electrical side of robot motion.
• You can instrument a motor or actuator system properly.
• You can connect power electronics behavior to control and thermal limits.
• You can document safe test procedures.

Evidence to include:

• Test rig diagram.
• Wiring diagram.
• Safety notes and current limits.
• Scope captures.
• Current and temperature plots.
• Encoder or feedback data.
• Failure or saturation cases.
• Root-cause analysis of one issue you found.

Project 4: Harness design and flex reliability test

Build: a small wiring harness for a moving joint, such as a simple elbow, wrist, pan-tilt head, or gripper. Select connectors and wires, document pinouts, design strain relief, and run repeated motion cycles while measuring continuity or signal quality.

What it proves:

• You understand that robot cables are moving parts.
• You can design for assembly, serviceability, and reliability.
• You can create production-like documentation.
• You can test physical durability instead of guessing.

Evidence to include:

• Harness drawing.
• Connector and wire selection rationale.
• Pinout table.
• Bend-radius and strain-relief notes.
• Photos of the harness in motion.
• Cycle-test results.
• Failure analysis if a wire or connector fails.

Project 5: Electrical pre-compliance debug report

Build: a documented investigation of a noisy circuit or subsystem. For example, show how a switching regulator, motor driver, or cable routing choice affects a sensor signal. Use measurements to compare the original issue and the fix.

What it proves:

• You can reason about EMI/EMC risk before formal compliance testing.
• You can use measurement tools instead of guessing.
• You understand grounding, shielding, filtering, layout, and return paths.
• You can communicate hardware trade-offs clearly.

Evidence to include:

• Problem statement.
• Test setup photos.
• Scope or spectrum captures.
• Hypotheses tested.
• Layout or wiring changes.
• Before/after results.
• Lessons learned.

Project 6: Factory electrical test fixture

Build: a simple fixture and script that validates a board, harness, or sensor assembly. Include pass/fail criteria, serial-number tracking, automated measurements, and a clear operator procedure.

What it proves:

• You understand production readiness.
• You can design tests other people can run.
• You can turn engineering knowledge into repeatable factory evidence.
• You can connect electrical design to manufacturing quality.

Evidence to include:

• Fixture photos or CAD.
• Wiring diagram.
• Test script.
• Example pass/fail output.
• Operator instructions.
• Error messages and troubleshooting guide.
• Notes on how the fixture would scale for production.

Electrical systems jobs rarely use one exact title. Use these titles and keywords when building the jobs taxonomy.

Direct titles

• Electrical Systems Engineer
• Electrical Engineer, Robotics
• Robotics Electrical Engineer
• Electrical Hardware Engineer
• Hardware Electrical Engineer
• Electrical Systems Integration Engineer
• Electrical Integration Engineer
• Robot Electrical Engineer
• Robot Hardware Engineer
• Mechatronics Electrical Engineer

Specialist titles

• PCB Design Engineer
• Mixed-Signal Hardware Engineer
• Power Electronics Engineer
• Motor Drive Engineer
• Actuator Electronics Engineer
• Battery Systems Engineer
• Battery Management Systems Engineer
• Charging Systems Engineer
• Compute Hardware Engineer
• Sensing Hardware Engineer
• RF / EMI / EMC Engineer
• Harness Engineer
• Cabling Engineer
• Electrical Test Engineer
• Manufacturing Electrical Test Engineer
• Hardware Validation Engineer
• Electrical Reliability Engineer
• Compliance Engineer, Robotics Hardware

Adjacent titles

• Embedded Hardware Engineer
• Systems Engineer, Electrical
• Mechatronics Engineer
• Hardware Systems Engineer
• Robotics Systems Engineer
• Product Compliance Engineer
• Manufacturing Test Engineer, PCBA
• Test & Validation Engineer, Motors and Actuators
• Functional Safety Engineer, Hardware
• Field Hardware Engineer

Search keywords

Use these as job-board filters:

• electrical systems engineer robotics
• robotics electrical engineer
• humanoid electrical engineer
• robot hardware engineer
• electrical systems integration
• PCB design robotics
• PCBA robotics
• mixed-signal hardware robotics
• power electronics robotics
• motor drive engineer robotics
• actuator electronics
• battery systems robotics
• BMS robotics
• charging systems robotics
• harness engineer robotics
• CAN robotics
• EtherCAT robotics
• EMI EMC robotics
• electrical validation robotics
• hardware bring-up robotics
• manufacturing electrical test
• robot charging
• sensor hardware robotics

Job openings change quickly. Treat this as a live company map, not a permanent list. These are strong examples to seed the Companies and Jobs sections.

Figure

Figure hires for humanoid electrical work across actuator systems, power systems, head electronics, manufacturing electrical test, PCBA test, charging, compliance, deployment support, and broader robot integration.

Why it matters for this role: Figure's electrical listings show the difference between board-level design and robot-level integration. Relevant work includes motor-control PCBAs, gate drivers, power distribution, mixed-signal sensing, Altium, LTspice, charging systems, power converters, EMI/EMC, thermal validation, high-speed interfaces, embedded compute, RF, audio, and manufacturing bring-up.

Useful internal links to create:

• /careers/companies/figure
• /careers/jobs?company=figure&role_family=electrical-systems
• /careers/role-atlas/actuator-engineer
• /careers/role-atlas/embedded-systems-engineer
• /careers/role-atlas/robot-test-validation-engineer
• /careers/role-atlas/robotics-safety-engineer

Apptronik

Apptronik hires electrical engineers for the Apollo humanoid robot across general electrical design, compute hardware, sensing, HRI electronics, dexterity electronics, motor drives, power and communications, RF/EMI/EMC, charging, and production-oriented electrical work.

Why it matters for this role: Apptronik's listings are useful examples of electrical systems work spread across the robot body: multi-layer mixed-signal PCBAs, rapid prototyping, board-level and system-level testing, audio/display electronics, sensor bandwidth, functional safety, communications hardware, EMI/EMC strategy, charging docks, and motor-drive electronics.

Useful internal links to create:

• /careers/companies/apptronik
• /careers/role-atlas/embedded-systems-engineer
• /careers/role-atlas/actuator-engineer
• /careers/role-atlas/mechanical-design-engineer
• /careers/role-atlas/manufacturing-engineer

Tesla Optimus

Tesla hires for Optimus electrical work across power electronics, charging, AI inference hardware, hardware systems, robotics systems, embedded software, actuators, motors, and validation.

Why it matters for this role: Optimus job titles show how humanoid electrical systems connect the robot's power delivery, compute, sensing, charging, and actuation hardware. Tesla's framing of robot electronics as the robot's power, sensory, and nervous systems is useful language for candidates trying to understand the role.

Useful internal links to create:

• /careers/companies/tesla-optimus
• /careers/role-atlas/actuator-engineer
• /careers/role-atlas/embedded-systems-engineer
• /careers/role-atlas/robot-test-validation-engineer
• /careers/role-atlas/robotics-safety-engineer

1X Technologies

1X hires across hardware engineering, including actuators and drives, battery testing, robot head/audio systems, mechanical hardware, safety, validation, manufacturing, and fleet operations.

Why it matters for this role: 1X is useful for candidates interested in home humanoid robots, where electrical systems must support safe operation around people, human-facing sensors and audio, battery behavior, actuator drive reliability, manufacturing, and long-term serviceability.

Useful internal links to create:

• /careers/companies/1x-technologies
• /careers/role-atlas/actuator-engineer
• /careers/role-atlas/robotics-safety-engineer
• /careers/role-atlas/robot-operations-fleet-operator
• /careers/role-atlas/field-robotics-engineer

Agility Robotics

Agility Robotics hires electrical engineers and hardware engineers for Digit and related robotics systems, alongside AI, manufacturing, testing, validation, deployment, and field roles.

Why it matters for this role: Agility is a useful example for electrical systems engineers interested in robots that ship into logistics and industrial environments. The practical themes are reliability, deployment, manufacturing, field service, and production hardware, not just prototype electronics.

Useful internal links to create:

• /careers/companies/agility-robotics
• /careers/role-atlas/manufacturing-engineer
• /careers/role-atlas/robot-test-validation-engineer
• /careers/role-atlas/field-robotics-engineer
• /careers/role-atlas/robot-operations-fleet-operator

Sanctuary AI

Sanctuary AI hires across physical AI, robotics, hardware, software, controls, manufacturing, and operations, with particular relevance to dexterous manipulation and real-world industrial automation.

Why it matters for this role: Sanctuary is useful for candidates interested in electrical systems that support advanced robotic hands, sensing, controls, teleoperation, and physical AI experimentation on real hardware.

Useful internal links to create:

• /careers/companies/sanctuary-ai
• /careers/role-atlas/manipulation-engineer
• /careers/role-atlas/embedded-systems-engineer
• /careers/role-atlas/robotics-ai-engineer

NEURA Robotics

NEURA Robotics hires hardware, production, PCB design, electrical, embedded, firmware, and robotics manufacturing roles across cognitive and humanoid robot systems.

Why it matters for this role: NEURA's listings show useful European hiring language around PCB design, electrical engineering, robotics manufacturing, test adapters, automated test and measurement systems, safe operation, standards, and series production.

Useful internal links to create:

• /careers/companies/neura-robotics
• /careers/role-atlas/embedded-systems-engineer
• /careers/role-atlas/manufacturing-engineer
• /careers/role-atlas/robot-test-validation-engineer
• /careers/role-atlas/mechanical-design-engineer

Boston Dynamics

Boston Dynamics hires across robotics software, hardware, test, systems, manufacturing, automation, and real robot applications depending on hiring cycle.

Why it matters for this role: Boston Dynamics is useful for candidates interested in advanced mobile robots where electrical systems must survive dynamic motion, field use, integration with complex software, and rigorous validation.

Useful internal links to create:

• /careers/companies/boston-dynamics
• /careers/role-atlas/robot-test-validation-engineer
• /careers/role-atlas/field-robotics-engineer
• /careers/role-atlas/robotics-technical-program-manager

A candidate becomes credible for electrical systems roles when they can show evidence in these areas.

Strong positive signals

• Can explain a robot electrical architecture clearly: power tree, compute, sensors, actuators, harnesses, charging, grounding, and diagnostics.
• Has designed, reviewed, or brought up a PCB.
• Can read schematics and explain layout trade-offs.
• Understands both analog and digital issues at a practical level.
• Has used an oscilloscope properly and can explain what they measured.
• Can debug power rail startup, ripple, brownouts, thermal rise, and intermittent behavior.
• Understands motor-drive noise, sensor integrity, current sensing, encoder interfaces, and power electronics basics.
• Can document pinouts, connector choices, test plans, and validation results.
• Has built or tested a wiring harness and understands strain relief, shielding, and connector reliability.
• Can turn a vague hardware failure into a reproducible test.
• Understands DFM, DFA, manufacturing test, and production support.
• Does not treat EMI/EMC as a final checkbox; understands design-time mitigation.
• Can work with firmware, mechanical, controls, manufacturing, safety, and field teams without throwing work over the wall.

Weak signals

• Only shows PCB renders with no measurements, bring-up notes, or test data.
• Cannot explain why a circuit failed or how they debugged it.
• Treats batteries, charging, and power electronics casually.
• Does not understand how moving cables fail.
• Has never used basic lab instruments independently.
• Ignores grounding, shielding, thermal behavior, or signal integrity.
• Designs boards without thinking about assembly, test, service, or manufacturing.
• Cannot explain interface requirements to firmware or mechanical teams.
• Talks about compliance only as paperwork, not engineering evidence.
• Has no failure analysis story.

Interview questions to prepare for

• Walk me through the electrical architecture of a robot subsystem you designed or debugged.
• How would you design the power tree for a humanoid robot head, arm, or actuator module?
• How would you debug a sensor that drops out when motors turn on?
• How do you approach grounding and shielding in a robot with motor drives and sensitive sensors?
• What would you measure during first power-on of a new PCBA?
• How do you decide whether an issue is hardware, firmware, mechanical, or software?
• How would you design a harness for a moving robot joint?
• What are the risks of a battery-powered robot charging dock?
• How would you validate a DC-DC converter rail for a robot compute subsystem?
• How would you prepare a board or harness for production testing?
• Tell me about a hardware bug that took you a long time to diagnose.
• How do you document electrical interfaces so other teams can use them correctly?
• What would you do before formal EMI/EMC testing to reduce risk?
• How would you use robot logs during electrical failure analysis?

• Using “electrical engineer” too generically. In robotics, the useful page is not about every electrical engineering career. It is about electrical systems inside robots.
• Only learning PCB design. PCB skill matters, but humanoid robots also require power architecture, harnesses, connectors, charging, safety, validation, and manufacturing thinking.
• Ignoring firmware. You do not need to be a firmware specialist, but you must understand board bring-up, communication interfaces, diagnostics, and hardware/software boundaries.
• Ignoring mechanical packaging. A board that cannot fit, cool, connect, or survive vibration is not a good robot board.
• Ignoring moving cables. Harnesses are failure-prone robot components. Treat cables, connectors, bend radius, flex life, and strain relief as design work.
• Skipping measurements. Hardware portfolios need scope captures, load tests, thermal data, current measurements, and failure reports.
• Overbuilding dangerous projects. Do not build unsafe battery packs, mains chargers, or high-voltage systems for a portfolio. Use safe low-voltage, current-limited setups unless supervised by qualified people.
• Treating EMI/EMC as optional. Motor drives, switching regulators, radios, high-speed links, and sensor front ends can break each other.
• Forgetting production. Humanoid companies need designs that can be assembled, tested, traced, repaired, and improved repeatedly.
• Not writing documentation. Pinouts, diagrams, BOMs, test plans, bring-up notes, and failure reports make electrical work understandable to the rest of the company.

This section is optional on Role Atlas pages, but useful for readers who are ready to act.

First 30 days: build the base

• Refresh circuit fundamentals: power, analog, digital, sensors, and protection.
• Learn one ECAD tool: KiCad for accessibility or Altium if you already have access.
• Practise reading schematics and datasheets.
• Learn basic lab instrument use: oscilloscope, multimeter, power supply, logic analyzer.
• Study robot electrical architecture: batteries, power tree, compute, sensors, actuators, harnesses, and charging.
• Create a simple block diagram for a robot subsystem.

Output: a documented low-voltage robot electrical architecture sketch with power budget, interfaces, connector list, and measurement plan.

Days 31–60: design and test hardware

• Design a small board or integration harness.
• Build a safe bench test setup.
• Measure startup, ripple, current draw, temperature, and fault behavior.
• Write a bring-up checklist.
• Document one hardware issue and how you debugged it.
• Add Python or LabVIEW test automation if possible.

Output: a portfolio page with schematic screenshots, board or harness photos, test data, scope captures, and a clear failure-analysis note.

Days 61–90: make it look hireable

• Add a proper README and architecture diagram.
• Create manufacturing-style documentation: BOM, pinout table, wiring diagram, test procedure, and revision notes.
• Add a simple validation matrix.
• Run a repeated-cycle or load test.
• Write a short design review explaining trade-offs.
• Map your project to real job descriptions.

Output: a hardware portfolio project that shows design, bring-up, measurement, debugging, documentation, and production awareness.

Is Electrical Systems Engineer the same as Electrical Engineer?

Not exactly. Electrical Engineer is the broad job title. Electrical Systems Engineer is the better Role Atlas title for humanoid robotics because the work spans robot-wide power, boards, wiring, sensors, compute, charging, integration, validation, production, and field reliability.

Do I need to design PCBAs for this role?

For many roles, yes. PCB design or PCBA validation is a common requirement. Some electrical systems roles are more integration-focused, but even then you need to read schematics, understand board behavior, and debug hardware confidently.

Do I need power electronics experience?

It depends on the role. Power electronics is essential for motor drives, charging, batteries, and power distribution. It is less central for some sensor, compute, or HRI electronics roles, but basic power literacy is still important in robots.

Is this role more hardware or software?

It is hardware-first, but it touches software constantly. Electrical systems engineers work with firmware, diagnostics, logs, test automation, embedded interfaces, and sometimes Python or C/C++ scripts for bring-up and validation.

Can a mechatronics student enter this role?

Yes, if they build stronger electrical evidence. A mechatronics background is helpful because robots are cross-disciplinary, but candidates still need credible circuit, PCB, measurement, and documentation skills.

What is the fastest credible portfolio project?

A low-voltage robot power distribution and diagnostics board is one of the best starter projects. It proves power architecture, PCB design, measurement, protection, documentation, and test thinking without requiring expensive robot hardware.

Should I learn Altium or KiCad?

Learn KiCad if you need a free, accessible tool. Learn Altium if you have access and want to match many professional hardware teams. The core skill is not the button-clicking; it is schematics, layout decisions, constraints, documentation, bring-up, and validation.

How much robotics theory do I need?

You do not need to be a locomotion or AI expert, but you should understand the electrical implications of robots: motors create noise and peak loads, sensors need clean timing and power, moving joints stress cables, batteries constrain duty cycle, and safety faults must be detected clearly.