I have the opportunity to greatly influence the development of our platform, and constantly evolve it. Some things I've done:- Architected a platform framework from the ground up that is able to map file changes to particular CDK stacks across our whole codebase using static code analysis, essentially turning our big monolithic pipeline into micropipelines, saving time and $$$- Created an intelligent testing framework based on the above, which based on the file changes in Git, dynamically selects the API tests needed to run for a particular change based on stack changes, which resulted in reduced E2E pipeline run times, and faster dev velocity across the team- Built multiple in-house linters that run as part of pre-commit hooks so that our infrastructure frameworks continue to operate as intended- Created a solution that allows env. var overflown Lambdas to still reference resources from lower lane stacks using Go + SSM- Implemented the adaptive ECS task feature for one of our most business-critical features (Data Export) saving $$$ on a daily basis- Shaped and refactored many parts of the infrastructure codebase- Contributed a lot to Go best practices + coding style discussions, trying to enforce these across our backend team with PR reviews, 1n1 discussions, etc.- Lead the platform side effort of the cell expansion project. As part of this, I rearchitected our cell-based pipeline to a wave-based deployment style, making it scalable to even hundreds or thousands of cells.- Contributed to the ever dangerous stack split efforts for scalability, and managed to get them through with zero downtime.- Contributed to many cost reduction effort items through deep analysis work (S3, CloudWatch, etc.)- Leading architectural discussions spanning across backend and platform- Created a terminal based incident management tool making the whole on-call process more scalable- Conducting platform interviews

My main focus was transforming microservices into containerized, K8s managed, highly available, robust microservices, and working on the whole CI/CD workflow by working on an internal PaaS for developers that ships our products from dev all the way to prod. I was also working on moving our services from on-prem to AWS. I deployed vital third party services for our microservices like RabbitMQ, Redis, Consul, Vault, etc. My work focused mostly around architecting and developing the infrastructure for our products on AWS using CDK.I was also conducting Staff and Senior level interviews, trying to focus on things that matter instead of asking candidates to invert a binary treeTechnologies I used on a daily basis were AWS, Kubernetes, GitHub Actions, Linux, Git, AWS CDK (switched from Terraform), Go and Typescript. I architected two production ready infrastructure stacks for 2 of our products in AWS from scratch, starting from setting up the basics (like networing) to having an EKS cluster with all the necessary addons and capabilities, alongside metrics forwarding + logging using Open Telemetry, and alerting - all IaC. I was also the main engineer on a greenfield project where I was mostly setting up infrastructure using ECS, ApiGateway and Lambdas.Before the company's focused changed to AWS, I also worked with on-premises infrastructure. I was handling the development K8s cluster of the company which was used by hundreds of developers. I migrated our oldest, "magic" stack that used Jenkins for CI and CD and Artifactory for artifact storage to a solution which uses GitHub Actions for CI, Octopus Deploy / Spinnaker for CD, and Cloudsmith for artifact storage, making our whole software delivery process much quicker and easier to understand.

I was mainly working on a containerized service that collects vital information about deployed Kubernetes resources in Oracle Cloud using the Kubernetes API for audit information collection. I developed features for it / enhanced the code written in Python.I also took part in creating CI/CD pipelines in GitLab, automated more information collection processes, documentation creation, and interviewed new candidates.

When I got to Bosch, I realized everything the Vehicle Application Engineers are doing can be automated, so without further questions asked I created a Python application which was able to evaluate every .MDF and .MF4 log that our measuring systems produced, and implemented all of the evaluation logic as a separate internal library that our engineers used out on the fields. This application drastically reduced the time and manpower it took to evaluate our results, and made it so that we could parallelize work more efficiently.I was also the first point of contact with Volvo, so any time a complex measurement needed to happen I was flown out to Sweden to analyze our test stoftware's results and perform the measurements myself.

I developed various applications for the company, including but not limited to:- a fast and reliable webscraper which pulls real estate market data into the company's database where it can be analyzed by multiple teams- developed a complete framework (using the company's evalution logic) for land price evaluation and forecasting, which is being used by the company and being sold to partners- worked on a piece of software which is able to pull Hungary's all officially registered house's and apartment's energy performance certificates- did various SysOps level tasks as well, including Linux server administration, networking, etc.