Problem
Job searching can quickly become messy: scattered notes, forgotten follow-ups, unclear priorities, and little visibility into what’s working. Most people end up tracking applications in fragile spreadsheets or not at all.
Archeway is designed to make job searching feel manageable by giving users a single, structured workflow for applications, deadlines, and progress.
Solution
I’m building a full-stack web platform centered on a Kanban-style pipeline (Applied → Interviewing → Offer, etc.) that supports notes, deadlines, and lightweight analytics so users can stay organized and iterate their approach.
What I built (so far)
- Kanban workflow for applications with status transitions
- Structured application model (company, role, links, notes, dates, outcome)
- Deadline / follow-up tracking to prevent missed opportunities
- Foundation for analytics (counts by stage, time-in-stage, response rates)
- Scaffolded backend routes and database planning for long-term scalability
Architecture (high-level)
The system is designed to keep the UI fast while keeping data validation and business rules in the backend.
Outcome
- Clear single workflow for managing applications and follow-ups
- Reduced “mental load” by capturing status + next action in one place
- Built a foundation for meaningful analytics and improvement over time
As the product matures, I’ll add screenshots, sample analytics, and a public live demo if appropriate.
Roadmap
- User authentication + multi-device persistence
- Calendar integration / reminders for follow-ups
- Analytics dashboard (conversion rates, time-to-response, stage bottlenecks)
- Import/export from spreadsheets
Lessons learned
- Strong data modeling early makes UX features easier later
- Simple UX beats feature overload for productivity tools
- Progress metrics are only useful when the workflow is consistent
Next up: