Streem Energy's SaaS runs 43 GW of wind and solar assets across 23 countries. Producers, aggregators and suppliers rely on it to operate their assets in energy markets: contracts, invoicing, market mechanisms and grid constraints. We are growing fast and are entirely self-funded: our growth comes from customer revenue alone. Our next goal is to cover every major European market within two years, then go global.

Main challenge. Energy markets change constantly, and every country has its own rules. We have to adapt the platform as fast as the markets move. At the same time, we must keep it coherent across countries and mechanisms, and simple for our customers. That depends on finding the right abstractions: ones that let us ship fast now and still hold up years from now. It also means mastering a business domain that takes real effort to understand.

How we work. Over the past year, we rebuilt the way we build software. Our engineers are Product Builders. Each one owns a track end to end: understanding the product and the customer, designing the architecture, building back and front, running the project and shipping to production. AI tools now do much of the implementation, so our people focus on architecture, business concepts and fast releases. Everyone who leads also builds, including the CTO and the Head of Engineering.

Today the team is a CTO, a Head of Engineering who directly manages 8 Product Builders, and 2 engineers who build our internal tooling. You will directly manage 4 to 6 Product Builders and run that team as autonomously as possible.

• Team management. Set clear expectations, give direct feedback and address performance issues early. Help each PB sharpen their judgment, planning and autonomy.
• Technical decisions. Challenge architectures, find abstractions that generalize, and cut coupling and unnecessary effort. Design and ship code yourself.
• Delivery. Deliver incrementally, spot risks early and remove blockers, while ownership stays with the PBs.
• Business knowledge. Learn energy markets deeply enough to make sound trade-offs and build solutions that work across customers and countries.
• Ways of working. Keep adapting how we work as AI tools evolve.

The problems we work on are hard, and we want to move very fast. That is why we are very selective. We are not trying to build a large team. We want a small and highly effective one: focused on what we build, quick to understand problems and to find the right solutions.

• 6–10 years of software engineering, including a successful first experience managing engineers.
• An outstanding engineering track record: hard problems solved and real ownership of production systems. You still build every week.
• A top academic background, typically from a leading engineering school, and a career that shows fast progression.
• The ability to bring structure, make pragmatic decisions under uncertainty and work easily with technical and non-technical people.
• An appetite for a complex business domain, and the willingness to keep changing your methods.

• Paris, hybrid. We value time together: solving a problem in a room beats a long thread.
• English is our working language. French is a plus, especially for management.
• Stack: Python, Rails and AWS (largely serverless).