Search jobs

ABOUT THE TEAM

Teams do their best work when they’re aligned, and alignment depends on shared context. Today, the context that matters most to a team is scattered across a dozen tools: tickets in Jira and Linear, specs in Confluence and Google Docs, decisions buried in meeting notes, threads in Slack and Teams. Every new conversation starts with someone hunting it down.

We’re changing that. The Integrated Workflows team is building the layer that brings a team’s real working context into Mural, so people (and the AI working alongside them) can align on shared knowledge and design the workflows they need. When this works, a person opens a canvas and the project, the open work, the last three meetings, and the doc everyone keeps referencing are already there. No team should have to start from a blank canvas. That’s the problem we’re solving, and we’re early enough that the person in this seat will shape how it’s done.

YOUR MISSION

This isn’t connector maintenance. You’ll be defining how an AI-native product reaches into the outside world: what context to pull, how to represent it so models can reason over it, how to respect permissions and privacy across systems that each model them differently, and how to make all of that feel effortless to the end user. Few teams anywhere are working at this intersection of AI, integrations, and collaborative product design.

WHAT YOU'LL DO

• Design and build connectors, including MCP-based connectors, that bring context from systems of record, docs and wikis (Confluence, Google Docs, Notion, and others), meeting notes, and communication tools into the Mural canvas
• Shape how that context is modeled, normalized, and made useful to users, so the canvas becomes a live picture of how a team works rather than a snapshot of one meeting
• Bridge product and engineering: translate messy realities (different auth models, data shapes, rate limits, permission systems, partner review processes) into a product experience that just works
• Build the integration platform, the shared frameworks, services, and patterns that let any team at Mural ship connected, context-aware experiences without starting from scratch
• Own the security and trust posture of everything crossing our system boundary, including permissions, data handling, and graceful behavior when an upstream service misbehaves
• Maintain and evolve our public API with the backwards-compatibility discipline a published interface demands
• Lead projects end to end, from research and prototyping through release and iteration, with a bias toward getting value into customers’ hands quickly
• Use AI tools as a core part of how you build, and help the team get better at it