Candidates report an initial recruiter call that checks for B2B SaaS growth experience, comfort with product-led funnels, and examples of experiments that moved activation or retention. A hiring manager interview typically follows, focusing on how the candidate would position Linear against incumbents in issue tracking and how they would prioritize channels given a developer-led buying journey. The process often includes a take-home style case or live working session where candidates propose a growth plan, for example improving sign-up to first-value, driving workspace adoption, or scaling SEO and lifecycle messaging around topics like triage and planning. Panel interviews commonly include product, engineering, and design partners to test how the candidate collaborates on in-product prompts, onboarding, and measurement instrumentation. A final conversation with leadership often centers on judgment, craft bar, and how the candidate balances experimentation speed with brand voice, with end-to-end timelines frequently landing around 3 to 6 weeks.
How would candidates position Linear to a team currently using Jira, and what messages would they avoid because they could backfire with technical buyers?
Given a drop-off between workspace creation and regular issue usage, what diagnostics would candidates run and what experiments would they queue first?
Describe a growth experiment candidates ran that failed, what they learned, and how they updated their operating cadence afterward.
What metrics would candidates treat as Linear’s activation moment, and how would they validate that the metric predicts retention?
How should a growth team preserve Linear’s product and brand craft while still iterating quickly on onboarding and lifecycle messaging?
Developer Advocate
virtual
· Difficulty 3/5
Candidates report starting with a recruiter screen that focuses on writing samples, community presence, and motivation for developer-facing work, often scheduled within a week of applying. The next stage is typically a hiring manager conversation centered on storytelling, technical credibility, and how the candidate would explain Linear’s workflow concepts like cycles, triage, and initiatives to different audiences. Many processes include a practical exercise, often framed as a short content or community task, such as drafting a blog outline, documentation improvement proposal, or a short demo plan using Linear’s API and integrations. A panel round commonly follows with cross-functional partners from engineering, product, and marketing to evaluate collaboration and how the candidate handles feedback and ambiguity. The final stage is usually a deeper conversation with leadership about voice, judgment, and how the candidate would represent the product publicly, with the overall loop frequently completing in roughly 3 to 5 weeks depending on scheduling.
How would candidates explain Linear’s approach to cycles and issue triage to a team migrating from Jira without sounding like a feature checklist?
What would candidates build or write in the first 30 days to help engineers adopt Linear, and how would they measure whether it worked?
Walk through a technical project candidates have shipped that required understanding an API or integration, and what they would do differently now.
Describe a time candidates received strong editorial or technical feedback on public content and how they incorporated it.
What does high craft in developer content mean to candidates, and how should it show up in docs, examples, and demos for Linear?
Customer Operations Manager
virtual
· Difficulty 3/5
Recruiter screen, hiring manager video, customer scenario, behavioral, and final with director. Customer Ops at Linear is a small but strategic team.
Walk me through driving customer onboarding at scale.
Tell me about handling a customer concerned about workflow change.
Describe partnering with engineering on a customer-driven bug fix.
How do you measure customer success in a PLG company?