OpenText Workflow Backend Developer – Operations Orchestration (DevOps Team)

Company Description Do you want beneficial technologies being shaped by your ideas? Whether in the areas of mobility solutions, consumer goods, industrial technology or energy and building technology - with us, you will have the chance to improve quality of life all across the globe. Welcome to Bosch.

Job Description Role summary

Full-stack backend developer in an Agile DevOps team that builds and runs automation on OpenText Operations Orchestration (OO). Designs, develops, and maintains OO flows, operations, and content packs in OO Studio, automating IT and business processes and integrating OpenText with enterprise systems. Owns the stability of these automations in production, and supports the team's move of selected workflows to ServiceNow by documenting and explaining existing OO logic.

Job Description or Responsibilities

Flow development in OO Studio

• Design, build, and maintain flows and subflows in OO Studio (and OO Workflow Designer where used), covering inputs, outputs, results, transitions, and responses.
• Develop custom operations using Java, Python/Jython, PowerShell, SSH, SQL, and HTTP/REST operations.
• Build reusable flows and operations, and apply consistent naming, structure, and versioning standards.
• Configure system accounts, system properties, selection lists, and configuration items securely, avoiding hard-coded credentials and environment values.
• Build robust error handling, retries, timeouts, and logging into flows so failures are clear and recoverable.
• Automate IT processes such as user provisioning, server and cloud operations, patching, monitoring remediation, and service request fulfillment.

Content packs

• Develop, package, and version custom content packs, and manage dependencies on OpenText base and integration content packs.
• Upgrade out-of-the-box content packs, test impact, and fix broken flows after upgrades.
• Promote content packs across dev, test, and production through OO Central, following the team's release and change process.
• Manage content in source control (Git/SVN with OO Studio SCM integration).

Integrations

• Build integrations between OO and enterprise systems, such as ServiceNow, Active Directory/Entra ID, VMware, monitoring tools, databases, and ticketing systems.
• Build and consume REST/SOAP APIs, including authentication (OAuth 2.0, basic auth, API keys, certificates).
• Configure and maintain Remote Action Servers (RAS) and worker groups for executing operations across network zones.
• Support triggers from other systems, for example SMAX processes, monitoring alerts, or schedules, and make sure results flow back correctly.

Full-stack development

• Develop backend services and scripts (Java, Python, PowerShell) that support automation.
• Build or maintain simple web front ends, APIs, or dashboards that start or report on automations where needed.
• Work with databases (SQL Server, Oracle, PostgreSQL) for OO data, reporting, and integration logic.

Operations (run)

• Monitor flow runs, schedules, RAS health, and OO Central, and act on failures before users are affected.
• Troubleshoot failed or stuck runs using run logs, debugger, and step-level details.
• Resolve L2/L3 incidents for the automations the team owns, within SLA, and turn permanent fixes into backlog items.
• Take part in the team's on-call or support rotation.
• Support OO platform upgrades, patches, and certificate renewals together with platform administrators.
• Maintain runbooks, flow documentation (purpose, inputs, dependencies, owners), and known-error records.

Migration support

• Document existing OO flows and integrations clearly, so the ServiceNow team can assess and rebuild them in Workflow Studio and IntegrationHub.
• Work with ServiceNow developers during migration waves, explaining flow logic, dependencies, and edge cases, and supporting side-by-side testing and cutover.
• Help decommission flows and content packs once replacements are live.

Qualifications Experience and qualifications

• 4 to 8 years in software development or automation engineering, with at least 3 years of hands-on OpenText (or Micro Focus/HPE) Operations Orchestration development.
• Deep experience with OO Studio: flows, subflows, operations, system accounts and properties, and debugging.
• Proven experience building, packaging, and deploying content packs, and upgrading OpenText content packs.
• Strong scripting and programming skills in Java, Python/Jython, and PowerShell, plus SQL.
• Strong integration experience with REST/SOAP APIs, JSON/XML, and authentication methods.
• Experience with OO Central administration basics and Remote Action Servers.
• Good knowledge of infrastructure: Windows and Linux, Active Directory, networking basics, virtualization, and cloud platforms.
• Experience troubleshooting production automation and doing root-cause analysis.
• Experience with source control (Git) and working in Agile DevOps teams.
• Understanding of ITIL processes, especially Request Fulfilment, Incident, and Change.
• Bachelor’s degree in computer science, Engineering, or a related field.

Additional Information Certifications

• Preferred: OpenText (Micro Focus) Operations Orchestration training or certification; ITIL 4 Foundation.
• A plus: ServiceNow Certified System Administrator (CSA) or Certified Application Developer (CAD), useful given the migration to ServiceNow; a cloud associate certification (AWS or Azure).

Nice to have

• Experience with OpenText Service Management (SMAX) Studio or Hybrid Cloud Management (HCMX).
• Experience with ServiceNow Workflow Studio or IntegrationHub.
• Experience with other automation tools, such as Ansible, Terraform, or RPA platforms.
• API testing tools such as Postman.