Technical Lead Engineer - Cybesecurity
Aptiv (company site, opens in a new tab)10–15 yrsBengaluruOn-siteDirect career pageEst. 30–48 LPA
Posted 7d ago
Reach people at Aptiv
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Aptiv you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own the product cybersecurity roadmap and prioritized backlog, translating security needs and technical debt into features, enablers, and testable acceptance criteria.
- Align release scope, dependencies, and objectives with customer, project, platform, software, and validation stakeholders; accept completed work using verification evidence and traceability.
- Track delivery KPIs, maturity, capacity, and risks; prioritize vulnerability fixes and field updates, and escalate gaps early.
Minimum Requirements
- Work Experience Required: 10–15 years only; embedded software product ownership or technical program experience is specified.
- B.E./B.Tech or M.E./M.Tech in Computer Science, Electronics, Electrical, Instrumentation, or a related engineering discipline.
- Knowledge of ISO/SAE 21434 work products, secure ECU features, Agile practices, and Automotive SPICE.
- Ability to write testable requirements and make data-based priority decisions.
Ideal Candidate Profile
- Best suited to someone with embedded-software product ownership or technical program experience who can turn automotive cybersecurity needs into scoped, verifiable releases.
- Likely to succeed in a cross-functional, global stakeholder environment, aligning customer, project, platform, software, and validation priorities.
- Shortlist signals include evidence-based feature acceptance, traceable requirements, and experience managing cybersecurity risks, dependencies, and release objectives.