Java Tech Lead

Requirements

• Act as the technical focal point of the project.
  
• Maintain and evolve the solution’s cloud native architecture, based on microservices, APIs, and event driven patterns, ensuring cloud agnosticism and support for Active Active topologies, with a critical and constructive mindset.
  
• Ensure that developments are aligned with the defined architecture, from solution design through to production deployment.
  
• Perform regular code reviews, promoting engineering best practices, clean code, and automated testing as guarantees of solution quality.
  
• Define and manage technical debt, prioritizing critical fixes and refactors.
  
• Ensure non functional quality attributes: performance, resilience, security, observability, and platform scalability.
  
• Support the design of high availability (active active) strategies, data consistency, and disaster recovery.
  
• Promote technical documentation (architecture, decisions, standards, development guides) and ensure its continuous update.
  

• Java expertise: deep knowledge of Java (recent versions) and solid experience with Spring Boot (ideally also Spring Cloud).
  
• Cloud Native Architect: proven experience in designing distributed systems, microservices patterns, event driven architectures, containers, and container orchestration.
  
• Strong knowledge of microservices management and patterns (circuit breaker, saga, retries, API gateway, service discovery, observability patterns, service mesh, REST, gRPC, etc.).
  
• Hands on experience with event driven architectures and messaging/streaming (Pulsar, Kafka, RabbitMQ, or similar technologies for asynchronous processing).
  
• Knowledge of active active typologies, geo distribution, fault tolerance, and high availability design.
  
• Experience with distributed databases and database engines (SQL and/or NoSQL), as well as data consistency models (eventual, strong, compensation patterns).
  
• Solid understanding of application and API security (authentication/authorization, OAuth2/OpenID Connect, secrets management, hardening).
  
• Experience with continuous integration/continuous delivery (CI/CD) tools and DevOps practices.
  

• Experience in legacy to cloud native system migration projects.
  
• Experience with observability (centralized logging, metrics, distributed tracing) and SRE.
  
• Previous experience in payment solutions, instant payments, or mission critical financial systems.
  
• Knowledge of standards and formats in the payments domain (e.g., ISO 20022, SEPA Inst).
  
• Cloud and/or Cloud Architecture and/or Kubernetes certifications.