SOFTWARE ENGINEERING · PLATFORM · PRODUCTION

I own technical delivery from application and backend to infrastructure and production.

I design and develop web systems, APIs, data flows, integrations, and delivery infrastructure. I can own a focused engineering area or take responsibility from requirement to working release.

Production experience, not just a technology list.

My professional path has moved through Linux and cloud infrastructure, SRE/reliability, platform/DevOps, and backend/product systems.

  1. Linux / Cloud

    UpCloud Oy

    07.2021–12.2022

  2. SRE / Reliability

    Aiven Oy

    01.2023–05.2024

  3. Platform / DevOps

    n8n GmbH

    06.2024–03.2026

  4. Backend / Product Systems

    Independent Work

    2026–Present

View experience

Engineering capabilities

Four areas of technical responsibility.

Select a node · connections & practice

SYSTEM OVERVIEW

From user to production

Each layer connects an engineering situation, tools and verified practice. Select a layer to inspect those connections.

Hover or focus to preview. Click to keep the selection. Click again or press Escape to clear.Tap a node to explore its connections. Tap it again to clear the selection.

01

Product / Full-Stack Engineering

Interfaces and applications for customers, teams, and internal operations — connected to real data, backend logic, and user flows.

A working product, not an isolated UI.

787 AirClub · Wedding Invitation Platform

React · Next.js · TypeScript

02

Backend & Integrations

APIs, server-side logic, roles and permissions, PostgreSQL, background processes, and external integrations.

Users, data, and external services operate as one workflow.

787 AirClub · n8n

Node.js · PostgreSQL · REST API

03

DevOps / SRE

CI/CD, deployment, observability, health checks, troubleshooting, rollout, and production reliability.

Changes can be released and diagnosed predictably.

Aiven · n8n

CI/CD · Terraform · Observability

04

Platform & Infrastructure

Linux, containers, networking, reverse proxies, PostgreSQL/Redis, environments, backups, and recovery.

The system has an understandable and maintainable production environment.

UpCloud · n8n

Linux · Kubernetes · Docker

Where I can help technically.

  1. 01PRODUCT

    A web application needs to be designed or taken into production.

  2. 02INCIDENT

    A backend or API is unstable and needs systematic diagnosis.

  3. 03DEPENDENCY

    Services, databases, or integrations are not communicating predictably.

  4. 04DELIVERY

    Deployment depends on manual steps or behaves differently across environments.

  5. 05OBSERVABILITY

    The system needs observability, health checks, backups, and a clear recovery path.

  6. 06ARCHITECTURE

    A prototype has grown into a product and now needs a more resilient architecture.

No selection

Technical evidence

Projects where the interface is part of the system.

787 AirClub brings together roles, lifecycle, backend, data, operations, and production. Wedding Platform combines product UX, data management, integrations, and full-stack delivery.

Operational Full Stack Platform

01

787 AirClub — Airport Transfer Operations Platform

An operational web/PWA platform connecting passenger, driver, dispatcher, and administrator roles, trip lifecycle, pricing rules, finance, notifications, and production delivery.

ResponsibilityProduct · Frontend · Backend · Data · Production

  • Passenger and driver flows
  • Dispatcher and admin operations
  • Ride lifecycle and assignment
  • Zones and pricing rules
Explore case study
787 AirClub synthetic driver dashboard
Guest experiencePrivacy-reviewed selection
Desktop guest navigation across the wedding platform sections01 · Desktop guide

Full Stack Platform

02

Wedding Invitation Platform

A full-stack personalised invitation platform with guest experience, RSVP, guest management, administration, data, integrations, and production deployment.

Core features

  • Personal pages
  • RSVP
  • Guest management
  • Administration boundary
Explore case study

System architecture

I separate the layers, but take responsibility for how they connect.

The interface, application layer, data, integrations, infrastructure, and delivery need to be designed as parts of one system.

System architecture

One connected delivery scope

From the first user action to data, integrations, and production infrastructure.

Request → rules → data & integrations

ResponsibilityEnd-to-end delivery

05 · Technology system

Tools follow the architecture, not the other way around.

Tools used in the documented projects, grouped by interface, application, data, infrastructure, and delivery.

Interface

What users see and interact with.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • responsive UI
  • PWA

requests

Application

Server-side logic, permissions, calculations and business workflows.

  • Node.js
  • NestJS
  • REST API
  • Socket.IO
  • JWT
  • RBAC
  • validation
  • business workflows

logic

Data

Storage, relationships, integrity and data processing.

  • PostgreSQL
  • Prisma
  • Redis
  • Neon
  • Supabase
  • migrations
  • data modelling

persistence

Infrastructure

The environment in which the system operates.

  • Linux
  • Docker
  • Docker Compose
  • Nginx
  • VPS
  • HTTPS
  • backups
  • monitoring

runtime

Delivery

How changes are validated and released to production.

  • Git
  • GitHub
  • GitHub Actions
  • CI/CD
  • Vercel
  • Render
  • build validation
  • deployment
  • diagnostics

release

Experience and responsibility

My career has progressively expanded the scope I can own.

Linux / Cloud → SRE / Reliability → Platform / DevOps → Backend / Product Systems

View experience

Have a technical problem or production issue?

Describe what should be working and where the problem currently appears. We can start from current system behaviour, architecture, or requirements for a new implementation.

Discuss the technical problem