POC of an AI-powered application that helps with SDMX-based survey configuration.Dev team: 1BE, 1 DMAchievements:• POC• Chatbot that is able to configure complex custom survey• Presentation for POC

A product that helps with the creation of different surveys and the collection of data into SDMX format. Dev team: 3 BE, 3 FE, 2 QA, 1 AQA, 1BA, 1 PMAchievements/Tasks:• Project interviewer• Created adapter that allows representing data with ‘SDMX’ format in more ‘free’ JSON • Designed and created a special validator for ‘surveys#questions’ -> ‘answers’ based on JsonSchema. This validator takes all ‘javax’ restrictions from ‘QuestionDTO’ and based on them creates JsonSchema for answers. Have used ‘Networknt JsonSchema validator’• Redesigned authentication model that separately loads user-info. This schema allowed us to handle the issue with a large token size and load all required claims on demand• Increased test coverage from 10% to 72+%, bug fix, security issues fix, and deduplication to achieve C level of the TIOBE application assessment• Design and implementation of the Hybrid Authorization model. With this model, we were able to mitigate multiple customer requests with authorization. The model is based on two strategies: 1 - internal authorization strategy that takes from auth token a principal unique identifier and searching in DB required permissions, and 2 - based on roles claim we convert them to permissions and authorize principal access• Design and implementation of S2S (service-to-service) authorization. We have multiple services that we communicate with each other, for authorization we retrieve MSI token that in claims has MSI roles. Authorization is performed on special endpoints (/internal)• Design, implementation, and rollout (Azure AppReg and MSI configuration, CI/CD setup, Helm configuration) of the Audit service• Configured Security incidents notification system that loads info about them to EventHub• Design and implementation of the Scheduled-events service to manage many different configurable events. DB was user for a fail-tolerance strategy

A medical enterprise that takes reports from almost all hospitals. The application collects reports and annually generates reports from them.Dev team: 3 BE, 1 PM, 1 DevopsAchievements/Tasks:• Created Onboarding process• Created tests that cover 60% of flow (from scratch) for project stabilization• Redesigned ‘Email Notifications’ flow with an async approach. When notifications spread after that the report was generated and sent to the sender with notifications statuses. With this approach, we bypassed long response times (~20 minutes) and suppressed errors related to long response time and notification duplications

A huge government-oriented medical enterprise that has a lot of applications. We have worked with one part of this and it was related to handling requests and generation of reports after 911 redirection an ambulance vehicle to a patient.Dev team: 1 Team Lead - BE, 3 BE, 1 PMMy responsibilities were to help to migrate the project from old architecture to new architecture.For this purpose, we used old code for the "black box" testing, then the results of those tests we saved as CSV files, and then I wrote the code flow that will pass all requirements of the tests. This approach was chosen because the new architecture should be able to change the old one.