I Couldn’t Find a Job for Almost a Year. Then I Accidentally Built a Startup.
About a year ago, I was in a place that honestly felt frustrating, exhausting, and confusing at the same time. I was trying to find work and build a future in tech, and I genuinely believed I was doing everything correctly.
I wasn’t sitting around waiting for luck.
I was learning constantly. I was building projects. I was improving my backend skills, working with Python, experimenting with ideas, and trying to become the kind of developer companies would want to hire.
I truly believed that if I became good enough, opportunities would eventually come.
That sounded logical.
Work hard. Improve. Become valuable. Get opportunities.
Simple.
At least that was what I thought.
But reality started feeling very different.
Whenever I got an interview opportunity, I treated it like one of the most important events in my life. I wasn’t preparing for interviews for an hour or quickly reviewing common questions.
Sometimes I spent an entire week preparing for a single interview.
I researched companies in advance. I read documentation. I watched videos. I reviewed technologies they used. I tried understanding their products, their stack, possible technical questions, and every scenario I could think of.
I wanted to remove every possible reason for failure.
Because when you spend months searching for opportunities, every interview starts feeling bigger than it probably should.
You begin thinking:
Maybe this is the one.
Maybe this changes everything.
Maybe this finally works.
But many times nothing happened.
Some companies rejected me.
Some disappeared completely.
Some never answered at all.
And honestly, after a while silence became worse than rejection.
Rejection at least feels human.
Silence feels strange.
Silence feels like sending something into a black hole and waiting for a response that never arrives.
I remember constantly refreshing inboxes.
Checking messages.
Opening email again.
Thinking maybe I missed something.
Maybe tomorrow there would be an answer.
Maybe next week.
Maybe something finally changed.
But weeks turned into months.
And after enough time something slowly starts changing inside your head.
You stop questioning technologies.
You stop questioning resumes.
You stop questioning the market.
You start questioning yourself.
You begin wondering whether maybe you’re not good enough.
Maybe everyone else knows something you don’t.
Maybe there is some invisible rule everyone understands except you.
I think many people who struggled with job searching understand exactly what I mean.
Because eventually it stops feeling like a process.
It starts feeling personal.
But the strange thing was that I wasn’t only seeing this happen to myself.
I kept seeing talented people around me struggling too.
Developers with serious projects.
People with real skills.
People with actual experience.
People who should have been getting opportunities.
And somehow many of them kept experiencing the exact same thing.
That part bothered me.
Because competition alone couldn’t explain everything.
There had to be something else.
So eventually curiosity took over.
I started asking questions I had never thought much about before.
What actually happens after someone presses “Apply”?
Who sees your resume first?
How are applications processed?
Why do some people receive interviews while others disappear?
Where exactly does everything break?
At first I was simply curious.
But curiosity slowly turned into obsession.
I started researching ATS systems.
Then recruiting platforms.
Then hiring workflows.
Then resume structures.
Then algorithms.
Then patterns.
The deeper I went, the stranger everything became.
Because I realized modern hiring often wasn’t:
Candidate → Recruiter → Interview
There was an invisible layer in between.
Systems.
Filters.
Ranking algorithms.
Matching mechanisms.
Automation.
And suddenly I realized something that completely changed how I looked at hiring.
People were not always competing against other people.
Sometimes they were competing against infrastructure.
And infrastructure behaves very differently than humans.
That realization stayed in my head for weeks.
Because one thought kept repeating itself:
What if many people don’t actually have a skills problem?
What if they have a visibility problem?
I started running small experiments.
I tested different resume structures.
Different wording.
Different ways of presenting projects.
Different positioning.
I wanted to understand whether systems interpreted candidates differently depending on how information was communicated.
And eventually I noticed something that felt almost unfair.
Two people could have very similar skills.
Very similar experience.
Very similar technical ability.
Yet one profile looked average while another looked highly relevant.
Not because one person was more talented.
Because one person communicated value differently.
That realization completely changed everything.
Because suddenly I couldn’t stop thinking about how many talented people might be filtered out every day without understanding why.
Eventually small experiments became prototypes.
Prototypes became algorithms.
Algorithms became ideas.
And one day I had a strange realization:
I wasn’t researching a problem anymore.
I had accidentally started building a product.
Three months ago I decided to stop treating the idea like a side experiment.
That eventually became CVBoosta.
What surprised me even more was realizing I wasn’t the only person experiencing this problem.
After launching CVBoosta and talking to users, I kept hearing similar stories.
Talented people with strong skills, projects, and experience kept struggling with the same thing I had experienced myself.
The first person I tested everything on was me.
I used my own resume.
My own applications.
My own frustration.
I kept experimenting with wording, structure, positioning, and presentation.
I wanted to understand what actually changed results and what didn’t.
And over time something interesting started happening.
Interview invitations started increasing.
Response rates started improving.
Compared to previous periods, I started seeing results that felt dramatically different.
In some cases the number of interview invitations became four to six times higher than before.
That was probably the moment everything became real.
Because suddenly this stopped feeling like curiosity.
Stopped feeling like experiments.
Stopped feeling like random ideas.
For the first time it felt like I had found something capable of helping people avoid spending months questioning themselves the way I did.
And honestly I think that’s why this became much bigger than simply building another product.
Because I know exactly what it feels like to spend months wondering whether you’re the problem.
I know what it feels like to spend days preparing for interviews and hear nothing back.
And now I know what it feels like to build something from frustration and watch other people benefit from it too.
That’s probably why I want to dedicate myself fully to this product.
Because for the first time I’m not building something random.
I’m building something I genuinely wish I had when I needed it most.
Replies