For one of the EU institutions we are looking for a Platform Developer to join the team and contribute to both platform delivery and the evolution of the tool portfolio.

Offer:

  • B2B contract

  • Remote + occasional trips to Luxembourg

  • Rate: up to 500 EUR/MD

Our team manages approximately 40 tools supporting infrastructure lifecycle operations. The squad is currently delivering two strategic platforms — Cycloid (self-service infrastructure portal) and n8n (workflow orchestration engine) while maintaining and evolving a broader portfolio of legacy and modern tools.

Tasks:

  • Develop and maintain components for the Cycloid and n8n platforms (APIs,integrations, automation scripts)

  • Build CI/CD pipelines to support automated delivery of platform components

  • Develop new solutions to replace or reinforce existing tools in the PAT portfolio

  • Collaborate closely with Domain Architects, the Lead Developer, and the Lead Architect to deliver robust, maintainable solutions

  • Develop and maintain the CJ API (Go/Python) that serves dynamic form data and handles request lifecycle

  • Build and maintain n8n workflows and sub-workflows (transversal building blocks)

  • Develop Cycloid Stack Forms (.forms.yml) and associated handlers (Python)

  • Implement integrations between platforms (Cycloid ↔ GitLab, n8n ↔ CMS, n8n ↔ ServiceNow, n8n ↔ CMS)

  • Write and maintain automated tests for platform components CI/CD & Automation

  • Design, build, and maintain CI/CD pipelines (GitLab CI, Concourse)

  • Automate build, test, and deployment processes for platform components

  • Manage container image builds and promotion across environments (Dev → Acceptance → Production)

  • Implement GitOps practices for platform deployments (ArgoCD, Helm)

  • Analyse existing tools to identify replacement or improvement opportunities

  • Develop new solutions (APIs, scripts, integrations) to replace legacy tools or extend platform capabilities

  • Ensure backward compatibility during migration from legacy to new solutions

  • Document all developed solutions (architecture, usage, operational procedures)

  • Participate in code reviews and enforce coding standards

  • Write clear technical documentation for developed components

  • Support Domain Architects in developing their Cycloid stacks and n8n workflows

  • Contribute to the definition of development best practices and reusable patterns

Technical Skills

Required

  • Proficiency in Python (primary development language)

  • Experience with Ansible (playbooks, roles, automation)

  • Experience with CI/CD pipelines (GitLab CI, Jenkins, Concourse, or similar)

  • Experience with Git (branching strategies, merge requests, GitOps)

  • Experience with containers (Docker, Kubernetes/OpenShift)

  • Experience with REST API design and development

  • Familiarity with YAML/JSON configuration and schema validation

  • Comfortable with Linux command line and shell scripting (Bash)

Nice to Have

  • Experience with Helm charts and Kubernetes manifests

  • Experience with n8n or similar workflow automation tools (Airflow, Temporal, AWX)

  • Experience with PostgreSQL or other relational databases

  • Familiarity with Terraform or other IaC tools

  • Knowledge of OIDC/LDAP authentication and authorization

  • Experience with observability tools (Prometheus, Grafana, Dynatrace)

  • Experience working in a regulated or institutional environment

Soft Skills

  • Adaptable - able to switch between products and technologies as the squad's missions evolve. Nothing is permanent; priorities shift based on project needs and the team must respond accordingly

  • Reliable estimator - able to assess effort and time required for each assignment before committing delivery timelines to stakeholders

  • Transparent communicator - proactively flags potential delays and difficulties early, and regularly updates progress on development tasks

  • Autonomous and proactive - able to pick up a problem and drive it to completion

  • Team player- works well in a small squad, shares knowledge, asks for help when needed

  • Clear communicator - can explain technical decisions to non-technical stakeholders

  • Pragmatic - delivers working solutions, iterates, avoids over-engineering