looking for a new contract. My LinkedIn profile: https://www.linkedin.com/in/alexkonioukhov/
Signed Alex
Channel
@job_it_recruit
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
117subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001870067476 |
|---|---|
| Type | Channel |
| Username | @job_it_recruit |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/job_it_recruit |
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 26 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 |
|---|---|---|
| 29 Sept 2026, 22:41 | 117 | +1 |
| 14 Sept 2026, 19:20 | 116 | +1 |
| 8 Sept 2026, 06:39 | 115 | +1 |
| 30 Aug 2026, 13:56 | 114 | +1 |
| 16 Aug 2026, 19:05 | 113 | -1 |
| 9 Aug 2026, 06:01 | 114 | no change |
| 7 Aug 2026, 21:31 | 114 | first reading |
20 posts held, back to 23 October 2024 — 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 4 November 2025. An engagement rate over an empty window would be a number about nothing.
22 reactions across 15 posts, in 2 distinct kinds. The most used accounts for 95.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 21 | 95.5% | |
| ❤ | 1 | 4.55% |
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 15 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 22 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 23 October 2024 to 4 November 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.
looking for a new contract. My LinkedIn profile: https://www.linkedin.com/in/alexkonioukhov/
Signed Alex
Data Engineer/Architect JD: Montreal, Canada - ONSITE. Data architect with minimum 10 years of overall experience Design and implement scalable data architecture solutions across cloud and on-prem environments. Lead data modeling efforts for structured and unstructured data systems. Architect and optimize data pipelines using Databricks and Apache Spark. Collaborate with engineering and analytics teams to ensure …
👍1
Signed Anand Verma
Data Scientist Montreal, Canada - ONSITE. Job description: Data scientist with minimum 10 years of overall experience Design and implement advanced predictive models to solve complex business problems. Lead end-to-end data science projects from ideation to deployment. Collaborate with cross-functional teams to integrate models into production systems. Analyze large datasets to extract actionable insights and trend…
👍1
Signed Anand Verma
I have a technical project manager
Signed Vaiinave
Hi Guys Good morning I have multiple job opening Role : .Net Full stack developer Location : Calgary,British Columbia ( Onsite) Location: Vancouver, Calgary,Burnaby, Toronto ( Hybrid) Client : Microsoft/ Infosys Kindly share me resume at [email protected]
👍2
Signed Vaiinave
Hi Everyone, I am hiring in Quebec province, 3 open roles - Software Engineer (Backend, Go, Python), Frontend Developer (Angular 10+, HTML, CSS), DevOps (Kubernetes, Rancher Kubernetes Engine), all these roles are Full-time Perm, and 100% remote. Please let me know if anyone interested, share your resume at [email protected].
👍2
Signed Mahendra Moure
Please let me know
Signed Sameer Khan
Hello. Is anyone looking for system Administrator job in Montreal QC
👍1
Signed Sameer Khan
Bonjour/Hello, Développeur Frontend Senior – CDI, 100% télétravail Nous recrutons un Développeur Frontend Senior (poste permanent, temps plein, à distance). 📧 Envoyez votre CV à [email protected] et nous organiserons rapidement un appel pour en dis-cuter. Merci, Mahendra Senior Frontend Developer – FT Perm, 100% Remote We’re hiring a Senior Frontend Developer (full-time, permanent, remote). 📧 Share your resume at…
👍1
Signed Mahendra Moure
Bonjour / Hello, DevSecOps & DevOps – CDI, 100% télétravail (urgent) Nous recrutons des profils DevSecOps et DevOps (poste permanent, temps plein, à distance). 📧 Envoyez votre CV à [email protected] et nous organiserons rapidement un appel pour en dis-cuter. DevSecOps & DevOps – FT Perm, 100% Remote (Urgent) We’re hiring for DevSecOps and DevOps roles (full-time, permanent, remote). 📧 Share your resume at mahendr…
👍1
Signed Mahendra Moure
👨💻 Hiring: .NET Full Stack Developer 📍 Location: Montreal, QC (Hybrid) ⏳ Contract to Hire | 5+ yrs experience Looking for a skilled .NET Full Stack Dev with: ✅ Strong C# / .NET Core skills ✅ Experience with enterprise microservices & APIs ✅ Azure cloud deployments via CI/CD ✅ Knowledge of Azure services: Service Bus, CosmosDB, API Management, Functions ✅ Familiar with Kubernetes / OpenShift ✅ Bonus: SwaggerHub / As…
👍2❤1
Signed Utsav Kumar
We have multiple requirements from Canada and US, If anyone is interested please email to [email protected] or Call to this number 248 607-6595
👍1
Signed Vjay Goud
Showing the 12 most recent of 20 posts we hold for @job_it_recruit. 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.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“job.IT” (@job_it_recruit), 117 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/job_it_recruit.
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.