All work

/03 · Full-stack / Job marketplace · 2026

CareerBridge

A job application is a workflow, not just a form.

MY ROLE

Full-stack development · Personal project

STATUS

v1.0 local release · Source available

CAREERBRIDGEWORKFLOW STUDY / 03
The next
step forward.
DiscoverApplyTrack
IMPLEMENTATION DIAGRAMSEEKERS ↔ EMPLOYERS
Architecture visualization drawn from the implementation.

Two roles. One connected workflow.

Candidates need to find suitable jobs and follow what happens after applying. Employers need to manage listings and applicants. These overlapping workflows require both role permissions and ownership checks.

I built a Next.js interface backed by a Fastify API, PostgreSQL, and Redis. The release covers job discovery, saved jobs, applications, employer management, and in-app alerts, with integration tests around the API.

How the pieces fit.

  1. 01Next.jsCandidate & employer interfaces
  2. 02FastifyValidation · Sessions · Ownership
  3. 03PostgreSQL + RedisPersistent records · Public-list cache
Next.jsTypeScriptFastifyPostgreSQLRedisVitest

Job discovery

Search, sorting, pagination, and location, job-type, and salary filters help candidates find relevant listings.

Applications with a history

Candidates can apply and follow status changes. Employers can review applicants and update the status of applications to their own jobs.

Employer workflows

Company management, job publishing, closing listings, and optional salary ranges live alongside applicant management.

Saved jobs & in-app alerts

Candidates can save listings and configure job alerts. Notifications stay inside the application; the project does not include email delivery.

01

Check ownership as well as roles.

Being an employer does not imply access to every company or application. The API enforces resource ownership alongside role permissions and input validation.

02

Cache selectively, accept a small delay.

Public job-list results are cached in Redis for roughly 20 seconds. That reduces repeated reads, with the explicit tradeoff that an edited listing may take a short time to appear in search.

03

Make the release scope explicit.

The v1.0 release is locally runnable, with migrations, Docker Compose, and API CI. Public hosting would need a separate operational and security review.

What’s there today.

The v1.0 release documents 79 passing API tests and successful API and web builds at release time. The source is available to inspect and run locally; there is no public live demo.