How to apply for Embedded Software Engineer (Remote)

About Fuse Energy

Fuse Energy is an energy startup building a fully integrated company that develops solar and battery projects, builds its own hardware, trades power in real time, and installs distributed energy in homes. It has raised over $200M from investors including Balderton, Lakestar, Accel, Creandum, Lowercarbon, Ribbit, 20VC, Hummingbird and Collaborative Fund. Working there means joining an early-stage company that controls the full stack from generation to consumer hardware.

About the role

This remote US role focuses on the connected hardware behind Fuse Energy's fleet of distributed energy devices. You will work on connectivity, networking, device security, secure provisioning, telemetry, and fleet-scale communication from prototype to deployment. The work directly affects how devices connect, communicate, and update securely as the fleet grows.

A typical day

A typical day might involve writing or reviewing embedded code for connectivity, provisioning, or telemetry, then debugging issues with firmware, hardware, or backend teams. You could also test device communication, review security or OTA update plans, and coordinate on fleet-scale deployment details. Because the role is remote, much of the work happens over written updates and calls with distributed teammates.

Who Fuse Energy is looking for

• Has hands-on embedded software experience in C or C++ on constrained devices, with exposure to networking stacks such as TCP/IP, MQTT, or CoAP.
• Has implemented secure provisioning, device authentication, or OTA update mechanisms for connected products.
• Has worked on fleet connectivity or telemetry systems, ideally for distributed or energy-related hardware.
• Is comfortable working remotely with firmware, hardware, and backend teams and can take prototypes through to production deployment.

Tips for this application

• Highlight any embedded work involving connectivity, networking, or device security, since the job description names those as core areas.
• Name specific protocols or stacks you have used, such as MQTT, TLS, cellular, Wi-Fi, or BLE, and describe the scale of the fleet or number of devices involved.
• Mention any experience with secure provisioning or OTA updates, because the role explicitly covers secure provisioning and robust telemetry.
• Reference Fuse Energy's model of building its own hardware and selling directly to consumers, and connect your embedded work to distributed energy devices.
• State your US location and remote-work setup clearly, since the role is remote in the US and the company is UK-founded.

What to cover in your cover letter

Explain how your embedded software work has directly addressed connectivity, networking, or device security in production. Describe a specific fleet or device deployment you supported from prototype to scale. Show that you understand Fuse Energy builds its own hardware and needs resilient connectivity and telemetry across distributed energy devices. Mention your ability to work with firmware, hardware, and backend teams in a remote setting.

Research before applying

• Read Fuse Energy's public materials on its integrated model, including solar and battery projects, hardware, and direct-to-consumer energy sales.
• Look into the investors named, such as Lowercarbon and Ribbit, to understand the company's stage and strategic direction.
• Find any public information on Fuse Energy's hardware or distributed energy devices and what connectivity or telemetry they might require.
• Check the company's engineering blog or job posts for details on its firmware, hardware, and backend stack.

Likely interview topics

Based on the job description, expect questions about:

• How you would design resilient connectivity for distributed energy devices that may face unreliable networks.
• Your approach to secure provisioning and device authentication at fleet scale.
• How you have implemented or improved OTA updates and telemetry pipelines in past embedded projects.
• Trade-offs between different networking protocols or hardware choices for energy devices.
• How you collaborate with hardware and backend teams when debugging connectivity or security issues in the field.

Common mistakes to avoid

• Submitting a generic embedded resume without mentioning connectivity, networking, device security, or fleet-scale deployment.
• Claiming experience with secure provisioning or OTA updates without being able to describe the implementation and scale.
• Ignoring the energy or hardware context and treating the role as a standard embedded position at any tech company.