Telegram RegisterThe public register of Telegram
Telegram profile photo for DevOps Jobs/Ads - DoNotJoin

Channel

DevOps Jobs/Ads - DoNotJoin

@securedevopsjob

On this record: Growth · Engagement · Posts · Citations · Cite this entry

75subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001497195110
TypeChannel
Username@securedevopsjob
Created2 November 2020measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live28 August 2026
Measurements held3
Confirmed unchanged3 times, most recently 28 August 2026
On Telegramt.me/securedevopsjob

Growth

747574.57 August 2026 — 74 subscribers9 August 2026 — 74 subscribers15 August 2026 — 75 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 74–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 06:1975+1
9 Aug 2026, 22:0174no change
7 Aug 2026, 14:4274first reading

Engagement

13 posts held, back to 2 November 2020the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 13 posts for this entry, the most recent from 24 January 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Jan 2024, 12:11 UTC351 viewsread 9 August 2026

AltexSoft is currently seeking a talented Senior Azure DevOps Engineer. Tech stacks-Azure( must have), AWS, Kubernetes Work Model- Fully remote Minimum of 4 years of experience Location- Portugal, Turkey, Poland, and Georgia If you're interested, please send your resume and LinkedIn URL to [email protected] with the job title as subject Please use the link below for more information about the compan

24 Oct 2021, 06:43 UTC527 viewsread 9 August 2026

Greetings. I am hiring for Security Engineer Work Location: Cyberjaya, Malaysia Status: Permanent Full Time (Onsite/Remote) Industry: FinTech Please apply if you match below requirements: ☑️ Experience with Linux and Windows operating systems, modern programming languages, and cloud environments like AWS ☑️ Familiarity with the implementation of security controls and best practices ☑️ Understanding of secure applic

10 Nov 2020, 19:21 UTC518 viewsread 9 August 2026

https://sken.ai/ Easily build DevSecOps CI/CD pipelines with a bunch of open-source tools integrated. Intelligent tool that automatically reads and understands your code, selects best code scanners and reports vulnerabilities. SAST/DAST/MAST/SCA/Container scanning/License compliance/Secrets Detection

2 Nov 2020, 15:46 UTC454 viewsread 9 August 2026

These four positions have the relocation package support (visa sponsorship, travel tickets, accomodation 1st month, etc for all the family)

2 Nov 2020, 15:17 UTC434 viewsread 9 August 2026

https://www.epam.com/careers/job-listings/job.50485.systems-architect_malaga_spain?utm_source=invite&utm_medium=web&utm_content=job_post_link&utm_term=rfr_WFhYWDE4NTRlMGMxLTViMjUtNDllMC1iZGQ1LWJlZDI5MDRjYzYxZlhYWFg_srcid_2

2 Nov 2020, 15:17 UTC341 viewsread 9 August 2026

https://www.epam.com/careers/job-listings/job.44651.senior-devops-engineer_malaga_spain?utm_source=invite&utm_medium=web&utm_content=job_post_link&utm_term=rfr_WFhYWDE4NTRlMGMxLTViMjUtNDllMC1iZGQ1LWJlZDI5MDRjYzYxZlhYWFg_srcid_2

2 Nov 2020, 15:16 UTC273 viewsread 9 August 2026

https://www.epam.com/careers/job-listings/job.44055.senior-application-support-engineer-analyst_malaga_spain?utm_source=invite&utm_medium=web&utm_content=job_post_link&utm_term=rfr_WFhYWDE4NTRlMGMxLTViMjUtNDllMC1iZGQ1LWJlZDI5MDRjYzYxZlhYWFg_srcid_2

2 Nov 2020, 15:15 UTC204 viewsread 9 August 2026

https://www.epam.com/careers/job-listings/job.50505.devops-architect-with-gcp-expertise_malaga_spain?utm_source=invite&utm_medium=web&utm_content=job_post_link&utm_term=rfr_WFhYWDE4NTRlMGMxLTViMjUtNDllMC1iZGQ1LWJlZDI5MDRjYzYxZlhYWFg_srcid_2

Showing the 12 most recent of 13 posts we hold for @securedevopsjob. 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.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“DevOps Jobs/Ads - DoNotJoin” (@securedevopsjob), 75 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/securedevopsjob.

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.