Operations dashboard
Seven areas organize overview, jobs, applications, activation, analytics, preferences, and sources.
Project 05 · Local-first product
Job Application Agent
A dashboard and automation system for job discovery, ranking, execution queues, confirmed applications, activation, and outcome tracking.
- PWA dashboard
- Local API
- Action queue
- ATS execution
Built and operated · local-first
Product walkthrough · fictional datasetFICTIONAL DATA
Control center
Run completeToday’s operation
Qualified roles9
Queued actions3
Useful blockers1
- Overview: Today’s operation — Run complete
- Jobs: Evaluated opportunities — 3 ready
- Queue: Execution controlled by policy — Policy active
- Sources: Every channel leaves evidence — Coverage complete
- Applications: The result comes from the external system — Receipt found
1 / 5
All records in this demonstration are fictional and generated for this page. No live user data is loaded.
The product
One control center for a fragmented operation.
A job search spans different sources, fit criteria, documents, human decisions, and ATS products. The system brings evaluated candidates, pending actions, external confirmations, and responses into one auditable state.
What shipped
From dashboard to execution, every module exists in the product.
Explainable ranking
Each opportunity combines a score, reasons, risks, compensation, and company signals before it enters the queue.
Agent action queue
Apply for me creates a traceable action: queued, running, needs review, blocked, or completed.
ATS execution
Materials are tailored per role, and an application enters history only after external confirmation.
Product architecture
Reusable code, private state, and automated checks.
Product and data separated
The dashboard, local server, helpers, and examples are versioned. Identity, private settings, documents, and history stay outside the repository.
Per-source coverage
Every source records its own status, volume, timestamp, and error. An unavailable source never becomes an empty market.
Role-specific documents
Resume, cover letter, and answers are assembled from verified facts and adapted to the opportunity context.
Activation and outcomes
After an application, the system prepares outreach, tracks responses, and records reusable learnings.
Implementation
Delivered components.
The implementation combines an installable interface, local API, persistent state, policies, an action queue, document generators, and checks executed by the agent.
- Responsive dashboard installable as a PWA
- Local server with an API and file-backed persistent state
- Match scoring, source coverage, and activation-package evaluators
- Action queue with explicit operational states
- Flows for Greenhouse, Lever, Ashby, and Workday
- Example configuration for bootstrapping another operation without private data