The Hidden Job Market in Tech: Career Pages and Referrals
"The hidden job market" sounds like a private club you need a password for. In tech, it's mostly two unglamorous things: company career pages that few people check directly, and referrals from people who already work there. If your search feels like you only ever see the same crowded listings, this post explains why many roles show up in those two places first, what's genuinely hidden and what isn't, and a weekly routine you can start today.
What the hidden job market actually is
You'll find claims that most jobs are never advertised. Nobody has a reliable number for this, especially for tech, so we won't quote one. What we can say is that most of what feels hidden falls into three groups:
- Posted, but only at the source. The role is live on the company's own careers page, usually run by an applicant-tracking system such as Greenhouse, Lever or Ashby, and it hasn't reached LinkedIn or the aggregators yet. Sometimes it never does.
- Posted, but buried. It is on a big board, but under a title you don't search for, or pushed down by promoted listings and reposts.
- Genuinely unposted. The role is filled through a referral, a former colleague or a hiring manager's network before anyone writes a job description.
The first two are about where and how you look. Only the third needs people. That's good news: the first two can be fixed with a better routine.
Why roles appear on career pages first
When a recruiter opens a role in their applicant-tracking system, publishing it to the company's careers page is normally the default, immediate step. Everything else is extra work: a paid slot on a big board, an integration, someone copying it over by hand. Aggregators then pick up postings on their own schedule, hours or days later.
So the careers page is the source, and other listings are copies with a delay. Some companies don't push every role to every paid board, so some roles stay on the careers page and nowhere else. We explain the mechanics in what Greenhouse, Lever and Ashby are, and compare the two sides in job boards vs company career pages.
Why so few people check them
If career pages are the source, why isn't everyone watching them? Because it's tedious:
- There are too many. Opening 40 bookmarks every morning is a chore, and most mornings nothing has changed.
- There's usually no alert. Many career pages have no "notify me" button, or only a general talent-pool form that doesn't tell you when a specific role opens.
- Habit. Most people search on the board they already have open.
That tedium is exactly why it's worth doing. A role that few people have seen yet is a role where your application gets read with less competition, which is the whole argument in why applying in the first 24 hours matters.
How to watch career pages: a practical setup
- Pick your companies. Write down 30 to 50 companies you would genuinely join and that can hire where you live. Our guide to building a target company list covers criteria and where to find them.
- Find each careers page. Search "
careers" and click through to the job list. Note the address: greenhouse.io,jobs.lever.coorjobs.ashbyhq.comtell you which system it runs on, and you can bookmark that board directly. - Put them in one bookmark folder. Most browsers can open a whole folder at once. Twice a week, open it and use each board's search or department filter for your titles.
- Automate what you can. Some systems offer alerts, some third-party tools watch boards for you. For the rest, the bookmark folder is fine.
- Log what you see. A simple sheet with company, role, date seen and link tells you which companies post your kind of role and how often. See how to keep a job application tracker.
Referrals: the part that is really hidden
Career pages cover the "posted but unseen" roles. Referrals cover the roles you'd never see at all, and they also help with posted ones.
- Start with people you've actually worked with. Former colleagues who moved to a company on your list are the easiest conversation. A short message is enough.
- Make the ask concrete. "I saw the Backend Engineer role on your careers page. Would you be comfortable referring me, or telling me who's hiring for it?" A live posting gives your contact something specific to act on. This is where watching career pages and referrals work together.
- With strangers, ask for information, not a referral. "Is the platform team hiring this year?" or "What's it like working on X?" is easier to say yes to. A referral may follow once they know you.
- Use communities you're already in. Meetups, alumni groups, Slack or Discord communities for your stack, and the local tech chats that relocated engineers tend to join. People do post "my team is hiring" there, often before a formal listing.
- Say thank you, and report back. People refer again when they know what happened last time.
Many tech companies run internal referral programmes, but how a referral is handled differs a lot. Treat it as a way to get read by a person, not as a shortcut past the interviews.
A weekly routine
| When | What |
|---|---|
| Twice a week | Open the career-page folder or check your alerts; apply the same day to anything that fits |
| Once a week | Send one or two referral or catch-up messages to people at companies on your list |
| Every two weeks | Add a few companies, drop the ones that never post your role |
It's modest on purpose. A routine you keep for two months beats an ambitious one you drop after a week.
What it won't do
Watching career pages gets you earlier, not certain. You'll still send applications that go nowhere, and some roles will be filled internally before you ever see them. What changes is that you stop relying on a single crowded channel and see more of the roles that are actually open.
Hot Jobs covers one slice of this for you: it checks the career pages of 390+ tech companies on Greenhouse, Lever and Ashby every 30 minutes, plus the Remotive and Himalayas boards and sends new matching roles to Telegram, often before they're reposted on LinkedIn. Referrals are still yours to do. €3, paid once. Connect the bot