Linear

Linear is one of the most selective employers in tech. Not selective in the "we reject 99% of applicants because of volume" sense — selective in the "we hire very few people, every hire changes the company, and we know it" sense.

The team is small by design. When Linear posts a role, it's a real need, not exploratory hiring. And when they hire someone, that person's work is visible. There's nowhere to hide and no reason to — the people who join want the responsibility.

The reality of getting in

Linear rarely posts open roles. When they do, the volume of interest is high and the team reviewing applications is small. Most hires at companies like Linear happen through networks and direct outreach before a role is ever posted — someone knows someone, or a founder noticed your work, or you wrote something that circulated in the right circles.

This doesn't mean cold applications don't work. It means the bar for a cold application is higher than usual: you need to make it obvious, quickly, why you specifically belong at this specific company.

What Linear actually cares about

Product taste. This is the real filter. Linear is a company built on the conviction that software can be fast, beautiful, and well-considered — and that most software isn't. If you use Linear and feel ambivalent about the difference between it and Jira, that's a signal. If you notice the details — the keyboard shortcuts, the performance, the care in every interaction — and you think about why those choices were made, that's more relevant than most of your resume.

Craft over credentials. Linear has hired people from non-traditional backgrounds because their work was exceptional. They've also not hired people from elite companies because the work wasn't. Show what you've built, written, designed, or shipped. Not as a portfolio exercise — as evidence of how you think.

Genuine opinions about product. Karri Saarinen (CEO) is opinionated. The team is opinionated. They're not looking for people who will execute on a spec — they're looking for people who will push back on the spec when it's wrong, and who have the judgment to know when it is. In interviews, being vague or deferential about product questions is a weak signal. Having a clear point of view, even one that differs from theirs, is a stronger one.

Speed. Linear's engineering culture ships fast and cares about it. People who are comfortable with ambiguity, who can make a call and move, who don't need extensive process to get things done — that's the profile. If you work best in an environment with a lot of structure and defined process, this is probably not the right fit.

The process

Because the team is small, the process tends to involve real people quickly. There's no large recruiting apparatus. Expect:

1. Initial conversation — often with someone doing the actual job, not just a recruiter
2. A work exercise or portfolio review — they want to see how you actually work
3. Conversations with multiple team members — because at a small company, cultural fit with the immediate team matters a lot
4. Founder involvement for senior roles

The process is collaborative rather than evaluative in the traditional sense. They're trying to figure out if working with you would be excellent, not just whether you can clear a bar.

How to get their attention

Do work that's publicly visible. The people who get hired at companies like Linear often have something people can point to: open source projects, writing about product or engineering, design work that's been noticed, something you shipped that other people use. This isn't required, but it's the most common path for people who didn't come through a direct referral.

Write a real application. Not a cover letter in the traditional sense — a direct, honest explanation of why you want to work at Linear specifically and what you'd bring. Not "I've always admired Linear's focus on craft." Something concrete: a specific thing you'd want to work on, a specific gap you think you could fill, a specific thing you think they could do better. Show that you've actually thought about the company.

Use the product deeply. Before any conversation with Linear, you should be able to talk about their product in detail — what's excellent, what's missing, what you'd change and why. If you're not a regular Linear user, start. You'll have a hard time being compelling about working there if you're not genuinely invested in what they're building.

The role scope

At a company this size, roles are broad and the work is direct. An engineer at Linear isn't working on a small slice of a large system with many layers of abstraction — they're shipping things that go directly to users. A designer isn't working within a design system built by a larger team — they're shaping the product directly.

That scope is what makes it attractive and also what makes the bar high. They can't afford someone who needs a lot of ramp time, who isn't self-directed, or whose judgment isn't trusted quickly.

Things worth knowing

They move slowly to move fast. Hiring decisions at a small company take longer than at large ones because each hire matters more. Don't expect a two-week process. Do expect the conversations to be substantive.

Remote-first. Linear is distributed. The team is spread across timezones. Strong async communication — writing, docs, clear thinking on paper — matters as much as synchronous collaboration ability.

Compensation is competitive given the stage and quality of the team. Equity at a company this tight-knit and well-regarded is meaningful.

Should you apply?

If you care deeply about product quality, want your work to have direct impact, and want to be at a company where the craft of building software is taken seriously — Linear is worth pursuing. The path in is harder than at larger companies, but the job itself is different: more ownership, more direct impact, more visible work. For the right person, there isn't a better place to be.