See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Monday.com is redesigning its core backend contracts and runtime so that autonomous AI agents, not just human engineers, are treated as first-class consumers of internal services, signaling that agent-driven traffic is becoming a foundational architecture concern rather than an edge feature.
About monday.com
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.
About the team
Server Foundations builds the core of monday.com’s backend: the runtime, the communication layer, and the standards that define how every service is built and operated. This is core engineering. We don’t sit at the edge of the system, we are the layer that every other team builds on.
Our users are the engineers and AI agents who run 300+ microservices and a growing fleet of autonomous agents. Our product is consumed through code: SDKs, runtime modules, async and sync communication, and applicative-level infrastructure. Through mondayCore, our flagship program, teams simply declare what they need, and the platform delivers it with the right behavior built in: resilient, observable, and scalable by default.
We’re in the middle of a significant architectural shift. Autonomous agents now invoke services, react to events, and make decisions without a person in the loop. We’re designing the contracts, runtime, and patterns that make monday.com’s backend reliable whether the actor is a person or a machine.
What we build becomes the standard for the entire engineering organization. When we get it right, every service and every agent benefits automatically.
About the role
This is a role for engineers who want to do architecture and hands-on engineering at the highest level. You’ll design the foundations and write the code that runs them, at a scale where every decision reaches hundreds of services.
Define the blueprint for how services get built, behave, communicate, fail gracefully, and are consumed, for human developers and AI agents alike.
Own significant technical initiatives end-to-end: from identifying the problem, through design and implementation, to rollout and adoption across the fleet.
Build core platform infrastructure hands-on, with the depth and quality bar that code at the heart of the system demands.
Design for agents as first-class consumers: machine-readable contracts and errors, clear delivery guarantees, and isolation between agent-driven and user-facing traffic.
Drive platform decisions across team boundaries. Platform work is organizational as much as technical.
Help define how we measure and enforce standards at scale.
Mentor engineers, lead design reviews, and help shape how the group thinks about platform problems.
Requirements
6+ years of backend engineering experience, with meaningful depth in distributed systems.
A track record of leading technical work that influenced design decisions across multiple teams, not just your own.
A genuine interest in platform and infrastructure work: building the foundations other engineers build on.
An AI-first mindset: you think about what happens when machines, not just people, consume your systems, and design for autonomous consumers as a first-class concern.
The ability to bring clarity to ambiguous, cross-cutting problems and drive them to executable solutions without waiting for a spec.
Experience with async and event-driven systems: Kafka, job queues, pub/sub patterns- advantage.
Background in developer-facing tooling, SDKs, or internal platform work- advantage.
Familiarity with multi-language backend environments (we work across TypeScript, Go and Rust, but we don't expect you to arrive knowing all of those)- advantage
Depth in observability, reliability engineering, or large-scale migration and rollout practices- advantage.
#LI-DNI
monday:67b42428-c5c6-4d2d-865d-1e35e271740cmondayThis posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.