How to Track Developer Internship Applications Without Losing Your Mind

Around application twenty, something predictable happens. You cannot remember whether you applied to a company, you send a follow-up to someone who already replied, and you miss a deadline for the one role you actually wanted.

This is not a discipline problem. It is a data problem, and it takes about twenty minutes to solve.

Why it falls apart

Applications are scattered across systems that do not talk to each other. Some go through university portals, some through company sites, some through Greenhouse or Workday, some by email to a person. Each has its own account, its own status vocabulary and its own notification behaviour, and several send you nothing at all.

Your email inbox is not a tracker. Confirmation emails get buried, rejections arrive from no-reply addresses that sort strangely, and a third of applications produce no email whatsoever.

What to record

A spreadsheet is genuinely fine. Notion is fine. A markdown file is fine. What matters is that it is one place and that it has these columns:

Column	Why it earns its place
Company	Obvious
Role	You will apply to two roles at the same company
Link	The posting, so you can re-read it before an interview
Date applied	Drives follow-up timing
Source	Where you found it — this is the column that pays off later
CV version	Which CV you sent, if you tailor them
Status	Applied / Screening / Interview / Offer / Rejected / No response
Next action	The single most useful column
Next action date	When to do it
Notes	Names, questions asked, anything the interviewer mentioned

Next action is the one that changes how the process feels. Without it you have a list of things that happened. With it you have a list of things to do, and you can open it each morning, filter to today, and act.

The follow-up rhythm

Most students either never follow up or follow up immediately and then never again. Neither works.

• 7 days after applying: nothing. Applications sit for a week as a matter of course.
• 10–14 days: if there is a named contact and no response, one short follow-up. Two sentences, reiterating interest, offering to answer anything.
• After an interview: a short thank-you within 24 hours, mentioning one specific thing from the conversation.
• After a rejection: if you got to an interview, ask once for feedback. Roughly one in four will give it, and that feedback is worth more than the interview was.
• No response after 30 days: mark it closed and stop thinking about it.

That last one matters more than it sounds. Applications that stay in an ambiguous state occupy attention. Closing them deliberately frees it.

What the data tells you after 20 applications

This is the real reason to track, and it is why the Source and Status columns matter.

Response rate under 10%. The problem is upstream of your interviews — it is the CV, the portfolio, or the roles you are applying to. If you are applying to roles asking for three years of experience, that is the finding.

Good response rate, no first-round passes. The CV is over-promising relative to what the portfolio shows, or your project explanations are not landing. This is usually fixable by writing the two-minute walkthroughs and saying them out loud.

Passing first rounds, failing technical. The portfolio is doing its job. The gap is interview practice, which is a different problem with different solutions.

One source producing most of your responses. Very common, and very actionable. If university-portal roles reply and cold applications through job boards do not, put your time where the replies are.

You cannot see any of this without a record. Twenty rows of data will tell you more about what to fix than another week of tweaking your CV.

Applying to fewer things, better

The instinct when responses are slow is to apply to more. Usually the correct move is the opposite.

A tailored application — where you have read the posting, adjusted your CV's top section to match, and mentioned something specific about what the company builds — takes about twenty minutes and converts several times better than a generic one that takes two.

The practical compromise: keep one strong base CV, and spend fifteen minutes per application adjusting the summary line and reordering the projects so the most relevant one is first. That is not "tailoring" in the exhausting sense. It is making sure the first thing they read is the thing they care about.

The things people forget

Record where you found it. Six weeks later you will want to know which channel works, and you will not remember.

Save the job posting text, not just the link. Postings get taken down. If you get an interview in three weeks, you will want to re-read the requirements, and the link will 404.

Note the interviewer's name and one thing they said. It makes the thank-you email specific, and if you reach a later round with the same company it is genuinely useful.

Set a weekly review. Twenty minutes on a Sunday: update statuses, clear the follow-ups due, close the dead ones. Without a fixed slot the tracker rots, and a rotten tracker is worse than none because you stop trusting it.

Build it yourself, if you want

This is one of the better beginner portfolio projects precisely because you will use it while job hunting, which means it gets finished and refined.

Core: add applications with company, role, link, date and status; a pipeline view grouped by stage; reminders for follow-ups; notes and contacts; search across everything. Stretch: parse a posting URL to prefill the fields, statistics on response rate and stage conversion, a browser extension to save a posting in one click.

It also gives an interviewer an easy and genuine question, and "I built this because I was losing track of my own applications" is a good answer.

The short version

One place. Ten columns. A next action on every row. Twenty minutes a week to maintain it.

That is the whole system, and it converts a process that feels like chaos into a list you can work through — which is mostly what you need, because the applications you send this month are worth more than the polish you would have added instead.

The application tracker is included in Developer Portfolio Builder, and the free toolkit has the final audit to run before you send the first one.