Content models as the contract
Strapi schemas define the fields available to the frontend. The jobs, applications, and profile collections keep those content responsibilities separate.
Full stack / Job platform
A job platform with job listings, candidate profiles, and applicant submissions, backed by a Strapi content API.
My role
Frontend & backend development
The Problem
Job seekers need clear job information and a consistent way to submit their details. A job platform also needs structured listings, candidate profiles, and application content that can be managed together.
The Solution
Job Junction pairs a Next.js interface with Strapi collections for jobs, profiles, and applications. Job information and applicant resume fields share a structured content layer; a live end-to-end recruitment flow has not yet been verified.
01 / Contribution
Built the frontend and Strapi backend, including content models for jobs, applications, candidate profiles, and supporting platform information.
02 / Capabilities
03 / Architecture
Responsibility map · Read alongside the implementation status above.
04 / Decisions
Strapi schemas define the fields available to the frontend. The jobs, applications, and profile collections keep those content responsibilities separate.
Applications model contact information alongside resume and cover-letter media. Profiles hold resume headlines and skills.
The checked-in configuration defaults to SQLite. Although it contains other database configuration branches, that does not establish a deployed PostgreSQL database.
05 / Validation
The frontend package identifies a Next.js/React application. Backend package and schema review confirms Strapi, TypeScript, and the listed content models. A running end-to-end deployment and production permissions have not been verified.
06 / References
Fields used for job listings.
Applicant contact and media fields.
SQLite is the default database client.
Next project