Please read before contacting me:I value my time, so, please, before requesting a meeting with me, make sure that you've sent me a JD, which is appropriate for me, along with the company name. I'd like to first do offline research about the company and check whether the position is right for me.If it's not right, there's no point in having "a quick 30-minute call" - let's invest our time in a better way by doing something else.About the companies - I want to work for a company, which does not make the world a worse place for living and has a somewhat good reputation.So, for example, I would not work for a gambling company or one supporting Russia in their war.About me:I'm a backend JAVA software developer and an Architect with 17 years of experience.I have expertise in building applications for a wide range of clients - from small businesses to state agencies and multi-billion companies.Throughout the years, I have worked on projects, utilizing different methodologies - Waterfall, Scrum, Kanban.I have experience with both Java EE/Jakarta EE and Spring. I've been using Java EE since Java EE 5 and Spring - since version 2.I also have limited experience with JavaScript, but front-end development is not my cup of tea.Linux has been my OS of choice for more than 20 years, so I know my way around. I also have a LinkedIn skill assessment badge for it.In the past 3 years, I have used multiple AWS services - SNS, EC2, RDS, S3, ELB, and Cloud Watch... to name a few and I have a LinkedIn skill assessment badge for AWS as well.I have experience with multiple databases - both relational and non-relational.I have used IBM Informix, SQL Server, PostgreSQL, Oracle, MySQL, Redis and MongoDB.As an Architect, I have fully designed the architecture of several projects - both utilizing monolith and microservice approaches.I have experience with Event-driven architecture as well - the last project I was assigned to, was already utilizing it (Scala, Lagom, and Akka were part of the stack), so part of my job was to implement changes to the architecture, which were necessitated by the new requirements.Part of my job was also to create proposals for new features, which included estimations, and technical documentation (different kinds of diagrams along with use-case descriptions, API changes and functional and non-functional requirements).