JOBWAVE VERIFIED

Software Requirements Engineer — Automotive Embedded Systems

Company: KPIT
Job ID: Not provided
Location: Bangalore, India
Work Mode: Not specified
Experience Required: 3–6 Years
Joining Preference: Immediate joiners preferred
Employment Type: Not specified
Salary / CTC: Not specified
Qualification: Full-time B.E. / B.Tech / M.Tech
Eligible Disciplines: Electronics, Electrical, Embedded Systems, Mechatronics, or related fields
Application Email: [email protected]
Role Type: Automotive Embedded Software Requirements Engineering
Core Domain: Automotive Electronics, ECU Software, Diagnostics, AUTOSAR, Functional Safety

────────────────────

JOBWAVE INSIGHTS

Who Is This Role For?

This role is suitable for automotive embedded engineers with 3–6 years of experience in software requirements engineering, ECU development, automotive diagnostics, and hardware-software interface requirements.

It is particularly relevant to candidates who can derive clear, testable software requirements from hardware datasheets, register maps, system architecture, diagnostics concepts, and functional safety requirements.

Important: This is primarily a software requirements engineering position, not simply an embedded C/C++ coding role.

Key Skills

• Automotive embedded software requirements engineering
• Hardware datasheet and register-map interpretation
• SPI, UART, I2C, GPIO, PWM, and Ethernet interfaces
• AUTOSAR services
• Automotive diagnostics: UDS, DEM, and DCM
• DTC lifecycle management and debounce strategies
• IBM DOORS / DOORS Next
• ISO 26262 functional safety
• Automotive SPICE (ASPICE)
• Device initialization and register configuration
• Sleep/wake management and fault handling
• Technical documentation and stakeholder management

Priority Skills

Highest Priority

1. Automotive embedded software requirements engineering
2. Requirements derivation from hardware datasheets and system architecture
3. SPI, UART, I2C, GPIO, PWM, and Ethernet
4. AUTOSAR concepts and services
5. UDS diagnostics, DEM/DCM, DTC lifecycle, and debounce strategies
6. DOORS / DOORS Next
7. ISO 26262 and ASPICE
8. Fault handling, safe states, and sleep/wake management

Strong Advantages

• Body electronics and lighting electronics
• Zone controllers
• LED drivers and power electronics
• Thermal management and derating functions
• Automotive Ethernet, including 100BASE-T1 and 10BASE-T1S
• IEEE 1722b and IEEE 802.1AS
• ECU development experience in BCM, engine, transmission, airbag, or ABS/ESP systems

────────────────────

JOB DETAILS

Role Overview

KPIT is seeking a Software Requirements Engineer to develop and maintain software requirements for automotive Edge Node software components.

The role involves translating hardware and system-level information into well-structured software requirements, defining diagnostics and fault-management behavior, and ensuring alignment with automotive process and functional safety standards.

Core Responsibilities

1. Software Requirements Development

Develop and maintain requirements for Edge Node components, including:

• LED configurator
• Diagnostics
• EEPROM handler
• Light source management
• Derating functions

Derive software requirements from:

• Hardware datasheets
• System architecture
• Register maps and timing diagrams
• Diagnostic specifications
• Functional safety concepts
• Fault tables and hardware behavior

2. Device and Interface Requirements

Define requirements for:

• Device initialization and register configuration
• Sleep and wake-up management
• Fault handling and safe-state transitions
• SPI communication
• UART communication
• I2C communication
• GPIO and PWM control
• Ethernet communication
• AUTOSAR services and related software interactions

3. Automotive Diagnostics

Create and maintain diagnostic requirements covering:

• UDS diagnostic services
• DTC lifecycle management
• Diagnostic Event Manager (DEM)
• Diagnostic Communication Manager (DCM)
• Fault detection and debounce strategies
• Fault reactions and safe-state behavior

4. Functional Safety and Process Compliance

• Ensure requirements align with ISO 26262 functional safety expectations.
• Follow ASPICE processes and requirements engineering practices.
• Maintain clear, traceable, and reviewable technical documentation.
• Support consistency between system, hardware, software, and validation requirements.

5. Cross-Functional Collaboration

Work with:

• Hardware engineering teams
• Embedded software development teams
• Functional safety teams
• System architecture teams
• Validation and testing teams
• External suppliers and stakeholders

────────────────────

REQUIREMENTS

Experience

• 3–6 years of relevant professional experience.
• Automotive embedded software or software requirements engineering experience.
• Ability to convert system and hardware specifications into software requirements.
• Experience with automotive diagnostics and embedded communication interfaces.
• Familiarity with requirements management tools and automotive development standards.

Technical Requirements

Embedded Interfaces

• SPI
• UART
• I2C
• GPIO
• PWM
• Ethernet

Automotive Software and Diagnostics

• AUTOSAR
• UDS
• DEM/DCM
• DTC lifecycle management
• Debounce strategies
• Fault handling and safe states
• Sleep/wake management

Requirements Engineering and Standards

• IBM DOORS or DOORS Next
• ISO 26262
• ASPICE
• Hardware datasheets and register maps
• Timing diagrams and fault tables
• Requirements documentation and traceability

Preferred Domain Experience

• Body Control Modules (BCM)
• Lighting electronics and LED drivers
• Zone controllers
• Engine ECUs
• Transmission ECUs
• Airbag ECUs
• ABS/ESP ECUs
• Power electronics and thermal management

────────────────────

QUALIFICATIONS

Required Degree: Full-time B.E., B.Tech, or M.Tech.

Relevant Disciplines:

• Electronics Engineering
• Electrical Engineering
• Embedded Systems
• Mechatronics
• Related engineering disciplines

Experience Range: 3–6 years.

Joining: Immediate joiners preferred.

Location: Bangalore.

────────────────────

POTENTIAL GAPS TO CHECK

• Experience writing software requirements for automotive embedded systems
• Ability to derive requirements from datasheets and register maps
• Understanding of SPI, UART, I2C, GPIO, PWM, and Ethernet
• Practical knowledge of UDS diagnostics
• Understanding of DEM/DCM and DTC lifecycle management
• Experience with DOORS or DOORS Next
• Knowledge of ISO 26262 and ASPICE
• Ability to define fault handling, debounce, and safe-state behavior
• Experience with AUTOSAR services
• Understanding of sleep/wake management and device initialization
• Familiarity with requirements traceability and validation
• Relevant automotive ECU or electronics domain experience

Potential screening risk: Candidates whose experience is limited to embedded coding without requirements engineering, diagnostics, or requirements-management tools may need to demonstrate how their experience maps to this role.

────────────────────

INTERVIEW PREPARATION

Phase 1 — Software Requirements Engineering

Prepare:

• Characteristics of a good software requirement
• Functional versus non-functional requirements
• Requirement decomposition and allocation
• Requirements traceability and change management
• Verification criteria and testable requirement writing
• Deriving software requirements from hardware datasheets
• Interpreting register maps, timing diagrams, and fault tables

Practice converting a hardware specification into clear, atomic, verifiable software requirements.

Phase 2 — Automotive Embedded Interfaces

Revise:

• SPI, UART, and I2C operation and differences
• GPIO and PWM use cases
• Ethernet fundamentals and automotive Ethernet concepts
• Device initialization and register configuration
• Communication failure handling
• Sleep/wake-up behavior and timing constraints

Be prepared to explain how interface-level behavior becomes software requirements.

Phase 3 — Automotive Diagnostics and AUTOSAR

Prepare:

• UDS fundamentals and commonly used diagnostic services
• DEM and DCM responsibilities
• DTC setting, confirmation, aging, and clearing concepts
• Fault detection and debounce strategies
• Diagnostic event handling and fault reactions
• AUTOSAR architecture and relevant services
• Safe-state behavior when faults occur

Phase 4 — ISO 26262 and ASPICE

Prepare:

• Functional safety lifecycle fundamentals
• Safety goals and technical safety concepts
• Relationship between system, hardware, and software requirements
• Requirement traceability and verification evidence
• ASPICE process concepts relevant to software requirements engineering
• Reviews, baselines, change control, and audit readiness

Final Interview Focus

Prepare practical examples that demonstrate:

• How you derived requirements from a hardware datasheet
• How you wrote requirements for a device initialization sequence
• How you specified a fault-detection and debounce strategy
• How you defined UDS/DTC behavior
• How you managed traceability in DOORS or DOORS Next
• How you handled a requirement change involving hardware, software, and validation teams
• How you ensured requirements were testable and aligned with safety constraints

────────────────────

APPLICATION DETAILS

Send your profile to: [email protected]

Recommended application details:

1. Updated CV
2. Total relevant experience
3. Current location
4. Notice period and earliest joining date
5. Automotive projects and ECU domains
6. Experience with DOORS / DOORS Next, AUTOSAR, UDS, ISO 26262, and ASPICE

Final Recommendation

This is a strong target for candidates with automotive embedded requirements experience, particularly those who understand diagnostics, hardware interfaces, AUTOSAR, and functional safety.

Recommended preparation order:

1. Requirements engineering and hardware datasheet interpretation
2. UDS, DEM/DCM, and DTC lifecycle
3. AUTOSAR and embedded communication interfaces
4. DOORS / DOORS Next
5. ISO 26262 and ASPICE
6. Lighting electronics, LED drivers, and automotive Ethernet, if relevant to your background

Before proceeding, confirm the exact salary range, work arrangement, project domain, and expected joining date with the recruiter, as these details are not specified in the advertisement.