Finding an internship should not require rebuilding the same spreadsheet every time a new recruiting cycle opens.
01 / The problem
The work starts after search.
A promising job title is only the beginning. A student still has to work out whether the role fits, what the employer requires, when to apply, and which details need another check. Those decisions usually get scattered across tabs, saved links, and notes.
I built InternshipDeadlines around that whole sequence, rather than treating a larger list of links as the finished product. The site brings discovery, shortlisting, comparison, deadlines, and preparation resources into one place.
Find. Start with role, company, or location. Narrow the field before reading every posting.
Compare. Bring requirements, work, location, and offer terms into the same decision.
Act. Keep a shortlist and next step. Check the employer’s current posting before applying.
Product workflow study. The panels explain the experience; they are not live employer records.
02 / The work
Give each decision a place.
Search and filters help students narrow the field. Saved roles and notes preserve the shortlist in the browser. Comparison puts options beside one another. Published deadlines and calendar feeds help turn a promising role into a next action.
The editorial layer answers questions that a listing alone cannot: how to interpret a rolling process, compare the work behind similar titles, and use existing experience in an application. My work spans product direction, the student interface, content operations, and the systems that keep those surfaces useful.
03 / The judgment
Do not manufacture certainty.
A collected posting is not automatically an open vacancy. A missing deadline is not permission to invent urgency. The product has to keep those distinctions visible, even when a cleaner-looking interface would be easier to build.
The next measure of quality is whether a student can make a better decision with less repeated research. Listing volume alone does not answer that question.
04 / Decisions
What I chose.
And why.
- A workflow, not just a directory
- Search, saved roles, comparison, and planning support different stages of the same decision.
- Unknown deadlines stay unknown
- Source gaps should prompt a check, not become invented application dates.
- Local shortlist storage
- The current product keeps saved roles and private notes in the student’s browser.
05 / Result
What came out of it.
A live student-facing product with searchable postings, comparison, saved roles, deadline views, calendar feeds, and application guides.
Status & source notes
The public product demonstrates the workflow, not independently verified vacancy coverage, placement results, or traffic growth. The separately documented Internship Aggregator Engine is an engineering project; this case does not claim it is the deployed backend.
Case study updated September 12, 2026.