Skip to content
monday.com

Design Operations Lead, AI Enablement

Tel AvivHybrid · Israel
Staff · FullTime · Product Design
POSTED 28 SEPTVERIFIED 19H AGO
Apply Ask
Role
41 days opentrue age
Posted 28 Sept
Pay
$56k–$137kno pay posted
Market p25–p75
$56k–$137k
Israel · n=8 · 365d to 6 Nov
Companymonday.com →
133open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
23,321open · Staff Other
All other
625,165open
All tracked boards · live 8 Nov · n=23,321

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.

Source · monday.comFirst seen 7 NovOriginal ↗