Channel
@empleostech
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
10,305subscribers
-126 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001293494944 |
|---|---|
| Type | Channel |
| Username | @empleostech |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/empleostech |
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 11 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 |
|---|---|---|
| 19 Sept 2026, 08:59 | 10,305 | -3 |
| 16 Sept 2026, 23:56 | 10,308 | -9 |
| 15 Sept 2026, 01:38 | 10,317 | -7 |
| 13 Sept 2026, 08:19 | 10,324 | -12 |
| 11 Sept 2026, 10:20 | 10,336 | -4 |
| 8 Sept 2026, 16:41 | 10,340 | -10 |
| 5 Sept 2026, 09:37 | 10,350 | -2 |
| 3 Sept 2026, 10:48 | 10,352 | -1 |
| 2 Sept 2026, 02:21 | 10,353 | +1 |
| 1 Sept 2026, 02:57 | 10,352 | +2 |
| 31 Aug 2026, 03:54 | 10,350 | -5 |
| 30 Aug 2026, 01:13 | 10,355 | -8 |
| 29 Aug 2026, 03:25 | 10,363 | -2 |
| 28 Aug 2026, 03:34 | 10,365 | +3 |
| 27 Aug 2026, 03:44 | 10,362 | +3 |
| 26 Aug 2026, 01:53 | 10,359 | +2 |
| 25 Aug 2026, 02:47 | 10,357 | -7 |
| 23 Aug 2026, 16:34 | 10,364 | -7 |
| 22 Aug 2026, 03:45 | 10,371 | -4 |
| 20 Aug 2026, 17:24 | 10,375 | first reading |
20 posts held, back to 20 June 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 38 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 20 posts for this entry, the most recent from 12 December 2025. An engagement rate over an empty window would be a number about nothing.
93 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 92.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 92.5% | |
| 👍 | 6 | 6.45% | |
| 🤩 | 1 | 1.08% |
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 19 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 93 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 20 June 2025 to 12 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Hola México, 👋🏻 estoy buscando un PM con inglés C1 o superior y experiencia en implementación de ERP, y Sistemas SASSpara encarar nuevos proyectos en Ciudad de México Si estás escuchando propuestas envíame tu cv a 👇 [email protected]
❤4👍3
https://www.linkedin.com/posts/carlosbedoya_bitsamaezricas-oportunidadlaboral-aeqnetealequipo-activity-7387259520722423808-NPzt?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAIkg_cB_OkxJrC1AKpnW5f59ioO8ioNg7g
❤3
#Hiring Argentina! Tech Lead PM!! Buscamos un Senior Tech Lead IT con experiencia como PM: Requisitos excluyentes: (todos) ✔️Título universitario IT (Ingeniero en informática o Licenciado en computación). ✔️4 años en proyectos de desarrollo de software + 2–3 años en un rol de liderazgo técnico. ✔️Certificación en gestión de proyectos. Experiencia en la gestión de proyectos de software y aplicaciones empresar…
❤6
📣Hello España and Europa!!!!!!!📣📣📣📣 📢📢We’re hiring a *Ruby on Rails Engineer* to join our *Core Ruby Team*, where performance, reliability, and clean code are essential.📢📢 🚨🚨Hybrid Role 4 days at home and one day at the office🚨🚨 👉What You’ll Do - Build and enhance core services using clean, efficient Ruby code - Write meaningful, well-structured tests - Collaborate across teams (Elixir, Java, RabbitMQ, Redis) …
❤3
🚀 We’re Hiring: Senior Full-Stack Developer (Next.js + Node.js) 🌎 Remote (LatAm ONLY) | US client | Long-term 📌 Tech Stack • MUST: Next.js + React, Node.js • Nice to have: PHP (plus, not core) • AWS, Serverless 📌 Requirements • ✅ 10+ years building production software • ✅ Advanced conversational English (mandatory) • ✅ Strong experience delivering Next.js + Node end-to-end (SSR/ISR, APIs, CI/CD) • ✅ Ownership mindset…
❤2
Modelos abiertos LLM - Ya en vivo 🔴 https://www.youtube.com/live/-hZxCBMRZlc?si=PrzBb4qS_iyPvKHb
👍1
📢 Oportunidad laboral !#España ! Estoy buscando un/a especialista de desarrollo de Soluciones Cloud (Gestión Documental) con residencia en Madrid para diseñar, implementar y optimizar soluciones Cloud para la Plataforma de Gestión Documental (ECM), garantizando seguridad, escalabilidad, rendimiento e integración con sistemas on-premise y cloud. 💼 Modalidad: Híbrida (Majadahonda, Madrid, España) 📩 Envía tu CV por mens…
❤8
🚀 ¡Estamos contratando en Colombia! 🚀 Tenemos nuevas oportunidades para unirte a proyectos internacionales con cliente en EE. UU. 🌎 Ingles B2+ 🔎 Posiciones abiertas: 1. QA (6+ años) – experiencia en sector financiero, SQL, Excel avanzado, Agile. 2. Business Analyst (8+ años) – fuerte en Finanzas y Private Equity, Excel avanzado, SQL básico. 3. IT2 Treasury Management System Senior Developer (5+ años en IT2, inte…
❤2
Hola red! Les comparto oportunidades laborales en Ernst & Young GDS! 🌍 ARGENTINA (Bs As) (Híbrido – CABA | 2 días presencial) - Requisito inglés avanzado (excluyente) 🔹 Supervising Associate para área de IAM (dentro de Information Security). (Híbrido – CABA | 2 días presencial) - Horario FLEXIBLE +6 años de experiencia Experiencia en: 📌 Active directory 📌 Azure 📌 Cloud experience 📌 SCCM 📌 Inglés avanzado (excl…
❤5
#hiring Argentina! DESARROLLADOR FRONTEND ANGULAR SSR! Los últimos 2 o 3 años avocado a puestos 100% FRONT ANGULAR, NO FULL STACK!!!!! Incorporación inmediata! Se requiere un perfil front end a incorporarse en la Software Factory para trabajar en proyectos en el área Ecommerce. Los últimos 2 años tienen que haber sido como Fron End Dev trabajando con las últimas versiones de Angular!!!!! +2 años de experiencia…
❤16
#Hiring · Everything is gonna be Playwright…🎶 Sumamos QA Engineers a nuestro equipo en Darwoft 😎👇🏻 Estamos sumando QA Engineers — manuales y de automatización — que quieran participar en la evolución de una plataforma digital financiera robusta, muy conocida, validando calidad en entornos web y mobile, desde etapas tempranas y con enfoque ágil. · Ubicación: Córdoba Capital, Argentina · Tecnologías clave: Postman, A…
❤6
📢 Oportunidad laboral !#Colombia! 🚀 ¡Estoy en búsqueda de un/a Fullstack Developer Java + Angular! …
Showing the 12 most recent of 20 posts we hold for @empleostech. 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.
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 2 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Empleos Tech 💼” (@empleostech), 10,305 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/empleostech.
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.