Principal Software Architect

Analog Devices•Durham, NC

About The Position

Analog Devices is seeking a Principal Software Systems Architect for Data Center Platforms to define next-generation embedded software and system architectures for data center infrastructure. The role works at the intersection of silicon, embedded computing, software, power, sensing, communications, security, and large-scale infrastructure. The architect partners with analog, digital, firmware, software, systems, applications, and product teams to translate customer problems into scalable product architectures. The position influences products from early architectural decisions through implementation and deployment, providing technical leadership across disciplines and helping teams deliver complex systems.

Requirements

Substantial experience in several relevant technical areas, including embedded systems and software architecture; C/C++ and low-level embedded software; real-time and bare-metal systems; microcontrollers and heterogeneous compute architectures; hardware/software co-design; device drivers and hardware abstraction; communications protocols and system interfaces; distributed embedded systems; configuration, telemetry, diagnostics, and fault management; embedded security; software platforms and APIs; or system integration, validation, and debug.
Deep software expertise combined with a broad understanding of underlying hardware and system architecture.
Ability to recognize cross-domain dependencies and make sound architectural tradeoffs.
Technical credibility and leadership skills to inspire teams and build alignment.
Ability to work across technical disciplines and take on problems outside one’s own area of expertise.

Responsibilities

Define embedded software and system architectures spanning devices, platforms, and applications.
Translate customer and system requirements into hardware/software architectures and engineering requirements.
Establish architectural boundaries and interfaces among hardware, firmware, algorithms, communications, security, telemetry, configuration, and higher-level software.
Drive early architectural decisions with consideration for capability, schedule, cost, reuse, and product differentiation.
Design for portability and scalability across products and product generations.
Provide technical leadership across teams, challenge assumptions constructively, mentor engineers, and build alignment around architectural decisions.
Convert ambiguous customer and system problems into concrete technical architectures.
Drive tradeoffs involving performance, reliability, security, memory, compute, interfaces, cost, and development complexity.
Establish interfaces and architectural contracts that enable parallel execution by multiple engineering teams.
Identify technical risks and critical dependencies early and resolve them through analysis, modeling, experimentation, and prototypes.
Drive decisions to closure and take ownership for results.
Balance innovation and differentiation with schedule, cost, risk, and customer value.