1. LandOffer
  2. Blog
  3. All articles
  4. Linear Paid Work Trial: Confirm the Project, Daily Rate, Access, and Schedule Before Starting

Job search

Linear Paid Work Trial: Confirm the Project, Daily Rate, Access, and Schedule Before Starting

Current official hiring guidance and two original completed planning cases separate trial scope, paid-day agreement, access and delivery from a hiring offer.

9 min readLandOffer team

Linear describes its final hiring stage as a paid, two-to-five-day work trial. Before setting aside that time, confirm the actual project, daily rate, working dates, required access and delivery expectations in writing. Use the public process as context, then confirm the terms of your own project.

Agree on a bounded collaboration with clear expectations on both sides. You should know what you are delivering, who can resolve a blocker and which hours you can realistically commit. You can browse recent roles on LandOffer.ai while keeping a trial decision separate from an application, an accepted project or an employment offer.

A project brief, calendar and access-key tray prepare a bounded work trial.

What Linear currently documents

Linear's April 28, 2026 hiring article describes the final stage for all roles as a paid two-to-five-day project approximating the work. It says candidates work with a small team, receive internal-tool access and get a detailed guide at that stage. Daily rates are communicated in advance, and scheduling is flexible; no universal dollar amount is published there.

The same article places a decision after the trial. Team members submit feedback independently before a debrief, with the hiring manager making the final call. Reaching or completing the project is therefore not an offer guarantee.

A December 13, 2023 article provides older operational detail: a project team, temporary tools, preparatory paperwork, kickoff, candidate-led check-ins and a final presentation. It mentions scheduling around commitments, including some weekend arrangements. Treat those as dated examples, not permission to assume your trial uses weekends or the same tools.

We read these official pages on October 21, 2026, along with current careers information. No candidate invitation, private guide, contract, tool account or actual work trial was accessed. LandOffer.ai publishes this guide; all completed examples below are original fictional planning exercises.

Convert the invitation into a specific project brief

The first useful document states the problem and the expected output. “Work with the team for three days” leaves too much unresolved: a prototype, a design proposal and a production-ready change require different preparation and acceptance criteria.

Record what is in scope and what is deliberately excluded. Ask which source of requirements governs if a kickoff conversation differs from an earlier message. A written clarification lets both sides resolve a scope difference before work expands.

For compensation, ask for the rate, currency, agreed compensated days, payment timing and administrative process. Do not substitute an online anecdote or the example below for the actual written terms. Clarify how an approved schedule change affects those terms rather than assuming every partial day or added day is treated identically.

Separate availability from calendar dates. State your time zone, actual working blocks and existing commitments. Flexibility is something to agree on; it is not an obligation to work continuous evenings or to move the trial into a weekend without discussion.

Worked preflight: a three-day proposal remains unconfirmed

Entirely fictional example: Lena is considering a three-day engineering trial. Her invented project brief concerns a read-only notification-preference summary using supplied sample records. This is not a Linear prompt, a real candidate invitation or work requested by the company.

She completes the following record before starting:

Field Lena's recorded position
Objective Explain how a user would understand current notification preferences and identify a missing or conflicting record.
Proposed deliverable A small reviewable concept, a behavior note and a handoff listing limitations; exact implementation depth needs agreement.
Out of scope Production deployment, real customer data, account-setting changes and a general notification-system redesign.
Proposed working dates November 2–4, 2026; not accepted dates or calendar bookings.
Availability America/Los_Angeles, generally 09:00–16:00; unavailable Tuesday 13:00–15:00. Team overlap and expectations remain to be confirmed.
Daily rate Illustrative $600 USD only—not Linear's rate or an actual quote. Ask the real parties to confirm rate and compensated days.
Conditional arithmetic Three agreed days at that invented rate would total $1,800 before any unconfirmed adjustments. No payment is due or recorded here.
Access Only the project resources required; no production or organization-admin access requested. Exact invitations and permitted actions remain pending.
Feedback owner A named project lead and a backup are required in the real brief; neither has been identified in this fictional proposal.
Finish condition Agreed artifact and final discussion, followed by access closeout instructions; no assumption of an offer.

She also proposes meeting times for a reviewer in New York. A local time-zone calculation produced:

Proposed meeting America/Los_Angeles America/New_York
Kickoff November 2, 10:00 November 2, 13:00
Check-in November 3, 10:00 November 3, 13:00
Final discussion November 4, 13:00 November 4, 16:00

These are invented proposals, not scheduled meetings. The local calculation used America/Los_Angeles and America/New_York for those dates: UTC−8 and UTC−5 respectively. It does not establish another person's availability or a required Linear working pattern.

Lena's full clarification draft, deliberately unsent, reads:

Before I commit to November 2–4, please confirm the project outcome, implementation depth, daily rate, currency, compensated days and payment process. My availability is 09:00–16:00 America/Los_Angeles, except Tuesday 13:00–15:00. The proposed meetings are listed in both time zones. Please identify the project lead, backup contact and resources I may use, including whether external tools are permitted. I will not start on a production system or supply existing-employer material. Please send the written guide and confirm the handoff and access-closeout expectations so we can agree on a workable scope.

Her completed decision is hold the start commitment. The schedule arithmetic fits her stated blocks, but payment, scope and the responsible contact are still unresolved. A complete preflight can legitimately end with “not ready to start.”

Confirm access and working methods before using them

The older detailed article names tools such as Slack, Notion, Linear, GitHub and Figma as examples of trial resources. It also describes preparatory confidentiality paperwork. Do not create accounts or request broad privileges simply because those names appear in a public post; follow the actual project team's approved setup.

Ask which repository, workspace, sample data and communication channel belong to the assignment. Confirm who can authorize a missing permission or clarify whether a resource is intentionally unavailable. If access is blocked, report the effect on the agreed deliverable rather than using a personal credential or unrelated account as a workaround.

Likewise, clarify the rules for AI tools, outside services and code reuse. A company's general product messaging does not authorize sending its private trial material to another service. Keep your current or former employer's code, customer information and confidential documents out of the project.

For identity checks, use the official careers route. The inspected Product Engineer posting states that official hiring communication comes from @linear.app and warns against candidate payment requests. A displayed sender address alone is not a complete authenticity check; reconcile the conversation with the official hiring process before taking action.

Worked scope decision: preserve a useful handoff

Separate fictional example: Sami has four hours left in an invented design-oriented trial. The agreed remaining output is a behavior note for the notification summary, evidence cases and a final discussion. A request arrives to add a polished export workflow. This is an original teaching scenario, not an account of a Linear trial or its private evaluation criteria.

His completed time record is:

Remaining work Estimated hours Decision
Complete the agreed behavior note 2 Retain.
Review the four sample-state cases 1 Retain.
Prepare and conduct the handoff 1 Retain.
Add the new export workflow 3 Defer unless scope or schedule is explicitly changed.

The agreed work totals four hours; adding the request makes seven. The local check confirmed that 2 + 1 + 1 hours fits the four-hour budget, while adding three hours makes seven. These are fictional estimates, not measured engineering effort or a basis for automatically billing another day.

Sami finishes the following paper behavior artifact rather than claiming he built software:

Invented sample state Specified behavior Remaining implementation question
All preferences present Show a read-only summary with the source version. Confirm the source-of-truth field and refresh rules.
One field missing Identify the unknown field without inventing a default preference. Confirm how incomplete records should be repaired.
Conflicting records Surface the conflict for review; do not silently choose a value. Ask the data owner to define precedence.
Access unavailable Explain that the summary cannot be loaded; keep account settings unchanged. Confirm the approved recovery path and owner.

This is a complete concept note, not an executed interface test. It gives a reviewer a concrete proposal to discuss while preserving questions that require project-owner decisions.

A bounded task frame and separate extra pieces support a clear handoff without silent scope expansion.

His full, unsent status and handoff note reads:

The behavior note now covers complete, missing, conflicting and inaccessible sample records. It is a paper proposal; no software was deployed or tested. Four hours remain for completing the agreed note, reviewing these cases and holding the final discussion. Adding the export workflow would bring the remaining estimate to seven hours. I recommend deferring export and retaining the original handoff. If export is now essential, please confirm which existing work to remove or agree a revised schedule and compensation treatment before I proceed. Source precedence and access recovery still need the responsible owner's decision.

The completed choice is to retain the agreed scope and escalate the change. Sami has not silently refused a priority or promised unpaid extra work. He has made the tradeoff visible and given the team a specific decision to make.

Close the project without confusing delivery and hiring

At the end, state what was delivered, what was actually verified, what remains open and where the team can find the agreed artifact. A paper concept, locally run code and a production deployment are different outputs. Name the one you completed.

If the project uses temporary access, ask how it will be ended and what materials you may retain. Do not assume you can publish the work in a portfolio or preserve private source files for later interviews. Follow the agreed handling of company materials before considering any portfolio use.

Keep a short closeout record with the artifact version, unresolved questions, the person receiving the handoff and any agreed next step. Mark receipt as pending until it is actually acknowledged; sending a file and receiving confirmation are separate events. This avoids treating a planned presentation as evidence that every deliverable was accepted.

Confirm the payment-administration step separately from the evaluation outcome. Delivery does not itself establish that an invoice was received or a payment made. This guide does not classify the legal status of trial work or determine anyone's employment, tax or contract rights.

Linear's public description offers a useful starting point: a paid, bounded project with direct team collaboration and a later hiring decision. The practical preparation is to turn that starting point into your own clear written scope, schedule and access plan. Browse recent roles on LandOffer.ai, then evaluate each trial invitation against its written scope, compensation, schedule and access terms.

Sources and Further Reading