Channel
@jobforphp
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,015subscribers
+105 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001270273504 |
|---|---|
| Type | Channel |
| Username | @jobforphp |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/jobforphp |
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 07:56 | 3,015 | +21 |
| 18 Sept 2026, 11:18 | 2,994 | +10 |
| 14 Sept 2026, 02:37 | 2,984 | +7 |
| 10 Sept 2026, 13:18 | 2,977 | +6 |
| 5 Sept 2026, 08:17 | 2,971 | +12 |
| 1 Sept 2026, 19:47 | 2,959 | +9 |
| 29 Aug 2026, 23:54 | 2,950 | -1 |
| 26 Aug 2026, 14:25 | 2,951 | +6 |
| 23 Aug 2026, 14:04 | 2,945 | +11 |
| 19 Aug 2026, 15:24 | 2,934 | +5 |
| 16 Aug 2026, 20:23 | 2,929 | +6 |
| 13 Aug 2026, 04:56 | 2,923 | +9 |
| 9 Aug 2026, 19:11 | 2,914 | +3 |
| 6 Aug 2026, 19:35 | 2,911 | +1 |
| 6 Aug 2026, 09:17 | 2,910 | no change |
| 6 Aug 2026, 09:08 | 2,910 | first reading |
21 posts held, back to 2 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 21 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
37 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 48.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 18 | 48.6% | |
| 👍 | 12 | 32.4% | |
| ❤ | 3 | 8.11% | |
| 😁 | 3 | 8.11% | |
| 💊 | 1 | 2.70% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 12 of the 21 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 37 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 2 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Chief Technology Officer Zofeur is a fast-growing mobility technology platform built around delegated mobility for car owners, powering on-demand chauffeur services, scheduled and subscription-based mobility, and enterprise driver logistics. Stack: PHP/Laravel, Swift, Kotlin, AWS, GCP, Redshift. Dubai, UAE. On-site. Job description on LinkedIn. Больше вакансий для технических менеджеров: @jobfortm
🔹 Full-stack Developer (PHP/React) 🔹 Senior Backend Developer (PHP) Firebird is an international online travel company that organizes trips to Europe for customers from around the world. Tech Stack: PHP | Drupal 11, MariaDB/MySQL, Bitbucket, Jenkins, Docker. Remote work.
Middle+ PHP / Go Developer в MaxLine — лицензированная iGaming-компания, которая создаёт высоконагруженные платформы для ставок и онлайн-казино. Офис (Минск, Беларусь). Ищет Карина Третьякова, её пост на LinkedIn.
Senior Full-stack Engineer (Laravel + Vue.js) в TrafficConnect — международная команда и аффилиат-агентство, которое разрабатывает собственные внутренние сервисы, автоматизирует бизнес-процессы и создает инструменты, помогающие командам быстро масштабироваться. Стек: PHP, Laravel, Vue.js, MySQL, Redis. Удалённая работа. Описание вакансии. Ищет Сергей Станкевич, его пост на LinkedIn.
Что писать в резюме в 2026? Если ты ищешь работу и чувствуешь, что резюме вдруг перестало работать так, как раньше, — с тобой всё в порядке. Изменилась реальность рынка труда и найма в IT. Что именно поменялось и как сейчас упаковывать свой опыт в резюме, чтобы превратить его в приглашение на собес? Разбираемся вместе с Кирой Кузьменко — фаундером рекрутингового агентства NEWHR и автором курса Hello New Job! 👇 1️…
❤1
PHP Middle Developer в AKDev Group — IT-компания, которая создает веб- и мобильные приложения, а также разрабатывает и поддерживает программное обеспечение под ключ для бизнеса. Локация: Минск, Беларусь. Ищет Анастасия Козлова, её пост на LinkedIn.
Middle+ / Senior PHP Developer в SkyCoach — сервис внутриигровых услуг, соединяющий профессиональных киберспортсменов с обычными игроками для бустинга, обучения и прохождения сложных заданий. Стек: PHP 8+, Laravel, PostgreSQL, Redis, Horizon. Удалённая работа. Ищет Лизавета Протасевич, её пост на LinkedIn.
🎙 Ищем партнёра для нового сезона «Собеса» 🚨 UPD Важно: в данный момент мы ищем НЕ экспертов/спикеров, а только компании-партнеров, которые хотели бы разместить рекламу в подкасте. Рынок найма в IT за последние пару лет изменился до неузнаваемости. ИИ-рекрутеры, фрод с обеих сторон, дипфейк-собеседования, AI-трансформация профессий — то, о чём мы писали в канале, стало повседневной реальностью. И кажется, пора дел…
Этой осенью состоится XI поток Hello New Job! — авторского курса Киры Кузьменко про поиск работы в современных реалиях. Hello New Job! — это курс-интенсив, на котором ты научишься искать работу в любых реалиях на рынках России, Европы и США. Для этого, в процессе обучения, ты: ⚡️ узнаешь, что на самом деле работодатели ищут в кандидатах и как сделать так, чтобы тебя заметили. ⚡️ научишься презентовать свой опыт и…
Middle / Senior Fullstack-developer в WIAM — компания-разработчик программного обеспечения, специализирующаяся на создании цифровых решений для бизнеса. Проект: рабочая CRM для отдела продаж застройщика жилой недвижимости (Дальний Восток). Удалённая работа. Описание вакансии на GeekJob.ru.
Senior Backend-разработчик в Beeone FMCG — международная компания, специализирующаяся на рынке товаров повседневного спроса, которая совмещает продажу потребительских товаров с современными технологиями. Стек: Rust, PHP, Go, Claude AI. Офис (Алматы, Казахстан). Гибрид после испытательного срока. Ищет Дана Табакаева, её пост на LinkedIn.
😁3❤1👎1
Миддл / Тимлид Разработчик 1С-Битрикс (PHP) / AI Tech Lead в Pva.expert — крупный официальный поставщик и дилер профессионального строительного оборудования и материалов. 150К–170К. Удалённая работа (РФ). Описание вакансии на GeekJob.ru Больше вакансий для технических менеджеров: @jobfortm
👎8
Showing the 12 most recent of 21 posts we hold for @jobforphp. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Job for PHP” (@jobforphp), 3,015 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/jobforphp.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.