Voke

Building Voke wasn't just about writing code; it was about solving a problem I lived through. I realized early on that the gap between being a 'good coder' and 'good at interviewing' was massive. I spent countless late nights building Voke to close that gap. The journey was full of tough product decisions. For instance, I debated whether to include a Resume Parser. It added complexity, but I realized that getting the interview is half the battle, so I built an AI agents tailored specifically to beat ATS filters. One of the hardest parts was getting the 'feel' right. I spent weeks tweaking the 'Road to Offer' dashboard. I didn't want it to feel like homework; I wanted it to feel like an RPG. Implementing the 'Level 5 Scholar' logic and the 'Dream Company' tracker was my way of gamifying the grind, making consistency feel rewarding rather than punishing. There were frustrating days—debugging race conditions in the voice simulations or realizing my database schema needed a complete overhaul to support robust account deletion. But every time I tested the Video Simulation and felt that nervousness of being 'watched' by the AI, I knew I was onto something real. Voke is the result of obsessing over every pixel of the candidate experience. It’s the platform I built to help you master the one skill that matters most: getting hired.