GCE Placify
A clearer path from opening to application.
GCE Placify is a college placement portal built around student profiles, job postings and applications. My project work included authentication, Neon-backed data and eligibility-based application flows; the public repository contains the backend. The backend represents criteria such as CGPA, department, graduation year and arrears alongside student and administrator roles. Applications have their own review state, making the project a practical exercise in turning a college workflow into explicit data and API behavior.
- MY ROLE
- Developer - placement portal
- PROJECT STATUS
- College project
- BUILT WITH
- JavaScript / Node.js / Neon / PostgreSQL / REST APIs
A problem
worth exploring.
A placement process has several moving parts: students need relevant openings, each opening has eligibility criteria, and administrators need to review applications. Those rules need a shared structure rather than being scattered across messages.
A concrete placement workflow covering job management, student applications and administrative review, with public backend code available to explain the implementation and its trade-offs.
How I approached it
- Represent job requirements and academic eligibility criteria in a relational data model backed by Neon.
- Separate student and administrator actions through authentication and role-aware backend routes.
- Model application submission, administrative approval and withdrawal as distinct parts of the workflow.
What I took away
- Permissions, eligibility and approval state answer different questions and should not be treated as one check.
- A useful backend model follows the real process closely enough that its rules can be discussed with the people using it.