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

Role brief

Our Job Chat As a modern company, we dispense with standard job postings and want to inspire you with a new format for CROZ DACH. 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 posting – the title is Senior webMethods Integration Engineer (f/m/d). Markus: But please no siloed thinking. We're looking for someone who takes responsibility for the entire integration lifecycle: design, development, release, and operations. Whoever designs the flow also builds it, deploys it, and maintains it. A true generalist. Peter: Specifically, 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, setting up adapter integrations (SAP, JDBC, Salesforce & Co.) as well as implementing data transformations with DTL or XSLT. Markus: And then 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 your cool when a broker queue fills up or the thread pool is exhausted. Joachim: Another major topic for our customers is migrating from other integration platforms to webMethods – for example from TIBCO, MuleSoft, Oracle SOA Suite, SAP PI/PO, or proprietary 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's 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 bring? Joachim: At least three years of practical experience with webMethods – Integration Server, Broker or Universal Messaging, Designer. Someone who can independently read, debug, and resolve integration problems. But honestly: if the experience is close, but not exact, and if someone really thinks through integration solutions end-to-end, we still want to talk. Markus: As a bonus, we appreciate experience with 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 turn a vaguely formulated requirement into a functioning integration, who doesn't pass problems on but solves them, who communicates clearly – even 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 language skills are important. Peter: Whether the knowledge comes from a degree, an apprenticeship, or years in enterprise projects is secondary for us. What matters is that it exists – together with the curiosity to keep pace with webMethods releases. Linda: Great, then I'll post the ad online. If this applies to you: we look forward to your application – and to a first conversation over a (virtual) coffee. [Auto-translated from German]