Archiviertes Projekt - Domain Architect Observability (m/w/d)

Für unseren Kunden in Berlin (50%) und (50%) suchen wir einen Domain Architect Observability (m/w/d). The infrastructure product group offers data center services that are provided via a software stack for other product lines within the program. The Observability 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., network, storage, software architects).
The Observability Architect is responsible for architecture of the infrastructure wide observability platform of which provides observability (metric, events, alerting, remediation) for the core infrastructure technology teams - Network, Compute, Virtualization, Storage Security and Software, and for products provided to EDP
Infrastructure customers. The infrastructure observability platform must also integrate with the EDP wide observability platform which encompasses other EDP technical towers (k8s, DevOps, Data, IAM, etc). 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 a 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.

Weitere Rahmendaten
Einsatzart: Freelance
Auslastung: 100 %
Branche: Other

Your tasks
• Proven architectural experience in large projects and private cloud environments.
• 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 **
• Continuous Improvement and Adaptation: The architect actively validates the status of the environment in his responsibility and ensures to keep the architecture and engineering teams up to date. They actively work to and with the lead infrastructure architect, further reporting observations in case architectures do not deliver the required security standards.
• Effective Collaboration and Communication: The architect has the capability to transform business and technical requirements properly into architecture proposal, principles and downstream to engineering. They have an open mindset to collaborate within technical alignments.
• Self-Organization: The architect engineer has the capability to organize the work handed over according to prioritization and complexity. They track the status and actively reports risks, issues and expected delays. In case further information is required, he will actively investigate to find the relevant contact and start resolving the issue in line with the project guidelines.
• Process Integration: The architect follows the designed processes to achieve successful work and collaboration as well as detailed documentation.
• 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.
• As this is an architecture role, it is expected that the individual is self-motivating, in that they take it upon themselves (be proactive) to identify and/or research new ways of doing things, new technologies and inventing new ways to provide the required solutions and overcome technical challenges.
• 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 Observability Architect is responsible for the following technology areas.
• Infrastructure Core Metrics, events and alerting (Compute, Network, Storage, Security, IaaS)
• Customer Metrics, events and alerting.
• Security events, alerting and remediation.
• IaaS Metrics, Events and Alerting
• EDP wide observability integration
• Internal Infrastructure Observability Platform
• Customer Observability Platform
• QA Team / Testing Observability Platform

Must have competences
• Fluent English in speech and writing (at least C1)
• MUST understand and have proven experience with observability (metrics, events, logging, alerting) for physical data center infrastructure. i.e., network devices, compute platforms, storage platforms, security platform.
• Have extensive experience with various observability platforms.
• Able to provide solutions with both COTS, open source and custom solutions (code) to fulfil end to end requirements.
• OpenTelemetry
• At least 3 or more of
• nbsp;- Loki, Grafana, Prometheus, DataDog
• nbsp;- AppDynamics, DynaTrace
• nbsp;- ELK
• Reporting tools and customizing for specific audiences
• Integrations with custom written software (i.e .Python) exposing metrics, events and alerting
• Integrations with hypervisor platforms (KVM, ESXi)
• ML experience used as a forecasting technology for scaling infrastructure hardware based on usage stats/metrics.
• eBPF experience to extract traffic flow metrics and analyze potential issues (performance, security)
• k8s CNI knowledge (i.e., Cilium) to extract traffic flow metrics and analyze potential issues performance, security)
• Database knowledge to support observability platform data storage requirements (i.e., TimeSeries, Graph)
• SNMP
• Packet Analysis, IPFIX, sFlow
• KPI Reporting