- design and development of the Group of Connected Customers (read) service. I took the major part of designing this new service which was simple enough to move fast with the implementation, but also complex enough to have some safety mechanisms and be able to handle a bigger load than expected.
- feature development and maintenance of the Customer Master Data Management system
- working on importing data from legacy system (ETL) and improving batch jobs performance by ~4x
- initiating technical improvements (splitting huge OpenAPI definition, using shared libs, using more idiomatic Golang patterns)
- taking part in technical discussions and helping in system design decisions
- making minor changes to the Angular Web UI
- tech stack: Go / Golang, Postgres, Gin, Ginkgo, Neo4j graph database, event sourcing, CQRS, Pulsar, Avro, Oracle, Java, TestContainers, DataDog, Angular, TypeScript

- development and improvement of Proto Energy SaaS product (mostly on payment and sales orders related features)
- building the WebSocket API for the event sourcing (and CQRS) based serverless backend
- writing and maintaining end-to-end tests
- creating the basics of the backend observability with the help of the DevOps team
- proposing code design improvements
- tech stack: Go / Golang, Postgres, Redis, RabbitMQ, WebSocket, AWS Lambda, AWS, Docker, Cucumber.js, TypeScript, Github, Grafana, Terraform, trunk-based development

– development and improvement of Alpaca's brokerage system; extracting some parts from the monolith application to microservices
– scale the monthly statement generation and reduce the job runtime by >10x
– build the scalable backend for mobile app push notifications
– working on subscription management and payment related features
tech-stack: Go (Golang), Postgres, RabbitMQ, gRPC, Testify, Iris, Kubernetes, Helm, Ansible, Google Cloud Platform, GitHub