Also known as: Memory Subsystem Architect; Memory Solutions Architect; Memory Architecture Lead
See this role on the Memory lifecycle
Decides what memory a system should use and how — capacity, bandwidth, hierarchy, media mix and interface choice — translating workload behaviour and cost constraints into a memory subsystem definition that design teams and customers can build to.
Work in progressNo day-in-the-life description has been written for this role yet. If you do this work, we would welcome yours. Suggest a source or a correction
The role's tasks, work products, gates, skills, career paths, listings and pay benchmarks are for registered members. Registration is free and takes a minute. You come back to this page afterwards.