Unofficial. A job application for Linear’s Product Manager role, built from public pages. Not affiliated with Linear.

The evidence.

Everything on this site comes from pages any visitor can open, read on November 22, 2026. I created no account, submitted no form and did not open the Linear app.

Where Linear already leads

Linear beside six rivals

What each vendor’s own pages say about planning above one team. Each name links to one of that vendor’s pages.

VendorOne date shared across projects or teamsUnfinished work at the boundaryA record of what moved onWhere it sits
LinearNot possible. A milestone is recreated in each project.Cycles and scheduled releases move it on automatically. Milestones do not move.Kept in issue history and the API. No summed view found in the docs.Milestones and initiatives on every plan
Jira with PlansA cross-space release lines up several releases on one date.At the end of a sprint the user chooses: backlog, a future sprint or a new one.Sprint and burndown reports list incomplete and removed items, per board.Plans need Premium or Enterprise
Jira AlignA program increment holds every team’s sprints.Not found for sprints. A feature belongs to one increment.Points planned against points accepted, by program and increment.A separate product that needs Jira Premium
AsanaHelp centre could not be readNot foundA baseline in Gantt view, per project. Source is a 2023 staff post.Portfolios on Advanced and up
ShortcutObjectives roll up work across teams. Iterations can belong to one team.An optional automation moves stories to the next iteration, per team.The burndown chart freezes at the end. No list of carried stories found.Iterations on every plan, the automation on paid plans
GitHubA milestone belongs to one repository. An iteration field belongs to one project.Moved by hand, in bulk.Not foundNot stated on the pages read
Azure DevOpsTeams share iteration paths. A delivery plan takes milestone markers.Moved by hand.Velocity keeps the original planned snapshot, per team.Not stated on the pages read

“Not found” means not found on the pages read, not that the vendor lacks it. An AI research agent gathered the rival rows from each vendor’s own pages and re-checked its wording against saved text. I checked the Linear row against saved page text, and I have not checked the rival rows line by line. The help centres of Jira Align and Asana could not be read, so those two rows are thinner.

What the table says: the rivals that share a date across teams do it with a heavier object, a release plan or a program increment. Linear can do it with the milestone it already has.

What a proposal to Linear has to respect

Linear publishes how it builds. A proposal that ignores it is not a proposal for Linear.

  • Do not invent terms.The Method says projects should be called projects. So this is a milestone, not a program increment. Linear Method
  • Say no to busy work.Nothing new to fill in. The carried-over record comes from moves Linear already keeps.
  • Build for the creators, not for perfect reports.The page is for the lead who has to decide. It costs the people doing the work nothing.
  • No OKRs and no A/B tests.So the test is customers and judgment. How we hire at Linear
  • Small projects.One to three people, one to three weeks. The first version is cut to be small. Scope projects down

What is not on this page

While reading, I found a handful of places where Linear’s public pages disagree with each other, two links that no longer resolve, and some small slips. None is serious.

Those are in a short findings report I will send to Linear directly. A public page is the wrong place for them.