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>
3.7 KiB
Jobjakt Product Roadmap
Purpose
Defines the strategic direction of Jobjakt.
This roadmap represents product priorities, not a strict development schedule.
Features should be evaluated against:
- Does this improve job tracking?
- Does this improve application success?
- Does this improve career management?
- Does this support future growth?
Product Strategy
The product evolves in layers.
The order is:
Job Tracking Foundation
↓
Application Workflow
↓
Career Workspace
↓
AI Assistance
↓
Automation
↓
SaaS Platform
Phase 1 - Core Job Tracking Excellence
Priority: Critical
Goal:
Make Jobjakt the best place to manage a job search.
Features
Job Management
- Add jobs manually.
- Import jobs from URLs.
- Extract job details.
- Store companies.
- Search jobs.
- Filter jobs.
Application Workflow
Support complete application lifecycle:
- Interested.
- Preparing.
- Applied.
- Interview.
- Offer.
- Rejected.
Communication Tracking
Support:
- Emails.
- Notes.
- Follow-ups.
- Timeline.
Dashboard Improvements
Provide:
- Application overview.
- Upcoming actions.
- Progress metrics.
- Recent activity.
Phase 2 - User Experience Improvements
Priority: High
Goal:
Make the application simple and intuitive.
Improvements
- Redesign navigation.
- Improve onboarding.
- Simplify settings.
- Improve empty states.
- Improve error handling.
- Improve mobile experience.
Phase 3 - Career Workspace Foundation
Priority: High
Goal:
Create a single professional source of truth.
Features
Career Profile:
- Personal details.
- Experience.
- Education.
- Skills.
- Projects.
- Certifications.
- Languages.
Phase 4 - CV Builder
Priority: High
Goal:
Create a premium CV creation experience.
Inspired by:
- FlowCV.
- Reactive Resume.
- Novoresume.
- ElegantCV.
Features
Content
Users manage:
- Personal details.
- Summary.
- Experience.
- Education.
- Skills.
- Projects.
- Certificates.
- Publications.
- Custom sections.
Themes
Support:
- Multiple templates.
- ATS-friendly designs.
- Professional layouts.
- Accent colours.
- Typography.
- Photo settings.
Builder
Support:
- Live preview.
- Structured editing.
- Section management.
- AI assistance.
- Export.
Phase 5 - AI Career Assistant
Priority: Medium
Goal:
Use AI to reduce repetitive career tasks.
Features:
- CV improvements.
- Bullet rewriting.
- Job matching.
- Cover letters.
- Interview preparation.
- Career advice.
AI must:
- Preserve facts.
- Require user approval.
- Explain changes.
Phase 6 - Job Discovery
Priority: Medium
Goal:
Help users discover opportunities.
Potential features:
- Job search integrations.
- Filters.
- Location search.
- Industry search.
- Remote options.
- Import directly into tracker.
Important:
Job discovery supports tracking.
It does not replace job boards.
Phase 7 - Public Career Profile
Priority: Medium
Goal:
Allow users to share professional identity.
Features:
- Public CV.
- Portfolio.
- Career profile.
- Shareable URL.
Example:
/cv/{random-guid}
Phase 8 - SaaS Platform
Priority: Later
Goal:
Commercialise the platform.
Features:
- User subscriptions.
- Premium themes.
- AI quotas.
- Storage limits.
- Billing.
- Admin management.
Long-Term Ideas
Possible future features:
- Interview preparation.
- Salary insights.
- Career analytics.
- Skill recommendations.
- Learning paths.
- Recruiter visibility.
- Portfolio hosting.
Roadmap Rules
Do not:
- Build future features before core workflows are excellent.
- Sacrifice simplicity for complexity.
- Add features because competitors have them.
Always prioritise user value.