Build the infrastructure
work runs on
Plane is work infrastructure, run by millions of people, and now by their AI agents. Over the next decade, teams will rebuild how they plan, decide, and ship. We are building the layer underneath all of it, and we are hiring in Hyderabad and San Francisco, across engineering, marketing, sales, and QA.
Why Plane, and why now
Every generation rebuilds the infrastructure of work. Paper gave way to the PC, the PC to the cloud, and each time a small number of teams got to lay the rails everyone else runs on. That moment is here again, and this time the newest workers are not people.
Agents are joining teams now, and they are arriving into a mess we made: work scattered across disconnected tools, context split between issues in one place, documents in another, and decisions in a chat that scrolled away. People barely cope with this. Agents cannot cope at all, because software can only act well on work it can see whole.
So the infrastructure problem of the next decade is this: put all of a company's work in one coherent space, where humans and agents can find anything, hand anything to each other, and act with full context. That is Plane, and that is the job.


Work sits in tools that cannot see each other. Plane gives humans and agents one coordinate space.
What we are building
Plane began as an open source project and grew into work infrastructure that millions of people run, from two-person startups to heavily regulated enterprises, many of them on their own servers. The codebase is public, so you can read what you would be working on before you apply.
Five things sit at the front of the roadmap: agents, both prebuilt and built by customers; an API other developers want to build on; interfaces designed for the decisions agents should not make; handoffs that work in both directions between people and agents; and a data layer that stays fast on a customer's own hardware under production load.


The next few years, in five directions. Everything on this figure needs hands. Some of them could be yours.
How we work
Six things you would notice in your first month.
Humans direct, systems structure, agents execute
We run the company the way the product works. Agents handle triage, scheduling, first drafts, and summaries here, the same as they do for customers. Most of your week goes to decisions.
We build in the open
The code is public and users read the commits. Your first pull request gets reviewed by people who do not work here.
We take the extra hour
Infrastructure earns trust over years and loses it in one bad release. Two million people depend on what ships, which is the argument for doing it properly the first time.
You own the whole problem
Teams are small and the authority is real. You will own an outcome end to end, and you will present the work yourself.
Speed of thought is the target
Every piece of toil we remove brings a team closer to moving as fast as it can think. We hold ourselves to the same bar we build for: less ceremony, fewer handoffs, shorter distance from decision to done.
Customers run us on their own hardware
Plane runs inside regulated institutions, often fully air-gapped, on machines we never see. Security and sovereignty are engineering constraints we design against.
Who does well here
Plane suits some people and not others.
This fits you if
Think twice if
How hiring works
You apply and a person reads it. We talk once or twice about work you have shipped and problems we currently have. If it still looks right on both sides, you do a paid work trial: two to five days of real work with the team you would join, scheduled around your existing commitments. Everyone at Plane has done one, engineers and executives alike. You are paid regardless of the outcome, and you get a decision with specific feedback within three working days of your last trial day. The reasoning and the commitments are at plane.so/work-trials.
The codebase is public at github.com/makeplane/plane. Contributors who ship are our easiest hires.


The work trial is the heart of the process.
Open roles
The practical terms
Equity in every offer
Everyone who builds Plane owns part of Plane. Every offer includes meaningful equity.
How we pay
The range in a listing is the range we hire in, and we do not pay people less for negotiating less.
Health cover for your family
Medical cover for you and your family, wherever the role is based.
Equipment
The hardware you want and a working home setup, arranged before your first day.
Time off
Time off that people visibly take, founders included. Infrastructure is a long game and we staff it like one.
Location
Every listing states its location and workplace type. If you are the right person in the wrong city, write anyway.
Paid work trial
Every hire, every level, does a paid work trial before an offer, with the rate agreed in writing first.. The full commitments are here.
You always get an answer
We answer every application, give specific feedback after every trial, and put honest numbers on the table at the offer stage.
Questions you might have
Anything not answered here goes to careers@plane.so, and someone from our team will get back to you.
Yes, through either door. Write to us about the thing you would build here and why it matters. Or skip the writing, since the codebase is public and a merged pull request tells us more than a cover letter.
No. We hold hiring to the same principle we build the product on: agents hold the toil, people hold the judgment. Agents help us schedule, transcribe, and organize. A person reads every application, people conduct every conversation, and the people you worked with during your trial make the call.
The last step of our process: two to five paid days of real work with the team you would join, on your schedule, with the rate in writing before you say yes and payment, whatever the outcome. It evaluates us as much as it evaluates you. The full page, including every commitment we make, is at plane.so/work-trial.
We hire for slope and for evidence of building, not for years served. If you have shipped things, show us the things; side projects, open source, and unreasonable personal obsessions all count. The pull request door has no seniority requirement.
The next era of work needs its builders
If you want your decade to compound into something everyone uses, there is room here.