Fredrik Johansson

• Understanding a legacy codebase and finding ways to start delivering solutions swiftly, while navigating the classic "we've always done it this way" territory translation: no one knows why it works
• Modernizing legacy systems piece by piece without breaking production (mostly)
• Building new features on top of old foundations and hoping the whole thing doesn't collapse

Multi-client consulting across diverse technical stacks and business domains, delivering front-end/back-end solutions, API integrations, and production systems under tight deadlines. Tight deadlines = "we needed this yesterday"

• QlikTech — Built custom documentation pipeline converting proprietary XML to HTML, replacing an unusable MadCap Flare output for a large technical documentation suite. Learned more about XSLT than anyone should.
• LinkMobility — Built digital loyalty card platform end-to-end (UI, API, database) serving thousands of end users. Integrated payment providers (they all claim to be "simple" — they're all lying) and made it work on mobile devices of questionable vintage.
• Tunstall — Healthcare planning and reporting systems where "it works on my machine" isn't an acceptable answer. Fixed critical bugs, added features, and kept the code clean and neat.
• Avensia — A natural fit, since they also built e-commerce and integrated with Microsoft Dynamics NAV and other product catalogue software.

• Built websites, intranets, and e-commerce platforms using our in-house CMS. Started with VBScript/JScript (yes, really), then .NET as we slowly dragged ourselves into the modern era.
• Talked to clients about what they actually needed versus what they thought they needed. Usually very different things.

• Led dev team building custom CMS, e-commerce, and corporate intranets. Discovered that "Chief of Development" means you get blamed when things break.
• Established coding standards and workflows (got pushback), implemented QA processes (got more pushback), eventually convinced team these were good ideas (mostly).

• Built web apps and provided tech support. Learned that "it's probably user error" is never the right thing to say to customers, even when it's true.

• Built websites when "cross-browser compatibility" meant testing in Netscape 4, IE 4, and praying. Made things work with tables for layout (we didn't know better), inline styles (we really didn't know better), and JavaScript that broke if you looked at it wrong.
• Helped establish what would eventually become best practices, though at the time we were mostly just figuring out what didn't catch fire.

Built an e-commerce platform after another company went bankrupt and left their clients stranded. Nothing motivates quite like angry business owners who can't sell things. Kanban boards were involved. So. Many. Kanban. Boards.

• Real-time ERP integration: Built bidirectional sync with Microsoft Dynamics NAV. Made inventory, pricing, and customer data flow reliably between systems that really didn't want to talk to each other — serving multiple B2B clients with thousands of SKUs each.
• Multi-tenant architecture: One codebase serving 10+ clients with different styling, business rules, and feature sets. Sounds simple until you realize everyone wants their own special snowflake features.
• Modular feature system: Component architecture where clients pick features à la carte. Kept it flexible without turning the codebase into unmaintainable spaghetti (mostly).
• Offline-first tablet platform: Trade fair ordering system that works without WiFi — used at live events to process orders that sync back once connectivity is restored, with conflict resolution when multiple reps edit the same customer simultaneously.

Foundation in information systems, database design, systems analysis, and early web technologies during the formative years of commercial internet. Basically learned to make websites before Stack Overflow existed. Dark times.