In a year when Layoffs.fyi logged Meta cutting 8,000, Amazon mid-stream on 16,000, and Oracle running 20,000 to 30,000, the design roles that are actually growing are not the ones on the old org chart. They are four new titles - Design Engineer, Design Systems Engineer, AI Design Lead, and Brand Systems Architect - that pay between roughly $150K and $320K base in major US markets per the 2026 ADP List, and that exist because an AI-native product org needs capabilities the traditional designer-and-design-manager structure never had a name for. As the leader, you will be asked to write the job descriptions, defend the comp bands to finance, and explain to your existing team what these roles are and how to grow into them. Get the definitions vague and you hire the wrong people into the wrong bands and your existing designers feel threatened by titles they do not understand. This lesson defines each role precisely - the mandate, the JD, the comp band, the career path, and the success metrics - and hands you four published JDs that survive a hiring committee and a budget review.

Why These Four Roles, Now

The four roles are not rebrands of existing jobs; each exists because AI created a capability gap the old structure could not fill. The Design Engineer exists because the boundary between design and front-end implementation collapsed - when v0 and Figma Make generate working code, the person who can move fluently across that boundary, deciding what the generated code should be and finishing it to craft standard, is more valuable than either a designer who cannot read code or an engineer who cannot see hierarchy. The Design Systems Engineer exists because the design system became the substrate AI agents read from, and maintaining an AI-readable system - tokens, MDX docs, MCP connections, drift detection - is now an engineering discipline, not a librarian task. The AI Design Lead exists because someone has to own the design function's AI strategy, governance, and tooling as a full-time mandate rather than a side-of-desk concern. The Brand Systems Architect exists because brand stopped being a set of finished marks and became a generative system - rules, tokens, and guardrails that resist model convergence - which requires an architect, not a mark-maker.

Defining these roles precisely is a leadership responsibility because the alternative is expensive. Vague roles get filled by whoever interviews well against a fuzzy bar, land in the wrong comp band, and either underperform (because the real mandate was never defined) or leave (because the band did not match the market). Vague roles also frighten your existing team, who hear "Design Engineer" and assume their own jobs are being replaced rather than understanding it as a distinct, additive capability with a path they can grow into. The four published JDs are as much an internal communication to your current designers as an external hiring document - they say, precisely, here is what is new, here is what it pays, and here is how you get there from where you are.

A note on the comp data: the $150K-$320K range comes from the 2026 ADP List, and it is a base-salary range across major US markets, with the spread driven by role, level, and geography. The Layoffs.fyi context matters here too - in a heavy layoff year, comp bands compress and candidates are plentiful at the lower end of each band, but the senior, genuinely AI-native versions of these roles remain scarce and command the top of the range. The leader's job is to band each role honestly against the market rather than against the org's nostalgia about what designers used to cost.

Design Engineer

Mandate. The Design Engineer owns the translation of design intent into shipped, production-quality front-end implementation, working fluently across the design-to-code boundary that AI tools made porous. They are the person who takes a generated component from v0 or a Figma Make prototype and decides what it should actually be - correcting the focus rings, the responsive behavior, the token alignment, the interaction states the generation got wrong - and ships it to a craft standard neither a pure designer nor a pure engineer would reach alone. They are not a designer who dabbles in code or an engineer who dabbles in design; they are a distinct discipline defined by genuine fluency in both.

The JD, in essence. Ships production front-end code (typically React and the team's framework) that meets the design system's standard. Reads and corrects AI-generated component code, catching where it drifts from design intent. Owns the design-to-code QA pass before handoff. Pairs with both designers and engineers as the bridge between them. Contributes to the design system at the code layer. Required: real front-end competence plus real design judgment, and the rare ability to hold both at once.

Comp band. Roughly $180K-$300K base in major US markets per the 2026 ADP List, with the spread driven by level (mid versus staff) and the depth of the dual fluency. The genuinely dual-fluent senior Design Engineer sits at the top of the band because the combination is scarce; the "designer who learned some React" sits at the bottom and is much more available in a layoff year.

Career path and success metrics. Path: a senior product designer who built real front-end skill, or a front-end engineer who built real design judgment, grows into mid-level Design Engineer, then staff, then principal - or laterally into Design Systems Engineering. Success metrics: design-to-code fidelity (how little hand-correction shipped work needs), QA-catch rate (drift caught before production), and the craft quality of shipped front-end against the system standard. Not measured by raw output volume, because the value is fidelity and judgment, not lines of code.

Design Systems Engineer

Mandate. The Design Systems Engineer owns the design system as AI-readable infrastructure - the substrate that AI agents generate against. This is the role that emerged when the design system stopped being a Figma library a librarian maintained and became a token-and-code system that determines whether AI generation across the whole org produces compliant work or plausible drift. They own the tokens (in DTCG-compliant form), the MDX component documentation that lets MCP-enabled agents read intended use rather than hallucinate props, the Figma Code Connect mappings, the Storybook MCP connection, and the drift detection that catches when the codebase and the system diverge.

The JD, in essence. Owns and evolves the token system in a DTCG-compliant, version-controlled form. Maintains the AI-readable layer: MDX docs, Code Connect, Storybook MCP. Builds and runs drift detection and the deprecation lifecycle. Ensures the system is the source of truth that AI agents and human designers both consume. Required: design-system depth plus genuine engineering practice (version control, CI, validation tooling) plus understanding of how AI agents read a system.

Comp band. Roughly $170K-$300K base per the 2026 ADP List, comparable to Design Engineer because the engineering depth is similar, with the top of the band for engineers who genuinely understand the agentic-consumption layer (MCP, Code Connect) rather than just maintaining a token file.

Career path and success metrics. Path: a designer who went deep on systems and learned engineering practice, or an engineer who specialized in design infrastructure. Success metrics: system-compliance rate of AI-generated work (the headline metric, because it is the whole point - an AI-readable system makes generation compliant), drift rate (how far the codebase diverges from the system between audits), and adoption (how much of the org's generation actually reads from the substrate). This role's success is measured by how well the rest of the org's AI works, which is a leverage metric, not an activity metric.

AI Design Lead

Mandate. The AI Design Lead owns the design function's AI strategy, governance, tooling, and capability-building as a full-time mandate. This is the role that does, as a job, the work the rest of this program teaches: running the pilot portfolio, writing the governance, selecting the stack, building the upskilling program, representing design in cross-functional AI governance, and defending the function's AI posture to executives. It exists because at a certain org size, AI strategy for design is too large and too consequential to be a design director's side concern, and needs a dedicated owner with the seniority to make calls and the credibility to defend them.

The JD, in essence. Owns the design-AI strategy, tool selection, and governance. Runs the pilot portfolio and the upskilling program. Represents design in the org's AI governance (ethics committee, IP review, accessibility). Defends design's AI posture and budget to leadership. Sets the standards for verification, provenance, and what stays human. Required: senior design leadership experience plus deep, current AI-design fluency plus the ability to write and defend executive-grade strategy. This is a leadership role, often reporting to the VP of Design or directly to the CPO.

Comp band. Roughly $200K-$320K base per the 2026 ADP List, at the top of the range because it is a senior leadership role combining strategy, governance, and deep AI fluency - a genuinely scarce combination. The band overlaps with director and senior staff because the role carries comparable seniority and scope.

Career path and success metrics. Path: a design strategist or design director who went deep on AI, or a principal IC who moved into AI leadership. Success metrics: the function's AI maturity (measured against a maturity assessment), the program's measured outcomes (pilot portfolio results, adoption, the cycle-time and quality metrics that hold up to finance), governance robustness (no IP, accessibility, or brand incidents), and crucially, the function's craft posture (that AI adoption raised leverage without breaking craft). Measured on outcomes and risk avoided, the way any leadership role is.

These four roles are not rebrands. Each exists because AI created a capability gap the old designer-and-manager structure had no name for: the porous design-to-code boundary, the system-as-substrate, the full-time AI strategy mandate, and brand-as-generative-system. Define them precisely or hire the wrong people into the wrong bands.

Brand Systems Architect

Mandate. The Brand Systems Architect owns the brand as a generative system rather than a set of finished assets - the rules, tokens, motion principles, voice, and guardrails that let the brand be produced at AI volume without converging toward the model's generic average. This role emerged when brand teams realized that a year of AI-generated marketing assets quietly homogenizes a brand toward the training-data mean, and that the defense is not more hand-made marks but an architected system that encodes distinctiveness into the rules the generation follows. They design the brand-anchor reference sets, the generative-brand-system spec, the distinctiveness budget, and the governance that keeps generated brand work recognizably yours.

The JD, in essence. Architects the brand as a generative system: tokens, motion, voice, generative rules, and anti-convergence guardrails. Owns the distinctiveness budget and the brand-asset governance. Designs the patterns (brand-anchor reference sets, voice scaffolds) that keep AI-generated brand work distinct. Audits for drift and convergence across the asset library. Required: senior brand and visual design depth plus systems thinking plus genuine fluency in how generative image and copy models converge and how to resist it.

Comp band. Roughly $160K-$290K base per the 2026 ADP List, with the spread driven by seniority and by whether the architect genuinely understands generative-model behavior (top of band) or is a senior brand designer with a new title (bottom). In a layoff year, traditional brand designers are plentiful; brand designers who can architect an anti-convergence system are scarce.

Career path and success metrics. Path: a senior brand or visual designer who went deep on systems and generative-model behavior. Success metrics: brand distinctiveness over time (measured against convergence - does the brand still look like itself after a year of AI-generated assets), brand-system adoption (how much generated brand work actually runs through the architected guardrails), and asset-library coherence. Measured by distinctiveness held, not assets produced, because production was never the scarce thing.

Banding and Defending the Comp to Finance

Writing the JDs is half the job; the other half is defending the comp bands to a finance team that, in a layoff year, has every incentive to push them down. The defensible argument is not "designers are worth this" - it is a scarcity-and-leverage argument grounded in the market data. These four roles command their bands because the dual or triple fluency each requires (design plus engineering, design plus systems plus agentic-AI understanding, leadership plus strategy plus AI, brand plus systems plus generative-model fluency) is genuinely scarce, and the ADP List bands reflect that scarcity. You are not paying for a designer; you are paying for a combination the market prices at $150K-$320K, and the top of each band is scarcer than the bottom.

The leverage half of the argument is what wins the budget: each of these roles is a force-multiplier on the rest of the function. A Design Systems Engineer who makes the system AI-readable raises the quality of every AI-generated artifact across forty designers; an AI Design Lead who runs the program well raises the whole function's leverage. You are not adding headcount that does one designer's worth of work; you are adding a role whose output is the improved output of everyone else. That is the argument a CFO funds, because it is denominated in leverage rather than in craft, and leverage is the language finance speaks. The Layoffs.fyi context, used honestly, actually helps here: in a year when the org is cutting traditional roles, the case for the few roles that multiply everyone else's output is stronger, not weaker, because they are how the smaller org stays capable.

A Worked Example: Writing the Design Engineer JD

Make the JD-writing concrete with the Design Engineer, the role most likely to be written badly because it is the most tempting to define as "designer who codes." A bad JD lists React, Figma, and "strong eye for detail" and attracts either designers who learned some code or engineers who learned some Figma - neither of which is the role. The good JD defines the role by its mandate (the design-to-code boundary) and its distinctive value (fidelity), not by a tool checklist.

It opens with the mandate in one sentence: "Owns the translation of design intent into production front-end, working fluently across the design-to-code boundary that AI tools made porous, and shipping to a craft standard neither a pure designer nor a pure engineer reaches alone." It names the AI-specific work explicitly: "Reads and corrects AI-generated component code, catching where it drifts from design intent - the focus rings, the states, the responsive behavior, the token alignment the generation got wrong." It states the dual requirement without hedging: "This role requires genuine fluency in both front-end engineering and design judgment; it is not a designer who dabbles in code or an engineer who dabbles in design." It names the band honestly ($180K-$300K, with the top for genuine dual fluency) and the success metrics that are not output volume (design-to-code fidelity, QA-catch rate, craft quality against the system standard). And it names the career path so an internal designer reading it sees a door rather than a threat: "Senior product designers who build real front-end skill grow into this role." That JD survives a hiring committee because it screens for the actual combination, survives a budget review because the band is market-grounded and leverage-justified, and reassures the existing team because it shows the path. Multiply the discipline across all four roles and you have the artifact: four JDs that hire the right people into the right bands and tell your own team what the new map looks like.

Putting It to Work This Quarter

Write each JD from the mandate down, never from a tool checklist up, because the tool checklist attracts the adjacent-but-wrong candidate and the mandate attracts the actual role. For each of the four, name the capability gap it fills, the distinctive value it provides, the band grounded in the 2026 ADP List, the career path from your existing roles, and the success metrics that measure leverage and fidelity rather than output volume. Pressure-test each band against the Layoffs.fyi reality - plentiful at the bottom, scarce at the top - and band honestly.

Then publish all four, internally as much as externally, because the JDs are how your existing team learns what the new map is and how they fit on it. The deliverable is not four hiring documents; it is a precise, defensible definition of the four roles an AI-native design org actually needs, banded to the 2026 market and pathed so your current designers see growth rather than replacement - which is the difference between roles that strengthen the function and titles that frighten it.

Key Takeaways

• The four growing design roles in 2026 - Design Engineer, Design Systems Engineer, AI Design Lead, Brand Systems Architect - each exist because AI created a capability gap the old structure had no name for, and pay roughly $150K-$320K base in major US markets per the 2026 ADP List.
• Design Engineer ($180K-$300K) owns the porous design-to-code boundary, reading and correcting AI-generated component code to a craft standard; measured on fidelity and QA-catch rate, not output volume. Requires genuine dual fluency, not a designer who dabbles in code.
• Design Systems Engineer ($170K-$300K) owns the design system as AI-readable infrastructure - DTCG tokens, MDX docs, Code Connect, MCP, drift detection - and is measured by the system-compliance rate of AI-generated work across the org, a leverage metric.
• AI Design Lead ($200K-$320K) owns the function's AI strategy, governance, tooling, and upskilling as a full-time leadership mandate, measured on AI maturity, program outcomes, governance robustness, and the function's craft posture.
• Brand Systems Architect ($160K-$290K) owns brand as a generative anti-convergence system - rules, tokens, guardrails, distinctiveness budget - measured by distinctiveness held over time against model convergence, not assets produced.
• Write JDs from the mandate down, never a tool checklist up; band against the 2026 market (plentiful at the bottom, scarce at the top in a layoff year); defend comp to finance with a scarcity-and-leverage argument; and publish internally so existing designers see a growth path, not a threat.