Building software is easy.
Building something people actually want to use is the hard part.
For the last few months, I've been working on CV Mimarı, a resume builder designed to make creating ATS-friendly resumes simple, fast, and accessible.
My goal wasn't to build "another resume builder."
I wanted to remove the usual pain:
confusing editors
unnecessary account creation
complicated formatting
resumes that look good but fail ATS screening
The idea was simple:
Spend your time improving your experience, not fighting with Word formatting.
What it currently does
Today the project includes:
Resume templates
AI-powered resume improvements
ATS score checking
Resume optimization
Cover letter generation
Resume examples and guides
PDF export
Modern responsive interface
I tried to keep everything clean and straightforward instead of adding dozens of unnecessary options.
Sometimes software tries so hard to become "professional" that it forgets people just want to click a button and move on with their lives.
Why I'm posting here
I'm not looking for compliments.
I'm looking for problems.
Imagine you were using this to apply for your next job.
I want brutally honest feedback.
Things like:
Is something confusing?
Does the UI feel slow?
What would make you leave the site?
Which feature feels unnecessary?
What's missing?
Would you actually trust this with your resume?
If something is bad...
Tell me.
If something is ugly...
Tell me.
If something makes you want to close the tab...
Definitely tell me.
The biggest challenge
One thing I've learned is that building features is much easier than understanding users.
I can spend a weekend implementing a new AI feature.
But discovering why someone leaves after 20 seconds?
That takes dozens of real users.
That's why I'm asking for feedback before continuing to add more features.
The roadmap
Some ideas I'm considering:
More resume templates
Better AI suggestions
Portfolio integration
LinkedIn import
Resume version history
More ATS analysis
International templates
But maybe I'm solving the wrong problems.
I'd rather hear what you think should come next.
Be brutally honest
Here's the project:
Please don't hold back.
Good feedback saves weeks of building the wrong thing.
I'd really appreciate any thoughts, criticism, or feature requests.
Thanks!
Top comments (0)