Lejla is a software engineer (currently based in Berlin) with more than 4 years of experience working both in enterprise and startup environments. Lejla started a career as a full-stack developer (backend-oriented) in a company that provides a global communication platform and worked on highly available and distributed systems for more than three years. In that period, Lejla cooperated directly with more than 10 teams all around the world.
After that, Lejla got a job in a fintech startup company in Berlin as a backend engineer and she becomes a part of the team based in two locations (Tallinn and Berlin). The team is developing the core functionality of the application.
Lejla is a self-motivated, team player with strong organizational skills and a great sense for process improvements.
Besides Lejla is a proactive, customer-oriented professional who is not afraid to take lead in urgent situations to find out the best solution for a client’s needs.
Since communication is key to success in remote environments Lejla always tries to keep in touch with clients and other stakeholders as much as possible while working on a potential solution.
Lejla enjoys working as part of a team and helping other team members. Lejla is always looking for growth opportunities and is never one to back down from a challenge.
Technology stack: Ruby on Rails, Bootstrap, React, MongoDB, Heroku
In meantime, Lejla created her Upwork profile and got the first contract.
She developed a small web application for SEPA payment using Ruby on Rails, React and MongoDB.
Application covered these functionalities: user was be able to enter payment details, generate appropriate SEPA file and download it (so it can be used later for upload to mobile banking application) and also he was able to review his payment history.
After she has finished that application client rated her job with 5 (highest value) in each category including: skills, availability, communication, quality, deadlines and cooperation.
Infobip is a global communications platform that enables developers and business alike to build connected customer experiences across all stages of the customer journey at scale, with easy interactions over customers preferred channels.
During these three years at Infobip Lejla was working on different products. In the first two years she was working on Infobip’s internal products and later Lejla switched to work on client-facing products.
IpCoreAdmin tool
Technology stack: Java, Spring, Hazelcast, Angular, Angular2, VueJS, MySQL
IpCoreAdmin is an internal tool for provisioning Infobip’s core platform service named IpCore. IpCoreAdmin is based on monolith architecture both on backend and frontend side and it is actively used by all Infobip teams from C level to client support level for more than 10 years.
Lejla was actually maintaining and improving the stability and visibility of that huge monolith.
One of the most important initiative Lejla was working on was making IpCoreAdmin multi-location while keeping it highly available. Lejla’s responsibility was to make the whole migration plan to new domain and additional DC, communicate and delegate appropriate tasks to other Infobip teams (and keep their progress), make appropriate adjustments in current project (some of them were related to different Hazelcast cluster issues) and make sure that this most important internal tool in Infobip will work despite any disaster or issue in one DC.
NOC – Network Operations Center tool
Technology stack: Java, SpringBoot, Hazelcast, Angular2, Rabbit MQ, Clickhouse, MongoDB
Infobip NOC platform is a network tracking and alerting platform, used by the company support team to track potential problems with the network.
The tool is used to monitor the entire network traffic (400 million messages a day), and alert the support team if there are any anomalies in the behaviour.
Lejla worked on front end part of this internal tool. This part is built on micro frontend architecture and Lejla was working on multiple micro frontend services written in Angular2. She was improving existing features and their performances but also actively gave UI/UX propositions and suggestions to Product Manager. Many of these suggestions were accepted, implemented resulted with positive feedback from users and decreased number of questions and unexpected results related to those features.
CSM – Customer success management tool
Technology stack: Java, SpringBoot, Hazelcast, Rabbit MQ, Angular2, Clickhouse, MongoDB
Customer success management tool is an internal tool intended for Infobip’s customer success management team. CSM Alerts are designed as a whole new way of alerting about client problems. The major goal is to inform CSMs about the problems as soon as they happen,
so they could proactively reach out to the clients, to resolve the issues for/with them before they reach out with a complaint.
Lejla worked both on backend and frontend part of this tool. She enabled alerts integration with other apps (like teams and mail), redesigned and simplified the most used components and flows, she improved caching mechanisms on FE side using IndexedDB and implemented automatically reload of js files after deployment, so users were able to use the most recent app version without need for re-login or clearing cache. Also, Lejla actively participated in meetings with all stakeholders. She did not only implement features but also participate in their design. She always try to challenge existing ides regarding new features to make that features simple and user friendly.
Regarding that, Lejla has always received very positive feedback from users and Product owner.
TS – Traffic status
Technology stack: Java, SpringBoot, Hazelcast, Rabbit MQ, Angular2, Clickhouse, MongoDB
Traffic Status alerts in NOC is the new, self serve-based type of alerts. The self-serve aspect of these alerts is a key difference. Users are able to create, adjust and delete configurations without the involvement of the development team, and practically create as many configs and analyses as they need. This allows users to be more experimental and more precise when trying to monitor for specific traffic issues.
Lejla was a member of team who took over development process of this service after its MVP phase was successfully finished by another team.
After this fast onboarding process to new service, Lejla worked both on frontend and backend side. Lejla took full ownership of initiatives from definition, over breakdown till development and testing phase. Lejla extensively communicated with users and incorporated theirs feedback in the initiatives.
Lejla introduced new parts like acceptance criteria and acceptance tests to Definition of Done for her team.
Also, in this period Lejla was maintaining existing NOC services and CSM and working on onboarding process for another team in Slovakia.
Voice portal
Technology stack: Java, SpringBoot, React
Lejla is working on one of the micro frontends on Infobip’s Voice portal product.
Voice portal is actually part of Infobip portal that enabled users to use Voice features through user interface.
Since there are many micro frontends incorporated in portal, the whole developing and deployment process was really slow and time consuming.
Lejla lead and finished two important initiatives for improving development and deployment process of these parts of product.
The first one is to have separate resources and availability for testing this part of Portal and the second one is having separate deployment process for this micro frontend. In that way, Lejla’s team started to be able to develop and deploy its services changes independently and decreased time needed for urgent fixes or feature delivery.
Moss – All-in-one spend management (Cards module)
Moss is a fintech startup that provides corporate cards and spend management solution for other businesses. Currently, thousands of businesses rely on Moss spend management solution and use Moss corporate cards.
Technology stack: Java, Spring boot, Kafka, Postgres
Lejla is working on the cards module of Moss’s spend management solution. The cards module is the core module and functionality of the Moss application. Lejla implemented on her own end-to-end new notification types for declined transactions in her 2nd week in the company. During the work on that ticket, she noticed messy logic and bad UX related to notification settings and she made notification settings cleanup. Thanks to that Moss gets rid of messy and complex notification settings logic (from the user’s perspective) and hard-to-maintain logic (from developer’s perspective). Lejla also managed to fix some of the existing bugs in that logic which proves that Lejla is always trying to understand and improve the existing behavior of the feature.
Lejla was part of the team that made the first big service logic extraction and migration to the new service in Moss. It was necessary for better scalability and performance for bigger customers. In Moss, this initiative is described as “a heart surgery on a running athlete, without killing him”. Lejla worked on different parts related to this migration. She implemented card processing logic on the new service in a way it supports switching the customers between the old and new service, so we were able to switch customers gradually and monitor the behavior during that migration. Lejla also initiated creating different kinds of metrics and alerts for that purpose and in general for new services. Until that time, team cards owned some of the critical flows without appropriate visibility. Lejla added different metrics and presented that on company-wide demo and the whole company started to adopt this approach and add more metrics to their service to increase visibility and stability.
Currently, Lejla is working on a refactoring of one of the crucial processors and trying to implement it using domain driven approach. Lejla recently read a book about that and this is only one example of how Lejla is expanding her knowledge and trying to apply it to improve the current state of the code and system.