DevOps Engineer

The ideal candidate for this assignment is a Senior DevOps Engineer someone who can operate confidently in a complex, multi‑team platform environment and who enjoys building reusable, scalable services rather than one‑off features.

Freelance mission! 6 month rolling! Full time! 1 day onsite!

🧩 Core technical profile

The strongest candidates share a blend of backend engineering depth and platform‑level thinking.

• Backend-for-frontend expertise — able to design and implement a BFF layer that cleanly abstracts multiple backend platforms, normalises data, and exposes stable contracts to the frontend.
• Python proficiency — not just scripting, but building structured, maintainable backend services with clear API boundaries.
• DevOps maturity — comfortable with CI/CD pipelines, GitLab CI, containerisation, Kubernetes, DTAP environments, and release automation.
• Identity & access management — hands-on experience with OAuth2, OIDC, SAML; ideally familiar with eduID or similar federated identity systems.
• Security-first mindset — understands privacy-by-design, secure coding, and ISO27001‑aligned practices.
• Open-source contributor — experience working in transparent, collaborative, community-driven development environments.

🤝 Collaboration and mindset

This project requires someone who thrives in a multi-team, multi-stack environment.

• Consensus-driven — open to architectural choices made by other teams; able to align stakeholders.
• Proactive communicator — flags integration risks early, proposes solutions, and keeps teams aligned.
• Comfortable with ambiguity — can operate in a POC/MVP environment where experimentation (and failure) is expected.
• Reusable-by-default thinking — designs components and services that can support multiple future portals, not just NKPH2.

🛠️ Practical experience that stands out

Candidates who excel typically have worked in environments such as:

• Platform engineering teams building shared services for multiple products.
• Large-scale integrations where multiple legacy and modern systems must be unified.
• Education, research, or public-sector digital platforms where identity, privacy, and interoperability matter.
• Open-source ecosystems where transparency and collaboration are core.