Tags: Role-Description

The 3rdparty software manager is responsible for approving the use of thirdparty software and open source in PCP.

The 3rdparty software owner is responsible for monitoring and maintaining 3rdparty software and opensource used in the development of PCP products.

The architect has overall responsibility for defining and describing the architecture, as well as driving major technical decisions.

The CCC Ex technical representative covers the requirements from the China Compulsory Certification (CCC).

The cluster lead is a local role at a site, serving as a line manager who oversees a group of employees.

The configuration manager has the overall responsibility for the strategy, process, and implementation of the configuration management (CM) system.

The cyber security engineer is knowledgeable in productrelated security issues and assists other roles in writing cyber security requirements, assisting with secure design, secure coding practices, security testing of software for products or systems, and assisting the product maintenance, e.g., with vulnerability handling.

Development, quality assurance, and operations are key elements in DevOps. This concept includes the entire agile and lean culture, and at PCP R&D, we want to fully embrace this working paradigm.

The Ex component responsible (ExCR) has the responsibility for a specific Excertified module.

The Ex representative has the overall responsibility for the process of the Ex standard. In addition, the role coordinates the Ex certification.

The functional safety management (FSM) manager is responsible for ensuring that the R&D organization adheres to the applicable functional safety standards, such as the IEC 61508 or IEC 61511, for safetyrelated development and maintenance.

The hardware engineer (electrical/mechanical/logical) develops hardware solutions by ​analyzing requirements, designing, implementing, integrating, and testing hardware for products or systems.​

The “Head of \” is a management role with responsibilities for a stream and/or an organization. They are part of the PCP R&D management team and are reporting to the head of R&D and technology manager.

The Head of Development is responsible for the development and release of products and components in the development stream.

The Head of System is responsible for the integration and release of deliverables from development streams to customers.

Responsible for the production of products. Involved typically in items concerning production at manufacturers. This role does not belong to R&D. For more information please visit Onepoint Quality team

The intellectual property (IP) champion has an overall responsibility to set the IP direction for the stream, consistent with PCP's IP strategy and competitive positioning.

The L4 coordinator is responsible for monitoring and prioritizing the support case backlog. Securing that the support cases are assigned to L4 engineers and are the single point of contact for escalations within its assigned product area.

The L4 engineer evaluates issues together with L3 Support and identifies either a workaround for the customer problems or creates product defects to be added to stream and team backlogs for corrections in future releases.

The process owner is responsible for creating, sustaining, and improving a specific process and has the authority to make the required changes to achieve the objectives of the process.

The product owner (PO) is a team member responsible for defining and prioritizing epics and features in the backlogs as well as securing the quality of resulting deliverables.

The quality control manager (QCM) performs quality assurance activities on development and system streams, identifies quality issues, and ensures they are managed to closure. He/she coordinates the activities required to ensure that the quality meets customer expectations, required quality standards, and defined processes.

The release owners play an active role in managing releaserelated activities across all organizational functions within PCP. They ensure that release planning is both realistic and aligned with the program increments (PIs). These release plans are developed based on input from product management, architects, stream owners, and other key stakeholders throughout the PCP organization.

The safety engineer (SE) is responsible for ensuring that the R&D organization adheres to the applicable safety standards, such as the IEC 61508 or IEC 61511, and that safety is achieved and demonstrated for all safetyrelated [^1] development and maintenance.

The scrum master is a servant leader and coach for an agile team. They help educate the team in scrum, kanban, and lean, ensuring that the agreed agile process is followed.

The software engineer creates highquality software solutions (incl. FPGA) by analyzing requirements and designing, developing, integrating, and testing software for products or systems.

The stream owner has an overall responsibility to facilitate the lean and agile execution of the stream, facilitate the stream events (increment planning, synchronization meetings), and assist the teams in delivering value.

The technical coordinator is responsible for making sure the system architecture is followed and supports development streams and teams with technical knowledge.

A technical writer is a professional responsible for creating, editing, and maintaining technical documentation.

The test engineer develops tests (test cases, test methods, test applications), performs the tests, reports the test result, and verifies the symptoms of reported defects.

The test lead has the responsibility for planning, performing, and evaluating tests before a system or products are released.

The test manager oversees the planning, execution, and coordination of testing activities within a project or organization.

The user experience (UX) designer creates meaningful and relevant user experience within a product by understanding the user, analyzing requirements, ideating and verifying the suitability of different solutions, designing and developing wireframes as well as the final design, and making sure that the final implementation is up to required standard from a UX perspective.