Skip to content

About Me

Hi, I'm Marcus — a fullstack .NET developer based in Stockholm, currently consulting through School of Applied Technology. I build web products where backend structure, frontend usability, and long-term maintainability matter just as much as shipping quickly.

My work is centered around C#/.NET, React, databases, cloud services, and AI integrations that solve real problems rather than just adding novelty. I'm at my best when I get to think across the whole system: domain modeling, APIs, data flow, architecture, UX, and the trade-offs that make a product easier to evolve over time. I care about clean architecture, but only when it creates clarity, reliability, and flexibility in practice.

Before moving into tech, I spent fourteen years working as a train driver at ProTrain, SJ AB, MTR Pendeltågen, and SJ Stockholmståg. That background shaped the way I work: calm under pressure, precise in execution, and highly aware that details matter when the system around you has to keep working. It also taught me responsibility, consistency, and the importance of earning trust through discipline rather than talk.

I also have a background in health science, which strengthened my interest in learning, coaching, and long-term development — both for myself and for others. Taken together, these experiences have made me a developer who values structure, clarity, and quality not as abstract ideals, but as practical tools for building better products and working well in strong teams.

I'm especially interested in .NET consulting, fullstack product development, and teams that care about ownership, thoughtful engineering, and building things the right way.

How I approach the work

  • I prefer systems that are simple to reason about over systems that are clever. Clean architecture usually wins over clever architecture.
  • I take precision seriously — from naming things clearly to writing tests that actually catch regressions.
  • Fourteen years in safety-critical operations left me with a habit of thinking about edge cases before they become incidents.
  • I communicate clearly with teammates and clients. Good code and a good explanation of it are both part of doing the job.