Senior Automotive Systems Engineer – BCM & Architecture

Praxy

Kraków

Hybrid

PLN 180,000 - 280,000

Full time

25 hours ago

Be an early applicant

Application generator

Turn this role into an interview — a resume and cover letter built around what this employer wants.

Get past ATS filters

Benefits offered by this job

Hybrid work policy

Private health care and life insurance

Well-Being Program

Job summary

Aptiv in Kraków, Poland seeks a Systems Engineer to lead analysis and clarify requirements for BCM functions; you will create interfaces and acceptance criteria in Polarion and ensure traceability from stakeholder needs to implementation.

You will design system architecture in Enterprise Architect, assess change impacts, mentor engineers, and collaborate with OEMs across time zones. English fluency is required; occasional travel may be needed.

Qualifications

Master's degree in electronics, computer science, automation, telecommunications or a related field.
Practical experience in systems engineering for complex embedded products, including automotive experience.
Strong requirements engineering capability: elicitation, analysis, decomposition, validation, traceability and change management.
Ability to model system architecture, interfaces and product behaviour.
Experience with Polarion or a comparable requirements management tool.
Experience with Enterprise Architect, SysML/UML or a comparable modelling environment.
Practical Jira knowledge covering backlog, workflow, dependencies, estimation and status reporting.
Knowledge of Automotive SPICE and its application to system work products and reviews.
Knowledge of BCM systems, automotive electronics, vehicle networks and common ECU interfaces.
Knowledge of AUTOSAR, diagnostics, cybersecurity or functional safety.
Advanced analytical thinking and ability to structure ambiguous problems.
Ability to lead technical customer discussions and communicate decisions to varied audiences.
Very good spoken and written English.
Ability to prioritise under time pressure without compromising engineering quality.
Ability to mentor others, collaborate, lead reviews and resolve conflict constructively.
Practical and responsible use of AI tools in engineering work.
Willingness to travel occasionally and collaborate across time zones.

Responsibilities

Lead analysis, clarification, decomposition and agreement of customer and internal requirements for BCM functions.
Create and maintain system requirements, interfaces, assumptions, constraints and acceptance criteria in Polarion.
Ensure bidirectional traceability from stakeholder needs through system requirements and architecture to implementation and verification.
Design and review system architecture and functional variants in Enterprise Architect, including allocation to hardware, software and vehicle networks.
Assess the impact of customer changes, carline variants, hardware revisions and available samples on features, timing, risks and verification scope.
Make and document technical decisions, trade-offs and architectural rationale; escalate unresolved risks with recommended actions.
Lead resolution of complex system and quality issues, including root-cause analysis and coordination with software, hardware and test teams.
Plan requirements and architecture reviews and ensure the completeness, quality and timely delivery of Automotive SPICE system work products.
Work directly with OEM customers in Europe, the United States and PACRIM to clarify expectations, present solutions and close open points.
Act as a subject-matter expert for System Leaders, architects and engineers through mentoring, constructive reviews and knowledge sharing.
Work with project leadership to prioritise the backlog, manage dependencies and support delivery planning in Jira.
Enable transparent Jira-based capacity planning through credible estimates, clear work breakdown, current status, dependencies and risks.
Use modern AI tools responsibly for analysis, requirements quality, documentation and productivity, while protecting confidential data and verifying outputs.
Identify opportunities to reuse platform solutions across programmes while managing OEM-specific needs.
Build a culture of collaboration, fact-based communication, ownership of outcomes and early escalation of problems.