Channel
@php_symfony_laravel_job
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,347subscribers
-18 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001602109821 |
|---|---|
| Type | Channel |
| Username | @php_symfony_laravel_job |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/php_symfony_laravel_job |
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 18 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 |
|---|---|---|
| 17 Sept 2026, 16:00 | 1,347 | -9 |
| 13 Sept 2026, 13:20 | 1,356 | +1 |
| 10 Sept 2026, 03:39 | 1,355 | -3 |
| 4 Sept 2026, 16:38 | 1,358 | +3 |
| 31 Aug 2026, 16:14 | 1,355 | +1 |
| 25 Aug 2026, 23:02 | 1,354 | -5 |
| 23 Aug 2026, 09:23 | 1,359 | +1 |
| 19 Aug 2026, 15:35 | 1,358 | +3 |
| 13 Aug 2026, 09:13 | 1,355 | -5 |
| 10 Aug 2026, 17:44 | 1,360 | -5 |
| 7 Aug 2026, 10:42 | 1,365 | no change |
| 7 Aug 2026, 01:18 | 1,365 | first reading |
20 posts held, back to 30 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 3 April 2026. An engagement rate over an empty window would be a number about nothing.
14 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 42.9% | |
| 👎 | 3 | 21.4% | |
| 🤡 | 2 | 14.3% | |
| ❤ | 1 | 7.14% | |
| 🔥 | 1 | 7.14% | |
| 😁 | 1 | 7.14% |
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 6 of the 20 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 December 2025 to 3 April 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.
💼 ВАКАНСИЯ: Middle Fullstack-разработчик Компания: Астронис Зарплата: 150 000-180 000 Локация/Format: Москва/Гибрид Мы ищем талантливого и мотивированного Middle Fullstack программиста для разработки и поддержки нашего продукта — современной программной IP-АТС, предназначенной для бизнеса. Если вам интересно сочетание frontend и backend разработки, работа с VoIP-технологиями и участие в создании корпоративной телеф…
👍1👎1
👤 РЕЗЮМЕ: Middle PHP Developer Опыт: 6 лет Зарплата: От 180 000 Навыки: PHP, MySQL, PostgreSQL, Docker, REST API, HTML, CSS, JavaScript, Laravel 12, Yii2 Опытный Laravel-разработчик с более чем 9-летним стажем в разработке и поддержке сложных веб-приложений и CRM-систем. Эксперт в PHP 7+, Laravel 11-12, Yii 2 и Symfony 5. Имею глубокое понимание принципов SOLID, DRY и опыт работы с REST API. Отлично владею реляцион…
✨ AI-подбор каналов для постинга вакансий и резюме Теперь в боте https://t.me/it_jobs_resumes_bot AI помогает подбирать подходящие каналы для публикации вакансий и резюме. Как это работает: 📝 вы заполняете форму вакансии или резюме 🤖 AI анализирует текст 📢 сервис сразу отмечает подходящие каналы ✍️ при желании выбор можно изменить вручную Это быстрее, удобнее и помогает не тратить время на ручной подбор. Попробов…
👤 РЕЗЮМЕ: Senior Backend Developer / PHP / Symfony Опыт: 20 Зарплата: 290000 Навыки: PHP 8, Symfony, Doctrine, MySQL, REST, RabbitMQ, Docker, CI/CD, Linux, Nginx, Vue.js, Git, SaaS Senior PHP Backend Developer / Tech Lead с ~20 годами опыта. Последние 7 лет развиваю финансовую B2B SaaS‑платформу на Symfony: архитектура, разработка, интеграции, инфраструктура и развитие продукта. Сильный опыт проектирования систем, …
👤 РЕЗЮМЕ: Middle Backend PHP laravel developer Опыт: 6 лет Зарплата: 200000 Навыки: PHP MYSQL Nginx Redis Laravel Docker HTML CSS JS Backend-разработчик на PHP (Laravel). Последние 3 года развивал крупный онлайн-проект в сфере микрофинансов — перенёс систему с legacy-CMS на Laravel 10, разделил монолит на микросервисы и ускорил работу API и баз данных. Работаю со стеком: PHP 8.1+, Laravel 12, MySQL, Redis, Docker, …
💸 Зарабатывайте вместе с GeekLink: Запуск Партнерской Программы Мы знаем, что нас читает много людей с широким нетворком: рекрутеры, тимлиды, владельцы каналов и карьерные менторы. Теперь вы можете монетизировать свои связи! Мы отдаем 50% от всех оплат приведенных вами пользователей. Как это работает? 1️⃣ Заходите в описание бота @it_jobs_resumes_bot 2️⃣ Нажимаете кнопку «Партнерская программа» и получаете уника…
❤1
👤 РЕЗЮМЕ: Php Backend Developer Опыт: 2+ года Зарплата: 130000 Навыки: PHP 7.4+, Symfony 5.4+, PostgreSQL, MySQL, RabbitMQ, Docker, REST API, PHPUnit, Git. Гибрид Москва или удаленно. Backend-разработчик с 2+ годами коммерческого опыта разработки backend-сервисов. Основной фокус — проектирование REST API, реализация бизнес-логики, асинхронная обработка задач и развитие legacy-систем. Стек: PHP 7.4+, Symfony 5.4+,…
👍5👎2🔥1
🔥 Скидка 50% на публикацию вакансий и резюме Если вы сейчас ищете сотрудника или работу - хороший момент разместиться дешевле. Мы сделали скидку 50% на публикацию во все каналы GeekLink. Это значит, что можно охватить сразу большую аудиторию IT-специалистов и компаний, но за половину стоимости. 👉 Посмотреть каналы: https://t.me/geeklink_ru/582 Разместить вакансию или резюме можно прямо через бота - быстро и без п…
AI-исправление резюме 🤖 Повышайте охваты своего резюме за счёт исправления типичных ошибок и улучшения формулировок. ИИ поможет сделать текст более понятным, структурированным и привлекательным для работодателей. Как использовать: 1️⃣ Запустите Telegram-бота: https://t.me/it_jobs_resumes_bot (выберите пункт «Разместить резюме»). 2️⃣ Заполните поля резюме. 3️⃣ Нажмите кнопку ✨ AI-исправление. Стоимость — 100 ⭐️ …
🤡2
⭐️⭐
IT нетворкинг 2.0! Встречайте Telegram-бот ☕️ Случайный кофе 2.0, который по пятницам подбирает собеседника для нетворкинга. В прошлой версии бота приняли участие более 1000 участников. В этой мы учли прошлые недостатки и пожелания. Теперь не нужно нигде дополнительно регистрироваться. Запускаете бот и принимаете участие! Для каких целей: - деловое общение (по работе, карьере, технологиям); - и/или свободное обще…
Вакансии PHP, Symfony, Laravel pinned «Как опубликовать вакансию или резюме? 📝 Мы максимально упростили процесс. Публикация происходит автоматически через нашего бота. 🤖 Бот: @it_jobs_resumes_bot Всего 4 шага: 1️⃣ Запустите бота и нажмите Start. 2️⃣ Заполните простую форму (вакансия или резюме).…»
Showing the 12 most recent of 20 posts we hold for @php_symfony_laravel_job. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 1 seed channel's Telegram-generated recommendation list 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Вакансии PHP, Symfony, Laravel” (@php_symfony_laravel_job), 1,347 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/php_symfony_laravel_job.
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.