Lead Systems Architect

Role Summary

As a Lead System Architect at Axiado, you will define the end-to-end architecture bridging silicon (ASIC/SoC), board-level hardware platforms, and low-level system software/firmware. Leveraging your deep expertise in the server and infrastructure industry, you will translate customer requirements into detailed technical specifications. This high-impact role requires navigating complex hardware/software tradeoffs while collaborating closely with Axiado’s engineering teams, customers, standards organizations and ecosystem partners.

Key Responsibilities

1. Architectural Definition & Detailed Specification

• Own and author comprehensive, unambiguous system architecture specifications, micro-architectural specs, and/or platform requirement documents.
• Define rigorous system-level hardware/software partition boundaries and map out register-level interfaces for hardware blocks and low-level software stacks.
• Drive micro-architecture specifications for high-security, AI-driven SoCs, including on-chip interconnects (AXI/AHB), memory hierarchies, and standard I/O interfaces (PCIe, Ethernet, SPI, eSPI, I3C, LTPI).

2. Customer Interfacing & Ecosystem Engagement

• Serve as a primary technical point of contact for enterprise and hyperscaler customers to gather, analyze, and scope their next-generation platform security needs.
• Present Axiado’s system architecture roadmap and technical whitepapers to strategic customers, steering-level partners, and standards committees.
• Align Axiado’s technology with modern server deployment topologies and open-source standards (such as OCP DC-SCM / DC-SCI).

3. Server Infrastructure & Board-Level Integration

• Architect platform-level designs optimized for enterprise server motherboards, baseboard management systems, and cloud data center environments.
• Guide hardware and SI/PI engineers on signal integrity, power delivery networks, and thermal/mechanical constraints for modular server building blocks.

4. Software, Firmware & Security Stack Partitioning

• Specify secure platform boot flows, Root-of-Trust (RoT) architecture, and Platform Firmware Resiliency (PFR) frameworks.
• Collaborate with firmware teams to define interfaces for BMC stacks (OpenBMC), Linux kernels, device drivers, and platform management protocols (MCTP, PLDM, Redfish).