Faces of EnergyTech →
Stories about the people
rethinking energy trading
Martin Nøhr, Software Developer at InCommodities Asset Management, ended up in energy trading by coincidence and thanks to his network. He was working in healthcare IT, a domain he knew well and appreciated.
But then an opportunity at InCommodities Asset Management came up. A former classmate, already working on the Asset Management team, reached out.
It wasn’t an obvious next step for Martin, not one he had been actively looking for – and not one he fully understood at the time.
“I didn’t know anything about the industry. All the terminology was new, the setup was different, and even though I came in as a developer, it honestly felt like starting from zero again.”
The timing didn’t help. A new job, a new domain – and a baby on the way.
So he said no.
But the decision didn’t sit well. It felt wrong not to try. So he reached back out, restarted the conversation – and this time, he joined.
Building from the ground up
Martin joined Asset Management early, when both the team and the platform were still taking shape. There was no established setup to step into – most of what exists today had to be built from scratch.
That has shaped both his role and the way the team works.
“We were a small group, and a big part of the job was figuring things out as we went. Not just implementing solutions, but deciding what we actually needed to build and how it should fit together.”
Today, that early foundation has grown into a complex system landscape. Dozens of services are running, connected across the platform, supporting trading and asset management.
And the complexity is no longer optional – it’s part of the job.
“You start out with a few services that talk to each other, and that’s manageable. But over time, you end up with 50 or 60 services running, with dependencies across everything. At that point, you can’t avoid complexity anymore – you just have to manage it.”
“If we don’t have a clear view of what we’ve traded, then we’re basically flying blind. So even if the solution itself is just moving data from one place to another, it becomes critical. It has to work, and it has to work reliably.”
Systems that matter to the business
At the core of Martin’s work is data – specifically, making sure the business has a reliable and timely view of the market to know what and when to trade. That includes building systems that capture trades, forecasts, and asset status – and reliably distribute that information across the organization.
On the surface, it can sound simple. In practice, it’s anything but.
“If we don’t have a clear view of what we’ve traded, then we’re basically flying blind. So even if the solution itself is just moving data from one place to another, it becomes critical. It has to work, and it has to work reliably.”
Alongside that, there are more complex systems where technical execution alone isn’t enough. Pricing tools, for example, require a deep understanding of the underlying business logic – not just the data flowing through them.
“You’re pulling in data from a lot of different sources and trying to produce something meaningful at the other end. But if you don’t understand what goes into that number, then it doesn’t really matter how well you’ve built it technically.”
At the same time, not every problem requires a complex solution.
“There are also tasks where the right answer is something simple. We might use standard tools to automate something instead of building it ourselves. We’re a small team, so we have to be very aware of where we spend our time.”
We rarely get something that’s fully specified. You can’t just pick up a task and start coding. You need to understand what the problem actually is, and that means talking to people, asking questions, and sometimes challenging what’s being asked for.
Knowing when to challenge and when to let go
One project in particular stands out.
Over more than a year, the team built a system designed to handle complex calculations and large volumes of data. From a technical perspective, it worked well. But over time, it became clear that it didn’t solve the right problem.
The team stepped back – and made the call to scrap it.
“We had spent a lot of time on it, and it was a solid solution technically. But when we looked at what the business actually needed, it just wasn’t the right fit. So we ended up throwing it away and building something much simpler instead.”
It wasn’t an easy decision, but it was a necessary one. In a fast-moving business, needs evolve. Scenarios change and teams mature. And the problem-solving has to keep up.
“You can get attached to what you’ve built. But if it doesn’t create the value you expected, then it doesn’t matter. You have to be willing to throw things away – otherwise you end up protecting something that shouldn’t be there.”
That mindset is closely tied to how the team collaborates with the rest of the business.
There’s no clear handover where requirements are defined up front and passed to tech. Instead, most work starts as a dialogue and evolves from there. That requires developers to operate beyond the technical layer.
“We rarely get something that’s fully specified. You can’t just pick up a task and start coding. You need to understand what the problem actually is, and that means talking to people, asking questions, and sometimes challenging what’s being asked for.”
It also changes how responsibility is shared.
“You get input from others, but in the end you’re responsible for the solution. You have to make decisions and move things forward.”
“There’s a very strong technical level across the team, and that shows in how we work. No one just pushes something without someone else looking at it, and there’s always room to challenge a solution if something doesn’t feel right.”
High standards, without the noise
Within the team, expectations are high – but the way they’re enforced is straightforward.
“There’s a very strong technical level across the team, and that shows in how we work. No one just pushes something without someone else looking at it, and there’s always room to challenge a solution if something doesn’t feel right.”
At the same time, the culture isn’t formal or rigid.
“You can disagree, and you can go in a different direction than what others suggest, as long as you’ve listened and thought it through. That balance between input and ownership is important.”
The same applies to feedback more broadly.
“In some places, feedback becomes too soft. You hear that you’re doing well, but you don’t really hear where you can improve. Here, it’s more balanced – you get both. Input providers are close enough to you and your projects to give constructive feedback. And that makes the positive feedback more credible.”
Pragmatism over perfection
Across both systems and collaboration, one principle stands out: pragmatism, as a way to move forward in a complex environment.
“We want to build good solutions, but we also need to get things done. If we can get most of the value with significantly less effort, then that’s often the right decision.”
That approach also reflects the reality outside the company.
“Not everything we integrate with is modern. Sometimes the solution is as simple as handling an email instead of building a full integration. That’s just how it is, and you have to adapt to that.”
For Martin, the defining factor isn’t a specific technology or system. It’s the way people work together to build them.
“You can build technically impressive solutions in a lot of places. But if they don’t solve the right problem, then it doesn’t matter. What makes the difference here is that we stay close to the problem and work together to get it right.”