Technical Architect

Sopra Steria is one of the largest players in the tech industry in Europe, known for its consulting, digital services and software development. We operate in nearly 30 countries in the world, hiring more than 55,000 employees. The Polish branch, as the Global Delivery Center, operates in Katowice since 2007 and has been growing ever since. Currently, our team consists of around 1,000 specialists. Within the Digital Platform Services department, our teams specialize in areas such as cloud, operating systems, virtualization, databases, backup or storage, as well as networking and security. We also have 1st line support consultants who speak French and English, but also Italian, Spanish, Portuguese and German. The Application Services department is responsible for areas such as software development, data engineering, testing services, CRM, ITSM and ERP platform integrations, as well as application management for customers in Scandinavia, Benelux, France, Germany, Switzerland and the UK. Job Description 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 have 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 Qualifications Must have requirements: At least 4 years of experience in solution and integration architecture for distributed platforms (APIs, event‑driven integration, IAM, security controls). Hands‑on experience with at least two of the following: IAM (Keycloak or equivalent), data sharing/connector concepts (EDC familiarity is a plus), policy modelling, cloud‑native platforms (Kubernetes), and DevSecOps practices. Ability to work across multiple organisations and teams, balancing governance, security, and delivery pragmatism. Knowledge of catalogue and discovery engineering, including metadata modelling, lifecycle management, and discovery workflows. Knowledge of catalogue and discovery engineering search and discovery pattern, including query translation/adaptation, relevance constraints, and policy‑aware filtering. Knowledge of catalogue and discovery engineering connector architecture, including control‑plane vs data‑plane separation, asset registration, and policy‑gated