Experience

Main projects

Larger assignments with role, responsibilities and technologies.

1. Banking Circle

   Period: Feb 2025 – Feb 2026

   Role: Senior backend engineer (hands-on), solution architecture and design

   Senior backend developer in a cross-functional team, responsible for the design, development and operation of event-driven backend services on Azure. I worked with modern .NET-based microservices, the AKS container platform and cloud infrastructure in an enterprise setup with strict requirements for robustness, traceability and operational stability.

   I was responsible for preparing and driving architecture and design proposals for new backend services, including data modelling, persistence and event flows, in close collaboration with the team lead and the other developers.

   Responsibilities and results (7)

   • Design and implementation of a greenfield reconciliation service, including the data model, persistence strategy and event contracts that ensure consistency between databases, Azure Event Hubs and Azure Service Bus.
   • Development of a new event subscriber service based on existing event streams, with a focus on idempotent processing, replay handling and scalability.
   • Migration of backend services from Azure App Services to Azure Kubernetes Service (AKS), including containerisation, Helm-based deployment and adaptation of the runtime configuration.
   • Improved observability and operational stability through health endpoints, distributed tracing with correlation across requests and events, and targeted use of metrics to analyse performance and bottlenecks.
   • Setup and maintenance of CI/CD pipelines for both application code and infrastructure as code, with a focus on reproducible builds and secure deployments.
   • Active knowledge sharing and mentoring in the team, including code reviews (particularly AKS and Terraform) and internal presentations on architecture and design choices.
   • AI-assisted development and review (GitHub Copilot) to speed up feature implementation, refactoring and quality assurance, with a focus on clear design constraints, testability and traceability.

   • C#
   • .NET
   • .NET Core
   • Azure Web App
   • Azure Service Bus
   • Azure Event Hubs
   • Azure Traffic Manager
   • Azure Application Gateway
   • Azure Key Vault
   • Azure Application Insights
   • Azure SQL
   • Azure Functions
   • Kubernetes
   • Helm
   • Terraform
   • Infrastructure as Code
   • YAML
   • Azure DevOps
   • Entity Framework Core

2. Letpension

   Period: Aug 2019 – Jan 2025

   Role: Solution architect, system developer and designer, team lead

   Maintenance and further development of pension advisory systems and of systems for exchanging data with banks, a bank data centre and PFA. Advice on improving workflows around software development and ALM. Implementation and operation of GDPR processes.

   Responsibilities and results (12)

   • Led the work on development and maintainability: optimisations, analysis and removal of dead code, refactoring for better design and testability, refactoring of document code so it could be shared across two technology stacks, and a redesign of the batch area for greater stability and isolation and to support two technology stacks.
   • Strategy for and implementation of automated tests: a reference implementation of BDD and Specification by Example with SpecFlow, with an isolated database instance for each test using DACPAC and SQL Server LocalDB.
   • Led the work on architecture and design: strategy for microservices vs. modular monolith, interface design and SOLID principles.
   • Led the work on databases and data access: resolved long response times and poor concurrency by moving to snapshot isolation and shorter, smaller transactions, analysed and fixed the biggest problems, and worked with batching, eager vs. lazy loading and more.
   • Led the implementation of GDPR processes: deletion processes for a very large database with 500+ tables and 8 TB of data, and interaction with data owners about interfaces and process.
   • Data intelligence: in-depth analyses of data across data sources and formats, data quality assurance and conversion of customer portfolios.
   • Continuous improvement of the development process: management of database changes, the release process and DevOps (Azure DevOps).
   • Cloud strategy: analysis and plan for migration to the cloud, and a proof of concept for applications using Azure Web App, SQL, Service Bus and Functions.
   • Monitoring: implementation of monitoring that gives insight into how the system is used, bottlenecks and other problem areas.
   • Handling of difficult incidents and troubleshooting: took part in the most serious and complex incidents, such as outages or degraded performance, analysing the cause, implementing a fix and identifying longer-term improvements.
   • Stakeholder management: on many of the tasks above I dealt with stakeholders directly, and throughout the period I kept an eye on the business side as well as the technical one.
   • AI-assisted development (GitHub Copilot) for implementing and reviewing features and for quick scripts for data extraction and manipulation, where I largely set the constraints for design, tech stack and quality.

   • C#
   • .NET
   • .NET Core
   • Azure Web App
   • Azure Service Bus
   • Azure SQL
   • Azure Functions
   • Azure DevOps
   • Visual Studio Data Tools
   • SQL Server
   • XML
   • XSD
   • Entity Framework
   • Entity Framework Core
   • SpecFlow

3. Saxo Bank

   Period: Aug 2017 – Aug 2019

   Role: Solution architect, system developer and designer

   Further development and maintenance of OpenAPI, which underpins the SaxoTraderGO and SaxoTraderPRO trading platforms, and the integration with third parties. The focus was on scaling, preparing for cloud enablement and automating the release process.

   Responsibilities and results

   • Architecture and design of a new distributed cache to cope with a growing number of clients. The implementation went into production.
   • Requirements analysis and implementation of new features.
   • Took part in the analysis of how the APIs could be migrated to Azure and .NET Core.

   • C#
   • .NET
   • Redis
   • WCF
   • ProtoBuf
   • Git
   • TFS Build
   • PowerShell
   • ASP.NET Web API
   • Azure

4. Danmarks Nationalbank

   Period: Aug 2016 – Aug 2017

   Role: Solution architect, system developer and designer, team lead

   Further development and maintenance of FIONA, a reporting system. The system handles reporting of economic and financial key figures for both Danmarks Nationalbank and the Danish Financial Supervisory Authority.

   Responsibilities and results

   • Analysis, design and implementation of changes in connection with new regulatory requirements and new legislation. Two production releases for updated schemas from the EBA and EIOPA.
   • Team lead for the outsourcing of operations and development. Specification of processes and knowledge transfer. The team was subsequently self-sufficient and supported the applications without problems.
   • Support and troubleshooting of more complex issues, mainly related to databases and replication.

   • C#
   • .NET 4.5
   • .NET 4.6
   • LINQ
   • SQL Server
   • Transact-SQL
   • Topshelf
   • WCF
   • SOAP
   • SOA
   • TFS
   • Continuous Integration
   • CS-Script
   • XBRL
   • XML
   • XSD
   • MSBuild
   • Confluence

5. Naturstyrelsen

   Period: Oct 2015 – present

   Role: Solution architect, system developer and designer

   Integration between an internal timber inventory system and an external timber measurement system, sScale from Dralle. The people measuring the timber are notified with coordinates as soon as a stack has been hauled out and is ready to be measured.

   Responsibilities and results

   • Gathering requirements in collaboration with the client and other stakeholders.
   • Producing the architecture and design.
   • Implementation, testing and release of the application.

   • C#
   • .NET 4.5
   • SQL Server
   • TDD/BDD
   • SpecFlow
   • Topshelf
   • Subversion
   • TeamCity
   • Continuous Integration
   • NLog
   • Unity
   • Rhino Mocks

6. BankInvest

   Period: Sep 2015 – Jul 2016

   Role: System developer and designer

   Maintenance, extension and new development of various core applications, including applications for maintaining instrument reference data, exchanging data for fee and commission calculation, and an application giving an overview of pricing and allocation keys across funds.

   I also drove an initiative to document and test the functional requirements of existing applications using BDD/SpecFlow, so that the knowledge needed for future maintenance was secured.

   Responsibilities and results

   • A presentation on how BDD/Specification by Example principles could improve the documentation of requirements while making the requirements directly testable.
   • Analysis, documentation and test coverage of a service using these principles, as a kind of reference implementation. Knowledge of the service had been lost because of staff turnover. The solution was then handed over to other developers, who quickly gained enough knowledge to implement new requirements and could be confident that they had not broken existing functionality.
   • Implementation of feature requests.

   • C#
   • .NET 4.5
   • .NET 4.6
   • ASP.NET MVC 5
   • Bootstrap
   • KnockoutJS
   • Oracle
   • LINQ
   • SQL Server
   • SQLite
   • NHibernate
   • TDD/BDD
   • SpecFlow
   • Topshelf
   • WCF
   • SOAP
   • SOA
   • Scrum/agile
   • Subversion
   • TeamCity
   • Continuous Integration
   • log4net
   • StructureMap
   • Rhino Mocks
   • NSubstitute
   • Confluence
   • Jira