I Asked Job Seekers What They Hate About Resume Builders. The Results Changed My Roadmap.

A developer building the resume builder "Here Is My CV" discovered that user frustration centered on ATS compatibility, not customization or pricing as expected. After polling job seekers, the developer found that the core issue was a lack of trust in whether resumes would pass automated screening systems. This feedback led to the creation of a new template, "ATS Classic," designed to prioritize simplicity and confidence over visual complexity.

I'm currently building Here Is My CV , a Canva-like resume builder that helps people create resumes and online CVs. Like many indie builders, I spend a lot of time deciding what to build next. Should I add more templates? More AI features? More customization? Recently, I realized I was making assumptions. So I asked a simple question: What frustrates you most about existing resume builders? The options were: The results surprised me. I expected customization or pricing to come out on top. Instead, ATS compatibility received the most votes. At first, I thought people were asking for ATS optimization tools. But after reading comments and talking to job seekers, I realized something else was happening. Most people don't actually know whether their resume is ATS-friendly. They don't know: The issue wasn't ATS itself. It was trust. As developers, we often think more features create more value. Users don't always agree. Many resume builders compete by adding: But the feedback I received suggested people wanted something simpler. They wanted confidence. A clean template they could trust. Based on that feedback, I introduced a new template called ATS Classic . Instead of focusing on visual complexity, the goal was: Nothing revolutionary. Just a template designed around the most common concern users shared. Make your own ATS-friendly CV at https://hereismycv.com https://hereismycv.com The most valuable product insights often come from asking simple questions. I could have spent weeks debating feature priorities. Instead, a small poll revealed a problem I had underestimated. As builders, we often focus on what we think users want. Sometimes it's worth pausing and asking them directly. The answer might completely change what you build next. What user feedback has completely changed the direction of a product you're building?