Context
CURIA — the Court of Justice of the European Union in Luxembourg — runs case-processing applications (SIGA, DGM) on Pega. On the TITAN-Middleware project I am responsible for keeping that estate healthy across four environment stages, from development through production, inside one of the strictest governance regimes in Europe.
Challenge
An EU institution cannot tolerate unplanned downtime, unaudited deployments, or unpatched vulnerabilities. The work is not building screens — it is the discipline underneath: deployment integrity, incident response, security advisories, and documented change.
What I do
- Environment management of the SIGA Pega estate over Dev, INT, QUA and PRD — resolving server connectivity and authentication failures, and streamlining application deployment.
- Deployment audits & SDLC compliance: auditing SIGA and DGM deployments and reporting compliance findings to the Change Manager.
- Change management: coordinating and executing RFC implementations under the Court’s formal change process.
- Security: identifying CVE vulnerabilities affecting the platform stack and handling security advisories conform governance.
- Knowledge base: extensive Confluence documentation of incident-resolution processes and deployment-history analyses for audit purposes.
Stack: Pega Infinity 24.1, Dev/Admin Studio, Deployment Manager, Pega PDC, WebLogic, PostgreSQL, Linux, Zabbix monitoring, Jira/Confluence, Azure DevOps, Git.
Outcome
Stable, audit-ready SIGA and DGM environments — and a working demonstration that I operate as comfortably in platform governance (deployments, security, change control) as in application development. This is the operational context most decisioning and platform programs at banks and governments actually run in.
Details limited to CV-public level; no screenshots of court systems.