Embedded Software Engineer

About the role

ALTEN Technology assigns engineers to solve demanding embedded problems for clients in automotive and related sectors. You will integrate and validate safety and multimedia subsystems to advance an Ok2Book proof of concept. The role supports program gate reviews through detailed bring-up and documentation. You will work closely with cross-functional teams to translate high-level requirements into low-level implementation plans that are testable and verifiable. You will own the execution of complex hardware and software interactions in a fast-paced environment where delivery quality and schedule adherence are critical. Your work will directly influence the platform capabilities and help define the baseline for future product features in the automotive domain. Communication clarity and structured thinking will be essential as you explain technical constraints and trade-offs to both technical and non-technical stakeholders.

Key facts

What you'll do

Execution of audio subsystem bring-up handles codec integration, ALSA, audio HAL, and latency measurement to ensure that platform audio expectations are satisfied. Interface with AMD to obtain safety and multimedia driver support aligns implementation with program requirements and accelerates integration timelines. Documentation of multimedia and safety bring-up state feeds program gate reviews and decision points, providing traceability and justification for technical choices. Camera bring-up on target hardware uses MIPI CSI-2, V4L2 driver stack, ISP integration, and Camera HAL to validate imaging functionality and performance. Safety subsystem integration covers watchdog, health monitors, and ASIL-aware software development practices to uphold functional safety objectives. Platform enablement uses the Linux kernel and multimedia frameworks such as GStreamer and camera2 API to build a coherent software stack. Implementation of subsystem integration and validation employs code written in C/C++, Python, and Rust to meet performance, reliability, and maintainability goals. Contribution to multi-camera pipeline or surround-view system experience supports advanced automotive use cases and prepares the platform for higher levels of autonomy. Application of ISO 26262 ASIL-B or higher safety development practices reduces integration risk and strengthens system robustness throughout the lifecycle. Possession of Android camera or audio HAL experience (AAOS / AOSP) aligns with platform-level software standards and simplifies adoption of reference designs.

Requirements

The posting states a pay range of $130000 to $140000.

Baseline qualification requires a Bachelor's or Master's degree in Computer Science, Engineering, or a related field.

Management of complex system integration tasks requires 7+ years of experience in Embedded Software Development.

Camera bring-up on target hardware uses MIPI CSI-2, V4L2 driver stack, ISP integration, and Camera HAL.

Audio bring-up relies on codec integration, ALSA, audio HAL, and interfaces such as I2S, SoundWire, and HDMI ARC.

Safety subsystem integration covers watchdog, health monitors, and ASIL-aware software development practices.

Platform enablement uses the Linux kernel and multimedia frameworks such as GStreamer and camera2 API.

Implementation of subsystem integration and validation employs code written in C/C++, Python, and Rust.

Drug screening is required as a condition of hire under federal contractor obligations.

Nice to have

Application of ISO 26262 ASIL-B or higher safety development practices reduces integration risk and strengthens system robustness.

Familiarity with AMD multimedia driver stack accelerates bring-up and debug activities for those with existing knowledge.

Contribution to multi-camera pipeline or surround-view system experience supports advanced automotive use cases.

Possession of Android camera or audio HAL experience (AAOS / AOSP) aligns with platform-level software standards.

Practical notes

Drug screening is required as a condition of hire under federal contractor obligations. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Embedded software roles emphasize low-level system enablement and hardware interaction. Common tools include version control, issue trackers, and code review systems to support team workflows. Safety-critical development often follows functional safety standards to ensure reliability in automotive contexts. Multimedia pipelines involve image signal processing, audio processing, and system integration across software components. Cross-functional communication with hardware and platform teams is typical in automotive and IoT projects.