My Interview Experience: Litmus (YC ‘26)
This was my first-ever interview with a YC-backed company, and honestly one of the more memorable processes I’ve been through. Most interview stories I share follow a fairly predictable shape — resume, DSA, system design, feedback. This one didn’t, and that’s exactly what made it worth writing about.
How it started
I sent a LinkedIn message to the founder, requesting an internship — nothing fancy, just a cold, direct ask. Then… nothing, for a while.
2–3 months later, out of nowhere, I got a reply. They weren’t hiring interns at that point, but they did have an opening for a contract role. If I was interested, the next step was simple: send my portfolio and projects to the email they shared. No formal application portal, no multi-page form — just an email.
I sent it over, and 2–3 days later got word that I’d been shortlisted for the next round. Fast turnaround, which I’d later realize was very on-brand for how this whole team operates.
The OA — where things got genuinely interesting
This is the part of the process I keep coming back to when I tell people about it. Litmus is an AI-native technical hiring platform — which means the way they evaluate candidates is itself a reflection of the product philosophy they’re building. It’s not a company bolting AI onto a traditional hiring flow; the assessment format itself was clearly designed around the assumption that working with AI tools is now a core engineering skill, not an accessory to it.
Instead of a typical coding test with a problem statement and a submit button, I was given a command to fork a repo directly and had to commit changes into it. Before I could even start, I had to give Litmus’s tooling access to my own system so it could install whatever it needed to run and track the assessment locally.
And then everything was tracked. Not just my final code — every command I ran, every prompt I sent to an AI model, and which model I chose to use, all of it fed into their evaluation pipeline. Every commit message, every prompt, every small decision along the way mattered, because none of it was invisible to them.
That reframed the whole exercise for me. In a traditional OA, the only thing that matters is whether your final solution passes the test cases. Here, the process was the signal. The underlying question wasn’t “can you solve this problem” — it was “can you actually work effectively with AI as a collaborator,” which, if you think about where software engineering is heading, is probably a more honest question to be asking candidates in the first place.
Get Divyanshu Rajput’s stories in your inbox
Join Medium for free to get updates from this writer.
Once I was done, I submitted the whole thing directly from my terminal — no separate submission form, no upload step. It closed the loop on how self-contained and tool-native the entire experience was.
The interview — with Litmus’s CTO
After the OA, I got an invite to interview with Litmus’s CTO.
She opened the conversation by introducing herself properly — what they’re building, when they started, and the story behind it — rather than jumping straight into grilling me. It set a tone early on that this wasn’t going to be a rapid-fire technical interrogation.
Then I introduced myself, and we got into my background and open-source journey — the kind of context that usually only comes up if an interviewer is genuinely curious rather than just checking a box.
From there, the conversation moved into the OA itself: what I’d actually built, how I’d approached the problem, what was going through my head at each step, and — this part I found particularly useful — what other approaches might have worked better. It wasn’t just “did you get it right,” it was a genuine back-and-forth about tradeoffs and alternate paths I hadn’t considered.
Beyond the formal interview
Once the structured part wrapped up, the conversation didn’t just end — it opened up. A good chunk of it was around YC itself: what the experience has actually been like for them, what changes internally once you’re admitted into the program, and how fast-paced building at a YC-backed startup really is day to day. Not the polished, PR version of “startup life” — an honest one.
We also ended up talking about AI more broadly. This happened to be right around the time Claude Code’s source code leaked online, so naturally that came up too, and we spent some time just discussing what it meant and how it was being talked about.
What stood out most to me, more than any single topic, was how the conversation felt. She made me genuinely comfortable — comfortable enough that I was sharing my actual thinking rather than reciting something I’d memorized from a textbook or read somewhere online the night before. That’s a surprisingly rare quality in an interviewer, and it changes the entire texture of the conversation. It stopped feeling like an evaluation and started feeling like two people talking about problems they both found interesting.
The outcome
As of about 8 months after this interview, Litmus still hasn’t hired anyone for the role. My best guess — and it is just a guess — is that they’re deliberately moving fast with a small, tight team, heads-down and focused on getting to Demo Day rather than expanding headcount right now. That’s a fairly normal rhythm for an early-stage YC company, even if it means the hiring loop itself stays open longer than usual.
Verdict: Don’t Know
LinkedIn: https://linkedin.com/in/divyanshu-rajput8171
Portfolio: https://divyanshu-rajput.vercel.app
What I took away
I’m genuinely grateful for the opportunity and for how the Litmus team handled the whole process, end to end. No offer came out of it, but that’s honestly not the part I remember most. What I remember is an OA that actually tested something real, and a conversation with a CTO who made space for honest thinking instead of rehearsed answers. As a first look at what interviewing with a YC company actually feels like, I couldn’t have asked for a better one.
