Experience Required
● 5–8+ years of professional Java development experience
● Minimum 3 years working with Spring Framework in production (both classic Spring MVC and
Spring Boot)
● Experience maintaining legacy enterprise Java applications alongside modern microservices is a
strong plus
Core Responsibilities
● Maintain and extend a Java 21 / Spring 6.2.x MVC / Hibernate 6.6.x order fulfillment backend for
visa, passport, and travel document services (not Spring Boot — manually configured, WARdeployed to Tomcat)
● Design, build, and support Spring Boot microservices that integrate with other platform services
● Work across two parallel data-access stacks in the platform: a legacy precompiled framework and a
modern JPA/Hibernate stack — both operating on shared database tables
● Develop and maintain JSP/Servlet views alongside newer Spring MVC views, plus supporting
jQuery/JavaScript
● Write and manage Flyway database migrations (MySQL/MariaDB) across multi-country/multidomain deployment configurations
● Implement and troubleshoot audit trails (Javers), authentication/SSO (SAML via OneLogin, JWT),
and authorization/IDOR protections across orders, payments, debtors, and documents
● Support payment processor integrations with correct handling of PCI-sensitive data and financial
precision (BigDecimal)
● Generate reports and PDFs via JasperReports and iTextPDF
● Build, containerize, and deploy services using Docker, front them with Nginx, and operate them on
Linux servers
● Maintain and extend Jenkins CI/CD pipelines (Groovy pipeline scripts) for build, test, and
deployment automation, including ad-hoc Flyway migration pipelines
● Collaborate with QA/DevOps to troubleshoot production issues across the monolith and
microservices, including cross-service data consistency (orders, milestones, billing)
Required Technical Skills
Languages & Core
● Java 17/21 (strong OOP, collections, concurrency fundamentals)
● SQL (MySQL/MariaDB), schema design, query optimization
Frameworks
● Spring Framework 6.x (Core, MVC, Data JPA, TX, AOP) in a non-Boot, manually configured setup
● Spring Boot 3.x for microservices development (REST APIs, auto-configuration, embedded Tomcat)
● Hibernate/JPA 6.x (entity mapping, inheritance strategies, lazy loading pitfalls)
● JSP, JSTL, Servlets (legacy web tier)
Data & Migrations
● Flyway (versioned and repeatable migrations, multi-environment strategy)
Security & Integration
● SAML SSO (OneLogin or equivalent), JWT-based authentication
● REST API design; exposure to SOAP/WSDL a plus
● Awareness of OWASP Top 10, especially IDOR/access-control issues in multi-tenant order/billing
data
Reporting
● JasperReports and/or iTextPDF (report/PDF generation experience)
Frontend (supporting, not primary)
● jQuery / vanilla JavaScript
● Exposure to a modern frontend (React) is a plus, as some admin tooling is React-based
Build & Tooling
● Gradle (multi-project builds, custom tasks/plugins)
● Git
DevOps / Infrastructure
● Docker (building/running containers, multi-service compose setups)
● Nginx (reverse proxy/routing configuration)
● Linux (comfortable administering/debugging services on Linux servers)
● Jenkins (writing/maintaining Groovy pipeline scripts, CI/CD for build+deploy)
Nice to Have
● Prior experience in travel, visa/passport processing, fintech, or order-management domains
● Experience with audit/versioning libraries (e.g., Javers) or similar change-tracking systems
● Exposure to Joda-Time and date/timezone handling across multi-country deployments
● Familiarity with microservice patterns: service-to-service communication, eventual consistency,
distributed transactions across a monolith + microservices boundary
Soft Skills / Working Style
● Comfortable navigating and safely modifying a large legacy codebase without full documentation —
must exercise judgment on what's safe to change vs. what's tribal-knowledge-dependent
● Strong attention to financial and PII data handling given the sensitive nature of orders, payments,
and travel documents
● Ability to work across both monolith maintenance and new microservice development without forcing
one architectural style onto the othe
