SOLUTION ARCHITECT (JAVA) - REMOTE

Job offer

From legacy to cloud. And you’ll help decide how we get there.

We are not looking for someone to keep legacy systems alive for another decade.

We are looking for a Solution Architect who wants to help redesign what comes next.

At FIEGE, we are moving through a major technology transformation. Some of our business-critical applications still run on proven IBM AS/400 (iSeries) environments. They have served us well – but our future is cloud-native, scalable, API-driven and built around modern Java technologies.

And this is where you come in.

You will have the opportunity to shape the architecture behind this transformation – from defining the target landscape to deciding how individual applications should move from legacy environments into the cloud.

This is not a maintenance role. It is a transformation role.

WHAT WILL YOU ACTUALLY BUILD?

• You will help define our future application architecture and turn business needs into solutions that can evolve for years to come.
• You will design modernization strategies for legacy applications – deciding where replatforming makes sense, where refactoring is the better option and where rebuilding is the right answer.
• You will work with modern architectural approaches such as microservices, event-driven architecture and API-first design.
• You will evaluate and work with cloud technologies across AWS, Azure or GCP.
• You will design solutions around Java, distributed systems, enterprise databases and integration technologies such as Kafka or RabbitMQ.
• You will create architecture that developers can actually build – supported by HLDs, LLDs, C4 diagrams and ADRs.
• And most importantly:
• You won’t just draw architecture diagrams. You’ll help turn them into reality.
• You will work closely with development teams, support technical decisions and promote modern engineering practices including CI/CD, Infrastructure as Code and DevOps.
  
  

THE INTERESTING PART? THE LEGACY IS REAL.

• We are transforming an existing enterprise technology landscape – not building another greenfield demo application.
• Our current environment includes IBM AS/400 (iSeries), RPG alongside modern technologies.
• That means you will face questions that don't have answers on Stack Overflow.
• How do we break down a business-critical legacy application?
• What should become a microservice – and what absolutely shouldn't?
• Where does the Strangler Pattern make sense?
• How do we migrate without disrupting the business?
• How do we transfer decades of knowledge from existing systems and teams into a modern architecture?
• These are the problems we want you to help us solve.

WHO ARE WE LOOKING FOR?

• You are an experienced architect or senior engineer who understands that good architecture is not about using the newest technology everywhere – it is about choosing the right technology for the problem.
• You have 5+ years of experience designing application or cloud architectures and a strong technical background.
• You have Java practical experience (Java will be one of the key technologies in the project)
• You have hands-on experience with at least one major cloud platform - Azure (preferred), AWS or GCP.
• Experience with AI tools and modern digital technologies.
• You understand enterprise databases such as PostgreSQL, Oracle or SQL Server.
• You know how modern software gets delivered – CI/CD, DevOps and Infrastructure as Code are more than buzzwords on your CV.
• And you can comfortably discuss architecture both with developers and with business stakeholders.
• English is essential, as you will work in an international environment.

YOU’LL GET BONUS POINTS FOR...

• Knowing your way around IBM AS/400 (iSeries), RPG
• Having already survived – and successfully delivered – a large legacy modernization project.
• Experience with DDD, Strangler Pattern or similar modernization approaches.
• AWS, Azure or GCP certifications.
• Experience with AI tools and modern digital technologies.
• And perhaps most importantly: knowing when not to introduce another microservice. 😉
• THIS ROLE COULD BE FOR YOU IF...
• You enjoy solving problems where there is no obvious answer.
• You want to influence technology decisions instead of simply receiving architecture from somewhere above.
• You can challenge existing solutions without disrespecting the people who built them.
• You enjoy working somewhere between architecture, engineering and business.
• And you would rather build the next generation of a system than spend the next five years maintaining the previous one.

WHY FIEGE?
Because this transformation is happening now.

You will join an international logistics company with complex, business-critical systems and a technology landscape where architectural decisions have a real impact.

There is legacy.

There is complexity.

There are constraints.

And there is a genuine opportunity to change things.

If that sounds more exciting than intimidating, we should talk.

Let’s build what comes after AS/400.