Skip to main content

Lead Embedded Software Engineer- Hybrid In San Diego

Posted today

a2e technologiesSan Diego (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Lead Embedded Software Engineer The Technical Lead, Embedded Software Development, is a senior technical role responsible for the architecture, design, and delivery of embedded software solutions across multiple concurrent client projects. Serves as the primary technical lead on embedded firmware and low-level software projects, mentor embedded engineers, and work closely with project managers, system engineers, hardware engineers, FPGA engineers and clients to translate requirements into reliable, maintainable, and well-documented embedded systems. This role blends hands-on engineering with technical leadership and requires strong communication skills in a client-facing, consulting-style environment.
Key Responsibilities: Serve as the technical lead for embedded software on client engagements, from proposal and architecture through implementation, verification, and production support. Define embedded software architecture, including RTOS selection and configuration, driver and middleware structure, communication protocols, and hardware/software partitioning, in collaboration with hardware and systems engineering teams. Establish and enforce coding standards, design review practices, and software development processes as applicable to the project. Lead and mentor a team of embedded software engineers, providing technical guidance, code and design reviews, and career development support. Primary technical point of contact with clients, translating client requirements into actionable technical plans and communicating project status, risks, and trade-offs clearly and proactively. Own technical estimation and planning for embedded software work packages, partnering with project managers to maintain schedule, scope, and budget commitments across multiple projects. Drive root-cause analysis and resolution of complex firmware, hardware/software integration, and field issues. Oversee unit, integration, and system-level test strategies for embedded software, including test automation and hardware-in-the-loop testing where applicable. Support bring-up and debugging of new hardware platforms, including bootloaders, board support packages, and low-level drivers. Contribute to proposal development, technical scoping, and pre-sales technical discussions for new and existing client engagements. Remain current with embedded software tools, microcontroller/microprocessor platforms, and industry best practices, and introduce relevant improvements into project workflows.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this