We're not hiring task executors. We're hiring product engineers who tell us what to build. The rules of software development have changed — code is cheap, iteration is cheap. The biggest risk now is being too slow.
We're building the platform that powers the energy transition. Utilities, installers, and energy service providers use epilot to digitize their customer journeys — from solar installations to EV charging to heat pumps.
It's a complex, regulated, fast-moving industry. And we're right in the middle of it.
Code is cheap. Prototypes are cheap. Experimentation is cheap. The biggest risk is no longer building the wrong thing — it's being too slow while others iterate their way to the right thing.
We're a lean team of senior engineers who've internalized this. We use AI agents to move faster, automate what used to take weeks, and focus human judgment on the problems that actually matter.
Click the traits that describe you — see how well you'd fit.
You care about the outcome, not the output. Business impact over technical elegance — though you can do both.
You don't wait for a ticket. You identify what matters, propose it, and build it.
By normal company standards. You ship rough, learn fast, and refine in production.
You use AI coding agents as a force multiplier and still write line by line when the situation demands it.
You design the API, build it e2e, deploy it, monitor it, fix it when it crashes. You built it, you own it.
Honest about tradeoffs, not precious about your code. You show up with a proposal, not just a flag.
Clear expectations, no surprises. Click each phase to expand.
Engineering here is a leadership function. No backlog handed to you, no ops team to hand off to.
No managed backlog. You understand the business, talk to customers, and come with proposals. Project Managers empower you, designers help with how things should ideally be.
No ops team to hand things off to. You own deployment, monitoring, and incidents — exactly why we build things carefully.
We use agents to accelerate the boring: bug fixing, test writing, standard feature work. That frees you for work requiring real judgment.
Design the contract before writing a line. OpenAPI, clear interfaces, no tribal knowledge required to integrate with your service.
Code wins arguments. A working feature beats an architecture diagram every time. Rent over build wherever possible.
Feedback is direct, praise is public, mistakes are owned. Remote-first, async-friendly — we write things down and keep meetings short.
Some behaviors that simply don't work in this team.
We're a lean team doing big things at the intersection of software and the energy transition. If this resonates, let's talk.