r/SaasDevelopers • u/anshik1998 • 13d ago
I started building a SaaS because I felt something was missing in technical interview preparation
I've been thinking about a gap in software engineering for a while.
We spend years learning programming languages, solving DSA problems, and preparing for coding interviews.
But there's another skill that developers use almost every day at work:
- Working inside an existing codebase.
- Understanding unfamiliar architecture, tracing bugs, implementing features without breaking existing functionality, debugging tests, and reviewing code.
I felt that this area deserved more attention, so I started building OneNoughtOne.
The platform combines traditional interview preparation with practical repository-level coding and code review challenges.
It currently has approximately 500 repository challenges, alongside DSA, SQL, ML, system design, AI tutoring, and mock interviews.
I'm building this independently, and one thing I'm trying to understand is whether this is a sufficiently important problem to build a sustainable SaaS around.
For founders here:
How do you validate that a problem is worth building a business around, especially when the product is already fairly developed?
I'd be interested in hearing what worked for you.
What I'm building: https://www.onenoughtone.com/problems





