Channel
@daily_IT_jobs_update
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
1,200subscribers
-1 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001199442755 |
|---|---|
| Type | Channel |
| Username | @daily_IT_jobs_update |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 25 September 2026 |
| On Telegram | t.me/daily_IT_jobs_update |
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 |
|---|---|---|
| 16 Sept 2026, 15:57 | 1,200 | +1 |
| 12 Sept 2026, 17:21 | 1,199 | -1 |
| 8 Sept 2026, 19:17 | 1,200 | +1 |
| 3 Sept 2026, 08:18 | 1,199 | -1 |
| 31 Aug 2026, 09:03 | 1,200 | -1 |
| 31 Aug 2026, 02:15 | 1,201 | first reading |
20 posts held, back to 26 August 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 1 page of 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 30 August 2026 |
|---|---|
| Posts held | 20 (26 August 2026 – 30 August 2026) |
| Views total | 153 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 02:15 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.
Openings for Quality Analyst – Manual Testing (2-4 yrs) | Bangalore Email: [email protected] We are looking for a Quality Analyst with 2–4 years of hands-on experience in Manual Testing to join our team. The ideal candidate should have a strong understanding of the QA lifecycle and experience working closely with Development and Product teams to ensure high-quality product releases and a seamless user experienc…
We’re Hiring: Manual QA Tester – Work From Home Mansa Infotech is looking for a detail-oriented Manual QA Tester with 1–2 years of experience to join our remote team. Key responsibilities: • Perform manual testing of web and mobile applications • Create and execute test cases and test scenarios • Identify, document and track bugs • Conduct functional, regression, usability and cross-browser testing • Collaborate wi…
🚨 Hiring | #Automation #QAEngineer | #Noida We’re hiring an Automation QA Engineer for a fast-growing product-based SaaS company. 📍 Location: #Noida 💼 Experience: #2–6 Years 🏢 Product/SaaS background preferred 🎯 Interview: #Onsite What you’ll work on: • Automation, API, Web & Mobile Testing • Test case design & UAT • Functional automation & framework enhancements • Shift-left testing & production issue debugging Te…
We're Hiring! Manual Tester – LOS + TCS Bancs (Mandatory) Domain: Banking Experience: 3–5 Years Location: Mumbai. (Serving / Immediate Joiners Preferred) 📩 Send your resume to [email protected]
🚨 We’re Hiring | SDET – Payment Domain 🎯 Looking for: Strong SDET profiles who combine Payment Domain expertise + API Automation + Programming skills to join our team in Bangalore! 🔹 Experience: 2–5 Years 🔹 Location: Bangalore 🔹 Mode: Work from Office 🔹 Notice Period: Immediate to 2 Weeks Must-Have Skills: ✅ UPI / Cards / Wallets / Payment Gateways & Processors ✅ Payment lifecycle – Authorization, Authentication, …
Hiring for Automation Engineer Location - Bangalore Experience - 3-5.5 years Immediate Joiners Core Technical Requirements 3–5 years of hands-on experience in test automation engineering. Strong proficiency in Selenium, WebdriverIO (WDIO) and Playwright with Java, JavaScript/TypeScript. Demonstrated experience practicing Behaviour-Driven Development (BDD) in real production codebases — not just familiarity with the …
We are looking Lead QA Engineer with Expertise in Playwright and Typescript at Crisil Location : #Hyderabad Experience : 8+ years Please DM or share profiles with [email protected]
🚨 We’re Hiring – QA Engineer 🚨 Job Title: QA Engineer 📍 Location: Baner, Pune – Work from Office 🕛 Time: 12:00 PM – 9:00 PM 💼 Experience: 4+ Years ⚡ Notice Period: Immediate Joiners Must-Have Skills: ✅ Manual Testing ✅ Automation Testing ✅ SQL ✅ Selenium or Playwright ✅ Agile & Jira ✅ Mobile Testing ✅ Experience with B2B or B2C applications 📩 Interested candidates can share their updated CV at: dhanshree@ipeopleinf…
Software Testing jobs & Devops Engg job: Automation Test Engineer Role: Automation Test Engineer Experience: 5+ Years Location: Bengaluru / Hyderabad / Pune Type: Contractual (MNC Client) Mandatory Skills: Playwright TypeScript Automation Testing Functional & Regression Testing Test Script Development & Maintenance Test Execution & Analysis Defect Identification & Reporting Interview: Face-to-Face Intervie…
Worked for 9s QA Automation Engineer Experience: 4–7 Years Location: Remote Required Skills: Functional, API & Automation Testing Postman Playwright / Selenium C# / TypeScript / Python Azure GitHub CI/CD Docker AI/LLM, RAG & AI Agent Testing Role Overview: The position is focused on QA automation across functional and API testing, using modern automation tools such as Playwright/Selenium. Candidates sho…
| 209 | We’re Hiring – Senior Automation Test Engineer (SDET) | - | [email protected] | 9 Years | Loc: Bangalore Experience: 5; Notice: Immediate Joiners Preferred | | 342 | Locations: Hyderabad / Chennai / Bangalore / Pune / Chandigarh- Locati | Firstcalli | [email protected] | 9 Years | Loc: s: Hyderabad | | 376 | WE’RE HIRING / ETL TESTING & AUTOMATION | Firstcalli | [email protected] | 9 Years | L…
| 881 | Urgent Hiring – Senior QA Engineer (TOSCA) | Onzestt | [email protected] | 8 Years | Loc: Hyderabad / Bangalore; Notice: Immediate Joiners or candidate | | 882 | We are looking for experienced Senior QA Engineers with strong experti | Onzestt | [email protected] | 8 Years | Loc: Hyderabad / Bangalore; Notice: Immediate Joiners or candidate | | 884 | Hiring: QA Engineer – Agentic AI & Chat / Sierra…
Showing the 12 most recent of 20 posts we hold for @daily_IT_jobs_update. 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 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Daily IT Jobs update” (@daily_IT_jobs_update), 1,200 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/daily_IT_jobs_update.
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.