Skip to main content

Original research

Tech Hiring Report

We watched 25,608 tech job postings from 1,681 companies between June 20, 2026 and October 22, 2026. This is what the data says about how long a posting stays open, who discloses pay, and which skills employers ask for.

By Sam K., Founder of InterviewChamp.AI · Updated October 22, 2026 · Free to cite with attribution

14.2%
Of 5,783 postings watched 60 days: gone within 7 days
47.2%
Of 5,783 postings watched 60 days: still open after 60 days
23.4%
Of postings are remote
62.6%
Disclose a salary figure

Quick answers

How long do tech job postings stay open?

Of the 5,783 postings we first saw at least 60 days earlier, 14.2% were gone within 7 days, 34.1% within 30 days and 52.8% within 60 days. That leaves 47.2% still open after 60 days. Remote postings leave sooner: 27.2% were gone within 7 days, against 10.5% of on-site ones. If a role interests you, apply within days, not weeks.

What share of tech job postings are ghost jobs?

No one can measure that exactly, because a posting doesn't show whether the company is really hiring. What we can measure is age: our ghost jobs study tracked 25,608 tech postings, June 20, 2026 to October 22, 2026. Of the 5,783 we first saw at least 60 days earlier, 47.2% were still open after 60 days.

Read the ghost jobs study

Where can I browse tech jobs without creating an account?

On InterviewChamp's jobs board: live engineering jobs in the US or remote, with senior titles left out, taken from companies' own hiring systems. You can browse, filter and open the job on the employer's own hiring page without an account.

Browse the jobs board

How long a posting stays open

Job-search advice usually treats a posting as a standing invitation. That is true for some and not for others. We took the 5,783 postings we first saw at least 60 days before October 22, 2026, found within two days of the publish date their job board gave, and checked how many were gone by day 7, day 30 and day 60. 14.2% were gone within 7 days, 34.1% within 30 days and 52.8% within 60 days.

That leaves 47.2% still open after 60 days. A posting that is still open counts as open here, it is not left out. Earlier versions of this page showed the median age of postings we had seen close. That number skipped every posting still up, so it made postings look shorter-lived than they are, and we no longer publish it. If you save roles to apply to later, expect about 14.2% of that list to be gone within 7 days.

Age alone does not show that a company has stopped hiring. Our ghost jobs analysis uses this same count and explains what it can and cannot tell you.

Within 7 days
14.2%
Within 30 days
34.1%
Within 60 days
52.8%

Cumulative share of 5,783 postings gone by that day, counted from our first sighting. "Gone" means the posting was no longer on the employer's careers page when we re-checked it.

Remote is one in four. Hybrid barely exists.

Hybrid work dominates the discussion but not the listings. Only 4.2% of postings were labelled hybrid, against 23.4% fully remote and 72.4% on-site.

One caveat worth stating plainly: this reflects how employers label a role in their applicant tracking system, not how the job is actually worked. A large share of roles tagged on-site are hybrid in practice; employers simply have no incentive to say so in the posting.

On-site
72.4% · 18,530
Remote
23.4% · 5,997
Hybrid
4.2% · 1,081

Remote postings leave sooner

The work-model split matters more for timing than for anything else we measured. 27.2% of remote postings were gone within 7 days, against 10.5% of on-site ones. After 60 days, 35.0% of remote postings were still open, against 50.8% of on-site ones.

If you are filtering for remote, the practical read is that a remote posting you find today is more likely to be gone by the end of the week than an on-site one.

On-site
10.5% in 7d · 50.8% open at 60d
Remote
27.2% in 7d · 35.0% open at 60d
Hybrid
12.0% in 7d · 47.0% open at 60d

Bar length is the share gone within 7 days. Hybrid's sample (166 postings) is small enough that we would not lean on it.

Remote roles disclose pay less often than on-site ones

62.6% of postings included at least one salary figure, and 53.1% published a full range. Across postings that disclosed a band, the median ran from $135,000 to $185,000.

The counterintuitive part is where disclosure happens. Remote roles disclosed pay in only 48.1% of postings, against 67.0% of on-site ones — a gap of 19 points, in the opposite direction from what remote-work transparency norms would predict.

The likeliest explanation is regulatory rather than cultural. US pay-transparency laws attach to a job's location, so an on-site role in a covered state is unambiguously in scope while a "remote" role is easier to leave unlabelled. We can measure the gap; we cannot prove the cause from this data.

On-site
67.0%
Remote
48.1%
Hybrid
67.1%

Share of postings in each work model that disclosed at least one salary figure.

What the skills pay, and which ones get you remote

Python leads on demand, mentioned in 37.2% of postings — roughly 3× the next-most-common technology. But demand and pay are not the same list.

On advertised pay, the spread across the skills we track is about $30,000. Postings mentioning Machine learning advertise a median floor of $160,000, against $130,000 for Docker. We ran the same comparison inside remote and on-site postings separately before publishing this, and the ordering held in both — so it is not simply a reflection of where the work happens, though that check is not itself in the table below.

Remote availability splits even harder, and along a different line. Google Cloud postings are remote 41.5% of the time against 10.8% for C++ — front-end and web skills cluster at the top, systems and hardware-adjacent ones at the bottom, against a site-wide baseline of 23.4%.

SkillMentioned inMedian advertised bandRemote
Machine learning11.7%$160,000 – $229,00033.7%
TypeScript10.3%$150,000 – $220,00037.2%
Google Cloud8.7%$150,000 – $202,40041.5%
Go1.4%$150,000 – $200,00028.2%
Kubernetes9.6%$148,000 – $213,60029.0%
Terraform5.5%$146,000 – $203,40041.5%
AWS13.2%$145,000 – $200,00031.6%
React9.0%$145,000 – $200,00040.0%
Python37.2%$140,000 – $196,75025.3%
C++12.0%$140,000 – $195,00010.8%
Azure7.7%$140,000 – $187,30036.6%
CI/CD11.1%$135,000 – $188,00027.5%
Java6.8%$135,000 – $192,00022.4%
JavaScript7.3%$134,437 – $182,45038.2%
SQL10.7%$130,000 – $178,00034.8%
Docker7.4%$130,000 – $190,00023.0%

Read this as a description of postings, not as a return on learning a skill. A posting mentioning machine learning is usually a different job from one mentioning SQL, and we cannot separate the skill from the seniority and role type that travel with it. Mention rate is measured over every scanned posting; pay and remote share are measured within the postings that mention the skill. Skills with fewer than 150 such postings are omitted from this table. A posting can mention several skills, so shares do not sum to 100%.

Two cities, the same employers, three times the jobs

Ranking cities by job count is misleading, because one large employer's campus outranks an entire metro. So we counted distinct companies hiring instead, which is closer to what a job seeker is actually shopping in — and then looked at how many roles each of those employers posts.

That second number is where it gets interesting. Washington DC and Chicago have almost the same number of employers hiring (86 and 88), but Washington DC carries 4× as many open roles. Its market is a handful of large employers hiring in volume; Chicago's is spread thinly across many.

Neither shape is simply better, and it is worth being clear about that: a low postings-per-company number means demand is distributed rather than dependent on a few employers, but it can equally mean the market is small. San Diego has the lowest concentration on this table and also the fewest openings on it. Read the two columns together, never the ratio alone.

MetroCompanies hiringPostingsPer companyRemote
San Francisco Bay Area5205,44310.518.5%
New York City2591,3455.219.4%
Los Angeles1051,45313.82.4%
Boston1005655.714.2%
Seattle988789.06.2%
Chicago883534.07.6%
Washington DC861,25214.63.6%
Austin7996312.24.0%
Atlanta592083.513.0%
Denver582414.29.1%
San Diego361333.79.0%

Metro grouping is hand-curated over free-text locations (2,586 distinct spellings), so it is approximate and deliberately conservative — city names that are ambiguous carry their state (a bare "New York" matches the state and drags in Buffalo; a bare "Austin" matches Austintown, Ohio), locations we could not confidently place are left out entirely rather than guessed at, and metros below 25 companies are not ranked. A posting open in several cities counts in each of them, which is right for "is anyone hiring near me" but means these rows overlap and do not sum to the total.

Methodology

Every figure comes from postings we ingested directly from employer applicant tracking systems, not from a third-party aggregator. We record each posting when we first see it and re-check it on a schedule, so "time open" is measured by observation rather than by a stated closing date.

  • Sample: 25,608 postings from 1,681 companies, collected June 20, 2026 to October 22, 2026, from the employers we were tracking on 4 September 2026 (later postings pass the same rule: engineering roles in the US or remote, senior titles left out). 11,459 were still open at the time of writing and 14,149 had closed.
  • Lifespan: measured on one group of 5,783 postings: those we first saw between June 20, 2026 and August 23, 2026, at least 60 days before October 22, 2026, and within two days of the publish date their job board gave. Every one of them was watched for the full 60 days. A posting counts as gone when it is no longer on the employer's careers page at our re-check; its last day open is the last time we saw it live. A posting still open counts as open, so the shares are of all 5,783, not only of the ones that closed.
  • What we leave out of lifespan, and why: a posting's age only means something if we saw it close to the day it appeared. 13,121 tracked postings are not in the group because the employer published them more than two days before we stored them, or gave no publish date. Most are postings that were already open when we first loaded an employer's board, so their start date is the day we loaded them, not the day they went up. Population figures (work model, pay disclosure, skills) are unaffected and use the full sample, because those are attributes of the posting rather than measurements over time.
  • Sources: Greenhouse (13,897), Ashby (7,332), Lever (4,379). These are modern ATS platforms, so the sample skews toward technology employers and venture-backed companies, and away from government, agency and enterprise-legacy hiring.
  • Skills: a keyword scan over an AI-extracted skill summary for each posting, so figures describe how often a technology is mentioned, not how often it is strictly required.
  • Salary: figures as published by the employer, restricted to a $20,000–$900,000 sanity window to exclude feed parse errors. No currency normalisation is applied.
  • Refresh: quarterly, at this same URL. Numbers on this page reflect the October 22, 2026 snapshot.

Cite this report

Free to quote, with a link back. If you need one line with the claim, the sample and the window attached:

InterviewChamp.AI tracked 25,608 tech job postings from 1,681 companies between June 20, 2026 and October 22, 2026. Of the 5,783 postings we first saw at least 60 days earlier, 14.2% were gone within a week, 34.1% within 30 days and 52.8% within 60 days, so 47.2% were still open after 60 days.

Source URL: https://interviewchamp.ai/tech-hiring-report

Working on a story or a piece that needs a cut we have not published — by title, by region, or over a longer window? Get in touch and we will run it.

InterviewChamp.AIInterviewChamp.AI

Most of these roles will not be open next month

Every posting in this dataset is on our board while it is still open, with the closed ones marked rather than quietly deleted.

Browse open roles