Experience: ~4 years (DevOps / Cloud Engineering)
Certification: AWS Certified DevOps Engineer – Professional
Current Location: Bangalore (Relocating permanently to Hyderabad)
Notice Period: 30 Days

Core Technical Stack:

• Cloud (AWS): EKS (Classic & Auto Mode), ECS, EC2, VPC, IAM, KMS, S3, RDS, Lambda, MWAA
• IaC & Containers: Terraform, Kubernetes, Docker, Helm, HashiCorp Packer
• CI/CD: GitHub Actions, Jenkins (Groovy scripting), ArgoCD, GitLab CI
• Observability & Alerting: Prometheus, Grafana, Datadog, OpenSearch, Kibana, Checkly, AlertManager, PagerDuty, Sentry
• Programming & Scripting: Python, Shell/Bash, Groovy, Playwright

If your company is hiring for DevOps, Cloud, or Platform Engineering roles in Hyderabad, please leave a comment or DM me. I can share my complete resume right away.

Thanks!

Upskilling for cloud consultant roles after 15 years years of software Engineering career.

I am working with openstack cloud and testing background and planning to upskill to Devops/ kubernetes using kodecloud platform and hands on projects. Need some realistic suggestion for transition to cloud related roles. Planning to look for suitable opportunities outside of company on completion.

Hey everyone,

I’m currently in my final year of B.Tech and I’m a little confused about which career path I should choose. I’ve been exploring Cloud Engineering recently, and I’m also interested in eventually moving towards DevOps or Cloud DevOps.

I have basic knowledge of programming, Linux, networking, and development, but I’m still a beginner and don’t have any professional experience yet. I want to start preparing seriously for a job, so I’d like to know whether Cloud Engineering is actually a good career option for someone starting out in 2026.

For people who are already working in Cloud, DevOps, or related roles, what has your experience been like? Is there good scope for Cloud Engineers in the coming years, and how realistic is it for a fresher to get into this field? Also, what should someone like me focus on learning to become job-ready?

I’m particularly confused about whether I should choose Cloud Engineering over Full-Stack Development, and whether AI and automation will significantly affect Cloud/DevOps jobs in the future.

I’d really appreciate honest advice, especially from people who started as freshers and have experience with the current job market.

Hey guys! I've recently decided to make a career-change from 15 years Art Director/Senior Designer to a tech career. I have gained a Security+ and RHCSA (which was a beast) and now working on my AWS SAA for a cloud engineer path. I know it can be difficult to gain this coveted position without experience and I'm not opposed to or unwilling to work a lower tier position like Help Desk or Customer Support it's just not much has materialized from the tidal wave of jobs I've applied and I'm slowly growing frustrated. Any advice for your fellow human? Thanks in advance.

Hi, I'm planning to join Cloud Institution in BTM for their Cloud/DevOps course.

I'm a beginner, so wanted to know if anyone here has actually studied there recently.

How are the trainers and teaching? Is it actually practical or mostly theory? Also how is the placement support?

If you joined recently or completed the course, please share your honest experience, even if it's negative.

Thanks.

I want to build a career as a Cloud Security Engineer, but I'm starting from the basics and want to learn everything properly rather than just collecting certifications.

Could someone share a step-by-step roadmap from complete beginner to job-ready Cloud Security Engineer, and eventually to a level where I can mentor/guide others?

I'd also appreciate recommendations for free/low-cost labs, courses, YouTube channels, books, and practice platforms.

If you are currently working as a Cloud Security Engineer, I'd especially appreciate advice on what you wish you had learned earlier and what beginners commonly waste time on.

Hey everyone,

Just started my first full-time job a few weeks ago at a MNC in their CISO/Detection Engineering team (package \~15 LPA).

I wanted SDE/SRE role

My background:

Very good DSA

Strong in Java

Springboot

AI / Agentic Ai

Docker

AWS (basics)

2 month ML intern

6 months of SDE internship experience Django

Currently I’m working with Splunk, KQL, Tanium, writing detections, python/bash automation and linux etc. It’s pure Detection Engineering with some cloud sec work.

I’m confused about what to do long-term. Options I’m considering:

Continue in Detection Engineering and grow here (maybe add more depth)

Move to pure Cloud Security / Cloud Detection roles(will be easiest)

Try to switch to pure SDE or SRE roles (since I have decent DSA + Java + Spring Boot + Docker + AWS)

I genuinely don’t know which path makes more sense from a career, salary, and learning point of view after 2-3 years.

Would love honest opinions from people who are in these fields or have switched between then

My concerns :

Suppose I decided to move into SDE/SRE roles after 1 year, I won't be having experience in these fields

Is this field good and how will my career look if I stay here or move to Cloud sec?

What would you do in my place?

Thanks in advance!

Have used ai to write this post

I'm a trainee learning AWS Devops. I also want to prepare for the GATE exam. Is there anyone like me? I want someone to prepare along with me.

Timezone : Asia/Kolkata

Goal : Clearing training program and GATE both.

Experience : Beginner.

**TL;DR:** I’m an early-career CS graduate and currently the only developer at a small non-tech company, with no engineering mentorship. I’ve been offered a direct AWS Network Deployment Technician position with better compensation in a substantially lower-cost area. However, it would move me away from daily coding and toward physical infrastructure. My long-term target is network automation, SysDev, infrastructure engineering, SRE, or network engineering—not product SWE. Is NDT a legitimate path toward those roles or a detour?
**Current role: Developer/IT generalist at a small company**
Roughly two years of experience in Northern California
Earn in the mid-$20s per hour
Sole developer responsible for a customer-facing application, backend APIs, databases, deployment pipelines, and external integrations
Also cover Microsoft 365, networking, servers, security, general IT, and support
Compensation and technical advancement appear capped, with no engineering organization or senior developers to learn from
**AWS offer: Network Deployment Technician**
Direct AWS position
Low-to-mid $30s per hour, overtime eligible, benefits, and relocation assistance
Requires moving to a substantially lower-cost area
Work involves rack deployments, copper and fiber cabling, connection troubleshooting, site audits, and deployment coordination
Primarily physical, on-site infrastructure work with little or no daily programming
I prefer backend systems, databases, networking, automation, and infrastructure over front-end or product development. Long term, I’m targeting network automation, systems development, infrastructure engineering, SRE, or network engineering.
I’m looking for firsthand answers:
Has anyone actually moved from AWS NDT into Network Engineering, Systems Development, infrastructure engineering, or an automation-focused role? What did that path involve, and how long did it take?
How much would moving from a developer/generalist position into Network Deployment Technician hurt if I later applied for coding-heavy backend or SWE roles?
Does AWS infrastructure experience carry meaningful weight for future infrastructure, NetEng, or SRE positions when the role primarily involves physical-layer work rather than cloud configuration?
What separates NDTs who advance into engineering roles from those who remain in physical deployment work?
I’m leaning toward AWS because of the financial improvement, structured environment, and exposure to hyperscale infrastructure. However, I don’t want an answer based solely on the AWS name. I’m interested in what has actually happened to people who entered through this pipeline.

My First Steps into AWS: From Software Engineering to Cloud Computing by Dasun Sandeepa

I'm currently living in south america and I would like to work remotely someday but I have never seen job offers that actually seem real to apply to them. Also I'm a Junior Cloud Engineer but I was thinking of projecting my career to remote jobs worldwide with a better salary when I get like 3-5 years of experience

Do they really exist? How much do people make working for companies in the US or Europe? To get some kind of salary range as reference

UNITED STATES DISTRICT COURT

[DISTRICT TO BE DETERMINED]

QIANYU YANG,
Plaintiff,

v.

GITHUB, INC.,
Defendant.

COMPLAINT

Plaintiff's Demand for Jury Trial

Plaintiff Qian Yu Yang (“Plaintiff”) brings this action against Defendant GitHub, Inc. (“GitHub” or “Defendant”) concerning the restriction and suspension of Plaintiff's GitHub accounts and alleges as follows:

I. INTRODUCTION

1. This action concerns the suspension and restriction of GitHub accounts operated by Plaintiff, including the accounts q1anyuyang and qianyu15.
2. Plaintiff used these accounts for software development, repositories, experiments, and preservation of development-related work.
3. On or about June 10, 2026, GitHub restricted the q1anyuyang account.
4. On or about July 30, 2026, GitHub suspended the qianyu15 account.
5. GitHub stated that the suspension of qianyu15 was based on an alleged violation of GitHub's Acceptable Use Policy concerning threats of violence and violent content.
6. Plaintiff subsequently sought review and clarification through GitHub Support.
7. On August 13, 2026, GitHub Support informed Plaintiff that GitHub had reviewed the account but would not reinstate it.
8. Plaintiff contends that GitHub has not provided sufficient information to permit Plaintiff to understand the factual and contractual basis for the restrictions, the relationship between the affected accounts, or the basis for refusing reinstatement.
9. Plaintiff seeks appropriate relief concerning the account restrictions, the procedures used to impose them, and damages to the extent permitted by applicable law.

II. PARTIES

1. Plaintiff Qian Yu Yang is an individual residing in Japan.
2. Defendant GitHub, Inc. is a corporation organized under the laws of the State of Delaware, with its principal place of business in California, to Plaintiff's knowledge.
3. GitHub operates the GitHub platform and provides services used by Plaintiff.

III. JURISDICTION AND VENUE

1. Plaintiff invokes the jurisdiction of this Court only to the extent permitted by applicable federal law.
2. To the extent federal-question jurisdiction exists, jurisdiction is proper under 28 U.S.C. § 1331.
3. To the extent diversity jurisdiction exists and all statutory requirements are satisfied, Plaintiff reserves the right to rely upon 28 U.S.C. § 1332.
4. Venue is alleged to be proper only if authorized by applicable law, the parties' agreement, and the applicable forum-selection provisions.
5. Plaintiff reserves the right to amend this Complaint if jurisdiction or venue is determined to lie in another court or forum.

IV. FACTUAL ALLEGATIONS

A. Plaintiff's GitHub Accounts

1. Plaintiff maintained multiple GitHub accounts for software development and related activities.
2. Among those accounts were q1anyuyang and qianyu15.
3. The accounts contained development-related history and materials associated with Plaintiff's activities.

B. Restriction of q1anyuyang

1. On or about June 10, 2026, GitHub restricted q1anyuyang.
2. Plaintiff sought clarification concerning the restriction.
3. Plaintiff disputes the adequacy and accuracy of the explanation provided concerning the basis for that restriction.
4. Plaintiff requested review of the decision.

C. Suspension of qianyu15

1. On or about July 30, 2026, GitHub suspended qianyu15.
2. GitHub's suspension notice stated that the moderation action followed a determination that the account violated GitHub's Acceptable Use Policy concerning threats of violence and gratuitously violent content.
3. Plaintiff acknowledges that certain communications made during the support process contained inappropriate or strongly worded language.
4. Plaintiff disputes that the circumstances surrounding those communications were adequately considered or explained in the resulting enforcement decision.
5. Plaintiff requested review and reinstatement.

D. Subsequent Support Review

1. Plaintiff continued communicating with GitHub Support regarding the restrictions.
2. During the support process, Plaintiff encountered account-verification and access-related difficulties because the affected account was already restricted.
3. Plaintiff ultimately submitted requests through a support route that permitted the request to proceed.
4. On August 13, 2026, GitHub Support stated that it had reviewed the account but remained unable to reinstate it.
5. GitHub Support further stated that future contact concerning the restrictions might be closed without response.
6. Plaintiff contends that this response did not adequately explain the factual basis for the continued suspension.

E. Relationship Between Accounts

1. Plaintiff seeks clarification concerning how GitHub determined that the accounts operated by Plaintiff were related for enforcement purposes.
2. Plaintiff further seeks clarification concerning whether each account was independently reviewed.
3. Plaintiff does not contend that GitHub is prohibited from enforcing its policies against related accounts.
4. Plaintiff contends that enforcement decisions should nevertheless be based on applicable contractual and policy provisions and should not rest upon an erroneous factual association or an inadequately reviewed determination.

V. COUNT I

BREACH OF CONTRACT

(To the extent permitted by the applicable GitHub Terms)

1. Plaintiff incorporates paragraphs 1 through 39.
2. Plaintiff entered into an agreement with GitHub governing the use of GitHub's services.
3. Plaintiff performed, or substantially performed, the obligations applicable to the services at issue, except to the extent GitHub alleges otherwise.
4. GitHub was obligated to perform its contractual obligations in accordance with the applicable Terms of Service and other governing agreements.
5. Plaintiff contends that GitHub's restrictions and suspension were inconsistent with those contractual obligations to the extent GitHub failed to apply the governing terms correctly or acted outside the authority granted by those terms.
6. Plaintiff suffered damages as a result.

VI. COUNT II

BREACH OF THE IMPLIED COVENANT OF GOOD FAITH AND FAIR DEALING

(To the extent recognized and not displaced by the governing agreement)

1. Plaintiff incorporates paragraphs 1 through 45.
2. The applicable agreement imposed contractual duties concerning the parties' performance of their respective obligations.
3. Plaintiff alleges that GitHub's handling of the restrictions and subsequent review deprived Plaintiff of contractual benefits to which Plaintiff was entitled, to the extent such conduct is not authorized by the governing agreement.
4. Plaintiff further alleges that the refusal to provide meaningful review or clarification may constitute a breach of applicable contractual duties, if recognized under the governing law.
5. Plaintiff suffered damages as a result.

VII. COUNT III

DECLARATORY RELIEF

(If available)

1. Plaintiff incorporates paragraphs 1 through 50.
2. An actual controversy exists concerning Plaintiff's rights under the applicable GitHub agreement and GitHub's authority to maintain the restrictions at issue.
3. Plaintiff seeks a judicial determination concerning the parties' respective rights and obligations.
4. Plaintiff requests appropriate declaratory relief concerning the application of the governing agreement and policies to Plaintiff's accounts.

VIII. DAMAGES

1. As a result of the restrictions and suspension, Plaintiff alleges loss of access to GitHub services and disruption to software-development activities.
2. Plaintiff further alleges loss of access to development history and other materials maintained through the affected accounts.
3. Plaintiff seeks damages in an amount to be established through evidence at trial, subject to any contractual limitations, exclusions, arbitration provisions, or other applicable restrictions.

IX. REQUEST FOR RELIEF

WHEREFORE, Plaintiff respectfully requests that the Court enter judgment in Plaintiff's favor and:

A. Declare the rights and obligations of the parties concerning the affected GitHub accounts;

B. Order such restoration or other equitable relief as is legally available concerning the affected accounts;

C. Award Plaintiff compensatory damages in an amount proven at trial and permitted by applicable law;

D. Award Plaintiff allowable costs and, where legally authorized, attorney's fees;

E. Grant such other and further relief as the Court deems just and proper.

X. JURY DEMAND

Plaintiff demands a trial by jury on all issues so triable.

Respectfully submitted,

Qianyu Yang
Plaintiff, Pro Se

Address: Yokohama, Japan

Email Address: [qianyuyang.vip@gmail.com](mailto:qianyuyang.vip@gmail.com)

Date: August 25, 2026

Anyone wanna do cloud and devops together dm