I am a senior Java, Scala, and DevOps engineer with a passion for clean, reactive, and functional code.

I enjoy working with a high level of autonomy and being responsible for my own decisions. Nevertheless, I do love discussing different approaches to how a particular problem could be solved, striving to improve myself and the products I build.

Although my primary expertise lies in Java and Scala, I am keen to learn new things. Throughout my journey as a developer I have also worked with a large number of technologies including, but not limited to:

• Java & Scala

• AWS: ECS, AMQ, RDS, Elasticache

• Terraform, Ansible

• SQL (DB2, MySQL, PostgreSQL)

• MongoDB

• Blockchain

• OpenShift & Docker

• JavaScript, Bash, & Python

• Continuous integration tools like Git, Maven, Bamboo, and sbt

• Frameworks and libraries such as Spring, Play!, Akka, Hibernate, & AngularJS

I extensively read about and follow acknowledged best-practices such as SOLID and DRY. I am sure my code could be labelled with more acronyms, but I try to simply stick to doing what seems best and ignore the fancy-sounding words. Although I am a Java developer by trade, I believe in the Scala approach where a system is defined using OOP principles, but the behaviour inside a class is implemented using functional programming paradigms.

I excel at building mission-critical applications since, due to my perfectionistic nature, I have very high standards of what is OK to be released. This attitude of mine extends to every step of the software building process, starting from clearly defining the technical requirements of a project to carefully setting up the deployment. Although technical decisions are my bread and butter, I also do take part in defining functional requirements and improving the product I work on.