AICVscreening
Screen hundreds of CVs in minutes with AI
Hey everyone,
I just pushed the "Launch" button on AICVScreening.com. It’s a tool designed to help recruiters/founders screen hundreds of CVs against a job description in minutes instead of days.
The Backstory
We’ve all been there: The "Black Hole" of job applications. I once waited 5 weeks just to get a generic automated rejection. That silence sucks for candidates, and for companies, it’s a massive loss of top talent. I wanted to build something that kills the "manual resume grind" bottleneck.
The Build Breakdown (Total Time: ~23 Hours)
I wanted to battle-test GoLiveKit to see how fast I could ship a production-ready app. Here is exactly where the hours went:
Day 1 (3h): Architecting. I drafted a massive
project.mdwith every requirement. Planning first saved me at least 10 hours of "coding in circles" later.Day 2 (4h): The "AI Heavy Lifting." Task splitting and core implementation using an AI-assisted task manager.
Days 3-5 (6h): The Polish. Bug fixing and manual testing (the "last 20%" of the build).
Day 6 (4h): The "Administrative Grind." This was the most annoying part. Connecting Cloudflare, R2, Stripe, Plunk, Google Auth, Analytics, GitHub keys... it’s a 3rd-party plumbing nightmare.
Day 7 (6h): The Creative Wall. Marketing assets, video demos, and social images. Honestly, as a dev, this was the hardest part.
The Verdict: Starter kits are a cheat code for the core build, but the "final frontier" of optimization is definitely the 3rd-party setup and marketing assets. We need a tool that handles the "plumbing" in one prompt!
The Tech Stack / Features
Input: Upload .PDF, .DOCX, .MD, or even a .ZIP of resumes.
Output: Ranked results with scores, pros/cons, and a "Detailed Why" for every candidate.
Export: Full .CSV export for your existing ATS.
I’d love your feedback on two things:
The "Day 6" Struggle: How do you guys automate the 3rd-party setup (Stripe/Auth/DNS/Email)? Is there a better way, or do we just have to suffer through it every time?
The UX: Is the "upload-to-rank" flow clear enough for a non-technical recruiter?
Check it out: https://aicvscreening.com
1 Comment
Recruiters and founders often get buried under a mountain of resumes only to realize they’ve spent days just to find a handful of decent candidates. It is a massive drain on time when you have to manually scan every single PDF just to see if someone actually fits the core requirements of the job. Since you built this to kill the "manual resume grind" how do you ensure the AI doesn't accidentally filter out great non-traditional candidates who might not have the perfect keywords on their CV?