[Hiring] Senior Software Engineer, Quality Engineering @Plane Software, Inc.

Role Description

Plane ships to our cloud, to customers' clusters, and to machines that never touch the internet, which means a release has to be right before it leaves, because we often cannot see what happens after it does. You will own the automated test suite that gives us that confidence: what it covers, what runs on every pull request, and whether engineers believe it when it goes red. The interesting problems here are the ones that resist automation, including:

• Two clients editing the same document
• A browser that went offline mid-edit and came back
• A desktop app
• Agents acting inside a workspace where the correct outcome is a range rather than a value

You will work with product and engineers in San Francisco and Hyderabad, and with community contributors whose pull requests arrive in public with varying amounts of test coverage.

Qualifications

• You have built an automation framework, not only written tests inside one.
• Structure, fixtures, and test data are decisions you have made and then lived with.
• You are fluent in Playwright or Cypress, and in TypeScript or JavaScript.
• Enough to debug a failure from a trace rather than by rerunning it.
• You have made a flaky suite trustworthy again.
• You test APIs as well as interfaces.
• You have run suites in CI and cared how long they take.

Requirements

• Decide what gets tested and what does not. Coverage is a budget, and you spend it where a failure would reach a customer.
• Keep the suite fast and trustworthy. A flaky test that engineers learn to ignore is worse than no test at all, and removing that habit is part of the job.
• Test what customers actually run: Cloud, self-hosted, and versions months behind ours, across browsers and hardware we do not control.
• Triage failures nobody else wants to own, separating a real defect from a script problem from an environment problem, and doing it again the next morning.

Nice to haves

• You have contributed to Plane, run it self-hosted, or maintained another open project people rely on.
• You have tested real-time collaborative or offline-first applications, and you know why they break testing assumptions.
• You have tested systems where AI agents act on real data, and you have thought about asserting on non-deterministic behavior.
• You have worked with cross-browser, visual regression, or Electron desktop testing (BrowserStack, Applitools, or comparable).

Tech

• Testing: Playwright, TypeScript, GitHub Actions
• What you will be testing: React and TypeScript client, ProseMirror based collaborative editor, Electron desktop app, local-first sync over WebSockets
• Services behind it: Python/Django, Golang, Elixir, Node.js, Postgres, Redis, public REST and GraphQL APIs
• Infrastructure: AWS, Kubernetes, Rancher
• Observability: Datadog, Sentry
• Everyday tools: GitHub, Plane (yes, we run on it), Figma, Slack

Why Plane?

• The scope is real. We are a passion team serving companies of every size, including some of the largest in the world.
• The constraints make you better. Plane runs in our cloud, in customers' clouds, and on machines that will never touch the internet.
• The people-and-agents future is being built here, in production.
• Your name is on the work. The teams are deeply connected enough that credit and responsibility both find you fast.

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.