Join Base Power as a Backend Software Engineer to build systems that support deployment operations for a next-generation power company.
Posted by employer 2 days ago
First seen on Joblaze 22 hours ago
Last verified on the company career page 22 hours ago
Skills & Technologies
What you'll build
Must have
Not disclosed in this posting: compensation, years of experience, visa sponsorship.
Joblaze summary
The Backend Software Engineer at Base Power focuses on developing and maintaining the software systems that facilitate the deployment of distributed battery networks, handling tasks from site evaluations to technician scheduling. Proficiency in backend languages like Go, Java, or TypeScript is essential, along with a solid grasp of distributed systems and API design. This role is suited for engineers who thrive in a fast-paced startup environment and are comfortable taking ownership of their projects. The team emphasizes collaboration and direct communication, allowing engineers to see the tangible impact of their work.
Joblaze insights
Quick facts
From the original posting
Every Base battery that ends up on a home runs through Deployments Software. We use it to evaluate sites, file permits, schedule installs, dispatch technicians, and maintain batteries once they're live.
We’re looking for a Backend Software Engineer to build the systems driving these workflows.
The problems we work on are varied. You might be building systems for 3D spatial analysis, developing automation platforms, designing scheduling algorithms for technician matching and route optimization, building real-time, multiplayer, offline-capable APIs, or designing infrastructure for monitoring and alerting.
Our software is used by teams across Base, subcontractor electricians, and utility partners. You'll work closely with engineers across Deployments, Inventory, Onboarding, Markets, and Embedded Software to design the services, APIs, and data models that support these products.
Design and build backend systems that support Base’s deployment operations, from site evaluation and scheduling to field execution and ongoing maintenance.
Solve a wide range of technical problems, including automation, scheduling and optimization, real-time systems, spatial analysis, and monitoring infrastructure.
Build reliable services, APIs, and data models that other engineers and teams depend on.
Work closely with engineers and operational teams to understand problems, challenge assumptions, and develop practical solutions.
Own your systems end-to-end, from architecture and implementation to deployment, monitoring, and maintenance.
Strong backend engineering experience in Go, Java, TypeScript, or similar languages.
Experience designing and operating production services, APIs, and data models.
A solid understanding of distributed systems, including reliability, concurrency, consistency, and failure handling.
Good engineering judgment, with an ability to balance simplicity, extensibility, and technical rigor.
High ownership, clear communication, and a willingness to dig into unfamiliar problems and domains.
The Deployments Software Team builds the software that runs Base’s deployment operations, from evaluating homes for installs to managing a growing fleet of batteries in the field. Our work directly impacts how quickly Base scales and how reliably we operate.
Base is vertically integrated, which means our engineers work directly with the teams that depend on our software, from field operations and inventory to hardware and embedded software. Within Deployments Software, you'll work alongside engineers who own different products and systems across the deployment lifecycle.
We are an in-person team that moves quickly, values simplicity, and gives engineers a lot of ownership. You’ll have the autonomy to make technical decisions, the responsibility to own your systems in production, and the opportunity to see the impact of your work in the real world.
First Principles Thinking: Question assumptions. Principles > rules.
Standard company text repeated across Base Power's postings is omitted here.