Work History

A list of work experiences related to Software development, with details of the work done.

  • May 2024 - Present

    Junior Software Developer

    Kreditz AB @ Stockholm

    After my internship, I was hired as a full time Software developer. I was put on a new project(or rather, I was put on it a few months prior, during my internship, but it extended beyond that). The project was a service which had to handle a lot of different API flows to different external providers, which all were different to each other. This made me develop a configuration-based system which allowed us to easily implement additional APIs against these providers. The configuration lets you define a main type of flow, and configure all of the steps and set up the provider in a matter of minutes compared to writing new code for them. It also required the use of meta programming, where it will read specific static variables from the configuration and execute code to get dynamic values. This allows us to be very dynamic in the code. Beyond my direct contribution to the project, I was also put in a Lead developer role for this, where I work together with my team to push forward what needs to be done, deligate tickets, and assure the quality of the code is up to standard.

  • October 2023 - April 2024

    Intern Software Developer

    Kreditz AB @ Stockholm

    I was taken in as an intern at Kreditz. The initial month was supposed to be dedicated to learning the stack which we use(React, and Ruby On Rails) and going through several courses, however I was able to finish the courses in a week. After that I was put to work on our main products. The highlights of my work was implementation of a feature to be able to dynamically create, update, and remove banners which displayed on our website and product, using an easy to use UI through our Admin panel. Afterwards I got to work on a Status view against all banks which we connect to. The gist was to have a view which showed both the status of banks over a longer period, but to also alert of any ongoing issues. The view is used by the team to help monitor any issues. Due to the sheer amount of banks, variables, and not so clear ability to verify whenever there is any issues, the project took a lot of work with optimization and had a lot of levers implemented. The last major project I worked on before my internship ended was an update to our Audit logs, which similar to the previous project, had a lot of room for optimization. The project required to both display a table of users and their logs, which was sorted in different tables due to the different kind of users(Normal users, Analysts, Admins). Beyond that it also had to be able to produce PDFs and CSV files of the logs. The main struggle aside from optimizing the querying as the architecture was not set up for this type of task, was the different types of users needed. This required the project to be very dynamic, which introduced me to minor meta programming in Ruby.