Position: Senior Software Engineer
Category: Java
Experience: 11 years | English: fluent

1. I was working on creating a back-end for a multiplayer video game, using a microservice architecture. I was responsible for the following: 
- designing the architecture of the system 
- setting up CI/CD (GitHub workflows + version release process to GitHub Packages & Azure Container Registry via Helm charts of our own making)
 - designing inter-service communication (REST API + event bus) 
- integration with 3rd party game services (namely Steam) 
- integration of an OpenID Connector solution into the chain “ExistingBackEnd-Client” 
- implementation of a scalability system within one app which revolves around the number of available k8s instances 
2.  There was a modular AngularJS application, and I was tasked to implement a mechanism of persisting and applying page filters across all the pages of the app - you add different filters on one page, then navigate to another one, and all applicable filters from the previous page are applied
3. Reworked (performed refactoring on) a piece of functionality (~1000 lines) with a convoluted flow (a lot of "if"-statements, a lot of execution jumps), which was faulty in production. I increased the test code coverage of the piece above of functionality first.
4. Along with a teammate of mine, we've drastically sped up the main page of the app, which resulted in local & written gratitude from the client + paid bills in any restaurant for the whole team (including everyone's significant other).
5.  I managed to build a friendly atmosphere in a team of 6 people (devs and QA):
- the team was self-sufficient (out of tasks -> grab one from the backlog, need help -> ask a lead/colleague );
- introduced knowledge cross-sharing - back-end devs were working on front-end tasks, and front-end devs were taking back-end tasks (no coercion, we were aiming to become full-stack devs). If/when there were questions/problems in the foreign field, the "native" developer (back end for server, front end for client) helped with resolving those
- taught colleagues to handle constructive criticism in pull requests
For my last project I was involved in creating a microservice-based system from scratch: 
- working on concepts
- inter-service communication
- setting up CI/CD
- feature implementation.
Prior to this, I was mainly working with web stack (JSP, Thymeleaf, Spring (MVC, Boot, Security, AOP, Data, Batch, WebFlux), Hibernate, AngularJS, etc).
I have a little bit of commercial experience with mobile platforms (Android, IOS (Objective C)).
I have experience being a team lead for 6 people. Built the team from the ground up. The team was operating for 2.5 years.
I was:
- mentoring colleagues
- discussing requirements with the client
- creating proof-of-concept solutions
- implementing new features
- fixing bugs
- helping my colleagues with demos to the client (highlighting business values of the features we demo).
I'm looking for a project which is (to be) written in Java-based language (Java, Kotlin, Groovy). Kotlin is preferable, but Java is OK too.
The usage of GraalVM would be a plus.
I prefer to work with the Spring Framework, but am not limited to it.
I'd like to work on a project which doesn't simply put deadlines before the devs, but also has an adequate amount of planning (grooming sessions, team velocity calculations/adjustments)

I prefer to work in the office, but that's not a critical point given the situation. If possible not an "open-space" office (or at least up to 20 people in it).

A huge plus would be an office with a parking lot (I'd prefer not to circle the block for 20 minutes to find a spot to park).