Backend / Full-Stack Software Engineer with strong systems and reliability depth.
Based in Copenhagen, I build software for environments where correctness, reproducibility, and operational clarity matter.
My background includes backend and full-stack development, internal platforms, simulation services, system-level testing, secure Linux administration, and automation architecture. I have spent years working in environments where software meets infrastructure, hardware, and operational constraints, which shaped how I design systems: clear contracts, low ambiguity, and software that is easier to reason about under pressure.
I do not define myself by one language. My leverage is in architecture, patterns, and system design, which lets me move across stacks without losing engineering clarity. A wide stack is one of my strengths, not because breadth looks good on paper, but because it is how I learn new technologies quickly and apply them with intent.
- Backend services and internal tools
- Full-stack applications with strong operational constraints
- Simulation and integration-heavy systems
- Secure Linux administration and platform workflows
- Testable architectures and deterministic environments
Most of my commercial work is in private repositories, so this profile is intentionally closer to an engineering portfolio than a public code index.
Recent and representative work includes:
- building internal web administration tooling for Linux-based systems in regulated maritime environments
- developing microservices that emulate physical devices and interfaces, reducing hardware dependency in validation workflows
- designing hardware-in-the-loop infrastructure with Raspberry Pi and industrial interfaces for reproducible system testing
- improving lab and network setup for remote access, lower operational friction, and better system observability
- restructuring automation and validation flows so failures become easier to reproduce, diagnose, and trust
A lightweight, secure self-hosted platform project for Linux and ZFS built around modular, event-driven services.
It focuses on configuration validation, security-oriented defaults, and operational clarity for home lab and self-hosted environments. The architecture direction is service-based and extensible, with clear boundaries between infrastructure, messaging, and interface layers.
Links: Repo · Public app intentionally not exposed.
A published Python package and cross-platform testing framework built around reusable abstractions rather than tool-specific scripts.
It unifies web, mobile, desktop, API, CLI, and visual testing behind a consistent programming model. I treat it as evidence of architectural thinking, API design, and framework engineering, not just automation experience.
A backend/full-stack project skeleton created for a volunteer teaching program.
It was designed to stay production-credible without becoming overengineered for learners: realistic project structure, migrations, API documentation, deployment guidance, and clear backend boundaries, while keeping the implementation simple enough to be teachable and usable by developers still building confidence.
The project is tied to a structured program flow: weekly sprint planning, explicit requirements, and concrete delivery artifacts (deployed API, docs, ERD, and Postman collection).
Links: Skeleton Repo · API README · Program Plan · Requirements
A learning-driven monorepo used to get productive in an unfamiliar stack without lowering engineering standards.
It combines a Scala 3 backend with a React/TypeScript frontend and focuses on clear structure, migrations, auth flows, GraphQL/REST boundaries, and explicit quality gates. The point of the project is not just learning syntax, but proving I can enter a new stack and still work with architectural discipline.
Reproducibility over guesswork.
Clear interfaces over accidental complexity.
Simulation when it removes ambiguity.
Architecture should fit the problem and the people working on it.
I am positioning myself primarily around backend and full-stack software engineering.
My SDET and systems background is still central to how I work, but I treat it as a differentiator, not the headline. The value is not only test automation. It is the ability to design software and environments that are observable, maintainable, and trustworthy.