I Built an AI Resume Builder in 48 Hours — Here is the Honest Truth
I Built an AI Resume Builder in 48 Hours — Here is the Honest Truth
No funding. No team. Just me, a coffee addiction, and a Next.js template. Here is what worked, what broke, and what I would do differently.
The Backstory
It was a Tuesday at 2 AM. I was helping a friend format her resume for the 47th time and thought: *"This should not be this hard."*
48 hours later, I had a working AI resume builder. Not a perfect one. A working one.
Here is the honest breakdown — revenue numbers, technical failures, and the feature nobody asked for but everyone uses.
Hour 0-8: The MVP
Tech stack:
What I built:
The prompt that actually worked:
``` You are an expert resume writer. Create a professional resume for: Name: {name} Role: {role} Experience: {experience} Skills: {skills}
Rules:
Output as markdown. ```
First mistake: I tried to get GPT to output HTML directly. It broke constantly. Markdown → HTML conversion was far more reliable.
Hour 8-16: The Launch
I posted on:
Results in 24 hours:
| Platform | Traffic | Signups | Paid | |----------|---------|---------|------| | Hacker News | 1,847 | 89 | 3 | | Reddit r/webdev | 432 | 31 | 1 | | Twitter | 298 | 22 | 0 | | Indie Hackers | 156 | 12 | 0 | | Direct | 67 | 8 | 0 |
Total: 2,800 visitors, 162 signups, 4 paid conversions. $20 revenue.
Not life-changing. But proof that people wanted it.
Hour 16-24: The Iteration
Based on user feedback, I built three features in 8 hours:
1. Real-Time Preview
Users wanted to see the resume as they typed. I added a split-screen layout with a live preview updating every 2 seconds.
Tech: React state + debounced re-render. No complex state management needed.
2. Multiple Templates
Turns out "modern but not flashy" means different things to different people. I added 3 templates:
The surprise: 67% of users chose "Minimal." Even for creative roles. The data contradicted my assumptions.
3. ATS Score
This was the feature nobody asked for but everyone shared. After generating a resume, the tool gives an "ATS Score" (0-100) based on:
How it works:
Result: Users screenshot their scores and post them on LinkedIn. Free marketing.
Hour 24-48: The Reality Check
By hour 30, the site had 400 signups and 12 paid users. $60 total.
Here is what I learned:
What Worked
What Broke
What I Would Do Differently
The Numbers After 30 Days
Not quit-your-job money. But a working product, 687 emails, and proof of demand.
The Code (Simplified)
Here is the core generation logic, abstracted:
```typescript
async function generateResume(data: ResumeData): Promise
The real code handles retries, streaming, and error states. But this is the heart of it.
Why I Am Telling You This
Because most "I built X in 48 hours" posts are humblebrags. This is not. I made $156. I broke things. I ignored mobile. I overpaid for AI.
But I also learned that:
If you are thinking about building something, do it. Use a weekend. Use a template. Use AI to move faster. The worst case is you learn something. The best case is you build income.
Tools I Used
What Is Next
I am turning the 48-hour project into a proper product. The current version at [DevelopersMatrix](/tools/ai-resume-builder) has:
Revenue target: $1,000 MRR by end of 2026.
References
Share this article
Alex Rivera
Writer & Technologist