cesnimda
263 lines
4.7 KiB
Markdown
263 lines
4.7 KiB
Markdown
# UX Flows
|
|
|
|
## Core philosophy
|
|
|
|
The user should usually know what to do next.
|
|
|
|
Jobjakt should not simply display information. It should guide users through a sensible career workflow while allowing experienced users to move freely.
|
|
|
|
## Primary job workflow
|
|
|
|
### Step 1 — Add or import job
|
|
|
|
User can:
|
|
|
|
- add manually,
|
|
- import from a supported URL,
|
|
- paste job content where appropriate.
|
|
|
|
After import, Jobjakt should confirm what was captured and show any fields that need review.
|
|
|
|
### Step 2 — Analyse job
|
|
|
|
System extracts and structures useful job information such as:
|
|
|
|
- role,
|
|
- employer,
|
|
- location,
|
|
- employment type,
|
|
- salary where available,
|
|
- deadline,
|
|
- requirements,
|
|
- desired skills,
|
|
- responsibilities,
|
|
- useful keywords.
|
|
|
|
### Step 3 — Compare with Career Profile
|
|
|
|
Present:
|
|
|
|
- overall match,
|
|
- strong matches,
|
|
- partial matches,
|
|
- missing or unverified requirements,
|
|
- relevant experience,
|
|
- suggested areas to emphasise.
|
|
|
|
Never convert an unknown or missing skill into a claimed skill.
|
|
|
|
### Step 4 — Suggested next action
|
|
|
|
Example:
|
|
|
|
`82% profile match`
|
|
|
|
Recommended next step:
|
|
|
|
`Tailor your CV for this role`
|
|
|
|
Provide a clear CTA while allowing users to ignore it.
|
|
|
|
### Step 5 — Tailor CV
|
|
|
|
User selects an existing CV or creates a job-specific variant.
|
|
|
|
AI can suggest:
|
|
|
|
- reordering skills,
|
|
- emphasising relevant experience,
|
|
- shortening irrelevant material,
|
|
- rewriting content using only known facts.
|
|
|
|
All AI changes require preview/review before application.
|
|
|
|
### Step 6 — Application material
|
|
|
|
User creates or edits:
|
|
|
|
- cover letter,
|
|
- application answers,
|
|
- supporting documents.
|
|
|
|
### Step 7 — Apply
|
|
|
|
When status changes to `Applied`, Jobjakt should be able to record:
|
|
|
|
- application date,
|
|
- CV used,
|
|
- cover letter used,
|
|
- source,
|
|
- optional notes.
|
|
|
|
### Step 8 — Track
|
|
|
|
Job page should become the ongoing source of truth for:
|
|
|
|
- status,
|
|
- tasks,
|
|
- deadlines,
|
|
- contacts,
|
|
- notes,
|
|
- events,
|
|
- interviews,
|
|
- documents,
|
|
- timeline.
|
|
|
|
### Step 9 — Interview preparation
|
|
|
|
When a job reaches an interview stage, surface relevant actions such as:
|
|
|
|
- prepare likely questions,
|
|
- research company,
|
|
- review job requirements,
|
|
- review personal examples,
|
|
- create preparation notes,
|
|
- add interview event.
|
|
|
|
### Step 10 — Outcome
|
|
|
|
Record:
|
|
|
|
- offer,
|
|
- rejection,
|
|
- withdrawal,
|
|
- acceptance,
|
|
- other final status.
|
|
|
|
Use outcome data for personal analytics without shaming or gamifying the user.
|
|
|
|
## Job detail UX
|
|
|
|
Use a dedicated page with a clear hierarchy.
|
|
|
|
Suggested header:
|
|
|
|
- Role title
|
|
- Company
|
|
- Location / work mode
|
|
- Current status
|
|
- Priority / favourite
|
|
- Match score
|
|
- Deadline
|
|
- Key actions
|
|
|
|
Suggested tab or section model:
|
|
|
|
### Overview
|
|
|
|
- description summary,
|
|
- role details,
|
|
- important requirements,
|
|
- salary/deadline/location,
|
|
- next recommended action.
|
|
|
|
### Match
|
|
|
|
- overall score,
|
|
- matched requirements,
|
|
- gaps,
|
|
- supporting evidence from Career Profile,
|
|
- suggested CV emphasis.
|
|
|
|
### Application
|
|
|
|
- current application status,
|
|
- application date,
|
|
- application material,
|
|
- answers / cover letter,
|
|
- submission information.
|
|
|
|
### Documents
|
|
|
|
- CV used,
|
|
- cover letter,
|
|
- attachments,
|
|
- generated variants.
|
|
|
|
### Timeline
|
|
|
|
Chronological history of:
|
|
|
|
- status changes,
|
|
- notes,
|
|
- messages,
|
|
- interviews,
|
|
- tasks,
|
|
- document generation,
|
|
- relevant events.
|
|
|
|
### Tasks / Notes
|
|
|
|
May be a dedicated section or integrated into Overview/Timeline depending on final usability testing.
|
|
|
|
## Status model
|
|
|
|
Provide sensible default statuses, with user-configurable custom statuses.
|
|
|
|
Suggested defaults:
|
|
|
|
- Interested
|
|
- Preparing
|
|
- Applied
|
|
- Screening
|
|
- Interview
|
|
- Final Interview
|
|
- Offer
|
|
- Accepted
|
|
- Rejected
|
|
- Withdrawn
|
|
|
|
Customisation should preserve analytics by mapping custom statuses to broader system categories where needed.
|
|
|
|
## Tasks and reminders
|
|
|
|
Users should be able to attach tasks to jobs.
|
|
|
|
Examples:
|
|
|
|
- Follow up with recruiter
|
|
- Prepare interview examples
|
|
- Submit application before deadline
|
|
- Update CV
|
|
|
|
Tasks should support due dates and notifications.
|
|
|
|
## Events
|
|
|
|
Jobs may be linked to events such as:
|
|
|
|
- interview,
|
|
- recruiter call,
|
|
- deadline,
|
|
- follow-up,
|
|
- networking event,
|
|
- career fair.
|
|
|
|
A future calendar integration should be possible without requiring it in the first redesign phase.
|
|
|
|
## Onboarding
|
|
|
|
New user flow:
|
|
|
|
1. What are you looking for?
|
|
2. Import/upload an existing CV if available.
|
|
3. Build/review Career Profile.
|
|
4. Add first job.
|
|
5. Arrive at personalised dashboard.
|
|
|
|
The first question may also support aggregate analytics, but it should still provide user value where possible.
|
|
|
|
## Goals
|
|
|
|
Allow optional weekly goals, but avoid language that makes the user feel they have failed.
|
|
|
|
Better framing:
|
|
|
|
- "Weekly target"
|
|
- "Your pace"
|
|
- "Application goal"
|
|
|
|
Avoid aggressive streak mechanics or punitive red states.
|
|
|
|
Goals should be optional and editable.
|