Principal Software System Engineer

Requirements Management

• Requirements management (system and software level)
• Risk management
• System hazard analysis
• Software hazard analysis
• Fault tree analysis
• System of systems issues management/investigation
• Connected eco systems

MUST Have

• Requirements Management and Compliance: Write, maintain, and own system-level and software-level design inputs/requirements, ensuring compliance with established Quality Management Systems (QMS) and regulatory frameworks.
• User Needs Translation: Identify and capture user needs for digital applications, translating them into functional and non-functional system requirements.
• Architectural Contributions: Assist in establishing robust system and software architectures for digital applications, ensuring alignment with established design inputs.
• Risk Management: Lead ISO 14971-based risk analysis activities, from identifying inherent hazards to implementing effective mitigation strategies.
• Agile Execution: Enforce and support teams in executing Agile/Scrum planning, including estimating, scheduling, and completing committed tasks.
• Hands-On Testing: Conduct ad-hoc testing of in-development and developed software systems to ensure ongoing product quality.
• Issue Resolution: Lead/assist in technical investigations for field issues and product complaints with appropriate impact assessments on requirements and risks.

Good to have

• Driving Best Practices: Implement and champion best practices in software systems development and product lifecycles, utilizing Agile PDLC/SDLC and Systems Engineering methodologies in collaboration with development and verification teams.
• Technical Leadership: Provide guidance, mentorship, and technical leadership to a distributed R&D team, fostering a culture of innovation and excellence.
• Complex Problem Solving: Develop innovative technical solutions to complex software system challenges, delivering high-quality results within tight deadlines.
• Verification and Validation: Collaborate with verification engineers to define test strategies for system and software verification and validation plans, utilizing requirement tracing methods.
• Stakeholder Collaboration: Drive collaboration with internal and external stakeholders to enhance processes, practices, and technical mentorship, transforming software requirements into effective test architectures.
• Design Transfer Process: Interface with manufacturing, field service, operations, and customer training staff throughout the design transfer process.
• Compliance Assurance: Uphold compliance with the product development process and quality system standards.