Jobs with positions and contributions #24

New issue

Closed

opened 2026-06-12 20:28:26 +00:00 by james · 0 comments

james commented

2026-06-12 20:28:26 +00:00

Owner

Structurally the most complex item in the career domain. Three nested entities.

Scope

Data:

Job: company name, start date, end date (nullable for current). Carries a user_id FK.
Position: title, start date, end date (nullable), FK to Job. user_id denormalized onto Position for queryability and isolation safety.
Contribution: problem statement, value proposition, accomplishment measurement, FK to Position. user_id denormalized here too.

UI:

Jobs list under Experience.
Drill into a Job to view/edit its positions.
Drill into a Position to view/edit its contributions.

Backend:

Entities + migrations for all three.
Cascading deletes (deleting a Job removes its Positions and Contributions). Handle in app code if engines diverge on FK cascade behavior.
Full CRUD API + DTOs. All queries scoped to the authenticated user at every level (Job, Position, Contribution); cross-user access returns 404.
Tests on both DB engines, including cascade behavior and cross-user isolation at every nesting level.

Acceptance criteria

A user can build a full career history: multiple jobs, multiple positions per job, multiple contributions per position.
Cascading delete behavior is identical on both engines.
User A cannot see, modify, or delete User B's jobs, positions, or contributions — including via direct ID access at any nesting level.

Part of epic #4. Depends on #8, #10, #20.

Structurally the most complex item in the career domain. Three nested entities. ## Scope Data: - `Job`: company name, start date, end date (nullable for current). **Carries a `user_id` FK.** - `Position`: title, start date, end date (nullable), FK to Job. **`user_id` denormalized onto Position for queryability and isolation safety.** - `Contribution`: problem statement, value proposition, accomplishment measurement, FK to Position. **`user_id` denormalized here too.** UI: - Jobs list under Experience. - Drill into a Job to view/edit its positions. - Drill into a Position to view/edit its contributions. Backend: - Entities + migrations for all three. - Cascading deletes (deleting a Job removes its Positions and Contributions). Handle in app code if engines diverge on FK cascade behavior. - Full CRUD API + DTOs. **All queries scoped to the authenticated user at every level (Job, Position, Contribution); cross-user access returns 404.** - Tests on both DB engines, including cascade behavior **and cross-user isolation at every nesting level**. ## Acceptance criteria - [ ] A user can build a full career history: multiple jobs, multiple positions per job, multiple contributions per position. - [ ] Cascading delete behavior is identical on both engines. - [ ] User A cannot see, modify, or delete User B's jobs, positions, or contributions — including via direct ID access at any nesting level. Part of epic #4. Depends on #8, #10, #20.

james referenced this issue

2026-06-12 20:28:30 +00:00

Contracts feature #25

james added the

area:pwa

area:service

feature

labels

2026-06-12 20:32:11 +00:00

james referenced this issue from a commit

2026-06-20 14:35:10 +00:00

feat(service+pwa): jobs, positions, contributions — three-tier career history (#24)