Position: Java Team/Technical Lead/Senior Engineer
Category: Java
Experience: 8 years | English: upper

Software Engineer with 8 years of the experience in the developing of the complex software solutions,
4 years of the team leading experience, different business domains, involved in:
• Participation in every stage of software development life cycle, from requirements analysis and
architecture design to UAT and handing over the final product release to the production, the
production product support and maintenance.
• Identification of business needs and creation of product backlog/road maps.
• Bootstrapping of development teams from scratch ranging from interviewing, on-boarding,
fulfilment of teams with all necessities to ensure reliable delivery.
• Handling different roles: Team/Tech Lead, Key Developer, Engineering Manager, Scrum Master.
• Leading development teams (functional and cross-functional), consisting of 4 and up to 10
engineers with a focus on effectiveness and industry best practices.
• Back-end development with high level of the experience of Java and Java-related technologies
and frameworks with a focus on reliability, performance and scalability.
• Experienced with SQL and NoSQL databases
• Experienced with messaging systems
• Working with different architectures: Micro services, SOA, Monolithic applications hosted on
Clouds and on Premises
• Working in business domains: Travel, Insurance, FX Trading.
• Good team player as well standalone worker, problem solver.
• High degree in learning of new technologies, solving of tech challenges.
February-2023 – Till now
Domain: Hybrid Cloud Provider
Project: Feature development and stabilisation assignments related to subscriptions, licensing and device management functionality for one of the Hybrid Cloud Platforms

June-2022 – January-2023
Domain: Open Source CDC Tools
Project: The goal of the project is to build low latency, auto scaled, fault tolerant Kafka Source Connector for Google Cloud Spanner DB based on Debezium / Kafka Connect frameworks

May-2021 - Jun-2022
Development Team Lead
Domain: FX Trading 
Project: The main goal of the project is to develop an innovation FX trading system with key characteristics to be high quality, high reliability, latency sensitive, cloud native.

Leading of the Core Team consisting of 5 Java Engineers. Core Team involved in delivery of critical
components: some of them are developed from a scratch, another part are forks from existing products
but migrated to a new tech stack and become Cloud-native.
Examples of Team deliverables and assignments:
• migration of schema for forked component from Oracle to MS SQL Server
• migration to JPA/Hibernate
• development of Redis-based Caching API for usage across the platform
• development of REST API's using Spring Boot
• development of applications which are integrating over: Kafka, Redis; stateful protocols:
WebSocket, FIX protocol
• POC's to define high-availability and horizontal scaling approaches for stateless and stateful
apps
• development and onboarding observability and testing tools for usage across the teams

Participation
• Involved in each phase of complex technical solutions and assignments (design, development,
deployment, maintenance)
• Analysis and alignment of business/technical requirements
• Code reviews
• Grooming/Planning
• Team management
• Interviewing and on-boarding of team members
Tech stack: MS SQL Server, Redis, Helm, Gradle, GitLab, Jacoco, Bamboo, Azure Data Explorer , Java
11, Spring Boot (Web, Data, Security, Hateoas), Kafka, Redis: Cache, Pub/Sub, Redis Java Clients:
Lettuce, Redisson, Jedis, MS SQL Server, Flyway, JPA/Hibernate, Docker, Kubernetes, Azure Cloud
(Event Hubs, Azure Cache for Redis, Key Vaults, ADS, ACR, AKS, VM's), MapStruct, QuickFixJ, Java
Concurrency: Executor services, Atomics, Thread-safe collections, CountDownLatch, Guava, Apache
Commons (commons-lang3, commons-codec), Lombok, Log4J, Junit 4/5, Mockito, AssertJ,
TestContainers;
- project with modern tech stack
- beginning phases of project are more preferable (but not critical)