Why I'm building YourMove
The job application process kept asking me to repeat work I'd already done. This is why I'm building a different approach.
I’m building YourMove because looking for work has a strange way of becoming its own full-time job.
You find a promising position, read the description, and decide it’s worth applying. Then another hiring system asks you to upload your résumé, re-enter your work history, and write answers you’ve already written somewhere else.
The effort doesn’t carry over. The next application starts from scratch.
I’ve spent years working in technical support, web operations, and software projects. I’m also looking for work myself. That combination made the repetition especially hard to ignore. I could see how much useful information was getting scattered across forms, documents, and browser tabs.
The idea is straightforward
YourMove is meant to give that work a place to live.
Keep track of opportunities. Keep the documents and answers that matter. Build a record of actual experience that you can return to instead of inventing a new version of yourself for every application.
When an employer form is supported, YourMove can help prepare it. You still review the information, correct what needs correcting, and submit the application yourself.
I’m not trying to build a tool that fires off hundreds of applications without reading them. I’m trying to make the applications you choose less wasteful.
Building it in the open
YourMove is an independent, free and open-source project. It’s still being developed, and the distinction between what’s implemented, what’s tested, and what’s ready for public use matters.
I’ll use this blog to talk about the product, the engineering decisions, the parts that work, and the parts that don’t. Some posts will be about job searching. Others will get fairly technical.
If you’re dealing with the same application grind, I hope this becomes useful.
— Joshua
