Internify centralises the ITS Batch 21 internship recruitment program: students browse the companies offered each round, apply, and manage their profiles and CVs, while admins manage the student roster (manually or via CSV import). I built front-end features — principally CV upload and management — on a group build; the Node/Express/PostgreSQL/AWS backend was the team's.
Internify - Intern Tracking System
Front-End Developer — Group Project
A React/Vite/TypeScript student recruitment portal for the ITS Batch 21 program, with a multi-round company application flow for students and a CSV-driven admin dashboard for managing the student roster.
Role & Context
Group project under the ITS-Development-Team org for the ITS Batch 21 internship recruitment program. I worked on the React/Vite/TypeScript front-end — my specific contribution was the CV upload and management features. The backend (Node.js/Express/PostgreSQL/AWS) was built by the team.
Problem
The recruitment program needed a central place for Batch 21 students to view the companies offered each round and submit applications, plus a way for admins to manage the roster — the admin CSV-import path indicates the prior bottleneck was manual, one-by-one entry of student records.
Approach & Architecture
Loading diagram…
Best Practices Followed
- Strict TypeScript across the project (strict mode plus unused-locals/params enforcement)
- Zero-warning lint gate (eslint --max-warnings 0) in the build scripts
- Feature-aligned folder layout: student (dashboard) vs admin UI separated, with widgets co-located per feature
- Mock-data abstraction (one module per entity) so the future swap to a real API is a one-file change per entity
- A single reusable drag-and-drop upload widget shared across avatar, cover, and CV uploads
- Bulk-import path (CSV via PapaParse) so admins onboard a roster instead of N manual form submissions
Challenges & Resolution
ChallengeCV and image uploads needed to work end-to-end in the prototype even though there is no file-storage backend yet.
FixUsed react-dropzone for drag-and-drop UX and FileReader.readAsDataURL to convert files to base64 for in-memory preview/storage, with a 50 MB client-side guard — structured so it can swap to presigned-URL uploads once storage is wired in.
ChallengeOnboarding a whole batch one form at a time wouldn't scale, but admins still needed to fix single records.
FixA dual-path Add Student flow — manual entry plus bulk CSV ingest (PapaParse) — both feeding the same admin table.
Outcomes
- Front-end shipped: a multi-round company application page (filter by round / role / apply-limit), a student profile editor (avatar + cover upload), and an admin manage-student table (search, edit/delete, add via manual form or CSV)
- My contribution: the CV upload and management features (drag-and-drop, base64 preview, 50 MB guard)
- Two merged feature PRs (epic/application-round, feature/student-profile) under the team org
Tech Stack
TypeScriptReactViteMaterial TailwindMUIReact RouterPapaParsereact-dropzoneNode.jsExpress.jsPostgreSQLAWS
Concepts & Skills Learnt
React 18 with TypeScript (strict mode)Vite build tooling & HMR workflowSPA routing with react-router-dom v6 (nested routes, layouts)Tailwind CSS utility-first stylingMaterial Tailwind + MUI component compositionReact Context + useReducer for global UI stateDrag-and-drop file upload UX (react-dropzone)Client-side CSV ingestion (PapaParse)Browser FileReader API & base64 DataURL handlingFeature-based folder architecture & component reuseESLint + TypeScript strict-mode quality gatingGit feature-branch + PR workflow under a team org