How to apply for Senior Software Engineer, Battery

About EnergyHub

EnergyHub builds software for distributed energy, including residential battery programs and virtual power plants. The company works with battery providers and utilities on grid flexibility. The Battery team is new and growing, so you would have room to own integrations and influence direction.

About the role

This is a backend engineering role on the Battery team. You would build services that connect to battery providers using protocols like OpenADR and IEEE 2030.5, maintain a client-facing REST API, and keep security and data protection in place. The work directly supports residential battery programs and grid flexibility.

A typical day

A typical day could involve writing backend code for a battery provider integration, reviewing protocol details, and testing against a client API. You might meet with product and OEM partners to clarify requirements, then adjust service logic or security controls. The exact routine is not stated, so ask about team meetings, on-call, and release cadence in interviews.

Who EnergyHub is looking for

• Has senior-level backend engineering experience, including designing and maintaining REST APIs and internal service integrations.
• Has worked with or is willing to learn energy protocols such as OpenADR, IEEE 2030.5, and smart grid/DER communication standards.
• Understands security and data protection practices for infrastructure and monitoring.
• Can collaborate with product, engineering, and battery OEM partners to clarify requirements and improve software quality.

Tips for this application

• In your resume, name any direct experience with OpenADR, IEEE 2030.5, DER, smart grid, or utility/battery integrations. If you lack it, describe similar protocol or device integration work in detail.
• Highlight backend services you have built that talk to external hardware or third-party providers, especially where you owned the integration end to end.
• Show examples of client-facing REST API work and the backend logic behind it, including how you handled versioning, reliability, or scale.
• Mention specific security and data protection work: authentication, authorization, encryption, monitoring, or incident response.
• Keep the application focused on backend engineering for energy or IoT integrations. Avoid generic full-stack or frontend-heavy framing.

What to cover in your cover letter

Explain why you want to work on residential batteries and virtual power plants. Describe a backend integration you owned that involved an external protocol, device, or provider. Show how you handle security and data protection in production systems. State how you would work with product and OEM partners to turn requirements into reliable services.

Research before applying

• Read EnergyHub's product pages and any public materials on residential battery programs and virtual power plants.
• Look up OpenADR and IEEE 2030.5 basics so you can speak to how they fit battery and grid communication.
• Check EnergyHub's engineering blog, talks, or GitHub if available to understand their stack and practices.
• Find public information on EnergyHub's battery provider partners and utility clients to understand the integration landscape.

Likely interview topics

Based on the job description, expect questions about:

• How you have designed and maintained a REST API used by external clients, including versioning, error handling, and scale.
• Your experience with OpenADR, IEEE 2030.5, or other smart grid/DER protocols, or how you would ramp up on them.
• A time you integrated with an external service or hardware provider and how you handled failures, retries, and data consistency.
• How you apply security and data protection practices in backend infrastructure, including monitoring and access control.
• How you collaborate with product and external partners when requirements are unclear or changing.

Common mistakes to avoid

• Submitting a generic backend resume with no mention of energy, IoT, device integration, or protocols.
• Claiming protocol experience you do not have instead of showing how you learned similar standards before.
• Ignoring the security and data protection part of the role, since it is listed as a core responsibility.