Embedded Software Engineer III

About the role

The position supports aerospace, medical, automotive, and other advanced technology programs.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

Requirements

Minimum of seven years of professional experience developing embedded software systems.

Strong understanding of embedded microcontroller architectures, hardware interfaces, and system operation.

Experience developing software in compliance with functional safety or design assurance standards such as DO-178 or IEC 61508.

Advanced proficiency in the C programming language for low-level implementation.

Experience using source code management and version control systems to track changes and releases.

Familiarity with application lifecycle management tools supporting requirements management, traceability, verification, validation, and issue tracking.

Demonstrated ability to diagnose and resolve software issues in embedded environments using hardware targets and simulation tools.

Strong written and verbal communication skills to explain complex technical concepts to diverse audiences.

Proficiency with Microsoft Office applications for documentation and reporting.

Ability to support long-term engineering programs throughout extended product development cycles.

U.S. Person status required as defined by applicable export control regulations.

Nice to have

Bachelor's degree in Electrical Engineering, Computer Engineering, Software Engineering, Computer Science, or a closely related technical discipline.

Knowledge of MISRA C coding guidelines and best practices for safety-critical systems.

Familiarity with power electronics principles and embedded control systems for advanced implementations.

Experience preparing technical presentations and participating in customer or regulatory audits.

Ability to interpret electrical schematics and hardware documentation for efficient integration.

Experience supporting the development of electrical power systems for military or aerospace applications in regulated contexts.

Skills & tools

General knowledge of embedded development toolchains, analysis utilities, and verification frameworks used in regulated industries.

Practical notes

U.S. Person status is required for employment due to export control regulations.

This role may involve extended program cycles and travel as required by project needs.

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 often involve close collaboration with hardware and systems engineering teams.

Work typically targets safety- and reliability-critical applications in regulated sectors.

C programming and compliance with functional safety standards are common expectations.

Version control and requirements traceability tools are central to development workflows.

Technical communication skills are essential for interfacing with multidisciplinary stakeholders.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.