The week after you submit is when searches stall. The application is in. The relief is real. Nothing on your list moves, because you are waiting to feel whether that one employer liked you. They have not decided, and your other postings do not pause for their decision.
A public thread on r/cscareerquestions shows the expensive version of waiting. After an internship interview that seemed to go well, the student followed up at two weeks, was told to expect a reply within 10 days, then heard nothing after that window. The portal still said interviewing. Summer was close enough that a local job had to be accepted or declined. A date you were given is the only schedule you control, and the rest of your life should not sit inside an unanswered email.
CareerOneStop tells applicants to send the materials a posting asks for, soon after it is posted, and then to keep using more than one search method. It says networking is still how a lot of resumes reach a hiring manager. A week with only one submitted form and no other action is a week that ignored that advice. NACE’s Job Outlook 2026 Spring Update adds a calendar fact: 37% of full-time college recruiting and 27% of intern recruiting, in that spring survey, is happening in the spring. A fall application that goes quiet means you still need a next task. Spring recruiting is still on the calendar.
The tracker for this week
Make a list with six columns: role, date applied, documents you sent, date they said they would reply, your one follow-up date, and next action. If you applied to three roles, you have three rows. Do not build a color-coded system you will abandon. A plain note is enough if you will open it.
Fill the documents column from the confirmation screen. Resume, portfolio link, transcript, nothing else. CareerOneStop says to send only what was requested. If you sent extra, note that too, so you do not wonder later whether the writing sample actually went.
If nobody gave you a reply date, set the follow-up for seven days after an interview or fourteen days after a form with no interview. Put that date in the column now, while you remember the submission. When the date arrives, send one note or do not. Do not keep the row in your head.
The rest of the week, scheduled
Give the fresh application one block of time and give every other day a different block.
Day one: confirm the files you sent opened the way you think. Save the confirmation email. Write the row.
Day two: pick the next posting and do the two-column check, their phrases against your real facts. If the gaps are too large, drop it the same day and pick another. Do not spend day two “researching the company” with no draft.
Day three: finish one proof line you can reuse. A project sentence, a campus-job sentence, a club-task sentence. NACE says employers want an example of a skill used on a problem. Day three is for writing that example while you are not panicking in an interview.
Day four: send one note to a person who has seen you work, about one specific role, or send nothing if you have no such person yet. Do not spend day four on a blast of connection requests.
Day five: if a follow-up date from an older row is due, send the four-line note and stop. If no date is due, apply to the posting you checked on day two, if it survived the gap check.
The weekend is for the course work you are already graded on. A search that eats the problem set creates a new problem in the major that the search is supposed to serve.
Close rows on purpose
A row closes when you get a written rejection, when you accept another offer, or when your follow-up date passes with no answer and you decide the role will not run your calendar. Closing a row keeps the list short enough to act on. You can reopen it if they write later. The thread’s student needed a local job decision. A closed row would have made that decision about the local job.
If they do write and ask for a time, answer the same day with two or three options. Speed on a real reply matters more than speed on a tenth cold application. Put the interview on the sheet you will use to practice, and stop adding new rows until that interview’s prep is done. One live conversation outranks five new forms.
Example
Example. You applied to a coordinator role on Monday and a lab assistant role on Tuesday. Monday’s posting said they review applications for two weeks. You set a follow-up for the Monday after next. Tuesday’s posting said nothing, so you set a follow-up for two weeks out and, on Wednesday, you write the five-line version of your methods project because both postings asked for a writing sample you can now attach to the next application. You do not refresh either portal on Thursday. On Friday you send a short note to the supervisor who saw the project, with the coordinator link, and you stop at one ask.
How Flightpath helps
You pin a posting, see gaps against confirmed facts, and track a role from saved to applied to interview to offer. Flightpath suggests a person from public contacts, or gives you a search link, and drafts the follow-up you approve. It does not send the email. You still decide what gets sent. A role you are not eligible for is labeled and is not ranked above one you can take, so day two’s gap check includes eligibility and not only skills.