Laufzeit:<\/b> 01.03.2026 - 31.12.2026
Volumen:<\/b> 600 Std. remote / 200 Std. onsite/ 20 Std. travel
Einsatzort:<\/b> Remote / München<\/div><\/div>The consultant
should be based within 100km of Essen and be available to work onsite at the
client on request.<\/span><\/span>
<\/p><\/div>
Project Description
<\/h3>- Implementation engagement to build the first on‑prem frontend/backend solution, based on the refined architecture and stepwise plan defined by the Solution Architect.
<\/li> - Design and implement a running single‑node PoC on an on‑prem server, focusing on the application layer (backend and frontend) within the provided infrastructure and deployment patterns.
<\/li> - Develop the central application components that expose device data and workflows to users and external systems, including data ingestion from Modbus and non‑Modbus devices, transformation/normalisation and persistence in the platform’s time‑series and relational data stores.
<\/li> - Implement a secure, token‑based access model for APIs and UI, integrated with the customer’s identity landscape (e.g. Keycloak and LDAP/OpenLDAP, or comparable solutions), and aligned with the architecture’s security guidelines.
<\/li> - Ensure that the implemented application components are observable (metrics, logs, traces) and support the operational needs of the platform, including the continuous 1 Hz device read/write behaviour.
<\/li> - Collaborate closely with the DevOps Engineer, Solution Architect and internal stakeholders to deliver a stable, maintainable initial implementation and to support its evolution and rollout in cluster setups.
<\/li><\/ul><\/div>
Job Description
<\/h3>
The external consultant takes on the following tasks within the project, which are carried out independently:
<\/p>
- Take end‑to‑end responsibility for the implementation of the backend and the frontend, ensuring they follow the agreed architecture, coding standards and API/UI contracts.
<\/li> - Design and implement the application‑level behaviour for Modbus and non‑Modbus device integration, including periodic data acquisition, transformation and persistence into the chosen time‑series and relational data stores (e.g. InfluxDB v3 or an equivalent time‑series database, and Postgres or a similar relational database).
<\/li> - Design and implement the internal APIs and, where applicable, gateway layer so that frontend, backend application and external systems can communicate reliably, securely and in a way that supports the 1 Hz device read/write requirements.
<\/li> - Shape and implement the application‑level security model together with the Solution Architect and DevOps Engineer: integration with the identity provider (e.g. Keycloak or a similar IdP), token‑based authentication/authorization and role‑based access to APIs and UIs.
<\/li> - Ensure that the backend and frontend are observable: define and expose meaningful metrics, logs and, where appropriate, traces that support effective operations, troubleshooting and capacity planning.
<\/li> - Collaborate closely with the DevOps Engineer to ensure that backend and frontend are buildable and deployable in the target on‑prem environment, including suitable health checks, configuration patterns and environment handling.
<\/li> - Contribute to the definition and refinement of the domain model, data model and workflows (e.g. device configuration, pipelines, alarms) and reflect these consistently in APIs, backend logic and frontend screens.
<\/li> - Establish and maintain an appropriate level of automated tests (unit, integration and basic end‑to‑end) for the implemented backend and frontend, aligned with the project’s testing strategy.
<\/li> - Produce and maintain application‑level documentation (READMEs, API documentation, configuration notes, operational considerations) and feed back implementation experience into the overall architecture.
<\/li><\/ul><\/div>
Required Skills/Competencies
<\/h3>Skills
<\/h4>- Strong hands‑on experience with backend development in a modern programming language such as Python, Java, Node.js or Go, and with frontend development using a modern web framework such as React, Angular or Vue.
<\/li> - Experience designing and implementing REST APIs, including error handling, pagination and versioning concepts.
<\/li> - Experience building and running containerised applications using Docker (or a comparable container runtime), including multi‑stage builds, non‑root containers and health checks.
<\/li> - Familiarity with working in environments that use orchestration and service discovery tooling such as Nomad and Consul (or similar), including understanding how applications should expose configuration, discovery and health information from an application perspective.
<\/li> - Experience with time‑series and relational databases: e.g. InfluxDB (or an equivalent time‑series store) and Postgres (or a similar relational database), including implementing read/write paths and managing connection handling from the application.
<\/li> - Experience implementing authentication and authorization in applications: Keycloak or similar IdP (OIDC/OAuth2), basic understanding of LDAP/OpenLDAP integration, and applying RBAC and token validation in backend and/or gateway.
<\/li> - Familiarity with observability concepts and instrumentation (metrics, structured logging, tracing) and their use with tools such as Prometheus, Grafana and logging stacks.
<\/li> - Experience with industrial/IoT/OT protocols (especially Modbus over TCP) and device‑oriented data pipelines is a strong advantage.
<\/li> - Comfortable working in isolated on‑prem environments with limited or no direct internet connectivity.
<\/li> - Ability to write clear technical documentation and collaborate effectively with architects, DevOps engineers and internal developers.
<\/li> - At least 3 years of experience in backend or data engineering; frontend experience in addition is strongly preferred.
<\/li> - Experience with on‑premise deployments.
<\/li> - Language: English, German is a plus.
<\/li><\/ul><\/div>
<\/div><\/span>
