Software & AI Engineer
From electrician, to offshore technology for oil production, to critical infrastructure projects onshore, to AI-driven applications — fifteen years turning hands-on curiosity into systems people depend on.
I've been around technology for about fifteen years, and it started with my hands. I trained as an electrician and earned a Bachelor's in Maritime Electrical Automation, then spent years commissioning systems offshore — wiring panels, chasing faults, and getting equipment running where failure isn't an option. That's where I learned how real systems actually behave.
Curiosity kept pulling me up the stack. From the physical equipment I moved into the software that controls it — subsea production systems, offshore platforms, and critical infrastructure — and from there into full-stack software and, more recently, AI engineering. Today I design, build, and operate LLM-driven systems and web applications end-to-end, and AI tooling is a core part of how I ship.
What ties it all together is simple: I like building things and making them work — not just to a demo, but running in production with real users. Whether it's a control system, a web app, or a side-project game, I want to understand every layer and own the result.
Hands-on industrial discipline paired with modern, AI-augmented software engineering — that's what I bring to a team.
End-to-end web applications — back-end services, data pipelines, APIs, and clean front-ends. I build the whole thing and I run it in production, not just to a demo.
LLM-driven systems built and operated for real use — agents, automation pipelines, and AI-augmented tooling. I use Claude Code daily as a core part of how I design and ship software.
Control software for critical systems — PLC programming, operator screens (HMI/SCADA), and the communication that ties field equipment to the systems above it. Proven on live oil & gas and infrastructure projects.
I run my own production-grade homelab — containers, reverse proxies, CI/CD, monitoring, and layered security with rehearsed backups. The same operational discipline I apply to client systems, applied to my own.
A selection of software and AI systems I've built end-to-end on my own infrastructure. Real users, real traffic, real consequences when something breaks. Each one focuses on the engineering — the architecture and the operational discipline — rather than the specific domain it serves.
A public analytics platform with a server-side parsing pipeline (worker-thread architecture for high-throughput ingestion), normalised relational storage, and a modern web front-end. Runs across four isolated containers — dev + prod per tenant — behind a shared reverse proxy. Built and operated single-handedly.
A computational simulator written in Go with a browser-based UI and a continuous evaluation harness that compares simulator output against real observed data — surfacing discrepancies explicitly rather than papering over them. Multi-class architecture with a shared widget system across simulators.
A self-hosted file-management platform (Go + React) built around a deliberate security model from day one — access control, audit logging, encrypted backups, and regularly rehearsed recovery. Designed so that “self-hosted” is safer than the cloud alternative, not an excuse to be sloppier.
An automation pipeline that pulls live vehicle telemetry into a structured database, then runs scheduled jobs that feed mileage and timesheet entries to downstream business systems. Replaces a recurring monthly manual task entirely — small in scope, real in time saved.
A multi-server environment grown over two years into a small private cloud — 15+ services across web apps, automation, monitoring, and home systems. Standardised deployment pipeline, layered defence-in-depth security, three-tier backups with rehearsed recovery, and a living architecture reference kept like a runbook.
A top-down 3D survival game built in TypeScript on Three.js with an entity-component-system architecture — chunked world streaming, a deterministic simulation core, hundreds of unit tests, and an automated play-testing harness that drives the real game over a debug protocol.
Most repositories are private, but I'm happy to do a code walkthrough or live demo for a serious conversation — just get in touch.
I design, build, and host websites end-to-end — from sites for local businesses to personal portfolios (including this one). I handle the whole stack myself: design, front-end, containerised deployment, reverse proxy, DNS, and hosting on my own infrastructure. Multiple sites live in production.
Software lead for complete subsea control systems on the Symra and Hanz tie-ins (Ivar Aasen). Built the software managing communication between the platform and underwater equipment, operator screens, simulation tools, and integration of valves, flow meters, and hydraulic systems — delivered through factory testing, on-site startup, and into production.
Control software and operator screens for critical infrastructure — a backup water-supply system for Norway's capital, and smart building automation (intelligent lighting and building management) for one of Norway's largest hospital construction projects, Nye SUS in Stavanger.
Modernizing and digitizing control systems on the Valhall offshore platform — upgrading monitoring software and producing safety documentation to Norwegian industry standards.
Bachelor's in Maritime Electrical Automation and certified electrician credentials, followed by hands-on offshore commissioning and startup work. This is where I learned how real, high-stakes systems behave — knowledge I still draw on when building software today.




The curiosity that drives my work doesn't clock out at five. Most of what I know I picked up by building things for myself — which is also the best way I've found to stay sharp.
I make 3D games in my spare time — a survival game in TypeScript on Three.js with a full entity-component-system, deterministic simulation, and hundreds of tests. It's where I get to over-engineer for the fun of it.
My homelab is a small private cloud — servers, containers, monitoring, and rehearsed backups running the same way real production does. If I want to learn something, I stand it up and run it for real.
I like it when everyday tech just works, so I automate it — a smart home I built and version-control myself, and a pipeline that turns my car's telemetry into finished timesheets. Small problems, properly solved.
I'm open to interesting roles and conversations — software engineering, AI engineering, or anything at the intersection of software and the physical world. Drop me a line and I'll get back to you.