We are looking for a Technical Architect to join the Sopra Steria Poland team responsible for a program that creates an open-source middleware platform. Its main goal is to support data access and interoperability in European data initiatives. It provides multiple compatible components, free to use, that adhere to a common standard of data quality and data sharing.
You will work with multi-party governance structures, heterogeneous technical stacks, and evolving EU-level standards and frameworks. Act as a solution and integration architect ensuring that Simpl-Open is applied consistently and effectively across three European initiatives with different domain constraints. Translate functional, governance, and non-functional needs into Simpl-Open-aligned architecture covering onboarding, publication and discovery, secure consumption, and operations.
Note that we can only offer cooperation to people who has EU citizenship, are located in Poland and are willing to commute to our office in Katowice Poland.
Responsibilities:
- Kubernetes literacy: deployment patterns, environment separation, configuration and secrets basics.
- Infrastructure-as-Code: Terraform and/or Crossplane; configuration management (e.g., Ansible) as applicable.
- GitOps and CI/CD patterns: release automation and environment promotion (Argo CD familiarity is a plus).
- Observability: logs/metrics/traces concepts; dashboards and alerting (Prometheus/Grafana, ELK/Loki patterns).
- Backup and restore readiness for platform components and operational continuity.
- Federated IAM: OIDC/OAuth2, identity provider federation, authentication federation, and attribute/role mapping.
- Mutual authentication and trust establishment: mTLS, certificate lifecycle basics, and governance-issued credentials where applicable.
- Security architecture fundamentals: least privilege, defence-in-depth, key management concepts, and secure communications design.
- Network security basics: segmentation, firewall/VPN concepts supporting secure exchanges.
- Architecture views per initiative: context, functional/logical, component, integration, and deployment views.
- Integration specifications: identity federation, policy model, connector and catalogue integration, interface contracts.
- Reference configurations and templates: IAM configuration patterns, policy templates, validation rules, onboarding guides.
- Operational playbooks: monitoring dashboards, alerting and log strategy, operational readiness checklists