Summary
Over the past year, Abbey Smalley, former Head of Design Programs at Amazon has taken a deep dive into the types of Design Ops roles and levels that exist in the market. She’s collected the themes of her findings as well as synthesized insights from interviewing several Design Ops professionals and hiring managers into a newly developed framework that will help you better understand the types of opportunities that exist in the field. She'll also share recommendations on core skills to learn and present in your portfolio to help you land your next dream role.
Key Insights
-
•
Design ops and design program manager job titles in 2023 are highly inconsistent and rarely reflect the same scope across companies.
-
•
Employers seek a mix of prior experiences including project management (40%), design (30%), design ops (20%), product lifecycle (14%), and communications (10%).
-
•
Most design ops roles today expect candidates to be generalists rather than specialists, though design systems and research are common specialties when they exist.
-
•
There is a significant gap in entry-level design ops roles, with few openings for candidates under 3 years experience.
-
•
Salary ranges vary widely, but most fall between $140,000 and $270,000 annually, with top-end salaries linked to seniority, company size, and location.
-
•
59% of design ops roles in 2023 require onsite presence, often in California, New York, or Texas; only 28% are fully remote, often with location restrictions.
-
•
Design ops career ladders include four levels: lead, senior, manager of people, and principal or individual contributor track, but many companies only hire at lower levels.
-
•
Design program manager roles are often not clearly distinguished from design ops roles; many require operational and program management tasks combined.
-
•
Economic downturns have hit design ops practitioners hard, many of whom never experienced a market contraction before, reducing available roles.
-
•
Hiring managers strongly agree portfolios with 2-4 case studies using frameworks like STAR are essential, showcasing operational artifacts such as project plans, communication, and metrics management.
Notable Quotes
"Design ops roles and titles do not equal the same scope or tasks between companies in 2023."
"I think a part of what makes a really strong design ops team is having a mix of previous experiences, to complement each other with different perspectives."
"The term program is being used in two very different ways today: managing a portfolio of products or managing a program initiative not tied to a product."
"This is the first economic downturn many in design ops are experiencing, which can feel very discouraging."
"The future is already here, it’s just not evenly distributed — some companies have mature design ops at scale, others are just beginning."
"More than 33% of design ops professionals hadn’t entered the workforce until after the great recession."
"Most roles require five or more years experience, and some require 10+ years even though roles weren’t called design ops back then."
"Hiring managers want to see case studies — two to three is typical; personally, I suggest three or four."
"Portfolios don’t need to show final design outputs, but artifacts that demonstrate process, communication, and metrics management."
"Senior leaders need to create more entry-level roles, standardize titling, set realistic years of experience, and allow location flexibility."
Or choose a question:
More Videos
"Don't be cool, be good—work hard at managing your teams because they need you to nail it."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Sometimes the director is the most senior design person in the org and ends up playing the executive role without the title or support."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Nobody knows who’s supposed to decide what around digital, and that’s the problem."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Transportation must evolve to be more sustainable and accessible for all."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you forget the individual, you cut out psychological safety, and that’s the foundation of strong teams."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Never be afraid to get into good trouble; start by asking why."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"We used a Python algorithm with a correlation matrix to identify meaningful clusters from survey responses."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Successful operations must have a well-laid-out and transparent process and documentation, but that process must become invisible in its application."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024