Channel
@IT_Outstaff_projects
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
16,385subscribers
+542 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001166934710 |
|---|---|
| Type | Channel |
| Username | @IT_Outstaff_projects |
| 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 | 21 October 2026 |
| Measurements held | 44 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/IT_Outstaff_projects |
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 10 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 |
|---|---|---|
| 21 Oct 2026, 13:45 | 16,385 | -1 |
| 20 Oct 2026, 12:45 | 16,386 | +6 |
| 19 Oct 2026, 09:15 | 16,380 | +4 |
| 18 Oct 2026, 08:49 | 16,376 | +10 |
| 16 Oct 2026, 12:16 | 16,366 | +11 |
| 15 Oct 2026, 11:37 | 16,355 | +11 |
| 14 Oct 2026, 14:59 | 16,344 | +4 |
| 9 Oct 2026, 00:00 | 16,340 | +22 |
| 4 Oct 2026, 13:35 | 16,318 | +62 |
| 26 Sept 2026, 02:59 | 16,256 | +105 |
| 19 Sept 2026, 08:37 | 16,151 | +22 |
| 17 Sept 2026, 00:00 | 16,129 | +37 |
| 15 Sept 2026, 02:57 | 16,092 | +6 |
| 13 Sept 2026, 15:37 | 16,086 | +2 |
| 11 Sept 2026, 18:00 | 16,084 | +3 |
| 9 Sept 2026, 05:58 | 16,081 | +22 |
| 5 Sept 2026, 22:41 | 16,059 | +16 |
| 3 Sept 2026, 17:18 | 16,043 | +1 |
| 2 Sept 2026, 10:42 | 16,042 | +7 |
| 1 Sept 2026, 09:34 | 16,035 | first reading |
40 posts held, back to 6 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 55 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 40 posts for this entry, the most recent from 3 September 2026. An engagement rate over an empty window would be a number about nothing.
In-house (not outstaff) ‼️ We are looking for a Senior Frontend Engineer (ReactJS) ⚛️ Requirements: • 5+ years of commercial experience in Frontend Development • Strong proficiency with ReactJS — Hooks, Context API, core principles & ecosystem • Solid experience with JavaScript (ES5–ES7) and TypeScript • Hands-on experience with Next.js • Strong knowledge of HTML5 — semantics, DOM, adaptive & responsive development…
We are looking for a Senior Infrastructure Engineer (GPU Platform) Requirements: • Production experience with multi-node GPU training infrastructure • Strong Linux, containers, CUDA, and NVIDIA GPU stack knowledge • Hands-on experience with NCCL and InfiniBand or RoCE/RDMA troubleshooting • Deep experience with Kubernetes or Slurm • Experience with infrastructure automation and observability • Experience diagnosing …
We are looking for a Senior .NET / AI Engineer 📍 Location: USA or Canada We’re looking for a Senior C#/.NET Engineer to help build AI-enabled migration accelerators and industrialize a large-scale migration program. Requirements: • 7+ years of C#/.NET experience • ASP.NET Core, REST APIs & enterprise integrations • Hands-on experience building production AI applications, AI agents, copilots, or code-generation sol…
We are looking for a QA Automation Engineer 🎯 Requirements: • Strong experience with WebdriverIO • Hands-on experience with BDD / Cucumber • Strong TypeScript or JavaScript skills (TypeScript is preferred) • Experience with Jira, Zephyr, and Confluence • Experience with BrowserStack is a big plus • Experience with Postman for API testing • Ability to optimize, maintain, and scale automation frameworks, not just auto…
We are looking for a Backend Developer w/ SAP Hybris Requirements: • 5+ years of backend development experience • Extensive eCommerce experience with SAP Commerce Cloud / SAP Hybris, Magento, Mirakl, or similar platforms • Strong knowledge of backend technologies such as SAP Commerce Cloud, SAP S/4, Elasticsearch/Solr, Redis, MSSQL, MySQL, and PostgreSQL • Strong Java and Spring Boot experience • Experience with clo…
We are looking for a Middle Power Platform Engineer Requirements: • 2+ years of hands-on experience with Microsoft Power Platform • Experience delivering enterprise or business-critical Power Platform solutions • Hands-on experience with Canvas Apps, Model-Driven Apps, Power Automate, and Dataverse • Good knowledge of Power Fx, Power Platform connectors, REST API integrations, and Microsoft 365 • Experience integrat…
We are looking for a Lead Data Engineer 📈 Requirements: • 5+ years of experience in Data Engineering, Analytics Engineering, or a related field • Strong SQL skills and experience with complex data transformations • Hands-on experience with modern data platforms such as BigQuery, Databricks, or Snowflake • Strong experience with ETL/ELT, data orchestration, and data warehousing/lakehouse solutions • Experience with A…
We are looking for a Senior AQA Engineer (Java) Requirements: • 4+ years of commercial experience in QA Automation • 3+ years of hands-on experience writing automated tests with Java • Strong experience designing end-to-end automated tests for mobile applications and microservice APIs • Practical experience using AI coding assistants such as Claude Code, Cursor, or GitHub Copilot • Strong SQL skills with PostgreSQL …
We are looking for a Senior Backend Engineer (Go) Requirements: • 5+ years of backend development experience with Golang (willingness to work with Ruby) • Strong experience with PostgreSQL and NoSQL databases such as Redis • Solid knowledge of RESTful APIs and HTTP • Strong understanding of system architecture, high-load applications, and concurrency • Experience building and maintaining backend microservices • Expe…
We are looking for an Azure DevOps Engineer (part-time) Requirements: • 3+ years of experience in DevOps • Strong hands-on experience with Microsoft Azure • Good English communication skills • Availability to work 3 full days per week: Wednesday, Thursday, Friday 📩 Send your CV: [email protected]
We are looking for a Backend Developer w/ SAP Hybris Requirements: • 5+ years of backend development experience • Extensive eCommerce experience with SAP Commerce Cloud / SAP Hybris, Magento, Mirakl, or similar platforms • Strong knowledge of backend technologies such as SAP Commerce Cloud, SAP S/4, Elasticsearch/Solr, Redis, MSSQL, MySQL, and PostgreSQL • Strong Java and Spring Boot experience • Experience with clo…
We are looking for a Frontend Developer Requirements: • 5+ years of frontend development experience • Expert knowledge of JavaScript, TypeScript, React.js, and Next.js • Strong eCommerce architecture experience; SAP Commerce, Magento, Mirakl, or Salesforce Commerce Cloud is a plus • Hands-on experience with headless, composable, and API-driven architectures • Experience building BFF/API layers with Node.js or Next.j…
Showing the 12 most recent of 40 posts we hold for @IT_Outstaff_projects. 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.
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 11 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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“IT Outstaff Projects” (@IT_Outstaff_projects), 16,385 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/IT_Outstaff_projects.
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.