Module 7: The Hiring Process in 2026

3. Finding Real Openings and Avoiding Noise

Next →

Description

In the previous lesson we broke down the complete 2026 hiring funnel, cold part included: a portion of the outcome doesn't depend on you. Budgets that freeze, internal candidates, postings published out of legal obligation. This lesson is about the part that does depend on you, and it's bigger than it looks: where you search and how you filter. Applying to everything that moves is the fastest way to burn three months with not a single response. Applying with judgment, to postings that can genuinely hire you, in your country and your time zone, is what turns a statistically cruel funnel into one where you have a real chance.

Here you're not going to read "apply to more." You're going to learn to read a posting like someone inspecting a house before buying it: where the cracks are, what it means that it's been posted for four months, why the one that says "remote" actually wants someone in California's time zone. And you're going to set up a system so you don't lose track of where you applied, because in a serious search you're going to have twenty, thirty, forty conversations open at the same time, and your memory isn't built for that. All of this is work that happens before you write a single line of your letter or talk to a recruiter: it's the aim before the shot.

An honest clarification before we start, because this guide owes it to you. This lesson won't teach you general English. It assumes you already read technical English with reasonable ease (B1 reading level: you understand a job description and a GitHub thread without a translator in between) and that you can hold up about two minutes of speech, with mistakes, without completely freezing. If your reading isn't there yet, this module is going to cost you double, and the honest path is reinforcing technical reading English first. I say this here because finding postings is, deep down, a fine-reading exercise in English: the difference between a real posting and a ghost one is almost always in how it's written.

Connection to the module: Lesson 2 gave you the funnel's map and the search's healthy metric. This lesson gives you the entry filter into that funnel — deciding which postings are worth applying to before you spend energy on materials and calls. Lesson 4, the next one, is what happens when one of these postings responds: the recruiter call in English. Here you decide what you apply to; there you learn how you sound when they answer.

Where postings that genuinely hire show up

Not all posting sources are equal, and the order you work through them changes your response rate more than any other decision in your search. The beginner's instinct is to open a giant portal, sort by "most recent," and apply to everything that sounds vaguely like theirs. It's the path of least effort and the worst return. Let's flip that order.

Think of sources as a pyramid. At the base, wide and noisy, are the massive aggregators: lots of volume, lots of competition, lots of postings that aren't even from the company that claims to be hiring. At the tip, narrow and quiet, are referrals: few opportunities, but with several times higher odds of a response. Your job is to spend as much time as possible near the tip, not the base.

SourceSign it's genuinely hiringNoise to expectPriority
Referral from someone insideA human moves your profile inside the systemAlmost noneHighest
The company's own careers page (/careers, /jobs)The company maintains it themselves; usually up to dateLowHigh
Niche-specific boards (genuinely remote, one stack, one region)Curated, less volume and more relevanceMediumHigh
Communities (tech Slack/Discord, #jobs channels)Someone on the team posts because they're genuinely hiringMediumMedium-high
Massive aggregators (giant generalist portals)Lots of volumeHigh: reposts, ghosts, scrapersLow

Reading the table is simple: start at the top and only go down once the top runs dry. Most people do the opposite, and that's why they live in the frustration of the pyramid's base.

A nuance about company pages almost nobody makes use of: when a posting on an aggregator interests you, don't apply there. Note the company's name, go to their site, and look for the same posting on their own /careers. Often the official process is shorter, goes directly into their tracking system (the ATS, which we discussed in lesson 2), and avoids the middleman that sometimes doesn't even forward your application. Same effort, better destination.

What to expect

If you do this right, you're going to apply to fewer postings and get more responses. It's counterintuitive, and that's why it's worth stating clearly: a healthy search isn't measured in number of applications sent, but in the quality of the conversations you open. Ten well-aimed applications to real postings, two of them with a referral, beat a hundred shots at the generalist portal. If by the end of a week you sent sixty applications and didn't get a single response, the problem is almost never that you sent too few: it's that you searched at the base of the pyramid.

Anatomy of a ghost posting

A ghost posting (ghost job, in English) is a listing that stays active but isn't going to hire anyone, at least not now. It exists for reasons that have nothing to do with you: the company wants to keep a flow of résumés coming in "just in case," it's fulfilling an obligation to post before promoting someone internal, it's gauging the market with no real intent to spend budget, or it simply forgot to take the listing down. Applying to a ghost posting isn't a sin, but investing a forty-minute personalized letter in it is wasting time. Learning to smell them out is one of the skills that saves you the most hours.

There's no foolproof test, but there is a set of signals that, added together, sound the alarm. Look at the posting with this list:

  • Old or vague posting date. A genuine technical posting rarely stays open for four or six months. If the portal shows "posted 4 months ago" or hides the date behind a "recently" that never changes, be suspicious. Check the company's own /careers too: if it's not there but it is on the aggregator, it's a scraper repost, not a live posting.
  • Generic description with no team or project. Real postings are written by someone who knows what they need: they mention the team, the problem, the specific stack, sometimes even who you'd work with. The ghost is an interchangeable template: "we're looking for a passionate, proactive developer."
  • An impossible or inflated requirements list. Ten technologies, eight years of experience for a "mid" role, three frameworks that don't coexist in any real project. Sometimes it's a ghost; sometimes it's a posting written with no judgment; either way, a bad sign.
  • The same posting reappears every few weeks with the same text. A sign they're permanently collecting résumés.
  • The company has been "hiring" for the same role in many cities at once for months with no visible growth of the team.

This is where your fine-reading English pays off. A lot of these signals are in the tone of the text, not in a hard fact. Compare these two posting openers, both in English:

A live posting: "Our payments team is 6 engineers and we're adding a backend developer to help us move off a legacy billing service. You'll work mostly in Go and Postgres. In your first month you'll ship a small internal tool so you learn our deploy pipeline."

Nuance translation: it tells you the team size, the real problem (getting off an old billing service), the exact stack, and what you'll do the first month. Someone who knows what they need wrote this.

A ghost posting / template: "We are looking for a passionate, self-motivated Software Engineer to join our fast-paced, dynamic team. The ideal candidate is a rockstar who thrives in a challenging environment and wears many hats."

Nuance translation: no team, no problem, no stack, no project. Pure filler adjectives (passionate, rockstar, fast-paced, wears many hats). It could be any company on the planet. Distrust it.

No single signal alone condemns a posting. But when you see three or four together, drop the posting down your priority list: apply fast without personalizing, or skip it entirely. Save your good letter for the live ones.

The geographic and time-zone filter, before investing a single minute

In module 1 you built your availability profile: your country, your time zone, your legal work situation, your overlap hours with different regions. That filter wasn't a warm-up exercise. It's the first gate every posting passes through, before you get excited reading it. Nothing hurts more in this search than spending a whole afternoon on the perfect application and finding out on the first call that the company can't hire someone outside the United States.

The word "remote" in English is tricky because it doesn't mean the same thing everywhere. Learn to read these variants:

What the posting saysWhat it almost always means
"Remote (US only)" / "Must be authorized to work in the US"They can't hire you if you're not in the US. Skip it.
"Remote (US timezones)" / "Overlap with PST required"You can be anywhere, but your workday has to overlap with Pacific time. Check your real overlap.
"Remote (LATAM)" / "Open to candidates in the Americas"They're looking for you. Priority.
"Remote (EMEA)"Europe, Middle East, and Africa. If you're in LATAM, your overlap might be uncomfortable but not impossible. Calculate it.
"Remote-first" with no more detailAmbiguous. The time zone shows up in the fine print or on the first call. Ask early.
"Hybrid" / "3 days in office"In-person in disguise. If you're not in that city, it doesn't apply.

The operating rule: if the posting can't hire someone from your country, or your time-zone overlap is unworkable, discard it in the first minute, no matter how attractive it is. It's not giving up; it's not wasting ammunition on a target that isn't there. And there's an exception worth testing: when a posting says "US only" but you know from experience the company hires through a third-party structure (an Employer of Record, which we'll cover in lesson 7), it's sometimes actually viable. When in doubt, that question gets resolved fast and at no cost during the recruiter call — but only if the rest of the posting justifies getting that far.

A phrase to ask early, with no beating around the bush

When a posting interests you but the geographic issue is unclear, don't wait until the technical interview to find out. You can write it in a short message or ask as soon as the recruiter call starts. In English, direct and professional:

"Before we go further — I'm based in [your country] and I want to make sure that works on your side. Are you able to hire contractors or employees outside the US, or is there a timezone overlap you need me to meet?"

In Spanish: "Antes de seguir — estoy en [tu país] y quiero confirmar que eso les funciona. ¿Pueden contratar dentro o fuera de EE. UU., o hay un solape de horario que necesitan que cumpla?"

Asking this doesn't cost you points. On the contrary: it shows you respect both people's time. A good recruiter appreciates it.

The referral: why it changes everything and how to ask for one without being invasive

Here's the fact most people ignore and that moves the needle the most: an application with a referral has several times the probability of advancing compared to a cold application. It's not magic or connections. It's that a referral solves, in one move, the funnel's two biggest early problems: it pulls you out of the pile of résumés the automated filter never reads, and it gives a human inside the company a reason to pay attention to you. One person inside saying "I'll vouch for this candidate" is worth more than the most polished letter in the world.

The classic mistake is thinking a referral is only available to someone "with connections." The truth is a referral almost always comes from an honest, low-cost-to-the-other-person interaction. You're not asking them to get you the job. You're asking them to press an internal button that takes them thirty seconds and changes the whole game for you.

How to ask well (in order from least to most closeness):

  1. Someone you already know who works at the company: a former colleague, a community friend, someone from a bootcamp. This is the ideal case. Be direct and make it easy for them.
  2. Someone with a warm connection: you interacted in a community channel, commented on their talk, replied to their thread. Reactivate that connection with context before asking.
  3. Someone totally cold who works there: here you have to earn the right to ask with a genuine conversation first. Never open with "will you refer me?"

The message's key is making it cheap for whoever refers you: send them the exact posting link, a couple of lines about why you fit, and your résumé ready to go, so all they have to do is forward it. The less the other person has to think, the more likely they are to say yes.

Here's a real template, in English, for asking a somewhat-known contact for a referral. Notice the tone: short, concrete, with an easy out.

Message to a warm contact (English):

"Hey [name] — hope you're doing well! I saw [company] has an opening for a [role] (link below) and it lines up really well with what I've been building. Would you be comfortable referring me? Totally fine if not — no pressure at all. I've attached my CV and a two-line summary so it's easy to forward. Thanks either way!"

Link: [job posting]

In Spanish, the key nuance: "Would you be comfortable referring me?" ("¿te sentirías cómodo refiriéndome?") is much softer than "can you refer me?" And "totally fine if not — no pressure" gives them a no-social-cost out, which is exactly what makes people say yes without feeling pressured.

For a cold contact, the fatal mistake is asking for the referral in the first message. Something gets built first. An example of a well-made cold opener, in English:

First message to a cold contact (English):

"Hi [name] — I really liked your talk on [topic] at [event]. I've been working on something similar with [tech] and your point about [specific detail] changed how I approached it. If you're ever open to a quick chat about how your team works, I'd love that."

Notice it doesn't mention the posting. You haven't earned that yet. The referral, if it comes, comes later, once you're a person and not a stranger asking for a favor.

What to expect from the referral

Not everyone will say yes, and some won't even reply. That's normal and not personal: people are busy. A healthy rate is about half responding and referring a portion of those. What matters is the change in probability for the ones that do work out. A referral doesn't guarantee you the job — you still have to pass the interviews from lessons 4, 5, and 6 — but it guarantees a human is going to read your profile, which in 2026, with the automated filtering at scale we discussed in lesson 2, is already half the battle.

A tracking system so you don't lose the thread

In a serious search you're going to have many conversations open at once, at different stages, in different time zones, some with a referral and others without. Relying on your memory is a guaranteed way to miss replying to an email, to show up to a call without remembering what the company does, or to apply twice to the same posting with two different versions of your letter. You need a board. It doesn't have to be sophisticated: a spreadsheet is more than enough.

These are the columns that genuinely serve you:

ColumnWhat it's for
CompanyThe company's name.
RoleThe exact role you applied to (keep the literal title).
SourceWhere it came from: referral, /careers, niche board, aggregator. This shows you which source gets you results.
Applied dateWhen you applied. Tells you when to follow up and when to consider a posting dead.
ReferralName of who referred you, if anyone.
StageFunnel stage (lesson 2): applied, recruiter screen, technical, panel, offer, rejected, ghosted.
Next action + dateThe most important one. What's next and when. Without this, the system doesn't work.
NotesTime zone, recruiter's name, posting details, what you asked.

Notice I use the column names in English on purpose. It's a useful habit: a large part of your search happens in English, and getting your eye used to these terms (stage, referral, recruiter screen) is free training for the calls to come.

Two rules so the board doesn't turn into another dead file:

  • Every posting goes in the moment you apply, not "later." Later doesn't exist.
  • No row is left without a "next action." If a posting has no clear next step, either you're waiting on a response (note the date you'll follow up) or it's dead (mark it ghosted or rejected and mentally let go of it).

That "mentally let go" isn't decoration. One of the reasons this stage is the one most people give up at — as we saw in the module's introduction — is the emotional weight of postings in limbo, the ones that say neither yes nor no. Marking them ghosted after two weeks of silence and one unanswered follow-up is an act of mental hygiene. The posting didn't reject you; the process simply went cold, often for budget reasons the company itself doesn't control. Close it out on your board and put your energy into the next one.

When to follow up, with a phrase that works

If you applied with a referral or made it through a first conversation and you're five to seven business days without news, a short, polite follow-up is valid and even well-regarded. One, not three. In English:

Follow-up message (English):

"Hi [name] — just following up on my application for the [role] position from last week. I'm still very interested and happy to share anything else that would help. Thanks for your time!"

In Spanish: short, no reproach, no "why haven't you answered me?" You reaffirm interest, offer to help, close with courtesy. Only one message of this kind per posting. If there's no response after that, mark it ghosted and move on.

What a well-aimed week looks like

To land all of this into something you can execute, here's what a healthy week at this stage looks like. It's not a volume race; it's an aiming routine.

  1. Gather ten to fifteen postings from the top of the pyramid (referrable ones, /careers, niche boards). Before saving them, run them through the geographic filter: discard in the first minute the ones that can't hire your country.
  2. Filter for ghost signals. Of those ten to fifteen, mark which are live and which are doubtful. The live ones get your good letter; the doubtful ones get a quick, unpersonalized application, or get skipped.
  3. Identify possible referrals. Do you know anyone at any of these companies, even loosely? That's where your energy goes first.
  4. Apply and log each one on the board immediately, with its next action and date.
  5. Close the loop: review previous weeks' postings, do the follow-ups that are due, mark the dead ones.

If you do this consistently, lesson 2's healthy metric starts making sense: you'll see which source your responses come from and be able to adjust your aim instead of blindly repeating what doesn't work.

Exercises

Exercise 1 — Smell the ghost posting

Read this posting opener, published five months ago on a massive aggregator:

"We are seeking a dynamic, results-driven Software Engineer to join our innovative, fast-paced team. The ideal candidate wears many hats and thrives under pressure. Requirements: 6+ years of experience with Python, Java, Go, Rust, Kubernetes, and machine learning."

What ghost-posting signals do you detect? Do you invest your forty-minute personalized letter, or move it to the bottom of your list?

See solution

Four signals, not just one: (1) old date — five months is a lot for a real technical role; (2) filler language with no team or project (dynamic, results-driven, innovative, fast-paced, wears many hats) — nobody who knows what they need writes like this; (3) impossible requirements — Python, Java, Go, Rust, Kubernetes, and machine learning with six years don't describe a role, they describe a recruiting fantasy; (4) no concrete detail about what you'd do in the first month.

Don't invest the good letter. Apply quickly with generic material if at all, or skip it entirely and use those forty minutes on a posting with signs of life.

Why this works: no isolated signal condemns a posting, but when three or four pile up — as here — the probability of it being real drops sharply. Your personalized-letter time is your search's scarcest resource; protecting it is the skill, not an act of cynicism.

Exercise 2 — Translate the "remote"

For each clause, decide on the spot what you do: discard, high priority, or calculate your overlap before deciding.

  1. "Remote — must be authorized to work in the United States."
  2. "Remote — open to candidates based in the Americas."
  3. "Remote-first company, fully distributed team." (with no further detail on time zone)
See solution
  1. Discard (unless you know the company hires via Employer of Record — then it's worth confirming quickly on the call, without investing more time before that).
  2. High priority. "Americas" includes you directly; it's exactly the posting the pyramid tells you to prioritize.
  3. Ambiguous — don't discard or celebrate yet. Apply if the rest of the posting looks alive, but ask about the time zone early, before investing more time than necessary, with the direct phrase you saw in this lesson.

Why this works: the geographic filter exists to save you hours, not so you memorize a list of countries. The operating rule is simple — if it can't hire you or the overlap is unworkable, discard it in the first minute — and applying it on the spot, without overthinking, is what makes it valuable.

Exercise 3 — Fix this referral message

This message was sent to a warm contact (they interacted once in a Discord channel months ago) as soon as the posting was seen:

"Hi! Can you refer me for the backend role at your company? I really need this job, please help me out."

What's missing to follow the principle of "making it cheap for whoever refers you"? Rewrite it.

See solution

Three things are missing: (1) it doesn't rebuild the connection before asking — it goes straight to the favor with no context; (2) it doesn't make the work easy — it doesn't send the posting link, a summary of why they fit, or the résumé; (3) it doesn't give an easy out — "I really need this job" adds pressure instead of removing it.

A version that works:

"Hey [name] — hope things are going well! I saw [company] is hiring a Backend Engineer (link below) and it's a strong match for what I've been building lately. Would you be comfortable referring me? Totally fine if not — no pressure at all. I've attached my CV and a two-line summary so it's easy to forward if you're up for it."

Why this works: it reactivates the connection warmly before asking, reduces the cost of saying yes to "forward a file," and gives a no-guilt out if the answer is no. That's what makes busy people who barely know you press the button anyway.

Exercise 4 — Decide with your board

You applied to a posting without a referral. At six business days with no response, you sent the one follow-up the playbook calls for. Four more days pass and it's still silent. What do you note in the Stage column, and what do you do?

See solution

Mark the row as ghosted and move on. The system is explicit: one follow-up per posting, not three. You already did it; insisting with a second message isn't in the playbook and starts to read as pressure, not interest. Closing it on the board isn't giving up — it's the mental hygiene that lets you put your full energy into the next posting in the pyramid.

Why this works: the board only serves its purpose if every row has a clear destination. Leaving a posting "just in case" unmarked is exactly the emotional limbo that makes people give up at this stage of the search.

Summary and next step

Before moving on to the next lesson, you should be able to:

  • Prioritize your search sources with the pyramid (referrals and company pages before massive aggregators).
  • Detect at least three signals of a ghost posting by reading only the tone of the English text.
  • Read a "remote" clause and decide, within the first minute, whether the posting can hire you.
  • Write a referral message that makes it cheap for the other person, with an easy out.
  • Keep a tracking board where no row is left without a next action.

In summary:

  • Work top-down through the source pyramid: referrals and company pages first, massive aggregators last. Fewer well-aimed applications beat a hundred shots into the void.
  • Learn to smell a ghost posting by its signals (old date, generic description, inflated requirements, reposting). Save your good effort for the live ones. Much of the clue is in the tone of the English text.
  • Run every posting through module 1's geographic and time-zone filter before getting excited. "Remote" doesn't mean the same thing everywhere; learn to read the variants.
  • The referral changes your odds more than anything else. It's asked for by making it cheap for the other person, with an easy out, and never in the first message to a cold contact.
  • Set up a tracking board from your first application onward. No row without a next action. Marking the dead ones is mental hygiene, not defeat.

With this you have your aim. You now know which postings are worth applying to and which ones are stealing your time. In the next lesson we move to what happens when one of these well-chosen postings responds: the recruiter call in English, that first twenty-minute conversation that decides whether you advance to the technical process.

Resources

← Previous2. How Hiring Works in 2026Next →4. The Recruiter Screen in English