Grove Journal
Home
on building Grove

I can't code, but I built the tool that fixed my job search.

I love building things. I also really don't know how to code. And I hate job hunting. This is the story of how those three things turned into an app called Grove.

For a while now I've been kind of obsessed with Claude and Claude Code. At first it was just for fun. I'd build little random things to see what I could pull off. Around the same time I was job hunting, which was making me miserable. You send out a bunch of applications and hear nothing back. You open your laptop, look at the pile, and close it again.

The worst part of my week

One day I had a random thought. What if I made this less miserable by building something while I did it. Take the worst part of my week and turn it into a project instead.

It started really small. Then it kind of snowballed. Every time something in my search annoyed me, I'd add a feature for it.

First I thought, what if the AI could actually learn about me, then go find jobs for me overnight and have them ready in the morning. So I built that.

career-kitchen.local — early build
Auto-playing
An early version — I'd made the whole thing chef themed: roles were dishes to "cook," to-dos lived "on the pass," it greeted me with "let's get cooking." Zero business branding a tool only I'd ever use. I just wanted to avoid job searching.

Then I thought, my résumé can only be so long. It wasn't showing half of what I've actually done. What if the app could look at the jobs I wanted and figure out what I was leaving off. So I built that too.

Then I thought, if it's finding me jobs every night, it should get better over time. So I added a way to rate the jobs and say why, so the next morning's batch would be a little better than the last.

grove.app — today
Auto-playing
A later version. The cooking gimmick was gone and it had become Grove: one clear "your move" for the day, an honest read on whether my search was working, and jobs tailored to me.

None of this was some grand plan. I was just making my own life easier one piece at a time. And at some point I noticed I wasn't even dreading the job search anymore. I was just using the thing I built.

Here's the part that stuck with me

I can't code. But I had the ideas. I knew what I wanted it to feel like. And I could tell the AI what I meant and keep fixing it until it was right. Turns out that's enough now. The hard part was never the code. It was knowing what to build and why.

And that's basically what Grove is about too.

I've always felt like it was almost impossible to show who I really am on one page, or in one quick phone call. Your skills, your work ethic, the way you think, all of it is about you as a whole person. A résumé and a fifteen minute call were never going to catch that.

For most of my life, being good at a lot of things but not a clean fit for one job title felt like a problem. Now that AI can do most of the actual work, it's the opposite. Having range and ideas is the valuable part.

You're worth more than a job title. You're definitely more than a résumé. The problem is hiring still can't see that. It just scans for keywords.

What Grove actually does

So that's what Grove does. It reminds you that you've done more than you think. It helps you find jobs you'd actually be good at, even ones you'd have skipped over. And it helps you show who you really are, without making anything up.

I built it because I needed it. And honestly, the fact that I could build it at all, with no coding background, kind of proves the whole point.

Really, it was just me following an idea to see where it went. I'm not trying to make it a company.

I made a small demo you can poke at. It runs on sample data and connects to nothing. Have a look around →

AV
Written by
Arber Velencia

I built Grove because I needed it. I'm also looking for my next role. And if any of this resonates with you, reach out to me. Even if it's just to chat.

Reader response

What did you think?

Comments
Loading…
Comments publish immediately. No account needed.