Most companies say they hire differently. Linear actually does. Founded in 2019 by Karri Saarinen (CEO) and Tuomas Artman (CTO) — both previously at Airbnb and Uber — Linear has built one of the most respected product development tools in the world with a team of roughly 80 people. The product is fast, opinionated, and exceptionally well-crafted. The team reflects those same qualities.
What separates Linear’s hiring process from almost every other company is the work trial. Before anyone receives an offer, they spend 2 to 5 paid days working alongside the actual team, using real internal tools, on real projects. It is not a simulation. It is not a take-home. It is as close as you can get to the first week of a job without signing an offer letter. That approach has produced a 96% retention rate over four years — a number almost no company of any size can match.
If you have been invited to interview at Linear, or you are preparing to apply, this guide covers the full process: every stage, what the team evaluates, how to prepare for the work trial specifically, and what it actually feels like to work at one of the most intentional companies in the developer tools space.
Linear at a Glance
| Company Size | ~80 employees |
| Founded | 2019 |
| Founders | Karri Saarinen (CEO) & Tuomas Artman (CTO) |
| Work Model | Fully Remote |
| Glassdoor Rating | 4.6 / 5.0 |
| Recommend to a Friend | 95% |
| Retention Rate | 96% (4 years) |
| Salary Range (Eng) | $160k – $280k TC |
| Open Roles on JBC | 23 positions |
| Culture Values | Deep Work, Remote, Async, Eng-Driven, Product Impact, Work-Life Balance |
Linear’s 4.6 rating is exceptional for a company that ships at this pace. The 95% recommendation rate is even more telling. These are not the numbers of a company that uses culture as marketing — they are the numbers of a team that has actually figured out how to hire people who belong there. The work trial is a large part of why.
Why Linear’s Hiring Process Is Different
Most hiring processes are built around inference: can this person solve a contrived algorithm problem, answer behavioral prompts with polished STAR stories, and appear confident enough in a video call to pass a gut-check? Linear’s process is built around evidence. The work trial removes nearly all inference from the equation.
When you do a work trial at Linear, you get access to their actual internal tools — the same Slack channels, GitHub repos, Notion docs, and Linear boards the team uses every day. You are assigned to work with specific people on specific problems. You see how decisions get made. You experience the communication style, the async rhythm, and the product philosophy firsthand. And the team sees exactly the same things about you.
This is not a coincidence. It is a deliberate investment in quality of signal. The team knows that four conversational interviews cannot tell them nearly as much as watching someone actually work for two days. And candidates get the same benefit: you are not evaluating a company based on a sales pitch during a series of interviews — you are experiencing it.
The Full Interview Timeline: Steps 1 Through 5
Linear’s process is deliberately slow relative to most startups. With a team of 80 people, adding even one wrong hire has an outsized impact on the culture. Expect the full process to take 4 to 6 weeks from first contact to offer.
Application Review
Linear reviews every application carefully, but the bar for advancing is high. They are not hiring at scale — they add a small number of people per year to a team of 80. A strong application includes a specific explanation of why you want to work at Linear (not just “I love the product” — what specific problems do you want to work on?), links to work you have shipped independently, and evidence of the craft quality Linear values. Generic applications do not advance. Applications that demonstrate you have thought deeply about what Linear is building do.
Initial Conversation
A 45–60 minute video call with a hiring manager or team lead. This is genuinely conversational — not a structured competency assessment. They want to understand your background, what you have built, what problems you care about, and why Linear specifically. Be prepared to go deep on one or two projects you are proud of. Linear values engineers who have strong opinions grounded in real experience, so bring perspective, not just a narrative.
Technical and Culture Conversations (2–3 more interviews)
Over the next 1–2 weeks, you will have 2 to 3 additional conversations with different team members. These cover technical depth (system design thinking, past architectural decisions, debugging instincts), product intuition (how do you think about trade-offs between features and simplicity?), and culture alignment (async communication, deep work habits, how you handle ambiguity). Unlike many companies, Linear’s conversations feel like genuine exchanges rather than interrogations. Expect them to share as much as they ask. The goal is mutual evaluation, not one-directional screening.
Paid Work Trial
The centerpiece of Linear’s process. For senior roles, this is a full 5 days; for other roles, 2 to 3 days. You are given access to Linear’s internal tools — including the codebase, design files, communication channels, and the Linear app itself — and you work on real projects alongside real team members. You will be paid for your time. You attend real meetings (or async updates), submit real work, and operate the way an employee would on day one. The trial is designed to be genuinely representative of the job, not an artificial test environment.
Blind Vote & Offer Decision
After the trial, each team member who worked with you submits independent written feedback — before seeing anyone else’s assessment. Then a blind vote is conducted. Only after both steps are complete does the team discuss the candidate collectively. This process prevents the most common failure modes in hiring: anchoring to the loudest voice, social pressure to match the hiring manager’s view, and recency bias toward whoever interacted last. The decision is collective and evidence-based. Offers typically arrive within a week of the trial conclusion.
What Linear Looks For: Slope, Taste, Ownership, Communication
Linear does not publish a formal competency framework, but based on the culture profile, employee accounts, and the structure of their process, four dimensions come up consistently in how they evaluate candidates.
Slope over credentials
Like Ramp, Linear cares more about your learning trajectory than your resume pedigree. They are a small team building a product that will be used for years. They need people who will grow with the product, not people who peaked at their most recent company. This shows up in how they conduct interviews: they are not looking for perfect answers, they are looking for how you reason when you encounter something unfamiliar. Demonstrating intellectual curiosity, being honest about the limits of your knowledge, and showing genuine enthusiasm for getting better all carry weight.
Taste
Linear’s product is known for its exceptional craft quality. The app is fast, precise, and opinionated in ways that reflect a deep understanding of how engineering teams actually work. The people who build it must care about craft at a level that most engineers do not. Taste, at Linear, means the ability to notice what is bad, articulate why it is bad, and have a point of view on what good looks like. This applies to code (is this API clean? is this abstraction right?), to product (does this interaction feel correct?), and to writing (is this message clear?). If you have shipped things you are genuinely proud of — things where you sweated the details — that is the evidence Linear wants to see.
Ownership
At a team of 80, there is no room for people who wait to be told what to do. Linear operates with a high degree of autonomy and expects engineers to take real ownership of problems end to end — not just coding tasks, but the shape of the solution, the communication with stakeholders, the quality of the documentation, and the long-term maintainability of what gets shipped. The work trial specifically tests this: are you the kind of person who identifies what needs to be done and does it, or do you wait for instructions?
Communication
Linear is fully remote and operates with a strong async culture. This means written communication is not a nice-to-have — it is the primary medium through which work happens. Your ability to write clearly, precisely, and with appropriate context matters enormously. During the conversations before the trial, pay attention to how you express yourself in writing (email, Slack, notes). During the trial itself, how you document your work, ask questions, and share progress will be as visible as what you ship.
Full-Stack Thinking: What Linear Means by It
Linear describes their engineering philosophy as “full-stack thinking.” This goes beyond technical generalism. It means engineers at Linear are expected to shape product direction, talk to users, make design decisions, and care about the outcome — not just the implementation. In practice, this looks like:
- Engineers participate in product discussions. At Linear, the line between product and engineering is intentionally thin. Engineers are not handed a spec and told to build it. They contribute to what gets built, why, and when.
- Frontend craft matters as much as backend performance. Linear’s product has extremely high standards for interaction quality. Engineers who dismiss frontend work as someone else’s problem will not fit. Everyone on the team cares about how the product feels.
- Shipping means owning the whole thing. A feature is not done when the code is merged. It is done when it works correctly, is well-documented, does not create regressions, and the team understands it. Linear engineers own that entire scope.
How to Prepare for the Work Trial
Most interview prep advice focuses on abstract preparation — practice algorithms, rehearse behavioral answers, research the company. Linear’s work trial makes most of that irrelevant. You cannot rehearse being yourself for two days on real projects. What you can do is reduce the friction so you can operate at your actual best level.
Use Linear obsessively before the trial
Not as a user — as a student of the product. Notice every interaction pattern. Understand the shortcut system. Read their product changelog carefully: what decisions did they make, and what tradeoffs do those reflect? By the time the trial starts, you should have strong opinions about what the product does well and where it could go next. This context makes you dramatically more useful on day one.
Set up your development environment in advance
Linear will give you access to their tooling, but your own environment — editor config, linting setup, keyboard shortcuts, debugging workflow — should be second nature before day one. You do not want to spend the first morning of a five-day trial figuring out how your tools work. Prepare to be productive from the first hour.
Practice async communication before the trial
If you are used to working in an office where you can ask a quick question verbally, the async-first environment of a Linear work trial may feel different. Practice writing precise, self-contained messages that give context, state your question clearly, and include what you have already tried. The goal is for your writing to minimize back-and-forth, not generate it.
Default to doing, not asking
In an async remote environment, waiting for permission is expensive. During the trial, when you encounter ambiguity, make a reasonable decision, document your reasoning, and keep moving. Share your progress proactively rather than waiting to be checked on. Ownership shows up in small behaviors, and the trial is where those behaviors are visible at full resolution.
Bring your actual taste, not what you think they want
Linear hires for genuine perspective, not people-pleasing. If you think a current design decision is wrong, or if you notice something in the codebase that could be cleaner, say so — constructively, with specific reasoning. They are not looking for someone who nods along. They are looking for someone who cares enough to have opinions. That said, the trial is not the time for sweeping architectural critiques. Earn context before you earn credibility.
Treat the trial as a mutual evaluation
The blind vote feedback system means the team is genuinely assessing you. But you are also assessing them. Pay attention to how decisions get made, whether the communication style matches how you work, whether the problems you are working on excite you. The trial gives you more real information about the job than a hundred interviews would. Use it to make a real decision, not just to perform for the camera.
Technical Expectations: Craft at Every Layer
Linear does not run traditional technical interviews, but the work trial makes technical expectations extremely clear. Here is what “good” looks like from Linear’s perspective:
Frontend: speed, precision, and interaction quality
Linear’s product is one of the fastest-feeling web applications in existence. Achieving that requires deep attention to rendering performance, animation quality, and interaction design. Engineers working on the frontend need to understand how browsers render, where performance budgets come from, and how to build interactions that feel native rather than web-ish. Strong TypeScript and React skills are table stakes. What distinguishes candidates is whether they care about the last 10% — the transition timing, the keyboard behavior, the scroll physics — with the same intensity they bring to the first 90%.
Backend: correctness and clean architecture
Linear’s backend powers a product that engineering teams depend on for their daily work. Correctness is not optional. They value clean architecture, well-considered APIs, and data models that are designed to evolve. Backend engineers should be comfortable with PostgreSQL at a level beyond basic CRUD: schema design, indexing strategy, query optimization, and understanding the trade-offs of different data modeling approaches. GraphQL fluency is a meaningful advantage given Linear’s API design.
The standard that applies everywhere
Across the stack, the consistent standard at Linear is: would you be proud to have your name on this? Code that works but is needlessly hard to understand, APIs that technically function but are unpleasant to use, features that ship but do not feel complete — these do not meet the bar. The team cares about craft as an end in itself, not just as a means to shipping faster.
Questions to Ask Your Linear Interviewer
The conversations before the work trial are genuinely two-directional at Linear. They expect candidates to have real questions — not questions designed to signal enthusiasm, but questions that reflect genuine curiosity about the work and the culture.
Questions Worth Asking
- How does the team decide what to build next? Who has the most influence on the roadmap, and how does that interact with user feedback?
- What does async collaboration look like in practice on your team? How do you handle disagreements or decisions that need fast resolution?
- Can you describe a decision you made in the last six months that you are genuinely proud of — not just the outcome, but how the process worked?
- How do engineers grow at Linear? Is there a defined path, or does it emerge from the work itself?
- What is the hardest technical problem you are currently working on, and why is it hard?
- How does Linear decide when something is “good enough” to ship versus when it needs more iteration?
- What kinds of engineers have thrived here long-term? Are there traits that predict who fits and who does not?
These questions give you real signal on whether Linear’s culture matches your working style, and they demonstrate the kind of genuine intellectual curiosity the team values. Avoid questions that could be answered by reading the careers page. The interviewers will notice.
Culture Fit Signals: Async, Deep Work, and Craft Obsession
Linear’s culture values — deep work, remote-first, async-first, engineering-driven, product impact, and a genuine commitment to work-life balance — are not aspirational. They are structural. The team of 80 people has maintained these values because they hire selectively for them and because the work trial makes mismatches visible before anyone signs anything.
Signals that you are a fit
- You do your best work in uninterrupted blocks, not in an environment of constant Slack pings and back-to-back meetings. You have actively sought out or created those conditions at previous jobs.
- You have strong opinions about what makes software good, and you can articulate them clearly with specific examples. “I think Linear’s offline-first approach is the right call because...” is the kind of thing Linear engineers say.
- You write well. Not just grammatically correctly, but precisely and with appropriate context. Your Slack messages, code comments, and documentation are clear enough that you are not generating follow-up questions all day.
- You have shipped things you are proud of at a level of quality that reflects care. Not just “it works,” but “it feels right.”
- You find it energizing to work independently and connect meaningfully with a small team, rather than needing constant interaction and visibility to feel engaged.
Signals that you might not be a fit
- You prefer frequent real-time collaboration and feel less effective working asynchronously or solo for extended periods.
- You are most comfortable in a structured environment with clear sprint cycles, standups, and explicit assignments — Linear’s high-autonomy environment may feel unmoored.
- You view the frontend as a lower-priority concern relative to the backend, or vice versa. Linear engineers care about the whole product.
- You are optimizing for compensation above all else. Linear’s pay is competitive for the developer tools space, but if you are maximizing total comp, FAANG or late-stage growth-stage companies will likely offer higher ceilings.
For a deeper look at what day-to-day life actually looks like at Linear, see the Working at Linear 2026 deep-dive.
See all open roles at Linear
23 positions currently listed — engineering, design, and more. Filter by culture values and location.
Browse Linear Jobs → See Linear Culture Profile →