Senior Software Engineer, Integrated Workflows
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 1d ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 47d ago
The date the source published, not the day we noticed it (2026-09-15). Last seen at its source just now.
We have tracked this listing since 16 Sep 2026 (47 days). The employer's own board has carried it every time we have read it, most recently just now.
Is it remote?
Canada Remote, Argentina Remote
That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.
Who may apply?
Argentina, Canada
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay $167.5k–230k/yr
Middle 50% of 2876 listings that do state pay — Engineering · Senior · Americas · USD/year. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Ashby employer's own board first seen 47d ago · last seen just now
- location Canada, Argentina
The listing
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
Mentor colleagues, contribute to technical design, and raise the bar on code quality, testing, and documentation
WHAT YOU'LL BRING
A product mindset: you care about why something is being built and who it’s for, not just how
5+ years building and shipping production software at scale, with fluency in TypeScript/JavaScript and Node.js (React and Python are a plus)
Hands-on experience integrating with third-party APIs and platforms: OAuth and token lifecycle, webhooks, rate limiting and backoff, pagination, versioning, and degrading gracefully when things fail
Genuine curiosity about AI-driven products and development practices, and a willingness to experiment
A track record of designing scalable, reliable systems and delivering them iteratively
Strong communication skills and comfort leading technical discussions and navigating trade-offs
NICE TO HAVE
Familiarity with the Model Context Protocol (MCP) or interest in learning it
Experience with the Microsoft ecosystem (Teams, Office add-ins) or shipping through a partner marketplace or app review process
Experience designing or maintaining a public developer API
Background in high-growth or startup environments
Compensation offered will be determined by factors such as location, level, job-related knowledge, skills, and experience.
Equal Opportunity
We will ensure that individuals with disabilities are provided reasonable accommodation to participate in the job application or interview process, to perform essential job functions, and to receive other benefits and privileges of employment. Please contact us to request accommodation.