Head of Product & Tech
I lead product and engineering as one function. Seventeen years of shipping, from ERP data migrations to running a learning platform used by thousands of professionals.
Product and engineering, one function.
I run product and technology at Videocation, a Norwegian B2B learning company. Product, engineering, architecture, delivery and hiring all sit with me, which means I get to close the loop between what we decide to build and what actually reaches a customer.
I did not start here. My first seven years were ERP: customising Logic Class for Spanish companies, migrating them off legacy accounting systems, and becoming the person who handled the deployments. Deploying Sage CRM on Windows Server was my first real contact with web services. I take things apart to understand how they were made, and I keep asking why until there are no layers left, so one web application was never going to be the end of it.
So in 2015, at 27, I stopped, went to a bootcamp, and rebuilt my career from the bottom. Agency work, then a startup where I became technical lead, then four years at Haufe Group building microservices on Kubernetes. In 2021 I joined Videocation as a full stack engineer and grew through four roles in as many years.
In 2025 I finished a Master's in Digital Product Management at Nuclio Digital School, where our final project was picked as the best of the cohort. But I have always been a product developer at heart, motivated by solving the problem in front of me.
Seventeen years, two careers, one throughline: get close to the problem, then ship.
2008 – 2012 · Education
Engineering foundation. Electrical, electronics and communications. Half the day at the university, the other half at the office, until the degree was finished and the job went full time.
2008 – 2013
Sage (via Servitel)
Started my career customising the Logic Class ERP to customer requirements, then moved onto the migrations team and moved customers off legacy Sage products onto it. Years of hands-on SQL, and where I started doing application deployments.
2013 – 2015
Sage Spain
Moved with my team from the subsidiary into Sage Spain itself. Same technical work, now customer-facing. Deployments became my specialism, on Logic Class and then Sage Murano. Sage CRM was in that set too, an on-premise web app on Windows Server, and my first real work with web services.
2014 · Education
Managing projects and businesses in the 21st century. The first formal push away from waterfall delivery.
2015 · Education
The pivot. Left a stable career as an ERP consultant at a large international software company to start over as a developer. Graduated with a top 5 project at Demo Day.
2015 – 2016
Season
Client projects at a development agency across Ruby on Rails, Drupal and JavaScript. Drupal meant learning PHP from scratch, which I did on the job. I took the operations side too: scripted deployments and provisioning, and fixed production servers when they broke.
2016 – 2017
DenDen
A startup with a mixed team, working hard to find product market fit. I architected the backend and frontend requirements and ran the technical screening for the engineer we hired. Shipped Forbidden City, an augmented reality iOS game built to get people into the shops in their own neighbourhood. The real problem was gamification: how to make the work we needed from users worth doing.
2017 – 2021
Haufe Group
On a team set up to test new business ideas and build out the ones that worked. Two app prototypes in six months, one of which went to production and shipped on both the App Store and Google Play. I owned features end to end, from shaping the idea through to the infrastructure they ran on. Also one of the cultural fit interviewers in the group's hiring process.
2021 – Present
Videocation.no
Four roles in four years at a Norwegian B2B learning company. Today product, engineering, architecture, delivery and hiring all sit with me. I redesigned the SDLC around AI-assisted development, rewrote the Product Engineer job description and the interview that goes with it, and lead the vision for a platform thousands of professionals learn on.
2024 – 2025 · Education
Product strategy, digital business and innovation management. Our final project was selected as the best of the cohort.
Unlearning is the hard part.
Early on I cared a great deal about clean code, patterns and finding the right abstraction, and I got good at it. What took longer was learning when any of it was actually needed. A team can spend weeks improving structure and refactoring: sometimes that is precisely the work, and sometimes it is craft for the satisfaction of doing craft. Seniority, for me, is being able to tell those two apart.
Now that the budget is mine to answer for, the distinction stopped being academic. Time spent on polish nobody will ever notice is time the roadmap does not get. So what I look for is the minimum that does the job properly: as simple as possible, not simpler.
AI is the current version of the same problem. It has changed how I work more in two years than anything did in the ten before it, and the difficult part was never learning the tools. It was being willing to throw out a workflow that still worked. I have had to unlearn about as much as I have learned.
I judge quality by who will feel it.
Leading this is mostly not a matter of telling people. It is pairing on the AI-assisted work, running the experiments on our own workflows first, and handing my own proposals to the engineers to pull apart before any of it becomes how we work. Ideas get the same treatment: the good ones tend to come from a group that has gone and looked properly on their own, then argued it out somewhere it is safe to be wrong.
It helps that I do this at a company that sells learning. Making continuous learning the default is easier when it is also the product.
Deciding what to build and being accountable for it reaching a customer should not be two different jobs. When they are, everyone optimises their half.
I would rather put something real in front of a user this week than something correct on paper in three months. Whatever you got wrong surfaces sooner, and you fix it against reality instead of against an argument.
I take things apart to find out how they were made. The real problem is usually two or three layers under the one you were handed, and you only get there by asking why one more time than feels comfortable.
No feature has a single author. Someone writes it, someone reviews it, someone finds the bug nobody expected. So delivery is attributed to the team rather than to individuals, for the same reason nobody wins a football match on their own.
Let's build something together.
Whether you have a project in mind, want to compare notes on running product and engineering as one function, or just want to say hello, I would like to hear from you.