Lead Developer
Tech stack:
ReactNext.jsCss ModulesMicro FrontendsTeam size and roles:
- 2 Backend engineers
- 2 Frontend engineers
- Product manager
- 2 QA engineers
My current position is Senior Frontend Engineer with a strong focus on Frontend and React JS.
I am involved in various projects within the MedTech industry at our company. These projects include developing and maintaining software applications tailored for dental clinics across Germany.
One of the key projects I work on is the Practice Management Software (PMS) called Claire. It is used by approximately 15 dental clinics and assists in managing essential aspects such as reception, treatment, billing, and more.
I collaborate closely with a team consisting of backend engineers, frontend engineers, a product manager, and QA engineers. We use Agile methodologies such as Scrum and Kanban for project management, ensuring the efficiency and usability of our MedTech solutions for dental clinics.
The Practice Management Software (PMS): It is a software currently used by ~15 Dental Clinics placed across Germany. It enables and helps the practice personal to manage the most important parts: Reception, Treatment, Billing and more
Calmaster is a clinical staff tool with a main view displaying practitioners and their appointments. Users can book, modify, or cancel appointments, as well as access patient details.
It shows upcoming patients and their document completeness, triggering document collection. Anamnesis forms are accessible to doctors. Calmaster integrates with the clinic’s phone system, displaying incoming calls linked to patient details.
Ongoing calls are listed. SMS communication with patients is also accessible.
UI Library compiles shareable interface elements (components) to maintain a consistent appearance and prevent redundant implementation across patient21 products.
Shift Planner streamlines scheduling for doctors' clinics, optimizing resource allocation and ensuring smooth operations. With its user-friendly interface and comprehensive functionalities, it simplifies shift management, helping clinics organize staff schedules efficiently.
Responsible for developing and maintaining before and after login user experience for gymondo web app.
Everything related to:
Developing new features, maintaining as well as refactoring help center and internal back office tools used to connect customers with customer support.
The most difficult part in resolving problems with your order is figuring out how to get help from the relevant source. How do you even know where to look, who to contact, and which information to provide?
Before the help assistant, users would navigate through a large number of self-help articles. This was not optimal. Imagine being hungry and angry because your food was not delivered, or not delivered as expected; the last thing you would want to do is read articles.
Having dedicated on-call agents is certainly the best way to resolve the issue. The problem was that it was very costly to run a call center big enough to serve so many order issues.
A product solution was offered in the form of an online self-help assistant. Depending on the order status, it would offer the best possible solutions which users could implement on their own, as most of the problems did not require a dedicated agent.
The user interface was agnostic of the possible resolutions. It hosted all the possible solutions fetched to the browser conditionally, but the decision about which one to show was outsourced to the backend services, which also knew the correct status of the order.
Worked on https://www.belvini.de/, online shop for wines. Joined in the finishing phase of product development, some of my tasks were:
Online shop for wines. Joined in the finishing phase of product development, I was mostly supporting design and UX changes.
Link: https://www.belvini.de/
Online shop for baking products, recipes and baking comunity.
Some of my task were:
Link: https://backen.de/
At Smava I am working on internal tool, which is used to connect Smava users with appropriate banks in cases where users does not enter all the necessary data for this process to be automatic. Since majority of customers/users, because of how complicated forms on the web can be especially the ones for bank loans, does not enter all the data, vast majority of conversations are happening through the app I am working on.
I was working on small and big project, ranging from 2 to 10 team members in agile like setup. I also worked on legacy project as well as project which used latest FE stack such as React|Redux|Webpack
.
Main focus of projects was e commerce and working with sensitive data inside Banking environment. I also had an opportunity to share my knowledge between all teams by holding workshops, and being responsible for junior level developers, making sure they are properly onboarded on the project and making sure they are following project standards.
Worked on complete redesign of the customer facing frontend app.
I was onboarded quite late to the project so I was giving the task of refactoring previously builded React components and developing few new features. Project had a really nicely defined processes, since the UI part was build by other company we had to implement their code into our application which then acted as a widgets on AEM powered website.
Nettoshop as a legacy project had its own set of challenges, manly how do you implement new feature which requires latest Front End standard on a project which wasn't build to support those latest standard in the first place. I ended up writing a lot of polyfills myself and tying to gracefully degrade features as much as possible.
Focusing just on a front-end technologies led me to discovering a wonderful world of component based development, rich new features of ES6, preprocessors, automated tasks, and Yeoman generator for faster kick starting new project using tools that compliance best practices.
Client goal was to enable the user quick and easy exploring of the Museum from the web browsers. But also to make onsite visitor a route guide from one exhibition to another. I was responsible for building the frontend part of the map by being provided with single design file crated in Sketch.
Client wanted to update new website with fresh and well responsive UI. My responsibility was to convert design files of every page (from Sketch) to web standard html, css, js. Later those templates were integrated in Wordpress.
Link: https://dktcomega.com/
My responsibility was to convert design files of every page (from Sketch) to web standard html, css, js. Later those templates were integrated in Wordpress.
During my time at Dresscode, my primary role was to accomplish the conversion of design files, specifically PSD, into dynamic website templates.
Through my utilization of HTML, CSS, and JavaScript
, I successfully transformed these static templates into CMS systems like WordPress.
While my primary focus revolved around front-end technologies, I recognized the necessity of delving into the entirety of the WordPress
ecosystem and getting to know PHP
as a programming language.