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

Shared milestones.

The proposal as a page you can use. Beta’s date has passed and four issues are still open. Decide what moves to Launch, then read what Beta carried over.

Start here

Why I did thisYour posting asks for discovery presented with conviction, and for product taste. Neither shows in a cover letter. So I did the discovery and built the proposal.

What I was thinkingI run a launch across many teams to a fixed date. I went looking for what Linear lacks for that, and my first guess was wrong: you already handle shared sprints. The real gap is smaller and sharper. A launch has one date, but each project keeps its own copy of the milestone.

What it showsOne milestone shared by every project in a launch. You can see what each project finished, what it carried over, and move unfinished work on with one key.

Try it in four steps

You lead a launch that spans six made-up projects. The Beta date has passed and four issues are still open.

  1. Read the grid. Projects run down the side and the shared milestones run across the top.
  2. Click the iOS app’s Beta cell, or use the arrow keys and Enter. The panel on the right lists what is still open.
  3. Press M to move the open work on to Launch. Press U to undo it.
  4. Press C to see only what was carried over, then read “What Beta carried over” under the grid.

Why I am the person for this job. I started as a front-end developer, and I still build: I made the planning board my ten-team program runs on because nothing we could buy showed what carried over. I have never held the title Product Manager. What I can show is the work itself: I found the problem, changed my mind when the evidence said to, and built the answer.

initiative · prototype Sample data. A made-up initiative. Not a Linear product.

Offline mode

Six projects, four shared milestones. The sample date is November 22, 2026.

What Beta carried over

Keys

  • ← → ↑ ↓Move between projects and milestones
  • EnterGo into the list of issues
  • J KNext and previous issue
  • MMove the issue to the next milestone
  • UUndo the last change
  • CShow carried-over work only
  • DChange the milestone’s date
  • EscBack to the grid

What this replaces

Today each project keeps its own copy of the milestone. Linear’s docs say a milestone cannot be shared and has to be recreated in each project.

When an issue moves to a later milestone, Linear records it in that issue’s history. I found no page that adds those moves up. I have no number for how many teams keep that sum in a spreadsheet. Finding out is the first step of the plan.

Choices I made in this page

  • A person moves the work. The page keeps the record.A cycle is a rhythm, so Linear rolls it over. A milestone is a promise, so someone decides.
  • No issues shows a dash, never 100%.An empty milestone has not been met.
  • One date, edited once.Change it in the column heading and every project follows.
  • Nothing new to fill in.Carried in and carried on come from moves that are already recorded.
  • Every action has a key and an undo.The page never asks you to confirm. It lets you take it back.