About
Built because spreadsheets aren't enough.
Lytmus started as a personal tool. I was three months into a job search, had a dozen applications in flight, and couldn't answer a simple question: where am I actually losing?
The kanban trackers showed me which stage each application was in. The notes apps held my prep notes. But nothing connected them. I couldn't see that I was consistently losing system design rounds, or that my confidence scores on graph problems were 1–2 points lower than anything else. That pattern was in the data — I just had no way to surface it.
So I built Lytmus. The idea is simple: treat the interview loop as structured data. Every round, every question, every confidence score. Once you have that, the patterns become obvious — and so does what to work on next.
What it does
Lytmus is an interview tracker focused on the post-apply phase. You log each round after it happens — what kind it was, what questions came up, how confident you felt. Over time, the metrics page shows you your real failure points: the round types you lose, the question topics where your confidence is lowest, the companies where things go sideways.
The AI coach (Pro) reads all of that and runs mock sessions that target exactly your weak spots — not generic LeetCode grind, but the specific areas your own data says you need.
Who built it
I'm Anuj Menta, a software engineer. I built Lytmus during my own job search because I needed it, and kept building it because other engineers did too. It's a small, focused product — one person, real users, no VC pressure to grow into something it isn't.
Get in touch
Questions, feedback, or just want to talk shop about interview prep — reach out anytime.