The job-search tab graveyard

Job hunting has a very specific kind of chaos. One tab has a role you saved three days ago. Another has a half-finished application. A third has a Notion board you promised yourself you would keep updated. Then there are the emails, the follow-ups, the resume versions, and the little voice in your head asking whether you should apply for one more role before sleeping.

I was in that loop myself. It was not that I did not know how to apply. It was that the process made every small action feel weirdly expensive. Finding the right role, understanding it, tailoring the next step, and remembering where I had already applied was eating more energy than the actual work I wanted to show up for.

The thing that finally clicked

The obvious answer was not another spreadsheet. I wanted something that could sit closer to the job hunt itself and make the repetitive parts less annoying. That became the first real thought behind Fylla: a career assistant that helps job seekers move from 'I should apply' to an actual next step without opening twelve tabs first.

It started as a personal painkiller, which is usually the best kind of product brief. No massive startup manifesto. Just: can I make this process calmer, more organised, and a little less soul-draining for someone who is already doing their best?

What Fylla is trying to make less painful

Fylla is built around the messy middle of a job search: finding roles, keeping applications from disappearing into the void, and having enough context to make a good next move. The goal is not to replace a person with an AI bot that fires off applications everywhere. That is not the vibe.

The better version is useful assistance. Help people organise the search, reduce the repeat work, and spend more time on the applications and conversations that actually matter. Career growth is already personal. The tooling around it should feel personal too.

• Find better-fit roles without losing the thread.
• Keep applications, notes, and next steps in one place.
• Use AI for the repeat work while keeping the decisions human.

The part I am building carefully

Fylla is built with Next.js, TypeScript, and PostgreSQL. The Chrome extension is important because job hunting happens inside job pages, not inside a perfect blank dashboard. Bringing useful context closer to the place where people are already researching makes the product feel less like homework.

I am also using MCP as part of the workflow so the right tools can share context without making the user copy-paste the same details all day. The technical stack is cool, sure, but the real test is simpler: does this save someone time when they are tired, stressed, or trying to apply before a deadline?

The early numbers, without the fake founder flex

Right now, Fylla has 400 registered users and 2 Pro users. That is not a giant number, and I do not want to turn it into a dramatic LinkedIn math problem. It is early. But it is real people choosing to try something I built because they also feel the friction in job searching.

The two Pro users matter too. They are a reminder that the product has to earn its place. You do not get to ask people to pay just because the landing page has nice gradients. You have to keep making the workflow clearer, faster, and worth coming back to.

Still early. Still building.

Fylla is very much a work in progress, and honestly that is the fun part. Every user question, rough edge, and 'why does this take three clicks?' moment is a better roadmap item than a random feature list.

I built Fylla because job hunting felt more complicated than it needed to be. The mission now is pretty simple: keep removing friction, keep listening, and make the search feel a little more human. One less tab open is a win.