Associate SE Lead

1.Purpose Systems Engineer - RnD (referred to as Systems Engineer in this document) plays a critical role in defining, implementing, and validating systems (i.e., products & services) during new development as well as product change management. Systems Engineer collaborates with multiple subsystem teams, to develop overall technical solution and ensure that subsystems are consistent at system level. Systems Engineer is responsible product to meet systems requirements. Systems Engineer actively collaborate with product managers, architects, and program managers. As a technical expert, contributes to planning, risk, and issue management at system level. 2.Responsibilities and key activities This section includes the responsibilities and key activities that the Systems Engineer is either accountable for, or responsible to execute. Responsibilities and key activities General Accountable for ensuring overall system level technical consistency. Responsible for advising and guiding the teams on technical risk assessments, Corrective Actions (CAs), simulations, root cause analysis and incident investigation. Interface management Accountable for governing the interfaces within a system which are not critical from integration and business point of view. Responsible to refer Interfaces which affect system architecture (system level, cross-category, and category level) to Systems Architecture Management (SAM) governance, who has decision making authority on such critical interfaces. Accountable to ensure that Interfaces within responsibility are defined as per the system level requirements, and the corresponding Interface requirements are properly documented and maintained in relevant KONE tools. E.g., In case of elevator and escalator platforms, systems engineers are accountable for interfaces that are not managed in the system architecture management process. (Criteria on how the interfaces are categorized in or out of SE responsibility, are part of the applicable product development processes). New product development initiatives Accountable for technical system requirements creation and their change management. SEs play the process roles, as a technical expert from system point of view, e.g., as member of extended Core team of development projects Accountable and responsible for requirement decomposition and allocation to component and subsystem level, based on the requirements and specifications defined by product manager, architect and other stakeholders. Accountable for creation and execution of system integration plan and system Verification & Validation plan. Contributes to review component and subsystem level Verification & Validation plans. Lifecycle management of products Accountable and responsible for Interfaces checks during product change management e.g., Change Requests (CRs). Accountable for creation and execution of system integration plan and system Verification & Validation plan. Develop Capabilities SE develops Systems Engineering competence, shares know-how within SE community. Contributes to optimization of processes (e.g., instructions, guidelines for efficient use of tools for Interface and Requirements mgmt.) Product roadmaps and prioritization Contributes to product roadmaps and portfolio prioritization, leveraging deep knowledge of the products and their engineering. 3.Performance measures Performance measures Quality of Projects and Releases Technical Solution at system level (e.g., FYCOR, EFR) # of CRs verified for system interface check # of System level Corrective Actions # of System Level requirements #Verification and Validation Coverage at System Level 4.Competence profile 4.1Behavioral competences Customer Perspective (KONE Leadership Competences) Takes customer´s perspective and focuses on those activities which are critical to customer satisfaction. Keeps up-to-date on current developments in the industry and constantly seeks opportunities for improvement. Impact and Influencing (KONE Leadership Competences) Communicates with confidence and clarity, identifies, and breaks down barriers to open communication. Considers and builds on others ideas. Innovation and creativity (KONE general competences): Produces original ideas. Looks at problems from new angles. Seeks out new and innovative ways of approaching situations or tasks. Conceptual Thinking (KONE general competences): Recognizes patterns and trends. Demonstrates an understanding of information in its broader context. Applies concepts and theories to practical situations. Generates theories and conceptual models to explain relationships between information. Simplifies complex information into a single, clear concept. Collaborating (KONE general competences): Shares information widely. Treats others with dignity and respect. Respects different needs and viewpoints. Creates trust and a sense of team spirit. Maintains confidentiality and holds to agreements. Admits own mistakes. Obtains co-operation by active listening and sensitivity towards situations and people. Establishes strong working relationships and effective internal and external networks. Achieves consensus, closes deals or discussions with clear understanding of agreement. Analysis and problem solving (KONE general competences): Distinguishes between important information and irrelevant or minor details. Analysis information in a logical and systematic way. Identifies the cause or causes of a problem. Proposes practical solutions to address identified problems. Explores a range of possible solutions. Judgement (KONE Leadership competences): Draws upon a wide range of information to make well informed decisions even when faced with ambiguity and uncertainty. Simplifies complex information to clear concepts and solutions. Stands by decisions and takes responsibility for them. 4.2Professional requirements System thinking – capability to understand complex systems, their dynamics, and interactions, and break them down to actionable inputs to different stakeholders. Experience and knowledge of Systems Engineering practices for physical and/or digital products: Requirements Engineering Interface mgmt. System architecting Awareness of “Design for X” methodologies Integration and implementation Verification & validation Systems modelling and analysis Knowledge of applicable patents on the specific subject matter expertise 4.3Entry-level requirements . or equivalent. Minimum design work experience at least in one main technology area Systems Engineer 1: 2 - 3 years Senior Systems Engineer 2: 3 - 5 years Systems Engineer (KG 4): 7 - 10 years Practical knowledge of professional SE work English language knowledge Working in global cross-functional teams and suppliers 4.4KONE specific issues – always need to be trained Fundamentals of elevator, escalator and smart building industry including the digital solutions. KONE engineering practices and tools Knowledge of the technology architecture of KONE physical products and interfaces to digital solutions Knowledge of relevant KONE Way processes and tools Knowledge of major stakeholder requirements Knowledge of industry related codes & standards Knowledge of applicable Safety processes At KONE, we are focused on creating an innovative and collaborative working culture where we value the contribution of each individual. Employee engagement is a key focus area for us and we encourage participation and the sharing of information and ideas. Sustainability is an integral part of our culture and the daily practice. We follow ethical business practices and we seek to develop a culture of working together where co-workers trust and respect each other and good performance is recognized. In being a great place to work, we are proud to offer a range of experiences and opportunities that will help you to achieve your career and personal goals and enable you to live a healthy and balanced life. Read more on