FOUNDING HIRE · FORWARD DEPLOYED ENGINEERING
| LOCATION London preferred. NYC and remote also open. | REPORTS TO Cofounders | TEAM Founding | TRAVEL Around 50% | | --- | --- | --- | --- |
Building the future is expensive. Around $4T is spent annually on infrastructure projects, with up to $2T financing the energy transition. Behind these projects are investors, developers, and advisors who rely on brittle, document-intensive workflows to make billion-dollar judgement calls that directly affect the physical world around us. We help them move with speed and confidence, greening the grid faster and driving down the cost of the new infrastructure our future demands. Situ’s customers include leading renewable energy investors with over 200GW of renewable energy projects in operation and development, roughly equivalent to the peak electricity demand across the UK, France, and Spain combined.
We started Situ with a simple conviction: the energy transition has to move faster.
To figure out what was slowing it down, Gene and Thomas spent months at industry events, developer meetings, policy tables, talking to anyone who would take the time. The problem we kept finding wasn't ambition or technology. It was financing, and the friction around it. Infrastructure investment runs on brittle, data-intensive workflows. The people financing the future are bottlenecked by the tools of the past.
Situ fixes that. We pair a purpose-built AI platform [“Deal Intelligence”] with engineers who embed directly at customer sites [“Deployed in Situ”], helping investors move at the speed the energy transition demands.
It's working. We've booked seven figures in ARR with leading energy transition investors.
You will be one of our first customer-facing engineers, working directly alongside the cofounders. The role has two halves:
This is product engineering with the customer in the room. You'll write production code in our core systems, but you'll also be the person who turns a question into a feature, ships a first version by end-of-week, watches it run on a live deal, and decides what to harden and what to throw away.
The gap between 'what does the client need' and 'what does the code do' is yours to close.