WillItSurvive
YC Summer 2026 · United States

Litmus

Litmus builds AI-resistant async work trials from a company's own code and tickets.

Losing its protection
Assessed 27 July 2026 · Evidence as of 27 July 2026
The structural protection is eroding.
On the recordSince 27 July 2026 · Checkable from Q1 2027 · Every call on the record Checkpoint: Deadline to publish predictive-validity data or claim a vertical wedge before Karat and CodeSignal close the gap
The call

Litmus has a real problem to solve and no customers yet, racing both incumbents and the AI models it screens for to prove its trials pick better engineers.

Litmus creates coding interview tests designed to work even when job applicants use AI tools, targeting a real problem for tech hiring. The challenge: Karat released a nearly identical product six months earlier and already has major customers, while bigger competitors like CodeSignal and HackerRank can easily add similar features to their existing products. The one thing that could save Litmus is proving that their tests actually predict who will be good employees better than rival tests do. If they can show that proof by early 2027 and lock in customers around it, they survive. If not, they become just another feature in a larger platform.

Why
01
AI pressure: Frontier AI models generating and grading coding tasks. The same models Litmus watches candidates use can generate and grade repo-based tasks, so its core tech is copyable by anyone with API access. Could AI do the core job? Yes, likely.
02
Bigger players: Karat (NextGen). Karat shipped NextGen in January 2026, six months before Litmus launched, pitching the same AI-detection idea to Roblox, Amex, Intuit, and Wayfair. Could a giant copy it? Yes, easily.
03
What protects it. Nothing proven yet. Only unbuilt ATS lock-in and未 unpublished hire-outcome data stand between Litmus and being copied as a feature.
What would change this call
Litmus publishes or secures design-partner hire-outcome data by Q1 2027. Would show predictive-validity moat beyond feature parity with Karat.
CodeSignal or HackerRank ship bespoke repo-based generation as a feature. Would confirm the core capability is easily copied, not a company.
Ashby, Greenhouse, or Lever add native repo-generated assessment features. Would show ATS platforms absorbing Litmus's function directly.
Key numbers
  • Litmus has 4 employees, based in NYC (2026-07-23)
  • Karat's NextGen shipped 6 months before Litmus, Jan 2026 (2026-01-14)
  • OpenAI runs its own internal async Work Trial for SWE hiring (2026-05-15)
Named risks
  • No shipped moat beyond unproven per-customer workflow lock-in at 4 employees. Severity: high
  • Karat NextGen already occupies identical positioning, launched 6 months earlier. Severity: high
  • Core repo-to-task generation and grading loop exposed to frontier-model commoditization. Severity: high
  • No public predictive-validity or hire-outcome data to prove the core claim of accuracy. Severity: medium
  • Name confusion with unrelated Litmus (Validity, email marketing) and Lytmus AI (NEET edtech). Severity: low
Rivals, as read in July 2026
RivalDirectionEvidence
Karatlosing toShipped NextGen with identical anti-AI-gaming positioning on 2026-01-14, ~6 months before Litmus launched
CodeSignalcontestingEstablished assessment platform with pre-built libraries; can add bespoke generation as a feature, no economic friction cited
HackerRankcontestingLarge pre-built question libraries as of 2025-12-18; positioned as broader/less bespoke than Litmus
ByteboardcontestingAlready emphasizes production-style, real-world evaluation over puzzles, per 2026-02-25 comparison
OpenAI (internal Work Trial)gaining onDocumented internal async work-trial format as of 2026-05-15, showing sophisticated buyers may build in-house
PerfectlycontestingYC W2026 peer building broader AI-native Recruiting OS covering sourcing through screening
Questions people ask
Is Litmus profitable in 2026?
No profitability or revenue figures have been disclosed. Litmus is a 4-person, YC S26 startup that publicly launched via Launch YC on 2026-07-09 and, as of 2026-07-23, shows no published customer count, revenue, or enterprise logos on its site or in YC's directory.
Could AI replace what Litmus does?
Possibly. Litmus's core loop, reading a repo, generating a task, grading the submission, sits squarely in frontier-model territory. OpenAI documented its own internal async 'Work Trial' format by 2026-05-15, showing large AI labs can build this in-house rather than buy it.
Who is Litmus's biggest competitor?
Karat, which shipped a competing product called NextGen on 2026-01-14, explicitly targeting the same problem (AI making old take-home tests unreliable) about six months before Litmus's own July 2026 public launch, with identical positioning language.
Who owns Litmus?
Litmus is privately held and YC-backed, part of Y Combinator's Summer 2026 batch. Co-founder and CEO Shaivi Rau previously worked at Morgan Stanley and in early-stage VC, and studied CS and Film at Columbia, per the company's YC profile dated 2026-07-09.
Does Litmus have any paying customers or case studies?
None are publicly listed. As of 2026-07-23 litmushiring.com solicits demo bookings rather than showing client logos or case studies, and no independent reporting on revenue, customer count, or churn has been found.
What makes Litmus different from HackerRank or CodeSignal?
Litmus generates async work trials from a specific employer's own repos, tickets, and job descriptions rather than using generic question libraries, and tracks AI-tool usage and commit history during the assessment, per its site as of 2026-07-09.
Timeline
  • 2026-07-23YC directory lists Litmus at 4 employees, based in New York City
  • 2026-07-09Litmus publicly launches via Y Combinator's Launch YC platform
  • 2026-05-15OpenAI's internal async 'Work Trial' SWE hiring format publicly documented
  • 2026-02-25Byteboard's production-style evaluation positioning noted in competitor roundup
  • 2026-01-14Karat ships 'NextGen' targeting AI-assisted test gaming, six months pre-Litmus
  • 2025-12-18CodeSignal, HackerRank, Codility and peers listed as assessment-library incumbents
Revision history
27 July 2026
First assessed. Losing its protection. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources