About Me
When I was a kid, I got a watch through Fantomen, a comic magazine my father subscribed to. I took it up to the hill nearby, with a hammer, and broke it open. I did not dislike the watch. I just wanted to see what was inside and understand how it worked. I wear a different watch today. That part of me has not changed.
The same thing happens when I work with software. Getting a feature to work is not really the goal. I want to understand why it works, how the parts depend on each other, what assumptions are baked in, and what happens when something goes wrong. I find myself thinking about domain models, data flows, API contracts, and whether the decisions being made today will make things easier or harder to work with later.
I am a fullstack .NET developer based in Stockholm. I work mainly with C#, .NET, ASP.NET Core, React, TypeScript, PostgreSQL, and Azure, and I have a Microsoft Certified: Azure Fundamentals (AZ-900). I am currently deepening my knowledge in cloud, architecture, and security. I use AI in my work, including Azure OpenAI in a few projects, but I do not want to use it as a substitute for understanding what the system is actually doing.
Before switching to software I spent fourteen years as a train driver, at ProTrain, SJ AB, MTR Pendeltågen, and SJ Stockholmståg. Several of those years I worked as a driving instructor too. Working in safety-critical operations for that long does something to how you approach problems. You get used to staying calm when things go sideways, to thinking about consequences before you act, and to taking your part of a system seriously. Teaching new drivers meant I also had to get good at explaining complex procedures clearly and figuring out how to reach people with different backgrounds.
I have a bachelor's degree in sports science and health pedagogy from GIH, and I worked as a personal trainer before I moved into development. I spent a lot of time helping people make progress they had not managed to make before, which I found genuinely interesting. Understanding what actually blocks someone, and helping them past it, is something I still enjoy.
People around me tend to ask for help with things I happen to know, whether that is technology, training, or learning something new. I like it when someone goes from being confused about something to actually understanding it. That has been a recurring pattern in my life, and I think it will carry over into how I work as a developer.
What I am looking for is a role where I can build real software and work with developers who are better than me. I want to keep growing in backend, fullstack, cloud, and eventually architecture. A team that thinks carefully about technical decisions and can explain the reasoning behind them is the kind of team I want to be part of.
How I think about the work
- Architecture should make a system easier to understand, not harder. Clean structure matters only when it serves the people working in the code.
- Naming, testing, and structure are not optional. Small things accumulate, and readable code is a form of communication.
- Fourteen years in safety-critical operations gave me a habit of thinking about edge cases before they become incidents, and of understanding root causes rather than treating symptoms.
- Technical decisions should be explainable. Good engineering and a clear explanation of it are both part of the job.
