Full Stack Developer

While being part of the regular development process, Fredrik also supported the team by advising and coaching on observability, test automation and continuous delivery.

Product Owner

Fredrik was responsible for conceptualizing, scoping, and planning new features for the customer portal in close collaboration with management, other Product Owners, and his team. In this fast-paced environment, it was essential to provide management and other POs with estimates, risk evaluations, and potential opportunities to support the development of related products. Fredrik also took on the task of translating external requirements into user stories for the development team to work on.

Team / Tech Lead

Fredrik's primary responsibility as a tech lead was to support and enable the team and each developer to perform and deliver at a high level. The role also involved close collaboration with the Product Owner during the conception phase and ensuring clear communication of expectations to the development team, as well as providing realistic evaluations to the product department and management. Additionally, Fredrik was responsible for ensuring that while product goals were met, tech debt remained low, and we addressed technical excellence topics such as disaster recovery, observability, and metrics.

Engineering Manager

Fredrik's main focus as an engineering manager was to support the company and the team in building a fast, scalable, reliable, and maintainable solution from scratch for the trade-in process at dealerships. This included being involved in and driving decision-making from high- to low-level topics related to the application, such as selecting technologies, choosing services, and establishing team processes. Fredrik supported the head of product and engineering in designing solutions for the broader IT landscape. He also took on the role of mentor and coach and was closely involved in the hiring process.

Tech Lead & Full Stack Developer

The team faced several challenges during the project. Fredrik worked on various tasks including cookie consent management, traffic migration, and setting up company-wide test systems. His most significant contribution was introducing monitoring and alerting, which added transparency and uncovered previously unknown bugs across the platform. Additionally, Fredrik designed and implemented a permission management module for easy and extensible permission checks across micro-frontends. He also improved the team's efficiency by enhancing agile processes, introducing quality gates, and focusing on clear acceptance criteria and collective alignment. These efforts significantly improved the team's performance and inspired other teams to review their processes.

Full Stack Developer

Fredrik joined the team responsible for core frontend and backend components. His main task was to support the development of Java-based microservices using Vert.X, as well as Angular components. During his time there, Fredrik noticed the lack of tests and worked to raise awareness and coach the team on the importance of testing to mitigate future issues.

DevOps

A new team called Developer Experience was formed to improve the speed and quality of development across all other teams. During his time there, Fredrik developed concepts for easy application testing with Cypress, introduced Helm to facilitate reproducible deployments in an OpenShift environment, and helped set up SonarQube and Snyk to enhance code quality. He also implemented several Golang-based Prometheus exporters, a custom Usabilla-Jira connector using Kotlin, Quarkus, and GraalVM, and a secure method for handling secrets in microservices with HashiCorp Vault. To promote these tools and processes, Fredrik wrote documentation, blog posts, and conducted lightning talks. He occasionally joined other teams to assist them in adopting new concepts and tools.

Full Stack Developer & Architect

Fredrik was part of the in-store administration application team. Using Scrum, he participated in defining stories, implementation, and quality assurance. Over time, he became a central point of information for both team members and external stakeholders. During his time on the project, Fredrik focused on stabilizing the Selenium test suite by creating a robust framework and automating its execution on the build server. Fredrik was also part of a special task force addressing performance issues in the application. He helped identify several pain points affecting performance, leading to action points that improved performance by up to 80%.

Fredrik was selected for a strategically important project in 2017: internationalization. Together with another developer and a product owner, he helped form a new team to prepare the application for multiple countries. They tackled challenges like country-specific product portfolios, localization, logistics, and unique features. As the technical team lead, Fredrik guided the team throughout the project. After two years of focusing almost exclusively on features, the monolithic backend became difficult to maintain and extend due to poor architectural choices. Fredrik was part of a select group tasked with modularizing the backend, beginning with the extraction of the employee management system into a separate module. Fredrik also optimized the build pipeline by reducing dependency on TeamCity through a build script, making it executable on any operating system. Additionally, he built a customized build monitor to provide teams with essential information.

Master Thesis Student

At the time the company mostly developed their software using C, but started to glance at other, more modern, languages. The purpose of the thesis was to investigate the challenges of introducing Go as the main language for development of their software. Because the standard compiler for Go did not support the architecture in many companies products, the Go front-end to GCC (GNU Compiler Collection) was also to be investigated.

The conclusion was that go is really easy to learn, it has great support for writing concurrent software, build tools (in comparison to C) are far easier and the builds are fast. Go also has a built-in package manager which makes it very easy to make use of third party libraries. However, the Go front-end to GCC was complicated to get to work in combination with the specific architecture that Axis is using.