Misiune
We are seeking a Vehicle Feature Requirements Engineer to join our team on behalf of our Client. In this role, you will lead the end-to-end lifecycle of technical requirements, translating complex stakeholder needs into clear, scalable automotive features.
Key Responsibilities
Requirements Ownership: Own the creation, authoring, review, approval, baselining, maintenance, and status tracking of requirements throughout the product lifecycle.
Requirements Analysis: Analyze requirements to ensure they are clear, complete, consistent, feasible, unambiguous, testable, traceable, and aligned with program objectives, architecture constraints, applicable standards, and customer expectations.
Stakeholder Alignment: Facilitate cross-functional requirement reviews and resolve gaps, conflicts, assumptions, and interface dependencies with global stakeholders while developing and applying consistent requirement-authoring standards and best practices.
Feature Definition & Tailoring: Lead the definition and decomposition of customer and stakeholder needs into platform-level functional and non-functional requirements for new features. Tailor and manage approved platform requirements for program-specific applications, documenting justified deviations and maintaining alignment with the global feature intent.
Customer-Centric Inputs: Use competitive benchmarking, voice-of-customer clinics, field insights, and stakeholder feedback to identify customer needs and convert them into measurable requirement inputs and acceptance criteria.
Traceability & Change Control: Maintain bidirectional traceability from customer needs and requirements through system, subsystem, software, hardware, and validation requirements; assess requirement changes for technical, timing, cost, compliance, and validation impact; and manage changes through the approved review and change-control process.
Validation & Compliance: Partner with validation teams to define acceptance criteria and verification methods, confirm requirement coverage, support issue resolution, and ensure applicable safety, cybersecurity, regulatory, and industry requirements are incorporated and documented.
Profil
Basic Qualifications:
Education: Bachelor of Science in Electrical, Mechanical, Software, or Systems Engineering (or equivalent) from an ABET-accredited university.
Experience: 1–5 years of automotive product-development experience, including responsibility for requirements definition, authoring, analysis, review, or lifecycle management.
Communication: Strong written and verbal communication skills, including the ability to write precise technical requirements, facilitate cross-functional reviews, and explain technical content to non-technical audiences.
Project Delivery: Demonstrated ability to coordinate requirement deliverables, manage priorities and dependencies, drive decisions, and meet program milestones across multiple cross-functional teams.
Systems Engineering Knowledge:
Working knowledge of automotive systems engineering, including functional decomposition, interfaces, architectures, and the interaction of software, hardware, network, and physical components.
Knowledge of INCOSE-aligned requirement engineering practices (elicitation, decomposition, allocation, analysis, traceability, verification, validation, and change management).
Standards & Regulations: Working knowledge of ISO 26262 and its implications for safety-related requirement definition, allocation, traceability, and verification. Ability to interpret regulatory requirements, standards, and industry best practices.
Preferred Qualifications:
Advanced Degree: Master of Science in Electrical, Mechanical, Software, Systems Engineering, or a related discipline from an accredited university.
Tools: Experience using IBM Engineering Requirements Management DOORS Next Gen, IBM DOORS, or a comparable requirements/application lifecycle management tool.
Domain & Architecture Expertise:
Experience applying systems engineering methods to complex automotive features.
Experience interpreting system architecture and network topology diagrams to identify interfaces, dependencies, data flows, and requirement allocations.
Knowledge of at least one automotive functional domain (e.g., body, chassis, electrical, propulsion, interior, infotainment, connectivity, or ADAS).
Ability to analyze issues across software, hardware, network, vehicle, validation, manufacturing, and field domains to determine associated requirement gaps or changes.
