Archiviertes Projekt - min. 50% remote: IaaS Architect (m/f/d) private cloud environments

For a client in the energy sector we are currently looking for an IaaS Architect (m/f/d) private cloud environments

Start: 01.05.2024
Duration: Long term
Capacity: 100%
Location: Remote and Berlin
Remote share: At least 50%, probably more remote possible
Language: English (must), German (nice to have)

PLEASE NOTE THAT EXPERIENCE IN PUBLIC CLOUDS (AZURE, GCP, AWS, ETC) IS NOT RELEVENT FOR THIS
ROLE. THIS IS A PRIVATE ON-PREMISES CLOUD BUILT FROM THE GROUND UP

Position Description:
The infrastructure product group offers data center services that are provided via a software stack for other
product lines within the program. The IaaS Architect is member of the Infrastructure Architecture team.
The architect is responsible for aligning with the strategy and vision of the Lead Infrastructure Architect and
with other architects in the group (i.e., lead, network, storage, compute, observability, security).
The IaaS Architect is responsible for architecture of the infrastructure wide IaaS platform of which provides an
fully automated internal platform for the core underlying infrastructure (network, compute, storage, security,
observability) and a fully automated platform for customer through a REST first approach.
The IaaS platform delivers software solutions for customer products in line with architectural strategy provided
by the lead infrastructure architect. The IaaS platform consists of multiple layers from customer facing to
infrastructure facing, between these layers the platform is built with a modular approach providing deeper layer
abstractions and well-defined interfaces between each of the layers allowing the building blocks to be easily
changed or modified. The architect does this in conjunction and through consultation with the other
infrastructure technology architects and the lead Infrastructure Architect.
The EDP project is in a startup mode and requires that architects are also engineers, meaning that the architects
can understand engineering problems and solutions within their architecture space. They are also expected to
be able to provide POCs of their solutions working alongside technical engineers to prove solutions are viable.
The architect must also be cost conscious, have an holistic approach and be aware of what the impact of the
solution is short term and long term to both overall strategy, engineering and customer products.
Within the Infrastructure product line, the engineering target is to be fully automated throughout any internal
or external product lifecycle. The goal is to build a fully automated environment where all steps after physical
installation will be automated. Therefore, the architects and engineers require the ability to align with the IaaS
team who implement the steps to automate the environment.

Targets in that Position
The architect has the responsibility for their technology domain which incorporates the end to end lifecycle of
the solutions from hardware to software and where required custom solutions (i.e. code) to deliver the required
results. The architect is responsible for the solution lifecycle, therefore being responsible for ensuring the
solution is correctly deployed by the engineering team. The architect is not responsible for engineering delivery
but is responsible for ensuring the architecture is adhered to and resolving design issues fed back from
engineering.
Architecture solutions are expected to be provided end to end providing a full solution even where this must be
coordinated with other architects or software engineering. Where gaps are apparent is up to the architect to
figure out how to correct this but holistically and not in a point solution manner.

The IaaS Architect is responsible for the following technology areas.
ICE (Infrastructure Cloud Engine) is the IaaS stack which is 80% custom inhouse developed software, this
software provides the northbound customer API interface and orchestrates the customer requests to manage
the resources (Network, Compute, Storage, PKI, DNS, etc.) requested. ICE is built from a stack of modules where
sub-teams work on different layers of the stack. The ICE stack also provides similar functionality for internal
usage for example, automated compute builds, asset management etc.). The IaaS architect (as stated) works
with the other technology architects to understand what is required to be delivered.

Profile Requirements
This is a senior architectural role, therefore the individual must have and at least 7 years working in the
specified technology area, and able to demonstrate this experience along-side demonstrating real world
experience of the entire life cycle of products and/or resources.
This is the lead software architecture role and the successful candidate will be responsible for the evolution of
the architecture towards a large and distributed infrastructure delivery system that will span 100’s locations,
proven software architecture capability is a MUST.
The individual must have the experience to think at a holistic level to ensure the work provided encompasses a
forward view to enable solutions to be built upon with minimal disruption upstream or downstream, therefore
understanding not just the core competency but surrounding aspects / technologies to ensure the architectures
fit into the overall strategy.

Must-have competencies / skills (must have unless otherwise noted)
? Proven architectural experience in large projects and private cloud environments
? Modular & Distributed Software Architecture
? Highly Available Systems Architecture
? Distributed Service Architecture (API, Messaging)
? Sequenced & Dependency Based Distributed Task Management
? Plugin Frameworks for Multiple Use Cases / Deployment Requirements
? Graph Modelling / Design
? HTML UI Architecture
? K8s Application Development
? K8s Operator Development
? Python
? GoLang
? Celery
? RabbitMQ
? Pydantic Models
? ArangoDB
? REST APIs (FastAPI)
? IAM / OAuth
? Prometheus, Loki, Grafana
? Fluent English in speech and writing (at least C1)

Preferred competencies / skills (should have unless otherwise noted)
? Understanding of physical datacenter infrastructure
? Understanding of basic datacenter concepts (VRF, VLAN, VXLAN, Hypervisors, Firewalls, Storage)