The short version
For a new graduate, the single biggest lever in a tech job search is not your resume, your projects, or your coding speed. It is timing. Most early-career software roles open in a predictable window each year, fill on a first-come basis, and quietly close long before any printed deadline. A strong candidate who applies two months late is competing for the scraps of a pool that a weaker candidate emptied on day one.
TL;DR: Find out when the season opens in your region and apply in the first week it does. In the United States, large-employer new grad roles cluster from late summer through October for the following year, with a thinner second round in the new year. In the United Kingdom, graduate schemes open in September and October and mostly close before Christmas. In India, campus placement season peaks from roughly July to October, with the highest-paying companies slotted first. Everywhere else, assume the same shape: rolling, early, and gone before the deadline. Have your resume, one portfolio project, and a data-structures baseline ready before the portals open, because the season does not wait for you to catch up.
Why the calendar filters harder than your resume
New grad hiring runs almost entirely on rolling review. There is no fixed date when every application is read together and the best rise to the top. Instead the portal opens, applications are read as they arrive, interviews run continuously, and slots disappear as offers go out. The Microsoft new graduate software program, for example, runs its primary application window from August through October for roles the following year, with a smaller round in January through March once returning interns have already converted to full-time and taken many of the seats (Simplify). Apply in August and you compete for the full set of openings. Apply in November and you compete for whatever is left.
The application that arrives in week one competes for the whole pool. The identical application in week eight competes for whatever is left.
This is why the usual advice to "polish your resume until it is perfect" gets the priorities backwards for a new grad. A resume that is good enough and submitted early beats a flawless one submitted late, because the late one is aimed at a pool that has already shrunk. The perfectionism is not free. Every week you spend refining is a week the early cohort spends interviewing.
The practical read: treat the opening date as a hard start line. Know it in advance, and be ready to move the day it arrives rather than the week you finally feel prepared.
When the season actually runs, by region
There is no one global calendar, and this is exactly where generic timeline articles fail international readers. Pay, formats, and deadlines differ, so treat the table below as the shape of each region and confirm the specific dates on each employer's early-careers page.
| Region | Main window opens | Effectively closes | The mechanic that catches people out |
|---|---|---|---|
| United States (large employers) | Late summer, roughly August | October, then a thin round in January to March | Rolling headcount; seats fill as interns convert, so day-one applicants see far more openings |
| United Kingdom (graduate schemes) | September and October | November and December, before Christmas | Assessed first-come; many close once the right people are found, not on the printed date |
| India (campus placements) | July to October peak | December, then off-cycle drives into spring | One Day One offer per student, decided in the first 24 to 48 hours of a company's slot |
| Rest of world / off-campus | Employer specific | Employer specific | No formal scheme, but the same rolling, apply-early pattern still holds |
In the United States, the season is front-loaded and rolling. Postings for the following year start appearing in the summer, the bulk of decisions happen through the autumn, and a lighter clean-up round runs early in the new year for headcount that returning interns did not fill (Simplify). Compensation varies enormously by company tier and city, so research a specific number for each target rather than assuming a national figure.
In the United Kingdom, most formal graduate schemes open for applications in September and October of your final year, and employers set deadlines in November and December because they want to send offers in the spring for a September start (targetjobs). Two details trip people up. First, banking and finance schemes open earlier, often in August and closing as early as October. Second, the printed deadline is frequently a fiction: top firms assess as applications arrive and close the moment they find enough strong candidates, and around 70 percent of top employers either recruit year-round or reopen roles later, so an early miss is not always fatal (Handshake).
In India, the calendar is set by your college placement cell rather than by each employer. The peak runs from roughly July to October, with Day Zero and Day One reserved for product companies offering the highest packages, while mass recruiters such as TCS, Infosys, Wipro, and Cognizant run national-level tests across the same window; mid-range companies and pool drives follow in November and December, and startups keep hiring into the new year (Claspire). The on-campus process itself is standardised: a pre-placement talk, an aptitude or online assessment as the first cut, technical rounds, then an HR round, usually gated behind a minimum CGPA of about 6.0 to 7.5 with no active backlogs (Placement Preparation). Because you can hold only one Day One offer, the first two days of your placement season are the highest-stakes hours of the year.
Everywhere else, and for anyone applying off-campus or across borders, there is no scheme to anchor to, so the rule is simpler: check each company's early-careers page directly, and assume the rolling, apply-early pattern until you learn otherwise.
Backwards-planning your application runway
Once you know your opening date, plan backwards from it. The goal is not to send the most applications; it is to send enough well-prepared ones before the early pool drains. A tailored application (a resume matched to the posting, a short referral note, and a tracked follow-up) takes real time, and untailored spray does little to move the odds.
Consider Leah, a final-year computer science student aiming at a summer start. The season's peak is eight weeks out. She can protect about six focused hours a week around her coursework, and she has drawn up a list of forty target companies. The temptation is to open forty tabs and start pasting. Instead she runs the numbers first.
// Estimate how many well-prepared applications you can realistically send before
// the season's early pool drains, and whether that clears your target list.
// A "quality" application (tailored resume, a referral note, a tracked follow-up)
// takes about 1.5 hours; padding the list with untailored submissions does not
// move the odds, so plan around quality throughput, not raw volume.
function seasonPlan({ weeksToPeak, hoursPerWeek, targetCompanies, hoursPerApp = 1.5 }) {
const capacity = Math.floor((weeksToPeak * hoursPerWeek) / hoursPerApp);
const covered = capacity >= targetCompanies;
return {
capacity,
shortfall: covered ? 0 : targetCompanies - capacity,
verdict: covered
? "list fits the runway, so protect quality over volume"
: "trim the list or add hours before the early pool drains",
};
}
seasonPlan({ weeksToPeak: 8, hoursPerWeek: 6, targetCompanies: 40 });
// -> { capacity: 32, shortfall: 8, verdict: "trim the list or add hours before the early pool drains" }The calculator tells Leah she has room for about thirty-two quality applications, eight short of her list. That is a useful reality check, not a failure. She cuts the list to roughly thirty companies in two tiers, ten reach targets and twenty realistic ones, and she starts referral outreach in week one instead of week five. When you run this against your own numbers and the answer is a shortfall, the fix is the same: shorten the list or free up hours, but do it before the season opens, not after you are already behind.
What to have ready before the portals open
The season rewards readiness, not scrambling. These are the assets that should exist before you submit a single application, because building them mid-season steals hours from applying and interviewing.
| Asset | Ready state | Why it has to exist first |
|---|---|---|
| Base resume | One page, quantified bullets, tailorable in minutes per role | You will submit dozens; per-application editing has to be fast |
| One portfolio project | Deployed or demoable, with a clear README and your specific role in it | It is the concrete evidence a new grad without work history can point to |
| Data-structures baseline | Comfortable with the core patterns, not cramming from zero | Online assessments arrive within days of applying |
| Referral list | Named contacts and alumni you can message in week one | Referrals are the single biggest boost to a new grad application |
| Application tracker | A simple sheet: company, date applied, stage, next action | Rolling processes move fast; an untracked pipeline leaks follow-ups |
Two of these deserve most of your pre-season effort. Build a single project you can talk about in depth rather than five shallow ones, and make its story legible to a reviewer; our guide on a GitHub portfolio for engineering interviews covers what a reviewer actually looks for. And get your algorithms baseline in place before applications open, because the first online assessment often lands within a week of your submission. A structured plan beats random grinding here, which is what our data-structures study plan is for.
The prep timeline: the eight weeks before day one
If the season is eight weeks out, the point is not to peak on the opening date but to be steady and ready by it. A workable shape looks like this.
| Weeks out | Focus | Concrete output |
|---|---|---|
| 8 to 6 | Foundations | Resume finalised, portfolio project deployed, tracker built |
| 6 to 4 | Algorithms baseline | Two or three practice problems a week across the core patterns |
| 4 to 2 | Target list and referrals | Tiered list set, referral messages drafted, company research started |
| 2 to 0 | Dress rehearsal | Mock behavioral answers, one timed assessment, applications queued to send on opening day |
Notice that applications go out at the end, not the start. The weeks before are for building the things that make each application fast and each interview survivable. Once interviews actually land, the intensity shifts, and a tighter, dedicated crunch plan such as our four-week interview preparation timeline takes over from this pre-season build.
The one thing not to defer is money research. Early-career pay ranges vary widely by company and by city, and offers can arrive fast in a rolling season, so know your numbers before you need them. Our guide on researching salary ranges before an interview walks through how to find a real, region-specific figure rather than a headline national average.
Where new grads quietly lose the season
Most lost seasons do not come from failing interviews. They come from calendar mistakes made weeks earlier.
- Waiting to feel ready. The cohort that applied on day one is interviewing while you polish. Ready enough and early beats perfect and late.
- Applying to everything untailored. A hundred generic submissions convert worse than thirty tailored ones with referrals. Volume is not a strategy when reviewers read for fit.
- Ignoring the region you are actually in. Assuming a United States fall calendar when you are applying to United Kingdom schemes, or the reverse, means missing the window entirely. Confirm the dates where you are.
- Skipping referrals. For a candidate with no work history, a warm introduction is the strongest signal you can add, and it costs one message sent in week one.
- No tracker. Rolling processes fire off assessments and interview invites quickly. Without a simple record of who is at what stage, follow-ups slip and stages time out.
- Refusing an early offer while gambling on a later round. In regions with an exploding-offer culture, this can leave you with nothing. Weigh a real offer against a hypothetical one honestly.
Fix these and you have already beaten most of your cohort, because you are competing on preparation and timing rather than on luck.
FAQ
When should a new grad start applying for software jobs? As soon as postings open for your region and start date, which for United States roles usually means late summer for the following year, and for United Kingdom schemes means September and October of your final year. Working backwards, your resume and one portfolio project should be ready one to two months before that.
Is it too late to apply if the season already started? Not necessarily, but move now. Early is best, yet many employers reopen roles or run later rounds, and a large share of top employers recruit year-round rather than in one closed window. Apply immediately to anything still open, and widen to smaller companies and startups, which hire on longer, looser timelines.
Do I need an internship to get a new grad offer? It helps, because many full-time seats are filled by returning interns, but it is not required. If you do not have one, lean harder on a strong portfolio project, referrals, and applying the moment the season opens, since the roles left for non-returners go fastest.
How many companies should I apply to? Plan around how many quality applications you can actually prepare, not a round number. Run the capacity check above; a tiered list of twenty to thirty companies with tailored applications and referrals usually beats a hundred generic submissions.
What if I graduate off-cycle, in December or mid-year? Apply into the main season that precedes your availability and be explicit about your start date. Off-cycle graduates often do well in the smaller new-year round and with startups, which care less about a synchronised class start.
Do smaller companies and startups follow the same calendar? Less strictly. Large employers drive the fall peak, but startups and smaller firms hire when they have a need, often three to six months before a start date and year-round. They are a good second wave if you miss an early large-employer deadline.
Should I accept an early offer or wait for a later round? Weigh the real offer against the odds and timeline of the ones you are waiting on, and check whether the offer has a hard expiry. In a rolling market, a solid offer in hand is worth a great deal, and later rounds are thinner than the first.
Where to go next
- GitHub portfolio for engineering interviews to build the one project that carries a new grad application.
- Data-structures study plan for interviews to get your algorithms baseline ready before the first assessment lands.
- Four-week interview preparation timeline for the crunch once interviews actually start arriving.
- Researching salary ranges before an interview so a fast offer never catches you without a number.