Senior webMethods Integration Engineer (f/m/d) full-time or part-time

As a modern company, we avoid boring job ads and would like to inspire you for us with a new format. Thank you for being interested in CROZ DACH and enjoy reading the following JobChat!

Recently in the team kitchen:  

Joachim: So, we need someone who knows their way around webMethods.
Linda: I've already prepared a job ad - the title is Senior webMethods Integration Engineer (f/m/d).
Markus: But please, no silo thinking. We're looking for someone who owns the full integration lifecycle: design, development, release, and operations. Whoever designs the flow also builds it, deploys it, and supports it. A true generalist.
Peter: Concretely, that 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.), and implementing data transformations with DTL or XSLT.
Markus: And after that the real fun starts: releases through 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 backs up or the thread pool runs dry.
Joachim: Another big topic with our clients is migrating from other integration platforms to webMethods - for example from TIBCO, MuleSoft, Oracle SOA Suite, SAP PI/PO, or home-grown ESB solutions. And the webMethods world isn't standing still: since the IBM acquisition it's all called IBM webMethods Hybrid Integration - so anyone who has also worked with containers and cloud integration is exactly right for us.
Peter: What matters 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 exposes and consumes APIs (REST, SOAP/WSDL).
Linda: And how much experience should they bring?
Joachim: At least three years of hands-on experience with webMethods - Integration Server, Broker or Universal Messaging, Designer. Someone who can read, debug, and fix integration issues independently. But honestly: if your experience is close but not exact and you think about integrations truly end-to-end, we still want to talk.
Markus: As a bonus, we'd be happy to see 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, and clustering/high availability in the webMethods stack.
Annabelle: Just as important as the tech: someone who is comfortable with ambiguity and can turn a loosely defined requirement into a working integration, who doesn't hand off problems but solves them, who communicates clearly - including 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 to us. What matters is that it's there - along with the curiosity to keep up with webMethods releases.
Linda: Great, then I'll put the ad online.

If this speaks to you: we look forward to your application - and to a first chat over a (virtual) coffee.