Experience
I’ve worked in software for twenty-five years, from writing the code myself to owning entire deliveries. Here’s a selection of that work and what it led to.
2025 – now
A small team with AI as a colleague
Co-founder and developer · VeliSpec
- Situation
- A brand-new product company setting out to build a CPQ tool, with AI on the team from day one.
- What I did
- We built a way of working where people and AI share rules, tools and memory in git. On top of that came a deterministic risk engine that scores every PR, our own CI runners and automated reviews before code is pushed.
- Result
- July to October 2026: an average of more than 11 merged PRs per working day. All with the equivalent of two developers working half-time.
2026 – now
One way of working across some 20 client projects
Tech lead, responsible for ways of working · Indpro
- Situation
- Some 20 client projects with tools and rules that varied from team to team, and issues tracked in Jira.
- What I did
- Moved all issue tracking from Jira to GitHub and set up shared rulesets, project board templates and new project lead roles. Automated the flow around issues, boards and PRs: every issue is linked to a PR and checked against its goals, partly with AI. Screenful tracks lead and cycle time per project and across the organisation, and we introduced time reporting with automatic budget alerts in Teams.
- Result
- Every team works the same way and work can be traced from issue to code. Issues that sit too long in one state show up straight away, so we can step in and help.
2025 – 2026
Laying the foundation for an energy analysis app
Frontend architect · Energenius
- Situation
- A new energy analysis app that needed a solid foundation.
- What I did
- Built the frontend architecture in Vue, including dynamic forms, and helped with deployment, observability and ways of working.
- Result
- Other developers use it and build on it today.
2025
A loyalty platform in India
Consultant · BigCity Promotions, Bengaluru (via Indpro)
Worked directly with BigCity Promotions to modernise their loyalty platform and the ways of working around it.
2013 – 2025
Along for the ride from 3 to almost 50 developers
Consultant, frontend coordinator and Engineering Manager · iBinder Group
- Situation
- A small company with a handful of developers wearing many hats, and growing pains once business took off.
- What I did
- Helped build structure and ways of working, plus a new platform from scratch with microservices and independent frontends. As Engineering Manager I led a team of six developers and shaped our Lean processes with the COO and CTO.
- Result
- The development organisation grew from 3 to almost 50 people and averaged 3.5 production changes per working day. Over the same period, revenue went from about SEK 23 million to several hundred million.
2001 – 2013
Twelve years in energy
Through Scimus I built bespoke systems for the energy sector. Together with Energivision we worked for clients including Vattenfall, Fortum, E.ON, Dinel and Bixia.
Toolbox
- Frontend
- React
- TypeScript
- Vue
- Svelte
- Next.js
- Tailwind CSS
- Micro-frontends
- Backend
- Node.js (NestJS, Fastify)
- .NET / C#
- MS SQL Server
- MongoDB
- PostgreSQL
- Redis
- Cloud, build and operations
- Azure
- AWS
- Docker
- GitHub Actions
- Bun (package management)
- CI/CD
- Quality and observability
- Vitest
- Playwright
- Storybook
- Sentry
- Application Insights
- Planning and tracking
- GitHub (Issues, Projects)
Screenful- DORA metrics
- Ways of working
- Lean
- Kanban
- Trunk-based development
- Feature flags
ConfigCat- AI-assisted development
- Claude
- Deterministic automation with AI
- Localisation