My Work

Work Profiles

While I work on various topics and technologies, most of the time I tend to work on these main areas:

Server/API Developer: ​ Development of NodeJS, Java or .NET API services which communicate with storage systems or other APIs. Quite often also includes security work such as SSO systems, JWT, Authentication/Authorization and general HTTP-related security topics.

Web Developer: ​ Development of browser-based (single page) applications usually with, React or

Devops/Infrastructure Engineer: ​ Development of CI/CD concepts with Gitlab-CI or Jenkins. Management of cloud/infrastructure services (usually Azure or AWS) with Ansible or Terraform (or the cloud provider console). Often also responsible for development environment setups, for example: git repository layouts, scripts and developer tooling.


I am the owner of my own company called Frostwoods. Frostwoods provides software development and consultation on various levels in addition to creating its own products, such as Journeys API

I am working as CTO at Exerium. Working on still unpublished stuff. =)

ITS Factory / City of Tampere
I am currently technical responsible of including
– virtual server infrastructure management, currently containing approx. 15 servers
– API development
– techincal management, design and consulting
I also work on the ITS Factory development support.

Nokia / Nokia Networks / Nokia Siemens Networks (1999 – 2012)
My first official job was at Nokia between 1999 – 2012. At Nokia I worked on various positions such as: testing engineer, project manager, product owner, developer and software architect. My latest work at Nokia were on software architecture and Big Data.

I have also participated in various projects in- and outside of my work related efforts. A list of the public ones (the ones that are not private) is here: (retired/on hiatus)
I was the lead developer on service. The service provided bus schedules and route maps for Public Transport passengers. Schedules and maps can be downloaded from Schedules are based on location data collected from the public transport network: the actual bus stop times (at given stop) are recorded and those measurements are used to calculate bus stop times as they occurred in the history for each bus stop. In addition to the schedules, the service calculates expected wait times for each bus stop, based on how well buses reached the stop in the history.

Leave a Reply

Your email address will not be published.