/careers

Largest Contentful Paint element

<video preload="metadata" crossorigin="anonymous" poster="https://linear.app/cdn-cgi/imagedelivery/fO02fVwohEs9s9UHFwon6A/860f87d1-2…" src="https://static.linear.app/assets/careers/linear-new-careers.mp4" width="2200" height="1160" class="_91f_Kq_video" style="aspect-ratio: 2200 / 1160; cursor: var(--cursor-pointer, var(--pointer, pointer…;" aria-busy="false">

• Improve image delivery

  Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

  Est savings of 2,872 KiB

  Covered by: Right-size and modernize images →
  −1.2 s
• LCP request discovery

  Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

  Covered by: Unblock the initial render →
• Forced reflow

  A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

  Covered by: Cut and defer JavaScript →
• Legacy JavaScript

  Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

  Est savings of 9 KiB

  Covered by: Cut and defer JavaScript →
  −150 ms
• Reduce unused JavaScript

  Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

  Est savings of 334 KiB

  Covered by: Cut and defer JavaScript →
  −1.2 s
• Network dependency tree

  Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

  Covered by: Unblock the initial render →

• Background and foreground colors do not have a sufficient contrast ratio.

  Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

  Covered by: Address accessibility gaps →
• Buttons do not have an accessible name

  When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

  Covered by: Address accessibility gaps →

• Browser errors were logged to the console

  Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
• Issues were logged in the `Issues` panel in Chrome Devtools

  Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

• ✓
  Canonical URL

  Page has a stable URL to cite
• ✕
  Author identity

  No author meta or schema — citation confidence drops without a named source
• ✕
  Publication date

  No publication or modification date in JSON-LD — answer engines deprioritize undated content
• !
  Article schema

  No Article / NewsArticle / BlogPosting schema — limits rich-snippet eligibility
• ✓
  Content depth

  1169 words — substantial for a citation source
• ✓
  Semantic structure

  Uses <main>, <article> or <header>