The Field Hiring Calendar, Paced From Posting Counts to Your Search

Most job seekers apply at a flat rate all year because the advice they find names one generic peak and stops. This playbook is for anyone who wants to time their own search instead: pick your exact role and city, pull a 12-month posting curve, mark its real peaks and troughs, and schedule applications, networking, prep, and materials refreshes backward from how long an offer actually takes. By the end you will have a dated, month-by-month operating rhythm for your field, not a borrowed one.

Why the generic January peak is the wrong number

The widely repeated answer - search in January and February - measures applicant behavior, not employer demand. At the demand level the shape is different and better documented. An analysis averaging four years of federal JOLTS hires found the peak lands in May and June, with April through August well above the rest of the year, and December the single lowest month in every one of the four years averaged. The spring-summer peak runs about 1.6 times the December trough.

The mechanism explains the gap. Budgets that open in January take weeks to become postings, and postings take weeks to become hires. So the money approved at the start of the year starts producing actual hires from February through April and builds into the May-June peak. January looks busy because applicants pour in - one secondary source cites a 15% January bump in postings - but January draws the most applicants without a matching rise in openings. You can be busy and early at the same time.

This is the core move of the whole playbook: you are going to replace a borrowed month with a curve you pulled yourself, for your own occupation and metro, and then schedule against it with your field's real lead time.

What a hiring calendar is, and what goes in each layer

A hiring calendar is a 12-month map of when demand in your field rises and falls, with each search activity assigned to the window where it pays off most. It has four layers, and you build them from the outside in.

The demand curve is the foundation and the layer people get wrong most often. The other three are judgment applied on top of it. The reason to build all four rather than just reading a month off a listicle is that each layer corrects a different error: the curve corrects for the generic-peak myth, the lead-time offset corrects for applying too late, and the activity assignment corrects for spending your scarce high-competition weeks on slow relationship work.

The two free data sources, and which one lies about seasonality

Two primary sources can measure a role or location for free, and they fail in opposite ways. JOLTS is authoritative but coarse, reporting by industry rather than occupation. Indeed's Hiring Lab is granular down to metro and sector, but its public index is seasonally adjusted, which removes the exact signal a calendar needs.

JOLTS estimates are not seasonally adjusted and run monthly from December 2000 to the present, so the seasonal rise and fall is right there in the numbers. That is why it anchors the curve even though it cannot see your job title. The public Indeed index is set to 100 on February 1, 2020, uses a seven-day trailing average, and covers U.S. states and the largest metros plus occupational sectors. It is seasonally adjusted, so if you chart it you will get a smooth trend with the seasonality mathematically stripped out. To recover the seasonal pattern at metro granularity, pull raw counts from the Hiring Lab repository rather than the headline index.

So treat them as a pair: JOLTS for the trustworthy shape of the year, Indeed raw counts for your specific role and city, and the public Indeed index only for level and trend comparisons across places.

Build the calendar, step by step

This is the full procedure, start to finish. Each step names who does it, how long it takes, and what done looks like so you can run it without improvising.

The chart from step two is the artifact everything else hangs on. Below is the national JOLTS shape to calibrate against before you trust your own narrower pull.

These figures are averaged from federal JOLTS across 2022 to 2025. Notice that January already sits well below April and June, and that December is more than a third below the June peak. If your own curve looks nothing like this, that is a finding, not an error - your occupation may genuinely run on a different cycle, which is exactly what step four is for.

Set lead time and schedule backward

Lead time is the number of days from your first application to an accepted offer, and it is the hinge that can flip your optimal apply month. The 2025 median was 63.5 days, with small-to-medium companies at 83.5 and enterprises at 51.7. SHRM-sourced time-to-fill runs lower at about 44 days, up from 33 in 2021. Use 42 to 64 days as a baseline and adjust from there.

Level matters more than most people expect. Here is the median days from first application to offer by industry and level.

A senior government candidate and an entry-level retail candidate are running on calendars that differ by more than eleven weeks. That difference changes which month you apply and whether your offer lands in a strong or weak start month.

Lead time can invert your plan. Applying at a May peak with an 83.5-day small-company lead time pushes a start into the summer. That is fine if your field hires through August, but in a field that dips in June and July it means your offer arrives into a trough. Always run the clock backward from when you want to start, never forward from when postings look busy.

Assign each activity to its window

Activities split cleanly between peak months and lull months because they have different competition profiles. Applications are competitive and should land when requisitions are open and demand is high. Materials and networking are slow relationship tasks that pay off best in low-competition months when hiring managers and your network have more time.

The practitioner consensus maps to four moves across the year:

• Refresh materials in the lull, roughly November and December. Rewrite the resume, update the profile, and fix formatting while demand is low.
• Submit high-volume applications at the peak open, from January into the spring build. This is when reqs start opening against approved budgets.
• Target spring sector peaks, March through May. Push into fields whose own curve crests here.
• Hit fiscal peaks in September and October. Many organizations open a second wave of reqs in the fall.

This is reasoning rather than measured outcome, so treat it as load-bearing opinion and let your own pulled curve override it where they disagree. The principle underneath is stable: put slow work where competition is thin, and put volume where demand is open.

Jan [building]   -> High-volume applications open; interview prep active
Feb [rising]     -> Applications continue; follow up on January submissions
Mar [spring peak]-> Target spring sector roles; interviews cluster
Apr [peak]       -> Peak applications; schedule interviews tightly
May [peak]       -> Peak applications; expect fastest responses
Jun [peak]       -> Applications land; watch for summer dip ahead
Jul [dip]        -> Networking; informational conversations
Aug [dip]        -> Networking; research fall targets
Sep [fiscal peak]-> Second application wave; interview prep active
Oct [fiscal peak]-> Applications continue; close live loops
Nov [lull]       -> Refresh resume and profile; rebuild network
Dec [trough]     -> Materials polish; rest; queue January batch

Tailoring a resume to every posting during a peak-application month is where the time goes. Volume is unforgiving: the average number of applications per job rose to 257.6 in 2025 from 207.2 the year before, so a generic resume disappears. Refolk writes your resume from your own history and tailors it to each posting, which is what lets you run a peak-month batch without hand-editing every version. Save that leverage for the months your calendar marks as peak open.

How this goes wrong

The calendar fails in predictable ways, and each failure has a check you can run before it costs you a season. These are the ones worth guarding against.

• Trusting the generic January-February peak. A blog asserts Q1 is best; JOLTS hires actually peak May-June. Check your schedule against a not-seasonally-adjusted hires curve before committing to any month.
• Using seasonally adjusted data to build a seasonal calendar. The public Indeed index is seasonally adjusted, so it removes the signal you want by construction. Confirm you pulled raw or NSA counts, not the headline index.
• Confusing applicant activity with employer demand. January draws the most applicants without a matching rise in openings. Track openings and hires, not search traffic.
• Applying industry-level data to a narrow occupation. JOLTS reports by industry, not job title, so a nurse in one metro may not follow the broad healthcare curve. Pull metro plus occupation wherever you can.
• Ignoring lead time. Applying at the posting peak lands the offer six to nine weeks later, possibly into a trough start month. Subtract 42 to 64 days from your target start.
• Mistaking one year for a pattern. A single 12-month pull can reflect a layoff or boom year. Compare three or more years; JOLTS supports a series back to 2000.
• Treating campus timelines as experienced timelines. Finance interns are decided about 18 months out. An experienced hire using that calendar wastes a year.

The campus-versus-experienced trap deserves its own note because the timelines are so far apart. Investment banking summer 2028 internships were expected to open applications between December 2026 and January 2027, roughly 18 months before the internship starts, and candidates commit 12 to 18 months before their start dates. Experienced hiring, by contrast, moves in weeks. Segment by hire type before you schedule, or you will build one calendar from two incompatible clocks.

Size your field before you trust the timing

Timing advice that ignores how deep your applicant pool runs is half an answer. Two fields can share a peak month and still demand completely different strategies because one has far more competitors crowding the same window.

In Refolk's index of professional profiles, the United States holds 657,653 registered nurses against 352,540 software engineers, a 1.87x difference. A nurse and an engineer told to "apply in the spring peak" face very different odds because one is competing in a pool nearly twice as deep. Geography multiplies the effect: the U.S. software-engineer pool is 15.6 times Germany's in the same index, so a global calendar misreads local supply entirely. Size your specific pool and treat a deep one as a reason to start earlier, apply harder at peak, and lean more on networking in the lulls.

Seniority reshapes the pool too. Entry-level roles are about 46% of U.S. postings and senior roles about 14%, but software development skews to 69.3% senior postings. If you are a senior candidate in a field like that, you are competing for a larger share of a narrow, slow pipeline, which is another argument for starting the clock earlier than the baseline.

Keep the calendar current

A hiring calendar is a living document, not a one-time chart. Posting data shifts month to month, and the mid-September 2026 snapshot showed 60% of U.S. occupational sectors with Indeed postings above the pre-pandemic baseline, up from 51% in June - a nine-point move in a single quarter. A calendar built on a stale pull will point you at last season's peak.

Set the re-pull reminder for the first week of each month. When you re-pull, check two things: whether your peak and trough months have moved, and whether the overall level has risen or fallen enough to change how aggressively you apply. Then adjust the activity assignment for the months ahead. The discipline is the same every month - pull raw counts, re-mark the peaks, re-confirm your lead time still holds, and shift the task list if the curve moved. That standing loop is what turns a one-time chart into an operating rhythm you can run a whole search on.