Project description The vehicles are now an integral part of the connected world as "mobile devices". By intelligently linking driver assistance systems and mobile online services, new business models can be developed that last throughout the entire life cycle of a vehicle model. Our goal is to increase customer satisfaction and enthusiasm through comfort and efficiency while driving. This is achieved primarily through the integrative use of infotainment, social network and security functions. The driver and passengers should always have the best possible driving experience and depending on the situation. As part of any vehicle-related project the location of new functionality must be defined including all communication between SW Components and ECUs. Within an ECU the Software must be part of a SW stack that meets the requirements of the desired functionality. This includes but is not limited to topics such as Privacy behaviour, Power Management and Startup requirements. Responsibilities Creation of architectural concepts for a (new) functional description. The documentation takes place on a Confluence page. Starting with a draft/brainstorming, there is constant development until a concrete functional architecture has been developed. The implementation of this functional architecture is not part of the specifications Creation of architecture documentation using the tools set for the specific Software Program. These tools may include standard SW such as Enterprise Architect. The documentation must include the following information which will then be aggregated into an Architecture Definition Document (ADD): * High Level Architecture Diagram * Use Cases Diagram * Component Diagram * Interface Diagram * Sequence Diagram * Technology Architecture Carrying out various architectural coordination with functional partners (internal and external) and system suppliers: * Architecture handover to the function owner for further processing * Planning, preparation and implementation of architectural workshops/appointments with other architects, for architectural reviews and know-how transfer * Regular coordination with E2E architects All architectures must be created taking into account the following criteria: Use of existing technical conditions such as supplier systems or technical resources. Consideration of the current state of technology: The ability to innovate is essential for existing functional architectures in order to keep up with changing times. The challenge is to combine old, historically grown systems with new technologies, such as the vehicle architecture requires. Skills Must have Expertise in field of System and Software Architecture Good experience with Non-Functional requirements including but not limited to Security (incl. Encryption), Performance, Scalability etc. Strong ability of creating precise requirements with high quality Service Oriented Architecture concepts Automotive communication protocols and APIs (CAN, Ethernet, Restful API, MQTT) Online Remote Update (ORU / OTA) use cases Automotive Engineering System Architecture SySML Programming Skills Experience with Stakeholder Management Fundamental knowledge of Adaptive AUTOSAR Nice to have German language Other Languages English: C1 Advanced Seniority Regular