I am part of the Magnolia team, where I joined during a critical growth phase of the company. My main responsibility was addressing the challenges associated with the increasing client base of our Platform as a Service (PaaS) product, which began to encounter its scalability limits.https://www.magnolia-cms.com/platform/architecture-and-tech-stack/platform-as-a-service.html- Design and implementation of an automation solution from scratch for a PaaS product on the AWS cloud provider(with plans for expansion to Azure and GCP).- Introduction of IaC for managing infrastructure for dozens of enterprise customers (dozens of AWS accounts and dozens of Kubernetes clusters) using Terraform/Terragrunt and GitOps (FluxCD), and implementation of deployment through GitLab CI.- Responsible for training team members on new technologies and solutions, while also coordinating tasks and collaborating with an external devops agency in the implementation of automation processes.Efforts significantly reduced the time required for onboarding new clients - from several days to just a few hours, saving substantial resources and making the entire system more efficient.

At Lumenax, our core service is to assist clients in identifying and resolving scalability challenges from a technical perspective that contributes to business success. Our unique approach addresses scaling issues holistically, considering the end-user experience. In my technical role, I focus primarily on infrastructure scaling and automation, overseeing the entire process from design to implementation.

In Gooddata I'm working on two projects. One is the ETL platform for one of our customers, and the second is a freshly new product where our team is building a new cloud platform from scratch that hosts Goddata cloud-native analytics service https://www.gooddata.com/developers/cloud-native/.Cloud platform product, https://www.gooddata.com/platform/- Provisioning and operating cloud infrastructure in AWS,- Configuring and managing tens of Gooddata and third-party services in k8s (AWS EKS),- Developing and maintaining a few backend services such as registration service,organization API service, or our own k8s operator https://www.gooddata.com/developers/cloud-native/doc/1.2/administration/organization/,- Configuring CI/CD Gitlab pipelines,- Participating in active monitoring and hunting of bugs over services, improving dashboards and graphs in Grafana, and writing Prometheus or Splunk alerts.ETL platform- Provisioning and operating cloud infrastructure in Private Cloud,- configuring and managing applications in k8s and VMs,- Developing, maintaining and operating a few backend services,- Maintaining DB nodes,- Configuring CI/CD Jenkins pipelines,- Participating in active monitoring and troubleshooting (Splunk, Grafana, Icinga)improving dashboards and graphs in Grafana, Prometheus and Splunk alerts,- Holding on-call duties# languages: Java, Kotlin, Python, Bash# provisioning and configuration: Terraform and Terragrunt, Ansible, Puppet, FluxCD, Kustomize# query languages: SQL, PromQL (Prometheus)# frameworks and libraries: Spring (Webflux), kopf# databases: PostgreSQL-ha, MySQL, Vertica, InfluxDB, DynamoDB,# queues: Pulsar, RabbitMQ# caches: Redis# build tools: Gradle, Maven, Helm# deployment: AWS, Private Cloud, Kubernetes (EKS), Docker, Linux# monitoring and observability: Splunk, Grafana, Icinga, Prometheus, Jaegertracing# CI/CD: Gitlab, Jenkins, Rundeck# version system: Git

In Avast I worked as a software engineer in the Account team where my role was developing and maintaining a few microservices and web portals based on micro frontends for Avast account related domain.- Developing and maintaining a few backend services related to the Avastaccount domain. We have been writing our backends in a reactive way mainly with the use of the Spring Webflux framework, and frontends were designed in micro frontend architecture.- Developing and maintaining a few web portals that were designed and written as small decoupled micro frontends with the use of Svelte or VueJS libraries.- Preparing TeamCity CI/CD jobs for both frontend and backend applications(release and builds).- We were packaging these applications with Helm charts which were thendeployed to Kubernetes clusters.I worked mainly with:# languages: Java, Kotlin, Javascript, Bash# frameworks and libraries: Spring, Spring Webflux, Vue.js, Svelte.js, Ractive.js, Vuex# databases: PostgreSQL# testing: JUnit# building tools: Maven, Gradle, npm, Webpack, Rollup.js, Helm# CI/CD: TeamCity# deployment: Private Cloud, Kubernetes, Docker, Linux# version systems: git

In Mavenir, I have worked as a full-stack software engineer on the distributed application for real-time monitoring of the state of other Mavenir services within a telecommunication network infrastructure that allowed their managing, monitoring and configuring. Application has been installed on-premise in customer infrastructure, where that was provisioned and configured with Ansible playbooks.- Developing and maintaining two big monolitic backend applications (Java), andone big monolitic frontend (AngularJs).- Maintaing and developing automation tests, and test framework based onSelenium- Preparing Jenkins CI/CD jobs for release, and tests- We were provisioning these applications by Ansible playbooks and wererunning on the RHEL platform.I worked mainly with:# languages: Java, Python, Javascript, Bash# provisioning and configuration: Ansible# frameworks: Spring, Hazelcast, AngularJs# databases: InfluxDb, ZooKeeper# testing: Selenium, JUnit, Mockito, Hamcrest# building tools: Maven, npm# CI/CD: Jenkins# deployment: Linux RHEL# version systems: git

I have worked as a part-timer, on a process management application, where I had been working on the server-side functionalities.http://mathesio.cz/systembaker/I worked mainly with:# languages: Java, Kotlin, XML, Groovy# frameworks: Hibernate, Vertx and many other libraries# databases: PostgreSQL# unit testing: JUnit# building tools: Gradle# version systems: git