Channel
@IT_Outstaff_projects
On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
15,889subscribers
+46 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 |
| Description | IT Outstaffing channel for companies ready to provide developers on a subcontracting model and for independent developers open to remote projects. Let’s code, connect and sparkle 🌟✨💫 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/IT_Outstaff_projects |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:23 | 15,889 | -1 |
| 11 Aug 2026, 20:47 | 15,890 | +4 |
| 10 Aug 2026, 19:18 | 15,886 | +16 |
| 9 Aug 2026, 17:23 | 15,870 | +6 |
| 8 Aug 2026, 17:42 | 15,864 | +1 |
| 7 Aug 2026, 18:46 | 15,863 | +2 |
| 6 Aug 2026, 18:43 | 15,861 | +18 |
| 6 Aug 2026, 03:46 | 15,843 | first reading |
25 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 18 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 25 (6 July 2026 – 11 August 2026) |
| Views total | 37,917 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 15:31 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
We are looking for a Testing Lead (L4) – UiPath Test Automation 🎯 Requirements: • 8+ years of IT experience, including 3+ years in a Test Automation Lead role • 5+ years of hands-on experience with UiPath Test Suite • Strong expertise in designing scalable test automation frameworks • Experience leading end-to-end test automation delivery and mentoring teams • Strong stakeholder management and client-facing communic…
We are looking for a Senior Ceph/Rook-Ceph + Kubernetes Storage Engineer Requirements: - 5+ years of experience in DevOps, SRE, infrastructure, or storage engineering - Deep hands-on production experience with Ceph - Strong experience with Rook-Ceph and Kubernetes storage/CSI - Solid Kubernetes and Linux administration skills - Experience with Ansible and Helm - Monitoring with Prometheus and Grafana - Strong troub…
We are looking for a Middle Flutter Engineer 📍 Berlin, Schöneberg — hybrid, 3 days office / 2 days remote Requirements: - 3+ years of commercial experience with Flutter & Dart - Strong experience building complex production mobile applications - Solid knowledge of state management, APIs, networking, camera/media, and UI/UX - Understanding of performance, offline-first architecture, security, and accessibility - Ex…
We are looking for a Solution Consultant (Salesforce B2B Commerce) Requirements: - 5+ years of commercial experience as a Solution Consultant, Functional Consultant, or Senior Business Analyst in e-commerce implementations - Hands-on experience with Salesforce B2B Commerce (or Salesforce B2C Commerce with strong B2B exposure) - Strong experience in requirements gathering, analysis, validation, and functional docume…
We are looking for a Dev Lead Backend Developer (SFCC / PWA Kit) Requirements: - 5+ years of commercial backend development experience (Node.js preferred) - Must-have commercial experience with Salesforce Commerce Cloud (SFCC) / Composable Commerce - Hands-on experience with PWA Kit (mandatory) - Strong knowledge of JavaScript (ES6+) and Object-Oriented Programming (OOP) - Experience building enterprise-level e-com…
We are looking for an Azure Cloud Architect ☁️ Requirements: • 5+ years of experience designing, developing, and deploying cloud architectures • Strong expertise with Microsoft Azure, including AKS, Azure SQL, APIM, Azure Service Bus, and other PaaS services • Hands-on experience with Docker, Kubernetes, and microservices architecture • Strong understanding of cloud networking, security, and database management • Ex…
In-house (not outstaff) ‼️ We are looking for an Azure DevOps / Data Platform Engineer ☁️ Requirements: • Strong hands-on experience with Azure DevOps and CI/CD pipeline development • Experience with Microsoft Fabric (Warehouse, Data Factory) and Power BI deployments • Solid knowledge of Azure SQL Database, Azure Data Lake Storage (ADLS), Key Vault, and related Azure services • Experience configuring and maintainin…
In-house (not outstaff) ‼️ We are looking for a Middle .NET Engineer (Backend) 💻 🎯 Requirements: - 3+ years of experience in backend development with .NET technologies - Strong experience with C#, ASP.NET Web API, .NET Core, Azure Functions, Entity Framework Core, and T-SQL - Experience designing and developing REST APIs, Microservices, or Serverless architectures - Good understanding of relational and non-relatio…
We are looking for a Senior Backend / Infrastructure Engineer (AWS Serverless)☁️ Requirements: • 5+ years of experience designing, building, and operating production-grade serverless applications on AWS • Strong hands-on experience with AWS CloudFront, API Gateway, Lambda, Cognito, and DynamoDB • Proven experience deploying and managing infrastructure across multiple AWS regions • Solid Infrastructure as Code expert…
We are looking for Senior Python Engineers 🐍 📍 Location: London, UK (Hybrid) Requirements: • 5+ years of Python development experience in enterprise or financial environments • Strong understanding of financial instruments (equities, derivatives, fixed income) and market data • Experience with Python libraries such as NumPy, Pandas, PySpark, Pydantic, PyTorch, or QuantLib • Experience with trading systems, risk eng…
We are looking for a Senior Salesforce UI/UX Designer 🎨 Requirements: • 5+ years of UI/UX design experience with enterprise SaaS products • Strong hands-on experience designing Salesforce UIs — required • Deep knowledge of Salesforce Lightning Experience and SLDS — required • Experience designing Lightning Web Components (LWC) — required • Experience with managed packages or AppExchange products • Strong portfolio o…
In-house (not outstaff) ‼️ We are looking for a Business Development Lead (Software Services) 💼 🎯 Requirements: - 3–6 years of experience in business development or sales within software services / nearshore / outsourcing - Proven experience running full-cycle sales (prospecting → discovery → proposal → negotiation → close) - Strong understanding of nearshore delivery models (dedicated teams, T&M, fixed scope) - E…
Showing the 12 most recent of 25 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 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“IT Outstaff Projects” (@IT_Outstaff_projects), 15,889 subscribers as measured 12 August 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.