Telegram Job Bot: How It Works, Step by Step, and Its Limits

A Telegram job bot can feel like a black box: you pick a few roles, and job postings start appearing in your chat. Knowing how it works helps you set it up well and trust it the right amount. Below is a step-by-step walk through how Hot Jobs, a Telegram job bot, finds, filters and sends postings, followed by an honest list of what it can't do.

The short version

1. The bot reads the public job boards of a fixed list of companies, plus two remote-job boards.
2. Every 30 minutes it checks them again and notes which postings are new since last time.
3. It compares each new job title with the roles you picked.
4. It compares the job's location with where you said you can work.
5. If both match, it sends you a message with the company, title, location and a link to apply.

Step 1: where the jobs come from

Hot Jobs reads the career pages of 390+ tech companies, including Figma, Linear, GitLab, Spotify, Monzo and SumUp. These companies publish their openings through one of three applicant-tracking systems: Greenhouse, Lever or Ashby. Each system offers a public version of the company's job board, the same list you see on its careers page. We explain why that page usually gets new roles first in What Greenhouse, Lever and Ashby are.

On top of the company pages, the bot reads two remote-job boards, Remotive and Himalayas. They cover many more companies than the 390+. When a posting comes from one of these boards, the bot tries to find the same role on the company's own careers page, so the link takes you to the original rather than to a listing.

That's the whole list of sources. The bot doesn't read LinkedIn, general job sites or Telegram channels.

Step 2: checking every 30 minutes

Every 30 minutes the bot fetches each company board and compares the open jobs with what it saw last time. Anything it hasn't seen before is a candidate. Himalayas is checked on the same cycle. Remotive asks tools that use its feed to fetch only a few times a day, so the bot respects that and reads it about every six hours.

Two rules keep repeats out:

• A job counts as new only once. After that it's never sent again.
• The same company and title isn't sent twice within 30 days, even if the posting is closed and re-opened or listed in several cities.

Because of the 30-minute cycle, a role on one of the 390+ company pages usually reaches you within about half an hour of going live. That's often before it's reposted on LinkedIn, though not always: some companies post everywhere at once.

Step 3: matching the job title

Matching uses the job title only, with a set of keywords for each of the 25 roles you can pick. A few examples:

Some details that change what you receive:

• Whole words only. "iOS" doesn't fire on "scenarios", and "QA" won't match inside a longer word. Capitals don't matter, and plurals are accepted.
• Leadership titles go to leadership roles. If you pick Frontend, an "Engineering Manager, Frontend" posting is not sent to you, because it's an Engineering Manager job. The same applies to titles with director, head of, VP or chief.
• Junior roles are hidden by default. Titles with words such as junior, intern, graduate, trainee or working student are skipped unless you turn junior roles on. We discuss that choice in junior IT job search filters.

Step 4: matching the location

Next, the bot reads the posting's location field and compares it with your choice:

• Remote · Europe & EMEA keeps remote roles open to Europe, the UK or the Middle East, and drops remote roles tied to another region, such as "Remote - US". A bare "Remote" with no region named is let through.
• Remote · Americas does the same for the US, Canada and Latin America.
• Remote · Anywhere keeps every remote role, whatever region it's limited to.
• Only my cities keeps on-site, hybrid and remote roles in up to 10 cities you type.

You can also add cities to a remote choice, so hybrid roles in your city arrive alongside remote ones. A location marked hybrid or on-site isn't treated as remote. For why location fields are so messy, see remote IT jobs actually open to Europe.

Step 5: the message

If a job passes both checks, you get a message with the company, the exact title, the location as written on the posting, and a link. The link goes to the company's own application page whenever the bot can find one.

Two more behaviours:

• Digests. If one check finds more than 10 matches for you, they arrive as a single digest message rather than a flood.
• A head start. When you first press START, you get up to 5 matching jobs that are open right now, so you can see your filters at work straight away.

What it can't do

A bot like this is narrow on purpose:

• It reads titles, not descriptions. A title with no role keyword, such as "Engineer II" or "Staff Engineer, Payments", won't match Backend even if the work is backend. "Software Engineer (any)" catches many generic engineering titles, but not every one.
• It reads the location field, not the fine print. A bare "Remote" can still say "US only" further down. Check before you apply.
• Cities are matched as written. If a posting says "München" and you typed "Munich", they won't meet. Add both spellings if in doubt.
• Only its sources. A company outside the 390+ that doesn't post on Remotive or Himalayas is invisible to it.
• No filters for salary, tech stack, company size or visa sponsorship. It also doesn't apply for you, review your CV or promise interviews.

Getting the most out of it

Pick the adjacent roles you'd really apply for, not one title. If you're in Europe, choose Europe & EMEA and add the cities you'd work in. Treat the first week as calibration: if messages feel off, send /settings and adjust, which is free. If you combine several sources, setting up job alerts without the noise covers how to keep them manageable.

Hot Jobs is an independent service running a regular Telegram bot, not something made by Telegram, and it works exactly as described above. It costs €3, paid once, with no account and no subscription. Connect the bot