Simon Aunér

I joined the BookBeat web team to accelerate the migration of the old React web platform to a new platform using Next.js. BookBeat was at the time also transitioning to a new graphical identity and I took responsibility to implement that in our own in-house component-library, visualized in Storybook. As such I worked with setting up a build and publish pipeline to consume it as an internal NPM package. I worked closely with UX and design to establish a design system that works for the brand, and for developers to deliver functionality in a rapid pace. I also migrated the entire new project pipeline from CircleCI to Azure Pipelines, and switched the logging to New Relic so that we had the possibility to trace calls through the entire stack. This aligned the frontend projects with the rest of the company.

I continued to work with the Content team after the actual team lead came back from parental leave, and took on the tech lead responsibility for the Content Controlling sub-team. The Content Controlling team is responsible for services regarding pricing of content, reporting and a Publisher Portal web page. It was my responsibility to plan and organize tasks for the team, collaborate with other parts of the company to bring out the best of our service. The biggest achievent during this time was that we migrated a complex .NET micro-service DB from Azure Table Storage to RavenDB to create more headroom for increased data traffic, better performance and a better feature-set. It was a complicated maneouver that took time to plan and execute but we managed to transition with zero downtime and a gradual shift in traffic while maintaining both DB:s live. During this time I also migrated the frontend web from Redux/MobX to Redux Toolkit Query, and from an old internal UI library to Ant Design - also updating everything around build-tooling and deployments for the front-end application.

The Content dev team's team lead went on parental leave so I joined the team as interim team-lead. As this was about the same time as COVID-19 hit Stockholm a big focus point for me was to keep our working process smooth and efficicent during the shift to remote work. Most of my time was spent as back-end developer, continuing to improve the process and system support for everything BookBeat did with regards to content - ingestion, curation, reporting. The team's responsiblity consisted of about ten .NET microservices and two React web sites, and a team of five developers. We handled everything from requirements specification, design, development, deployment, monitoring and logging.

BookBeat's Marketing development team needed senior experience to design and deliver a Campaign Engine to empower the Marketing Team with a flexible and customizible software where they could tailor different offers to customers depending on where they are in the customer journey and other traits. I used my previous experience from Mr Green and took the responsibility of defining the feature set along with business stakeholders. I helped design and implement the Campaign Engine and it was launched in time for a large cooperation with a significant new business partner.

I joined the Engineering team at BookBeat, which was reponsible of the developer experience and overall quality of the back-end platform. I migrated several microservices from .NET and EF 6 to .NET Core and EF Core, then did R&D for making them run on Linux, and subsequently helped out launching everything on Azure Kubernetes services. I also researched and implemented the boilerplate for moving all .NET services from TeamCity to Azure Pipelines, which also was a stepping stone towards building containers.

I got the chance to work in the Gametek management team as a technical program manager. My responsibilities were to plan how to advance the technical platform together with the chief architect, tech leads and product owners in the organization, to make sure that we could meet future business demands while delivering a technologically top-of-the-line platform.

I joined Mr Green Technology as an employee and front-end lead developer. During these years Mr Green transitioned their entire stack from the old .NET service-side rendered web to an AngluarJS web backed with a REST API. I took on the role of lead front-end developer, being responsible for delivering this new SPA mobile-first web. In this position I focused a lot on making the delivery process fast - focusing on testing, code quality and code reusability. We worked with two brands at the same time so all components were made to be re-usable and configurable so that different brands could cherry-pick the features that they wanted on their web page. The complexity with multiple brands, multiple features and multiple market configurations was a big challenge. I was responsible for recruitment, planning and the technical quality of the team, which at most consisted of around ten developers.

After parental leave I joined Mr Green Technology as a frontend developer. I worked with both the front-end and back-end for the mobile web, at the time in .NET and jQuery. Shortly after, I was hand-picked to a new team spear-heading a new SPA frontend that was to replace both the desktop and mobile web pages.

Net Entertainment is a highly successful gambling company, at the time around 150 employees in the tech department. In 2011 all of NetEnt's games were based on Flash, but mobile gaming was growing fast and it was clear that Flash was never going to work on iPhones, thus NetEnt set out to find a replacement to keep an attractive offering. I was hired as a consultant and took the role of lead developer for a new JavaScript gaming team. I created the game framework architecture for the gaming client which was based on rendering with CSS3 animations and HTML5 audio elements, both of which were highly experimental at the time. I continued to take on a team lead role with hiring and setting up more gaming teams, over time taking the role as scrum master and project manager for all JavaScript game releases, being responsible for planning the releases and making sure the teams delivered on time and with quality, while at the same time expanding and enhancing the gaming framework to support future games and features.