> Markdown version of [/jobs/ext/4593293-staff-system-architect](https://www.wearedevelopers.com/jobs/ext/4593293-staff-system-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Staff System Architect

- **Company:** SIEMENS, S.A.
- **Location:** Valencia, Spain
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Amazon Web Services, Audit Trail, Big Data, C Sharp (Programming Language), Cyber Security, Databases, Data Architecture, Data Stores, Distributed Systems, Identity and Access Management, Python (Programming Language), Key Management, Role-Based Access Control, Software Engineering, Systems Architecture, TypeScript, Workflow Management Systems, Openapi, Rust (Programming Language), Kotlin, Event Driven Architecture, Terraform, Webhooks, Serverless Computing, Golang
- **Published:** November 6, 2026
- **Apply:** https://www.adzuna.es/details/5954169758

## About the Role

* Experience: 10+ years in software engineering and architecture, including owning architectures across multiple systems and taking systems from design to production.
 * Architecture practice: ADRs, C4 or similar models, threat modeling, capacity planning, and proof-of-concept-led build-versus-buy analysis.
 * Distributed systems and integration: event-driven design, workflow orchestration, resilience patterns (idempotency, retries, sagas, outbox, CDC), and versioned REST/OpenAPI contracts.
 * Data architecture: selecting relational, document, graph, search, and analytical stores; large-scale data modeling, retention, and classification.
 * Security architecture: RBAC/ABAC, identity federation and SSO, least-privilege IAM, secrets management, and auditability.
 * AWS and operations: cost-aware multi-service AWS designs with Terraform or CDK; SLOs, observability, incident response, and non-disruptive migrations.
 * Hands-on engineering: production experience in at least one of Go, Java, Kotlin, C#, Rust, Python, or TypeScript.
 * Technical leadership without authority: guide architects and engineers, resolve cross-team design disputes, and build agreement through clear reasoning and excellent written and spoken English.

## Description

* Architect enterprise-scale greenfield systems and evolve existing architectures to meet stringent service-level agreements for availability, performance, and reliability.
 * Connect many enterprise systems including systems you do not own and cannot change into one coherent, trustworthy platform.
 * Keep product-security attributes accurate and current across a large, continuously changing estate of products and components.
 * Enforce consistent identity, access, and data-boundary controls across systems, so that trust and auditability hold at scale.
 * Evolve live systems toward the target architecture without stopping them, while balancing performance, resilience, and cloud cost.
 * Align architects, engineers, and system owners on decisions without formal authority over them., * Own the target architecture and the roadmap from today's landscape to it, including migrations and cutovers for systems that cannot be switched off.
 * Translate enterprise architecture into system architecture: partner with the Principal Key Expert Enterprise Architect to turn enterprise-level capabilities, principles, and target states into concrete, implementable system designs, and feed system-level constraints and trade-offs back into the enterprise architecture.
 * Design component and data architecture: decompose the platform into well-bounded serverless functions, containerized services, and managed cloud services; select and model databases and storage.
 * Define APIs and integration interfaces: design synchronous request/response, push-based events and webhooks, pull-based polling and batch synchronization, and streaming, with clear ownership, contracts, and SLAs.
 * Define boundaries and contracts: decide which system owns which data and decision, and make the interfaces between systems explicit and versioned.
 * Architect security and identity: role and permission flows across systems, data-boundary controls, threat modeling, and audit evidence by design.
 * Set and meet non-functional targets for performance, availability, scale, and cloud cost; choose data stores and justify each choice.
 * Make and record decisions: drive build-versus-buy calls, maintain architecture decision records, and keep documentation trustworthy.
 * Lead technically across teams: review designs and technical decisions of architects and engineers, prototype risky parts yourself, and explain the architecture to engineering, security, and management.