Independent Senior Java Consultant · Amsterdam

Difficult Java
problems.One senior specialist.

I help engineering teams understand, stabilize, improve, and modernize business-critical Java systems through focused senior interventions.

Java, Spring, Kafka, databases, and any tool the problem needs. Clear scope, hands-on work, and a practical handover.

The problem comes first

When your team needs
a focused intervention

Production is unstable or slow

Recurring incidents, intermittent failures, or performance problems are taking attention away from delivery. I investigate the evidence, identify the likely causes, and work on the agreed stabilization or performance improvements.

Service codenames: Java CPR, Java Rescue, Java Reliability, Java Turbo.

Nobody has a clear picture of the system

You have inherited a Java application with undocumented decisions, unfamiliar dependencies, or parts nobody wants to change. I map what matters, explain the risks, and identify a practical next step.

Service codenames: Java Archaeology, Java Architecture Check, Java Health Check, Java Therapy.

Development has become painfully slow

Fragile tests, slow builds, awkward environments, and unreliable releases keep interrupting capable engineers. I trace the friction and address the most important technical bottlenecks within an agreed scope.

Service codenames: Java Flow, Java Safety Net, Java Cleanup, Java Detox.

Modernization keeps turning into a rewrite

Your Java or Spring stack needs to move forward, but uncertainty makes every change feel risky. I assess the dependencies, establish useful safeguards, and help plan or implement a controlled upgrade.

Service codenames: Java Upgrade, Java Recovery, Java Architecture Check, Java Safety Net.

An important decision needs an independent technical view

Before an acquisition, system takeover, major investment, or rewrite, you need evidence you can act on. I examine the code and architecture, challenge assumptions, and explain findings, uncertainties, and options.

Service codenames: Java Due Diligence, Java Intervention, Java Architecture Check.

AI coding needs stronger control

AI-generated code is becoming difficult to trust or maintain, or your coding tools keep repeating the same mistakes. I assess existing code or improve your approved tool configuration, depending on the problem, and validate the work on representative tasks.

Service codenames: Java Reality Check, Java AI Tune-Up.

The service codenames are starting points for a conversation. We agree the scope around your problem, its impact, and what you need to decide or change.

From uncertainty to a practical next step

How I work

  1. Understand the problem. Discuss the symptoms, business impact, previous attempts, and constraints.
  2. Agree a bounded engagement. Define the scope, access, deliverables, capacity, and price before the work starts.
  3. Investigate and act. Build a system map, test working hypotheses against evidence, and make only the changes covered by the agreed scope and permissions.
  4. Validate and hand over. Check the work, explain remaining risks, and leave findings, changes, and practical next steps with your team.

For production changes, agree the rollback boundary before acting. For assessment work, make the decision limits and uncertainty clear.

Work directly with me

Ievgen Liutyi

Independent Senior Java Consultant

I'm Ievgen Liutyi, an Independent Senior Java Consultant based in Amsterdam. I bring more than 15 years of professional software engineering experience, including Java development and solution architecture.

My core tools are Java, Spring, Kafka, and databases, complemented by any tool the problem needs. I work directly with technical leaders and software engineers, focusing on difficult problems and providing a clear handover.

Engagements

A clear scope and price

Regular consulting

€250 / hour

Excluding VAT

Fixed engagements

From €7,500 / week

Excluding VAT, for a separately agreed scope and capacity.

My regular working pattern is four client days per week. Timing, availability, and any urgent or out-of-hours work are agreed individually.

Start with a conversation

Tell me what
is happening

A short description is enough

  • The problem and its business impact.
  • What your team has already tried.
  • What you need to decide or change, and by when.

Please do not send passwords, source code, production logs, customer records, or sensitive personal information. I can arrange a secure channel for sharing technical material if needed.

How I handle your information