Job Description

Tired of manual builds, unstable deployments and logs that go silent exactly when you need them most?

We’re looking for a Java and DevOps expert who wants orderly pipelines, predictable systems and a real voice in technical decisions. Our dedicated engineering team is responsible for the design, build, and operations of cloud-native services — including Java/SpringBoot microservices, CI/CD pipelines (e.g., Jenkins), containerization and orchestration (Docker/Kubernetes), and modern cloud platforms.

Tech stack

You don’t have to know everything, but most of this should look familiar:

• Java / SpringBoot
• JavaScript / TypeScript
• Jenkins and/ or GitHub Actions (CI/CD)
• Kubernetes / Docker
• Infrastructure as Code with Terraform
• AWS and Azure
• Interest in business workflow automation and orchestration – you’ll work with BPMN 2.0 and Camunda in real scenarios (a rare combination with Java + DevOps)

What we’re looking for

• You think in automation, not in “clicking around” – when something repeats, your instinct is to turn it into a script, a Jenkins job or a pipeline step instead of relying on manual procedures.
• You have a production mindset – you care about how the system behaves in production; if you see strange behavior or risk, you raise it early and help find a sustainable fix, not just a quick patch.
• You speak like a Consultant and play as part of a tech team – you describe problems with facts (logs, metrics, steps), suggest a logical next step and have no issue helping a teammate who’s stuck instead of letting issues sit and grow in silence.

What we offer

• A voice in decisions, not “you just code”
  You have direct contact with the architect and the technical lead and take part in the conversations about architecture, pipelines and tooling instead of just executing tasks passed down to you.
• A rare combination of skills
  You combine Java/Spring with a DevOps stack (Jenkins, Kubernetes, Docker) and BPMN / Camunda in real scenarios – a profile that will later make you stand out on the market.
• A small team, little bureaucracy
  A team in an early phase, clear technical goals, short decision paths and a normal tone; the idea is to build stable systems, not to live in status meetings and reports.