Product Designer

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.

• Own the design of core workflow surfaces (issues, cycles, views) end to end — from problem framing through high-fidelity spec, with the judgment calls in between being yours to make.
• Decide where Plane's design system bends and where it holds. You'll build new patterns when the system doesn't have an answer, and push back when a one-off request would fragment it.
• Run usability tests and read the resulting friction points as design problems, not just bug lists — then reprioritize your own roadmap based on what you find.
• Design for two audiences at once: people using Plane's cloud product and people running it self-hosted on infrastructure and screen sizes you can't control or predict.
• Work daily with engineers and PMs across San Francisco and Hyderabad, and expect your Figma files to get scrutinized in public issue threads by users you'll never meet.
• Defend a design decision to an engineer who's already scoped the easier version, in writing, without a research study to hide behind — this happens more than the polished parts of the job.

• You've shipped end-to-end product design work — you can walk us through one project from ambiguous problem to shipped interface, including a decision you'd make differently now.
• You design dense, data-heavy interfaces well — task lists, tables, kanban boards, or similar — not just marketing pages or onboarding flows.
• You're fluent in Figma and can produce developer-ready specs — a component built from your file shouldn't need a clarifying Slack message.
• You've worked inside or built a design system, and you understand the tradeoff between consistency and a designer's desire to solve each screen fresh.
• You write and present clearly enough that your rationale survives contact with an engineer who disagrees with you — in a doc, a Slack thread, or a room.

• 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.
• 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.