Key Responsibilities

• Rewrite legacy Perl modules into Java (Spring Boot) and integrate them into the new monolithic codebase.
• Analyze and reverse-engineer legacy logic with minimal documentation.
• Implement Angular components, connect backend APIs, and deliver complete end-to-end feature flows.
• Debug and resolve complex behaviors stemming from inconsistent legacy business rules.
• Collaborate with PMs, BAs, and technical leads to clarify requirements and provide technical insights when documentation is incomplete.
• Participate in estimation discussions and highlight risks, assumptions, and hidden complexity.
• Contribute to maintaining code quality, refactoring, and improving internal consistency of the new system.

Required Qualifications

• 5+ years of hands-on Java experience (Spring Boot, REST, Hibernate).
• Solid Angular experience (component development, forms, routing, API integration).
• Proven experience working on legacy modernization or rewrite projects.
• Ability to work confidently in monolithic architectures, not only microservices.
• Strong debugging, code-reading, and problem-solving skills in undocumented environments.
• Comfortable taking ownership of full feature delivery (backend-heavy, frontend-capable).
• English level B2+ for direct communication with the European delivery team.

Nice-to-Have Skills

• Exposure to Perl, Cobol, or other legacy languages.
• Experience using AI-assisted tools for code analysis or refactoring.
• Understanding of enterprise database constraints (restricted schema modifications).
• Previous experience working in fixed-price or time-critical projects.

Ideal Candidate Profile

• Backend-driven full-stack engineer who can connect UI without relying on FE-only teammates.
• Comfortable joining a project in a critical phase and becoming productive quickly.
• Thrives in ambiguity; able to work effectively with incomplete specifications.
• High ownership mindset focuses on delivering the full solution, not just “my part”.
• Communicates clearly, pushes for clarification when needed, and can challenge assumptions constructively.

Project Background

The client is rewriting a 20-year-old Perl monolithic system into Java and Angular. The legacy application is part of a larger ecosystem and communicates mainly through the database, so the team cannot change the existing DB structure.

There is very little documentation, and the business logic is complex and inconsistent across modules. The project was severely underestimated, and after 11 sprints the team realized the scope is much larger than planned.

The project is in a critical phase and needs strong engineers who can join quickly and help stabilize delivery.