Design Operations Lead, AI Enablement

monday.com is the AI work platform powering the most ambitious teams. 250,000+ customers across departments use us to bring people, workflows, and AI agents together on one flexible platform where AI doesn't just assist, it executes. We move fast, build things that matter, and foster an ownership-driven culture where you're empowered to shape how organizations work and outpace their competition.

Design sits at the center of that. We're a large guild, 80+ designers and user researchers across Tel Aviv and London, shaping how millions of people and their agents get work done together.

About the role

Your mission: make it easy for designers to do their best work, and make working with agents a normal part of how they do it.

You'll join PD AI Foundations, the group that supports Product Design's AI needs and the systems behind it. Design Operations is the foundation of the guild: the systems, cadences, tooling, and enablement programs that let designers focus on craft instead of process friction.

We're building the platform for people and agents, so we expect you to work that way. When a problem lands, your first question is which part a person should handle and which part belongs to an agent, an automation, or a tool. That applies to your own work as much as the guild's.

The shape of the work stays the same whatever the problem: find the root cause, get people to agree on the fix, drive the plan, measure what changed, and scale what worked.

You'll work daily with design directors, guild track owners, and designers. User researchers are part of the guild and run their own operations, so you'll partner with Research Operations rather than own that side. You'll also work with Product Operations, Engineering, and Product Management, IT, Legal, Finance, Security, and People. The best partnerships here happen because people want to work with you, not just because the process says they have to.

What you'll own

1. The operating backbone Owning design operations means keeping work moving so designers have time to invent. This scope covers tooling, licenses, procurement, vendors, contracts, budget, travel, and designer onboarding. In practice, you automate repetitive tasks, plan ahead, document progress, keep teams informed, and resolve blockers early. You also maintain an active view of guild operations for leadership.

2. Agents and AI in daily design work Go looking for problems, gaps, and repetitive work, and build the agent, automation, or tool that fixes them, for your own work and the guild's. Decide when something still needs a person. Build it, ship it, and make sure people actually use it.

You'll also run enablement (access, learning tracks, office hours, champions, showcases) so working with agents becomes normal across the guild. Craft experts own the content. You own whether it reaches people and changes how they work.

3. Problems, found early Go looking for problems instead of waiting for them to reach you. Talk to designers directly, and come back with a solution already moving.

4. Change that sticks Launching is easy. You own what follows: who works differently, who knows why, who has the skills, and who follows up. You will define and measure program impact qualitatively and quantitatively.

5. Two sites, one rhythm Grow each site's own ownership and rituals, keep the guild-wide ones running across both, and keep everyone aligned on what's happening and who owns what.

What success looks like

Friction disappears before designers have to escalate it, because you found it first.

Agents and automations you built are used by people who aren't you, and nobody has to remember to run them.

New ways of working are still in use three months later.

Ambiguity turns into action: a fuzzy ask becomes a clear problem, an agreed plan, and a next step.

Cross-functional approvals move, because you know how the org works and who needs what.

The operating layer runs whether or not you're in the room this week.

Leadership can see how the guild is operating without chasing.

What you bring

Required

Design or creative operations experience at team or org scale, ideally across multiple sites, enough to run the operating backbone, build and ship automations, and drive change that actually sticks.

People person. You're approachable and comfortable with the operational and HR side of the job, not just the strategic parts. Designers bring you their problems and their wins, because they know you'll actually listen.

Building and automation. You automate your own work and other people's: workflow automation platforms, AI agents, scripting or low-code tooling, prototyping with AI coding tools. We care that you ship working things.

Proven adoption. You have introduced a change, driven a lasting shift in how people work, measured the result, and can account for one effort that did not stick.

Influence without authority. Nobody in the guild reports to you, and the work still moves. You get directors, partner teams, and designers behind something because the problem is clear, the evidence is there, and they trust you to deliver.

Root-cause diagnosis. You go to the people doing the work rather than relying on secondhand summaries, and you can tell a symptom from a cause.

Cross-level stakeholder alignment. You can turn a vague senior ask into something specific and agreed, including telling a leader that the problem they named isn't the one worth solving.

Organizational judgment. Procurement, vendors and contracts, security reviews, legal, HR, and budget cycles come with the job. You know when to work the process, when to find another route, and when to escalate, and you escalate with a recommendation attached.

Just-enough process. You put in the structure work needs, and you remove what slows people down.

Self-direction. You operate without oversight and surface status before anyone asks.

Design judgment. You don't need to be a designer, but you need to recognize excellent work and support teams pushing on UI, UX, interaction, and motion.

Clear written English. Plans, updates, and docs people actually read.

Nice to have

Design systems experience, and a sense of how they scale.

Background in design, research, product, or program management.

Comfort with data: you'll pull the numbers yourself to check whether something is working.

How you'll work

You own your work end to end. Find the problem yourself, get people aligned on a solution, run the program, show it worked, then scale. People always know where it stands.

You reach for agents first. Before adding a process or a person's time, you ask what an agent, an automation, or a tool could do instead.

You build first, then scale. A rough prototype that proves value beats a polished proposal waiting for approval.

You decide at your level. Most calls are yours. For the rest, bring options and your pick.

You close the learning loop. Anything you pick up externally comes back to the guild as a concrete takeaway within a week.

Why this role

monday.com is building the platform where people and agents work as one team. The design guild building that product should be one of the clearest proofs that it works. Today there's a gap between that ambition and what a designer's Tuesday actually looks like. Closing that gap is this job.

You get a large, respected design guild as your canvas, and an operating foundation solid enough to build on. You'll be shaping how the guild works and making a real impact. You support and guide how 80+ designers and researchers work: the tools and agents they reach for, the practices they pick up, and what "normal" looks like six months from now.

Leadership sets the direction. You turn it into something people can actually do on a Monday morning. If you want to be able to point at how a design organization works and say you built that, this is the role.

You'll also get:

Visible impact on how millions of people w