Senior Engineer

Project overview

Three reasons why this is your assignment:

Because as a senior DevOps engineer, you don't just want to build, but also understand what problem you are solving and for whom.

We offer you a key role in the migration from IBM Content Manager to OpenText, where you combine change and run and achieve directly visible results together with the team.

You can use your experience to reduce complex domain and business issues to clear, testable backlog items and then help build and test the solution yourself.

You do it:

The assignment:

As a senior DevOps engineer, you help ensure the progress of the migration from IBM Content Manager to OpenText, while maintaining the continuity of the current Document Management System (DMS).

The main bottleneck is not just in development capacity. Too much time now elapses before actual development and testing can begin. Problem, business context, and business rules are not always sufficiently clear in backlog items in a timely manner, causing discussions to take a long time and items to be ready late.

At the same time, an experienced functional designer with a lot of domain knowledge of the DMS will leave shortly. You help land this knowledge with the team, without taking over the role of functional designer yourself.

You therefore combine two qualities: you are an experienced engineer who builds, tests, and manages yourself, and you are able to quickly reduce complex problems to a clear and testable issue together with the Product Owner and the team.

Responsibilities

You:

You are responsible for:

You will be given the space to ask critical questions from your seniority, to model, to test technical and functional assumptions, and to propose improvements in development, testing, and management processes.

Product prioritization and roadmap remain the responsibility of the Product Owner. Supplier and project management fall under project leadership.

Scope:

This is explicitly not an assignment for a functional designer. You do not write detailed functional or technical designs for the team. You help clarify the problem, the context, business rules, solution direction, and test approach. The team jointly makes the final design, with you as a senior engineer contributing conceptually while also building and testing yourself.

This combination is precisely what is important: we want to prevent technical solutions from being conceived solely functionally without a direct link to buildability, testability, and manageability.

Furthermore, the assignment is not a one-to-one replacement for the departing functional designer. It is a temporary bridge to ensure continuity and structurally embed the capability within the teams.

• build and test the migration to OpenText, the necessary integrations, and components on OpenShift;
• fully participate in the DevOps responsibility for change and run, including incidents, vulnerabilities, and operational management;
• map domain knowledge, business context, and business rules together with the Product Owner, so that it is clear what problem is being solved, for which users, and within what constraints;
• help the team make backlog items ready in a timely manner, for example by modeling together and separating main and secondary issues;
• make interests and dependencies between different user systems transparent, so that choices are not solely determined by the party that shouts the loudest;
• help develop a test approach that can demonstrably confirm that the original problem has been solved;
• substantiate assumptions with measurements and facts where possible;
• obtain domain knowledge from the departing functional designer in a targeted manner and do this as much as possible with other team members, so that this knowledge is broadly shared within the team;
• improve testability and maintainability by making automated tests part of the CI/CD pipeline.
• contributing from an engineering perspective to getting backlog items ready on time;
• actively acquiring, clarifying, and sharing relevant domain knowledge and business rules;
• delivering working, tested, and maintainable software within the agreed DevOps methodology;
• shaping a suitable technical solution and test approach together with the team;
• contributing to the continuity of the existing DMS during the migration;
• increasing the team's independence in answering domain questions and making their own design.

Requirements

You have extensive, demonstrable experience as a senior DevOps or software engineer.

You have extensive experience with Java 17 or higher, Spring Boot, and API development.

You have experience with OpenShift and container-based environments.

You have experience with test automation and CI/CD, preferably with Jenkins.

You have experience with Jira and Confluence.

You have demonstrable experience with the full DevOps responsibility: you build, test, and manage yourself.

You have experience with both change and run work in a business-critical environment.

You are able to understand complex business rules, dependencies, and system interactions and translate them into clear, testable backlog items together with the Product Owner and team.

Wishes:

It is a plus if you have experience with one or more of the following topics:

data migration projects;

Azure;

document management or ECM platforms, especially OpenText;

complex landscapes with multiple user systems;

functional design, where you use that experience within a multidisciplinary DevOps team without taking on the classic role of functional designer yourself.

Competencies:

Analytical ability: you ask questions until the actual problem is clear and you can separate main from secondary issues.

Collaborative: you actively seek collaboration with the Product Owner, developers, testers, and other stakeholders and bring different perspectives together.

Decisiveness: you prevent analysis from becoming an end in itself and help the team quickly move from discussion to buildable and testable work.

Knowledge transfer: you do not make yourself indispensable, but consciously ensure that knowledge is shared among multiple team members.

Environmental awareness: you recognize the different interests of users and stakeholders and make them explicit without automatically optimizing for the party with the loudest voice.

Ownership: you feel co-responsible for both production operation and the progress of change.

-When offering a candidate for the above request, a sub-contracting arrangement is not allowed. The candidate must be employed by your organization. If there is an extra link in the chain, we will not consider your offer and will reject it immediately.

-A valid VOG (Certificate of Conduct) is required upon deployment; starting earlier is not possible.

Additional information:

When you, as a supplier, offer a professional to us and they are placed, we will need information from you as a contracting party, including regarding the Chain Liability Act (Wet keten- en inlenersaansprakelijkheid).

The purpose of the 'WKA' is to prevent abuse in the remittance of payroll taxes at all links in the chain, from supplier to client. We cover these risks for our clients by using a blocked account, the G-account. This is an account to which a portion of the invoice amount is deposited, from which you can pay payroll taxes and VAT to the Tax Authorities. The percentage to be deposited depends on whether you have a SNA certification (NEN-4400-1 or NEN-4400-2) and whether your company is located in the Netherlands or abroad. You can apply for the G-account from the Tax Authorities.

If you cannot obtain a G-account (and you can provide proof of this from the Tax Authorities), you also have the option to provide an accountants' report (assurance report regarding personnel lending) every quarter. In this report, a certified accountant (AA or RA) will issue a statement about the accuracy, completeness, and timeliness of the remittances. Please note that the costs for this report are at your own expense.

Project details

• Start: 2026-11-01T23:00:00
• Location: Amstelveen Noord-Holland, NL
• Languages: Dutch