Senior "Agent Wrangler" at the LEGO Group / Denmark / .NET, cloud, integrations, and agent-shaped workflows
LinkedIn / Stack Overflow / HackerRank / Email
I build software at the point where architecture, product judgment, and hands-on debugging meet. I like the work of making complicated systems legible: the API that finally reads clearly, the integration that stops surprising people, the deployment path that becomes boring in the best possible way.
I have moved between backend engineering, cloud platforms, ecommerce integrations, developer tooling, and engineering leadership. Lately I have also been spending a lot of energy on agent-assisted workflows: not as magic, but as another sharp tool that needs taste, constraints, and a human who still knows where the dragons are.
| Area | What that usually means |
|---|---|
| Backend systems | .NET, C#, API design, integrations, data flows, reliability |
| Frontend and product | Blazor, React, Svelte, TypeScript, pragmatic UX decisions |
| Cloud and operations | AWS, Azure, Docker, CI/CD, observability, production debugging |
| Agent wrangling | Tooling, prompts, repo harnesses, review loops, and keeping agents useful instead of theatrical |
| Engineering leadership | Architecture clarity, team enablement, technical strategy, mentoring |
| Project | Why it exists | Focus |
|---|---|---|
| RechargeSharp | A .NET client and entity layer for the Recharge Payments API. | Ecommerce integrations |
| QuickPaySharp | A modern .NET client library for the QuickPay API. | Payments |
| WebshipperSharp | A .NET client for integrating with the Webshipper API. | Shipping and logistics |
- Making complex technical organizations easier to understand and improve.
- Building agent-assisted workflows that help software teams move faster without losing judgment.
- Turning operational mess into systems that are observable, maintainable, and calm to run.
- Keeping .NET integrations pleasant for the next developer who has to touch them.
- Take responsibility for the systems I touch, including the human ones.
- Prefer clarity over cleverness, and precise language over comforting fuzziness.
- Build with enough care that the next person feels less alone in the codebase.
- Stay curious, keep learning, and treat good pushback as a gift.
- Stay useful under pressure, and keep the work grounded when things get noisy.
- Make room for gratitude, because software is still built by people.
Daily drivers
Frontend and product work
Cloud, data, and operations
Also in the toolbox
LinkedIn is the best place for professional context. Stack Overflow has the old Q&A trail. Email works when the thing is specific.
If you like calm systems, useful agents, and codebases that are kind to the next person, we will probably get along.