Figma Just Made My Front-End Job Spec Obsolete: the 4 Screens I Added After Config India

I had a front-end requisition open on Wednesday morning. It asked for four years of React, “pixel-perfect translation of Figma designs into reusable components”, and familiarity with Tailwind. By Thursday I had closed it and written a different one. The reason was a product announcement from an event I was not at, in a city I have never hired in, and a single ratio buried in a quote.

What Figma announced, and the one number that matters

On 15 October 2026, at its first Config event in India, Figma announced a set of features aimed squarely at the problem of AI agents producing output nobody asked for. TechCrunch covered it under the headline Figma announces new features to define how agents work on its platform, filed at 9:30 PM Pacific on 14 October, which is the morning of the 15th here in the Gulf.

Three things shipped:

• Figma Specs. A Markdown-based editor where a team writes down its design language in plain text. The document can reference elements on the canvas and embed FigJam diagrams, code layers and designs. It is readable by people and, crucially, by agents, which are meant to treat it as the rulebook.
• Code layers in public beta. Announced in private beta in June, now open to a wider group. Code sits on the canvas alongside the design, prototypes become genuinely interactive, and the agent can turn a design into code or edit a portion of existing code on request.
• MCP support for over 20 new tools, including Open Code, Dia, Grok Bot and the Indian AI startup Sarvam. Figma also wired Payload, the headless CMS it acquired last year, into Figma Make, and said Payload downloads have risen sixfold in twelve months.

None of that, on its own, would make me rewrite a job advert. This did. Figma’s chief design officer Loredana Crisan told TechCrunch:

“There are 17-times more lines of code being produced today than in the past. But when you’re looking at releases, only 1.3-times more releases. A lot of that code actually is not necessarily built to ship, but really built to discover what the product is. It’s built to design.”

Read that twice if you are hiring. Seventeen times the code. One point three times the shipped work. The ratio between what gets written and what survives contact with a release has collapsed by roughly a factor of thirteen. A company publishing that figure is not selling you more output. It is telling you, in its own numbers, that output stopped being the constraint.

Expert take 1: the handoff role is the one being automated, not the engineer

For a decade the entry point into front-end work in this region was translation. A designer produced a file, an engineer turned it into components, and the gap between the two was absorbed by Slack messages and a shared sense of what looked right. That gap was the job description. I have written it dozens of times for employers in Dubai Internet City and DIFC.

Specs closes the gap by writing it down, and code layers close it by removing the handoff altogether. When the design, the rulebook and the code live in the same file, and an agent can move between them on request, nobody is being paid to carry a design across a boundary. What remains on the engineering side is harder and more senior: authoring the rulebook that is precise enough to constrain an agent, and reviewing what comes back when it is not.

I want to be careful here, because the easy conclusion is wrong. This is not a story about hiring fewer people. Figma’s own ratio says the volume of candidate code went up seventeenfold while the volume of shipped work barely moved. Somebody has to triage that. In my experience the teams that get into trouble are the ones that read “AI writes the components now”, cut the front-end requisition, and then discover six months later that their component library has four greys, three button variants that are nearly identical, and no one who can say which is correct.

Expert take 2: in the UAE, the spec has a clause most teams forget

There is a regional wrinkle that makes the spec question sharper here than in most markets. A large share of products built in Dubai ship in Arabic and English, which means right-to-left mirroring is not a nice-to-have at the end of a project. It is a property of every component: icon direction, padding asymmetry, numeral formatting, text truncation, the direction a drawer slides in from.

An agent working from an underspecified rulebook will produce a left-to-right component that passes every visual check an English-speaking reviewer runs, and then breaks the moment the locale flips. I have seen this on a government-adjacent portal where the Arabic build shipped with a progress indicator that filled from the wrong side. Nobody caught it for three weeks, because the person reviewing the generated code was reviewing code, not behaviour in the second locale.

So when I evaluate a front-end candidate in Dubai now, bilingual layout competence has moved from a bonus line at the bottom of the CV to one of the first things I probe. It is also an efficient screen, because it is hard to fake: either someone has shipped a mirrored interface and has opinions about logical CSS properties, or they have not.

Expert take 3: MCP support turns your design system into an interface with a contract

The MCP expansion got the least coverage and will matter longest. Once more than twenty external tools can read a design system through a protocol, that system stops being a folder of files that a team maintains loosely and becomes something closer to an API. Things that were previously untidy but survivable, such as a token named grey-400 that is actually used for borders, become breaking changes for whatever is reading them downstream.

That changes the seniority of the person who owns it. Maintaining a public interface requires versioning instincts, deprecation discipline and the willingness to say no to a one-off colour for a campaign page. Those are platform engineering habits applied to design. In the Dubai market, very few CVs state them outright, which is why the screens below are behavioural rather than technical.

The four screens I added this week

Each takes under an hour, and each one is designed to be unfakeable by a candidate who has only consumed a design system rather than maintained one.

1. The deliberately incomplete spec

I hand over a one-page Markdown spec for a data table component and a generated implementation that technically satisfies every line of it. The spec says nothing about keyboard navigation, loading states, right-to-left behaviour, or what happens when a cell value is empty. Then I ask a single question: is this ready to ship?

What I am listening for is whether the candidate interrogates the brief or the code. Strong candidates spend the first two minutes listing what the spec fails to say and ask who decides. Weaker candidates start reading the implementation top to bottom and report formatting preferences. The second group will approve an agent’s work all day long.

2. The token audit

I give them a component library containing four near-identical greys, two spacing scales that disagree, and a button component with a hard-coded hex value. The task: propose a consolidation that does not break existing screens, and explain the order you would do it in.

The answer I want includes an inventory step before any change, a deprecation path rather than a find-and-replace, and a question about who else reads these tokens. Candidates who immediately propose deleting three greys are telling me they have never had a downstream consumer complain.

3. The right-to-left pass

Screenshot of a component in English, and a request: list everything that has to change for the Arabic build, and which of those changes the code should handle automatically. Good answers reach for logical properties and locale-aware formatting rather than a mirrored stylesheet, and they mention the things that must not flip, such as phone numbers, code snippets and media playback controls.

4. The review budget

This one is a conversation, not an exercise. I describe a week in which agents have opened eleven pull requests against the component library, and I ask how they would spend their review time. The answer reveals whether someone has a model of risk. I am looking for triage by blast radius: a change to a shared token gets a careful read, a change to one screen’s copy does not. Candidates who say they would review all eleven equally have not yet worked in a team where generation outpaced review, which, per Figma’s own ratio, is now most teams.

What I would not change yet

Two cautions, because newsjacking a product launch into a hiring strategy is how people end up with an org chart built on a press release.

First, code layers are in public beta and Specs is in open beta. Beta features get rebuilt. I would not restructure a team around a workflow that may look different in March, and I would not write a job title with a vendor’s product name in it. The screens above deliberately test judgement about specifications and generated code in general, not fluency in one tool.

Second, the 17x figure is a vendor statement about an industry, not a measurement of your codebase. If your team ships four releases a quarter and nobody is using an agent on the component library, none of this is urgent for you. Check your own ratio before you act on someone else’s. The cheapest version of that check is a count of pull requests merged against pull requests opened over the last eight weeks, split by whether a human or a tool authored them.

What this costs in Dubai, concretely

The gap between the first and second row is roughly AED 10,000 a month. In a team of six front-end engineers, promoting or hiring one person into the second row costs less than the salary of one additional implementer, and it is the single change most likely to keep a component library coherent while agents write against it. That is the trade I would make this quarter.

If you are reworking front-end roles more broadly, our guides on building a dedicated front-end team in Dubai and writing a developer job description that attracts the right applicants cover the mechanics, and structuring technical interviews for remote developers covers how to run the screens above without burning a candidate’s weekend. For stack-specific hiring, see hiring a React developer in the UAE.

Frequently asked questions

What did Figma announce at Config India on 15 October 2026?

Three things that matter to engineering teams. Figma Specs is a Markdown-based editor that lets a team write down its design language in one document, which can reference canvas elements and embed FigJam diagrams, code layers and designs, and which both people and AI agents read as the rulebook. Code layers moved from private beta, announced in June 2026, into public beta, adding real code to designs on the canvas so prototypes become interactive and an agent can turn a design into code or edit part of that code. Figma also said its MCP now supports over 20 new tools, including Open Code, Dia, Grok Bot and the Indian AI startup Sarvam, and it integrated the Payload headless CMS it acquired last year with Figma Make. TechCrunch reported the announcements on 14 October 2026 Pacific time, which is 15 October in the Gulf.

Does Figma Specs mean Dubai employers need fewer front-end developers?

No, and the numbers Figma itself published point the other way. Chief design officer Loredana Crisan told TechCrunch that roughly 17 times more lines of code are being produced today than in the past, while releases have risen only 1.3 times. The gap between code produced and code shipped is where the work now sits: deciding which generated code is worth keeping, folding it into a design system, and getting it through review and release. That is judgement work, and it is senior. What changes in Dubai is the shape of the requisition rather than the headcount. Teams that used to hire a front-end developer to translate a Figma file into components now need someone who can author the spec the agent follows, review generated output against it, and keep a token and component library honest while several agents write against it at once.

How do I test whether a front-end candidate can work with design system specs and generated code?

Give the candidate a short, deliberately incomplete spec and a generated component that technically satisfies it, then ask them to find the gaps. A strong candidate will ask what the spec does not say: focus and keyboard behaviour, right-to-left mirroring for Arabic layouts, loading and empty states, the token that should have been used instead of a hard-coded hex value, and what happens at 200 percent text zoom. A weaker candidate reviews the code line by line and never questions the brief. The second exercise worth running is a token audit: hand over a component library with four near-duplicate greys and ask how they would consolidate them without breaking existing screens. Both exercises take under an hour and they separate engineers who own a system from engineers who close tickets.

What should a Dubai employer pay a front-end engineer who owns the design system in 2026?

In the Dubai market in Q4 2026, a mid-level front-end engineer who implements components to a brief sits around AED 22,000 to 30,000 per month. An engineer who owns the design system, writes the spec that agents and other engineers work from, and reviews generated code against it commands AED 32,000 to 45,000 per month, and the top of that band goes to people who have shipped and maintained a token-based library across several products. The premium is real but it is narrower than the premium on AI infrastructure roles, which makes this one of the better-value senior hires available in the UAE right now. Remember that Dubai salaries are quoted gross and gross equals net take-home, so the comparison against a London or Berlin offer is wider than the raw figure suggests.

Sources

• Figma announces new features to define how agents work on its platform, TechCrunch, 14 October 2026, including the quoted remarks by chief design officer Loredana Crisan.
• Figma product news and release notes, for the current beta status of Specs, code layers and MCP support.

Sebastian

Mobile App & Hiring Expert at HireDeveloper.ae. Works with UAE employers on front-end, mobile and design system roles, with a focus on bilingual Arabic and English products and on screening for judgement rather than tool fluency.