Professional thread · product engineering · interaction

Experience

My work has moved from graphic design, audiovisual production and teaching into public-facing web applications and increasingly deep product/system engineering. The useful continuity is not a list of technologies; it is the ability to connect how a system works with how a person understands and controls it.

Current focus
Product and systems engineering
Core strengths
React · TypeScript · Rust · interaction architecture
Background
Design · multimedia · public-service software · education
Region
Professional history in Malmö / Skåne, Sweden

IKEA planning tools

Large planning interfaces are not ordinary forms: they combine constrained product configuration, visual feedback, business rules, accessibility and long-lived interaction state.

Public LinkedIn material from a close collaborator documents work on the significant rebuilding of the IKEA Kitchen Planner and the creation of IKEA's Planner tooling, with modern React, TypeScript and web accessibility as important parts of the engineering approach.

The work fits the same pattern visible in my independent systems today: make complex state understandable, preserve clear ownership of behavior, and treat accessibility as part of the product model rather than a final compliance pass.

Product complexity

Configuration tools have many valid and invalid states, and need to communicate constraints without turning the interface into documentation.

Accessibility as engineering

Interaction semantics, keyboard behavior, focus, structure and state communication have to be designed into the system rather than overlaid afterward.

Länsstyrelsen Skåne

My public-service application work in Skåne connected frontend engineering with a real physical place and the practical needs of visitors.

Historical public profiles identify my role as Front-End JavaScript Application Developer at the County Administrative Board of Skåne. The clearest surviving product evidence is the Kullaberg family of applications for Naturum Kullaberg: bilingual trail information, offline-capable visitor guidance, maps, GPS-linked points of interest and later citizen-science concepts.

The product constraints were concrete: mobile visitors, variable connectivity, institutional visual standards, outdoor use, bilingual content and a need to bridge digital information with physical navigation rather than keep users trapped inside an app.

Design & media foundation

Before software engineering became the center of my work, I already worked across interaction, visual communication, audiovisual production and technical delivery.

An older public professional profile records experience as Owner & Multimedia Producer at 2Active Design and as Graphic Design Department Chair & University Professor at Central American Technological University in Honduras. It also describes work spanning digital signage, web applications and digital media broadcasting.

That background still affects how I build software. I tend to treat typography, motion, sound, information hierarchy and user feedback as parts of system behavior, not as decoration applied after implementation.

Teaching sharpens architecture

Explaining a system exposes vague concepts quickly. Documentation, naming and model boundaries benefit from the same discipline.

Design literacy changes implementation

Visual hierarchy, interaction feedback and motion are easier to build well when they are considered constraints of the component/system model from the beginning.

How the work evolved

The trajectory is from designing surfaces, to designing interactions, to designing the systems that make those interactions trustworthy.

Current projects go deeper into deterministic simulation, playback authority, native capabilities, firmware and graph-based knowledge systems, but the underlying product question is similar: what is the user's mental model, what state is actually authoritative, and how can the interface make that model visible without overwhelming them?

This is why I position myself as a software engineer who works comfortably across product, interaction and systems boundaries rather than as a narrowly defined frontend specialist.