JOBWAVE VERIFIED

Middleware Developer — Automotive Infotainment, Camera & Connectivity

Company: Capgemini Engineering
Role Title: Middleware Developer / Middleware Stack Integration SME
Job Reference Code: 527646
Location: Bangalore, India
Work Mode: Not specified
Employment Type: Permanent
Experience Required: 15+ years
Experience Level: Experienced Professionals
Professional Community: Software Engineering
Posted On: 10 October 2026
Salary: Not specified
Education: Not specified

Core Technology Stack

• Programming Languages: C, C++
• Operating Systems: Android Automotive OS (AAOS), Embedded Linux
• Android Middleware: Android Framework, System Services, Hardware Abstraction Layer (HAL), Binder IPC, HIDL, AIDL
• Camera Middleware: Camera HAL, Camera Frameworks, GStreamer, video capture, streaming, multimedia pipelines
• Automotive Camera Systems: Rear View Camera (RVC), Surround View System (SVS), Driver Monitoring System (DMS), Cabin Monitoring System (CMS)
• Connectivity: Bluetooth Classic/BLE, Wi-Fi, Ethernet, USB, GNSS, cellular connectivity
• Vehicle Networking: CAN/CAN-FD, LIN, Automotive Ethernet, SOME/IP, DoIP
• Automotive Hardware Platforms: Qualcomm, NXP, Renesas, TI, Samsung Exynos Auto, MediaTek, or equivalent automotive SoCs
• Debugging & Performance: ADB, Logcat, GDB, Wireshark, Linux Trace Tools, Perf, memory profiling, boot-time optimization
• Engineering Practices: Middleware architecture, platform integration, code reviews, root-cause analysis, ASPICE, functional safety, cybersecurity, SDLC
• Leadership: Technical architecture, cross-functional coordination, customer engagement, mentoring, solution design, pre-sales support

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

JOBWAVE INSIGHTS

1. Who Is This Role For?

This is a senior automotive embedded software architecture and integration role, not a typical application-level middleware developer position.

The ideal candidate has 15+ years of embedded software and automotive infotainment experience, with deep knowledge of Android Automotive or Embedded Linux. They should be capable of owning middleware architecture across camera and connectivity systems, integrating hardware-specific software stacks, solving complex platform issues, and leading engineering teams.

The role also includes customer-facing responsibilities, technical solution proposals, effort estimation, and support for RFP/RFI responses.

Main Areas of Responsibility

1. Middleware Architecture: Define reusable middleware frameworks and integration strategies across automotive programs.
2. Camera Systems: Architect and integrate camera pipelines and features for RVC, SVS, DMS, and CMS.
3. Connectivity Systems: Lead integration of Bluetooth, Wi-Fi, Ethernet, USB, GNSS, and cellular technologies.
4. Platform Integration: Connect applications, Android framework services, HALs, device drivers, and hardware platforms.
5. Vehicle Networking: Integrate automotive communication technologies and services.
6. Performance Engineering: Optimize latency, throughput, memory, CPU usage, boot time, and system stability.
7. Technical Leadership: Lead design reviews, mentor engineers, and establish engineering best practices.
8. Customer & Pre-Sales Engagement: Support OEMs, chipset vendors, Tier-1 suppliers, proposals, estimations, and technical roadmaps.

2. Key Skills Required

Highest Priority

• 15+ years of embedded software development and automotive infotainment experience.
• Strong expertise in AAOS and/or Embedded Linux.
• Advanced C/C++ programming skills.
• Deep middleware architecture, development, and integration experience.
• Android Framework, HAL, Binder IPC, HIDL, and AIDL knowledge.
• Camera middleware and multimedia pipeline integration.
• Automotive connectivity stack integration.
• Experience with automotive SoCs and hardware platform bring-up.
• Technical leadership, architecture reviews, and customer issue resolution.

Specialized Technical Skills

• Camera HAL and camera framework integration.
• GStreamer and multimedia processing.
• RVC, SVS, DMS, and CMS implementation.
• Bluetooth Classic/BLE, Wi-Fi, USB, Ethernet, GNSS, and cellular connectivity.
• CAN/CAN-FD, LIN, SOME/IP, and DoIP integration.
• ADB, Logcat, GDB, Wireshark, Perf, and Linux tracing.
• Memory, CPU, boot-time, latency, and throughput optimization.
• ASPICE, functional safety, cybersecurity, and SDLC.

Strong Advantages

• Experience across multiple OEM automotive programs.
• Hands-on integration with Qualcomm, NXP, Renesas, TI, Samsung Exynos Auto, or MediaTek platforms.
• Experience with digital cockpit and connected vehicle architectures.
• Direct collaboration with OEMs, semiconductor vendors, BSP teams, and Tier-1 suppliers.
• Pre-sales engineering, RFP/RFI responses, technical estimation, and solution proposals.
• Experience leading architecture and technology roadmap decisions.

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

JOB DETAILS

3. Role Overview

The Middleware Stack Integration SME will drive architecture, development, and integration of camera and connectivity middleware for Android Automotive and Embedded Linux platforms.

The engineer will work across the automotive software stack, from application-facing middleware and framework services down to HALs, device drivers, and hardware platforms. The role involves developing reusable components, enabling features on new hardware, optimizing system performance, and resolving complex customer or production issues.

The position combines deep technical ownership with engineering leadership and customer engagement.

4. Main Responsibilities

A. Middleware Architecture & Integration

• Lead architecture, design, development, and integration of camera and connectivity middleware.
• Define reusable software components, middleware frameworks, and platform integration strategies.
• Design interfaces between applications, Android framework services, HALs, device drivers, and hardware.
• Support platform bring-up and feature enablement on new infotainment hardware.
• Drive architecture reviews, design reviews, code reviews, and technical audits.

B. Camera Middleware & Multimedia

• Develop and integrate camera solutions for RVC, SVS, DMS, and CMS.
• Architect and integrate Camera HAL, video capture pipelines, streaming frameworks, and multimedia components.
• Troubleshoot camera pipeline failures, latency, video processing, and system-level integration issues.
• Optimize camera performance and stability across target platforms.

C. Connectivity & Vehicle Networking

• Integrate Bluetooth, Wi-Fi, Ethernet, USB, GNSS, and cellular technologies.
• Collaborate with vehicle networking teams on CAN, LIN, Ethernet, SOME/IP, and DoIP integration.
• Resolve connectivity, networking, and vehicle communication issues.
• Work with chipset vendors, BSP teams, hardware teams, application teams, and OEM customers.

D. Performance & Quality Engineering

• Optimize camera latency, connectivity throughput, memory utilization, CPU performance, and boot time.
• Improve overall system stability and reliability.
• Conduct root-cause analysis for critical customer issues and production defects.
• Apply debugging and profiling tools to diagnose issues across middleware and hardware interfaces.

E. Technical Leadership & Customer Engagement

• Mentor engineers and establish middleware development and debugging practices.
• Lead cross-functional engineering discussions and technical reviews.
• Support customer engagements, solution proposals, effort estimates, and technology evaluations.
• Contribute to roadmap planning and pre-sales activities, including RFP/RFI responses.
• Drive innovation in digital cockpit and connected vehicle platforms.

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

REQUIREMENTS

5. Mandatory / Core Requirements

Based on the supplied job description, the primary screening criteria are:

• Experience: 15+ years in embedded software development and automotive infotainment.
• Platform: Strong expertise in Android Automotive OS and/or Embedded Linux.
• Programming: Proficiency in C and C++.
• Middleware: Strong architecture, design, development, and integration experience.
• Android Internals: Android Framework, System Services, HAL, Binder IPC, HIDL, and AIDL.
• Domain Expertise: Camera middleware and connectivity integration.
• Hardware: Experience with automotive SoCs and platform-level integration.
• Leadership: Technical leadership, stakeholder management, and customer engagement.

6. Additional Domain Requirements

Candidates should be prepared to demonstrate experience in the following areas:

• Camera HAL, multimedia pipelines, video capture, and streaming.
• RVC, SVS, DMS, and CMS.
• Bluetooth, Wi-Fi, Ethernet, USB, GNSS, and cellular connectivity.
• CAN/CAN-FD, LIN, SOME/IP, and DoIP.
• Platform bring-up, BSP coordination, hardware integration, and feature enablement.
• Debugging with ADB, Logcat, GDB, Wireshark, Perf, and Linux trace tools.
• Performance analysis, memory profiling, boot-time optimization, and stability improvements.
• ASPICE, functional safety, cybersecurity, and SDLC.

Important: The description says AAOS and/or Embedded Linux, so expertise in both is not explicitly mandatory. However, strong proficiency in at least one is expected. The listing does not specify a particular camera or connectivity vendor stack as the exclusive requirement.

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

QUALIFICATIONS

7. Experience Profile

Qualification	Requirement
Total experience	15+ years
Primary domain	Embedded software and automotive infotainment
Platform experience	AAOS and/or Embedded Linux
Programming	C and C++
Architecture	Middleware design and system integration
Camera domain	Camera HAL, pipelines, RVC/SVS/DMS/CMS
Connectivity domain	Bluetooth, Wi-Fi, Ethernet, USB, GNSS, cellular
Leadership	Architecture ownership, mentoring, customer engagement
Education	Not specified
Salary	Not specified

8. Potential Gaps to Check

Before applying, candidates should assess the following:

• Experience gap: Does the candidate have at least 15 years of relevant embedded and automotive infotainment experience?
• Platform depth: Can they explain Android Automotive internals or Embedded Linux integration beyond application development?
• Camera specialization: Have they worked directly on camera middleware, HAL integration, or multimedia pipelines?
• Connectivity specialization: Have they integrated actual connectivity stacks rather than only consumed application-level APIs?
• Hardware integration: Have they worked with automotive SoCs, BSP teams, drivers, or hardware bring-up?
• Vehicle networking: Can they demonstrate experience with CAN/CAN-FD, LIN, SOME/IP, DoIP, or Automotive Ethernet?
• Performance debugging: Can they provide examples of reducing latency, boot time, CPU usage, memory consumption, or system instability?
• Leadership: Have they owned architecture decisions, mentored engineers, and resolved customer-critical issues?
• Customer-facing experience: Can they discuss OEM engagement, solution estimation, and technical proposals?

A candidate who primarily develops Android applications, web applications, or generic backend middleware may not be a strong match without substantial embedded automotive experience.

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

INTERVIEW PREPARATION

Phase 1 — Embedded C/C++ & Operating Systems

Prepare for:

• Pointers, memory management, concurrency, synchronization, and debugging in C/C++.
• Processes, threads, IPC, scheduling, and Linux internals.
• Shared memory, mutexes, semaphores, deadlocks, and race conditions.
• Device drivers, kernel interfaces, system services, and hardware abstraction.
• Memory leaks, CPU bottlenecks, crash analysis, and resource management.

Practice task: Explain how you would diagnose a middleware service that crashes intermittently after system startup.

Phase 2 — Android Automotive & Middleware Architecture

Focus on:

• Android Framework and System Services.
• HAL architecture and communication with lower software layers.
• Binder IPC and service lifecycle.
• HIDL versus AIDL and their roles in Android interfaces.
• AAOS architecture and automotive platform integration.
• Embedded Linux middleware architecture.
• BSP integration and platform bring-up.

Practice task: Draw the architecture of an automotive camera feature, from the application through framework services and HAL to the device driver and camera hardware.

Phase 3 — Camera, Connectivity & Vehicle Networks

Prepare to discuss:

• Camera capture pipelines, Camera HAL, GStreamer, and multimedia streaming.
• RVC, SVS, DMS, and CMS use cases and system constraints.
• Video latency, frame drops, synchronization, and camera performance.
• Bluetooth, Wi-Fi, Ethernet, USB, GNSS, and cellular integration.
• CAN/CAN-FD, LIN, SOME/IP, DoIP, and Automotive Ethernet.
• Integration issues across SoC, BSP, middleware, and application layers.

Practice task: Design a middleware integration plan for a new infotainment platform that supports multiple camera inputs, Wi-Fi, Bluetooth, and vehicle network services.

Phase 4 — Performance, Debugging & Technical Leadership

Prepare examples involving:

• A critical production issue and how you identified its root cause.
• Camera latency or video frame-drop optimization.
• Connectivity throughput or intermittent disconnection issues.
• Boot-time and memory optimization.
• Debugging with ADB, Logcat, GDB, Wireshark, Perf, and Linux tracing.
• Architecture trade-offs, reusable middleware, and design reviews.
• Mentoring engineers and coordinating across OEM, chipset, BSP, and application teams.
• Effort estimation, technical proposals, and customer communication.

Practice task: Present a real project where you owned a system-level issue from investigation through root-cause identification, implementation, validation, and customer acceptance.

Final Interview Focus

The strongest interview answers should demonstrate architecture ownership, hands-on embedded debugging, automotive camera/connectivity integration, and measurable performance improvements.

Use real project examples. Explain the system architecture, your individual contribution, the constraints, the debugging approach, and the final result. For a senior SME role, describing tools or technologies without showing ownership of complex engineering decisions is unlikely to be sufficient.

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

APPLICATION SUMMARY

Company: Capgemini Engineering
Position: Middleware Developer — Middleware Stack Integration SME
Reference Code: 527646
Location: Bangalore, India
Employment: Permanent
Experience: 15+ years
Posted: 10 October 2026

Overall recommendation: Best suited for a senior embedded automotive engineer or technical architect with strong AAOS/Embedded Linux fundamentals and substantial experience integrating camera and connectivity middleware on automotive infotainment platforms. Candidates should be comfortable with both deep technical problem-solving and customer-facing technical leadership.

Information not provided in the listing: Salary range, educational qualification, exact work arrangement, and application contact details.