cesnimda
b176a44627
Active docs/ was stub scaffolding while the real docs sat in docs/_archive/. Restore and correct them, and record the Phase 0 work. - docs/architecture/current.md: verified system map (from archived SYSTEM_OVERVIEW, 9 corrections against code). - docs/research/competitors.md: sourced competitor analysis (from archived PRODUCT_RESEARCH, feature matrix corrected). - docs/decisions/ADR-002-job-application-model.md: the Job/JobApplication split. - docs/application-discovery-report.md, docs/implementation-roadmap.md, docs/phase-0-foundation-report.md, docs/career-workspace-branch-assessment.md. - Remove 10 zero-byte placeholder files that advertised content that never existed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.6 KiB
overview
TODO: Complete documentation.
Job Tracking Overview
Purpose
Job tracking is the primary purpose of Jobjakt.
The application exists first to help users manage their job search.
Career features, CV generation, AI assistance, and job discovery support this workflow.
They do not replace it.
Core Product Statement
Jobjakt helps users:
Find opportunities
↓
Track applications
↓
Manage communication
↓
Prepare better applications
↓
Secure employment
Core Objects
The main entities are:
Job
The opportunity itself.
Examples:
- Software Engineer position.
- Developer role.
- Marketing position.
Contains:
- Title.
- Company.
- Description.
- URL.
- Location.
- Salary information.
- Requirements.
Application
The user's attempt to obtain the role.
A job can exist without an application.
Example:
User saves an interesting role.
Later they apply.
Company
The organisation offering the role.
Should be reusable.
Example:
Multiple jobs from Google should link to one company.
Communication
Interactions related to the application.
Examples:
- Emails.
- Calls.
- Messages.
- Notes.
Follow-up
A planned action.
Examples:
- Contact recruiter.
- Check application status.
- Prepare interview.
Product Principles
Reduce manual work
Import information where possible.
Keep users organised
The user should always know:
- What jobs exist.
- What stage applications are at.
- What action is next.
Avoid unnecessary complexity
Do not require users to complete every field.
Smart defaults are preferred.