InternshipDeadlines
I built InternshipDeadlines to keep an employer’s closing date and a student’s own target date from becoming the same field.
The deadline can be unknown
Employer deadlines can stay unknown. InternshipDeadlines keeps employer-posted dates, first detection, last verification and personal targets attached to their own meanings.
Acquisition, serving and notes have different jobs
The separate KING MAKER engine validates employer and applicant-tracking-system sources. A catalog release feeds Cloudflare D1, which serves the Next.js site through OpenNext and Workers. Validation runs before a release becomes the active catalog.
Stages, notes, next actions and personal target dates stay in the visitor’s browser. A confirmed closure can change a listing’s availability while its saved plan remains.
| Responsibility | Implementation |
|---|---|
| Public site | Next.js, React, TypeScript, Tailwind CSS |
| Catalog serving | Cloudflare Workers, OpenNext, D1 |
| Acquisition authority | Separate PostgreSQL-backed engine |
| Application plan | Browser-local state and backup/import |
From a listing to the next application
The directory, saved-plan page and preparation guides are public. A walkthrough follows a listing’s source and dates, then the application stage and next action. The résumé worksheet helps turn experience into a draft the student can edit.
A plan can move forward with an unknown deadline
Method & limits: availability follows the listing’s displayed source and verification dates. The public workflow demonstrates the product; student outcomes and conversion improvements have not been measured here.
I’d preserve an unknown employer deadline and let the student choose a target. Filling the empty field would make the interface simpler and the decision worse.