I've been thinking about a problem that sounds simple:
Why does applying for a job still require so much repetitive work?
We already have:
- Indeed
- Resume builders
- AI resume tools
- Autofill tools
- ATS platforms
- Application trackers
Yet the workflow still looks something like this:
Find a job.
Read the description.
Change the resume.
Fill out another application.
Enter the same information again.
Go through a different ATS.
Submit.
Track the application.
Then repeat everything for the next job.
The problem isn't one bad tool
Most of these tools actually do their individual jobs reasonably well.
The problem is what happens between them.
Your job search becomes a collection of disconnected steps.
The candidate ends up doing all the "glue work":
- moving information between systems
- maintaining resume versions
- repeating application details
- remembering where they applied
- tracking application status
That's the part I wanted to attack.
So I started building something
I'm building AAOS around a simple idea:
The job seeker shouldn't have to manually coordinate the entire workflow.
The system is designed to bring the repetitive parts together:
Discover → Match → Tailor → Apply → Track
The goal isn't simply to submit more applications.
It's to reduce the repetitive work around a serious job search while keeping the candidate in control.
For example, instead of manually opening a job, figuring out what needs to change in the resume, and then repeating information through another application flow, the system can handle much more of that workflow.
What surprised me
The hardest part isn't generating a resume.
AI can already do that.
The harder problem is building a reliable workflow that survives the messy reality of actual applications:
Different job platforms.
Different ATS systems.
Different questions.
Different resume requirements.
Different application states.
That's where I think there's still a lot of interesting engineering work to do.
I'm building AAOS to explore that problem.
I'm currently testing the workflow with real job seekers and looking at where it actually saves time versus where automation still falls short.
If you're interested in the engineering/product side of AI automation, I'd be happy to share more about how I'm approaching it.
You can also see the product here:
Top comments (0)