Software Engineer, Full Stack at Plane

Job description

ABOUT PLANE Plane's mission is to build the infrastructure the world's work runs on. Every organization runs on three things: the projects it's driving, the knowledge it keeps, and the requests it fields. Plane brings all three into one open, adaptable platform: simple enough for any team to adopt, dependable enough for organizations to build on. And we are building it for a future where humans and AI agents do that work together. Plane began in public on GitHub at the end of 2022. Since then it has grown into a work management platform used by teams around the world: 55,000+ stars, 5,000+ forks, and a contributor community that reads our code and files our issues. Organizations run Plane as a managed Cloud service, on their own infrastructure, or inside fully isolated environments. Building in the open keeps us close to users and raises the standard for everything we ship. Plane is the #1 work infrastructure in aerospace, defense, financial services, and other regulated industries: organizations whose requirements for control, auditability, and data residency rule most software out. When the strictest buyers pick a system of record, that choice means something. Adoption is growing fastest on Plane Cloud and in sovereign clouds, deployments that keep everything inside a country's own borders and rules. Plane is backed by top investors and built across San Francisco, London, and Hyderabad. We work in tightly knit teams, stay close to users, and care about the visible product as much as the unglamorous details that make software dependable. People own problems end to end, and we add process only when it helps the work. HUMANS AND AGENTS We believe the next decade of work will be done by humans and AI agents together. Not agents replacing people, and not a chat window bolted onto software built for humans clicking around, but both working in one system of action, where an agent's work is as visible and as accountable as a person's. Most software treats AI as a feature. We treat agents as a kind of worker, and that changes what the system underneath has to be. Agents are only as good as the context they can see and the state they are allowed to change, so shared context, explicit state, durable history, and accountable action are not items on our roadmap. They are the product. Plane is built so that when an agent acts, the humans responsible can see what happened, why, and on whose authority, and the record survives. This is what the infrastructure is for: making the future where humans and agents work together useful, legible, and fully within the organization's control. Every role at Plane is some part of building that. ABOUT THE ROLE Collaborative editing is the one feature where the client and the service cannot be reasoned about separately. A cursor moving in someone's browser, the document state on the wire, the queue that fills up while a laptop is closed, and the reconciliation when it opens again are all the same problem, and splitting it across two teams is how products end up losing people's work. You will own that problem on both sides: the React editing surfaces and the Node services carrying document state, including what happens when the network disappears mid-sentence and when two edits, or a person's edit and an agent's, cannot both be right. You will work from San Francisco with designers and backend engineers here and in Hyderabad, and with community contributors who will find your edge cases faster than you will. WHAT YOU'LL DO - Own collaborative editing end to end, from the React editor surface through the Node services that carry and persist document state. - Own what happens offline: what the client keeps, what it queues while the network is gone, and how it reconciles when the connection returns without asking the user to think about it. - Design the realtime transport and the conflict resolution behind it, including which change wins when two cannot both apply and how that decision is recorded. - Build the editing surfaces agents act through, so an automated change shows its authorship and authority as clearly as a person's. - Work daily with designers and backend engineers in San Francisco and Hyderabad, and answer community contributors in public issue threads. - Chase data loss reports you cannot reproduce, on networks, browsers, and self-hosted versions you will never have in front of you, because a lost paragraph is the bug people remember. WHAT YOU'LL BRING - You have shipped both React and Node in production, in TypeScript. Not a frontend engineer who once wrote an endpoint, or the reverse. Point us to something that was yours on both sides. - You have worked inside a rich-text editor framework. ProseMirror, Lexical, Tiptap, or comparable, at the level of schema and document model rather than plugin configuration. - You have built realtime features over WebSockets. Reconnection, ordering, and what your system does when a client has been away for ten minutes. - You have built an application that works offline. Service Workers, IndexedDB, queued mutations, and a reconciliation strategy you can defend. - You are comfortable in Postgres beyond the ORM. You can read a query plan, add an index, and say why it helped. NICE TO HAVES - You can argue about CRDTs and operational transformation from experience rather than from blog posts. - You have contributed to Plane, run it self-hosted, or maintained another open project people rely on. - You have built and shipped an Electron desktop application, including packaging and updates. - You have built systems where AI agents act on real data, and you have opinions about state, permissions, and audit trails. TECH - Frontend: React, TypeScript, Tailwind CSS, MobX - Backend: Node.js and TypeScript, Python/Django, Postgres, Redis - Editing and sync: ProseMirror based editor, WebSocket sync engine backed by Elixir, Service Workers, IndexedDB - Desktop: Electron - Build: Vite, Rolldown, shared React component library - Infrastructure: AWS, Kubernetes - Observability: Datadog, Sentry - Everyday tools: GitHub, Plane (yes, we run on it), Figma, Slack WHY PLANE? Every company says it is different. We will try evidence instead. The scope is real. We are a passion team serving companies of every size, including some of the largest in the world. Something you ship this month will run inside a Fortune 500 company and a 50-person startup in the same week, and you will hear from both. The constraints make you better. Plane runs in our cloud, in customers' clouds, and on machines that will never touch the internet. Much of the work happens in the open, where the issues, the fixes, and the roadmap conversations are public. Building software that survives all of that is harder than building an ordinary SaaS product, and it is a better education than most companies can offer. The people-and-agents future is being built here, in production. We think humans and AI agents will share one system of action for work. We are building that system now, for customers who already depend on it, and you will work on that problem directly whatever your role. Your name is on the work. The teams are deeply connected enough that credit and responsibility both find you fast. That is some pressure. Mostly it is the fun part. If that sounds like your kind of place, we would like to meet you. Plane is an equal opportunity employer. We do not discriminate based on race, color, religion, gender identity or expression, sexual orientation, national origin, age, disability, veteran status, or any other protected characteristic under applicable law.

Requirements

Must-haves

This is what the infrastructure is for: making the future where humans and agents work together useful, legible, and fully within the organization's control. Every role at Plane is some part of building that.
Own collaborative editing end to end, from the React editor surface through the Node services that carry and persist document state.
Own what happens offline: what the client keeps, what it queues while the network is gone, and how it reconciles when the connection returns without asking the user to think about it.
Design the realtime transport and the conflict resolution behind it, including which change wins when two cannot both apply and how that decision is recorded.
Build the editing surfaces agents act through, so an automated change shows its authorship and authority as clearly as a person's.
Work daily with designers and backend engineers in San Francisco and Hyderabad, and answer community contributors in public issue threads.
Chase data loss reports you cannot reproduce, on networks, browsers, and self-hosted versions you will never have in front of you, because a lost paragraph is the bug people remember.
You have shipped both React and Node in production, in TypeScript. Not a frontend engineer who once wrote an endpoint, or the reverse. Point us to something that was yours on both sides.
You have worked inside a rich-text editor framework. ProseMirror, Lexical, Tiptap, or comparable, at the level of schema and document model rather than plugin configuration.
You have built realtime features over WebSockets. Reconnection, ordering, and what your system does when a client has been away for ten minutes.
You have built an application that works offline. Service Workers, IndexedDB, queued mutations, and a reconciliation strategy you can defend.
You are comfortable in Postgres beyond the ORM. You can read a query plan, add an index, and say why it helped.
Frontend: React, TypeScript, Tailwind CSS, MobX
Backend: Node.js and TypeScript, Python/Django, Postgres, Redis
Editing and sync: ProseMirror based editor, WebSocket sync engine backed by Elixir, Service Workers, IndexedDB
Desktop: Electron
Build: Vite, Rolldown, shared React component library
Infrastructure: AWS, Kubernetes
Observability: Datadog, Sentry
Everyday tools: GitHub, Plane (yes, we run on it), Figma, Slack

Nice-to-haves

You can argue about CRDTs and operational transformation from experience rather than from blog posts.
You have contributed to Plane, run it self-hosted, or maintained another open project people rely on.
You have built and shipped an Electron desktop application, including packaging and updates.
You have built systems where AI agents act on real data, and you have opinions about state, permissions, and audit trails.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

aireacttypescriptpostgresnode.jspythonawskubernetesfigma

Platform: ashby
Effort: quick

Benefits

Benefits detected in the listing.

Pto