I built this because I was tired of the most tedious part of job hunting - rewriting my CV for every single application.
The process always looked the same: find a job, open a separate AI tool, paste the job description, paste my CV, wait for the result, download it, go back to the job board, apply. Repeat 20 times a day. It felt broken that job boards and CV tools existed as completely separate products when they should be one workflow. So I started building Karriero - a job aggregator that scrapes listings directly from company career pages (not employer-paid placements) and lets you tailor your CV to any job in a couple of clicks.
What started as a simple scraper with an AI prompt evolved into a full platform with compatibility scoring, so you can see how well you match a role before you even open it. The idea is simple - stop applying blindly and focus your energy on the jobs where you actually have a shot.
The approach changed a lot along the way. I initially tried to build the "perfect" CV tailoring algorithm before launching, but realized the real value was in the feedback loop - letting people see their match score first, then deciding whether it's worth tailoring their CV for that specific role. That shift from "tailor everything" to "match first, tailor smart" shaped the entire product.
The frustration of manually jumping between job boards and AI tools makes an already stressful job search feel like a repetitive data entry chore.
Most applicants spend way too much time perfecting resumes for roles where they might not even be a strong technical match based on hidden recruiter criteria.
Since you are focusing on "matching first" do you think users will start using Karriero more as a discovery tool for new career paths or strictly as a way to speed up their current search?
Yeah, that "hidden recruiter criteria" part is exactly what bugs me too. You tailor a resume for hours and have no idea if you're even in the ballpark.
Honestly I think it'll be both, but speed-up is the main job-to-be-done for most people. When you're actively searching, you just want to stop wasting time on roles you won't get shortlisted for, and see where you actually stand before investing effort into tailoring. That's the immediate pain.
The discovery angle is interesting though, and I didn't really plan for it. A few early users mentioned they were surprised to see strong matches in adjacent roles or industries they hadn't considered, which is a nice side effect of matching on skills rather than job titles. I want to lean into that more over time, but I don't think it replaces the core use case, more like a bonus layer on top of it.
That focus on the "job-to-be-done" is spot on because efficiency is usually what keeps people coming back. It is interesting that the skills-based matching is naturally opening up discovery since it proves the logic is solid even beyond what you initially planned.
That unexpected "discovery" angle is actually a great story for building authority around the platform. By the way I handle digital PR and media placements for brands so I see how these unique angles help products stand out. Have you thought about showcasing those specific "adjacent industry" success stories to grow your reach?
Appreciate that, and yeah, I hadn't really thought about the adjacent-industry angle as a growth story until you framed it that way. Makes sense though, those are probably the most interesting anecdotes anyway since they're counterintuitive.
Honestly I'm still heads-down on the product side and not ready to invest in PR or media placements yet, but I'll keep the idea in mind once there's enough signal to actually build a narrative around it. Thanks for the thought.
Totally understand being heads-down on the product, that’s the priority. However, the reason I mentioned the discovery angle is because technical journalists are currently shifting away from generic AI news and looking for exactly these kinds of 'counterintuitive skill-matching' stories.
I actually have a couple of specific media touchpoints in the HR-tech space that would love this. When you have 5 minutes, I’d love to share a quick framework on how you can start collecting these anecdotes now without it taking time away from your dev work. What’s the best way to send that over to you?