About

About Thomas Bonderup

I'm a software engineer based in Aalborg, Denmark. I work on backend services, integrations, and connected devices, with experience in energy platforms and distributed systems.

I have an MSc in Computer Science and Informatics. Alongside my professional work, I build independent IoT and security tools.

Aalborg, Denmark · Danish & English · Remote & on-site

My background

Backend development

C#/.NET and PostgreSQL for energy platforms, with work spanning APIs, databases, and integrations.

Connected systems

Gateways, telemetry, and device communication, alongside experience in distributed systems and secure software.

Independent projects

IoT security reviews, certificate management, and gateway software built with Rust, Java, and Scala.

Thomas Bonderup

My background spans backend development, distributed systems, secure software, and data platforms.

My master's thesis explored digital twin modeling and streaming telemetry for peak shaving in virtual power plants. It brought together my interests in energy systems, data processing, and connected devices.

My professional experience includes telecommunications, secure messaging, and energy technology. In my current role, I develop backend services and integrations using C#/.NET and PostgreSQL, including communication with connected energy devices.

Technical focus

  • Software architecture and modernization
  • Failure handling, monitoring, and debugging
  • Device identity and secure communication
  • Backend services and system integrations

Working style

  • Explain the options and their tradeoffs
  • Work through implementation, testing, and deployment
  • Document decisions and share technical context
  • Collaborate remotely and on-site

Approach

How I approach software development

I start by understanding how data moves through a system, which components own it, and what happens when a dependency fails. Those questions help me identify where a change is needed.

I have worked in both product teams and client projects. In either setting, I want to understand the existing code and the people using it before proposing a solution.

I look for changes that are straightforward to test, deploy, and maintain. That includes useful logs, clear interfaces, and a way to check whether the change solved the problem.

I discuss concerns directly and explain the alternatives. I'd rather make a decision with the team than leave an important assumption unstated.

Education and experience

From computer science to software development

My studies covered software architecture, distributed systems, secure programming, and machine learning. Academic projects gave me experience with streaming data, digital twins, and deep learning before I applied those ideas in further software work.

I'm interested in how design choices affect day-to-day development: how easily a team can diagnose a failure, change a service, or add a new device.

Working together

How I work with a team

I work with other engineers and the people responsible for the product to understand requirements, discuss design options, and agree on what to build next.

I prefer small changes that can be reviewed and tested. I share progress, document decisions, and raise problems when they appear.

Working on product and client projects has taught me to explain technical choices to people with different backgrounds and to keep track of changing requirements.

For an example of the design decisions behind one of my projects, read the Rust IoT gateway article.

Projects

Selected work

Projects in IoT, backend development, and data processing.

Questions about a project? Get in touch.

View all projects →

Get in touch

Have a question about my work, a job opportunity, or a project you would like to discuss? Feel free to reach out.