Senior webMethods Integration Engineer (m/f/d) in Part-time or Full-time

As a modern company, we dispense with standard job advertisements and want to excite you about CROZ DACH with a new format. Thank you for your interest in us and enjoy reading the following job chat!
 
Recently in the team kitchen:

Joachim: We need someone who knows webMethods.

Linda: I've already prepared a job advertisement – the title is Senior webMethods Integration Engineer (f/m/d).

Markus: But no silo thinking, please. We are looking for someone who is responsible for the entire integration lifecycle: design, development, release, and operation. Whoever designs the flow also builds, deploys, and maintains it. A real generalist.

Peter: Specifically, this means: Designing integration flows with Designer – from simple point-to-point connections to complex orchestrations. Developing services in the webMethods Flow language (BRANCH, MAP, INVOKE, LOOP, SEQUENCE) and in Java, building adapter integrations (SAP, JDBC, Salesforce & Co.), as well as implementing data transformations with DTL or XSLT.

Markus: And after that, the real fun begins: Releases via CI/CD pipelines with Deployer, Command Central, and tools like Jenkins or GitLab CI – across DEV, TEST, UAT, and PROD. In operations: Monitoring with My webMethods and Optimize, incident resolution, performance tuning – and keeping calm when a broker queue overflows or the thread pool is exhausted.

Joachim: Another major topic with our clients is the migration from other integration platforms to webMethods – for example, from TIBCO, MuleSoft, Oracle SOA Suite, SAP PI/PO, or in-house ESB solutions. And the webMethods world doesn't stand still: Since the IBM acquisition, everything is called IBM webMethods Hybrid Integration – so someone who has also worked with containers and cloud integration is exactly right for us.

Peter: What is important to us is a solid foundation: Integration patterns like Request-Reply, Pub/Sub, Dead-Letter-Queues, and well-thought-out error handling – plus a good understanding of how webMethods provides and consumes APIs (REST, SOAP/WSDL).

Linda: And how much experience should they have?

Joachim: At least three years of practical experience with webMethods – Integration Server, Broker or Universal Messaging, Designer. Someone who can independently read, debug, and fix integration problems. But honestly: If the experience is close, but not exact, and someone who truly thinks through integration solutions end-to-end, we still want to talk.

Markus: As a bonus, we would be pleased about experience with the webMethods API Gateway, webMethods B2B (Trading Networks), Managed File Transfer with webMethods MFT (ActiveTransfer), Optimize for SLA and process monitoring – or with LDAP integration, SSL/TLS setup, as well as clustering and high availability in the webMethods stack.

Annabelle: Just as important as the technology: Someone who is comfortable with ambiguity and can transform a vaguely formulated requirement into a working integration, who doesn't pass on problems but solves them, who communicates clearly – also with non-technical stakeholders – and who thinks about logging, alerting, and recovery from day one. And since our colleagues in Zagreb are already looking forward to regular exchange, very good German and English skills are important.

Peter: Whether the knowledge comes from a degree, vocational training, or years in enterprise projects is secondary for us. What's important is that it exists – along with the curiosity to keep up with webMethods releases.

Linda: Great, then I'll put the ad online.

If this applies to you: We look forward to your application – and to an initial conversation over a (virtual) coffee.

Find Jobs in Germany on Arbeitnow