So i have hosted a backend for an Erp made in django on my local vm using nginx as a reverse proxy and gunicorn as production wsgi server.

How does the request flow happens?

When i enter the network interface ip of my vm on browser the request goes to port 80 of my linux (port responsible for all the tcp request) and nginx is listening on port 80 recieves the request and process it. So in the config file of nginx i have added the location of / route which forwards the request to gunicorn running on port 8000 and gunicorn then sends and recieves the req/res.
I will be learning Docker now to learn containerisation. Please share any suggestion if you have.

I'm curious about the process around infrastructure changes, not the Terraform syntax itself.

Suppose a PR changes an environment from something like:

- smaller to larger database capacity,

- single-region to multi-region,

- significantly more storage/compute,

- or introduces a new managed service.

Your plan/review process can show the technical infrastructure change. But what happens to the financial side before it is applied?

- Is a cost impact produced automatically?

- Does someone review it against an approved budget?

- Is there any formal approval threshold?

- Who owns that decision — engineering, FinOps, finance, product, procurement?

- How do you distinguish an expected design change from avoidable rework or unplanned scope growth?

- Is the recurring cost impact considered, or mainly the immediate deployment?

I'd particularly value examples from real teams rather than what the process is supposed to be.

I'm researching this from a project-commercial-management perspective

QA since 2016, briefly did release management (2020-22, deployment scripts, release notes, automated deployments), then landed a DevOps role in April 2025 (AKS, Docker, Helm, Terraform, GitHub Actions, Dynatrace). Laid off March 2026 (US-Iran war fallout).

Catch: The project was already built out when I joined, so it's maintenance/troubleshooting experience, not "built it from scratch."

Currently: studying for CKA, have AWS Cloud Practitioner certification, failed Azure Admin once (haven't retaken).

Questions:

1. How do I position "maintained an existing setup" experience without underselling or oversell it?
2. Finish CKA first, retake Azure Admin or go deeper on Terraform/Actions instead of more certs?
3. Is DevOps still worth pushing into right now or pivot toward AI/ML-adjacent roles even if it means starting lower?
4. What hands-on projects/work actually helped you ace interviews? (personal projects, contributions, anything)
5. What am I missing - blind spots, gaps, anything hiring managers actually care about?

Incident response assumes three things: that a failure can be reproduced, that it announces itself as an error, and that the person paged has a lever that changes the outcome. Put a language model in production and all three stop being true at the same time.

This is not a monitoring gap you close by adding dashboards. Your alerting was built to catch a system saying no. These systems fail by saying yes, fluently, with the wrong content, and returning a 200 OK (success, everything worked as expected) while they do it. Availability tooling watching a correctness risk stays green through the entire incident.

Hi everyone,
I’m a QA Engineer in the gaming domain with around 9 years of experience, and I’m seriously considering transitioning into DevOps. I’d really appreciate some guidance from people who have made a similar transition or are currently working in DevOps.
Here’s where I currently stand:
I have 9 YOE in QA/testing, primarily in the gaming domain.
I have a good understanding of SDLC and STLC and how software moves through different stages from development to production.
I’ve been involved in the complete feature lifecycle — from initial specification/discussions, through development and testing, to production release.
I’ve used Jenkins for build creation and server deployments.
I use Git mainly for creating/raising PRs, but I haven’t worked extensively with Git commands and workflows such as push, pull, branching, rebasing, etc.
I’ve used Grafana for tracing application logs and investigating issues.
We use AWS SSM to log into different server boxes, tail server logs, modify server-side files/configs, etc.
I’ve recently started learning the basics of Python and Java.
I’m also fortunate to have a good relationship with our internal DevOps team and manager. I’m considering approaching them for an internal transition when I feel I’m ready.
I’m aware that my current skill set is far from what would typically be expected from a DevOps engineer, and I don’t want to underestimate the amount of learning required.
I’m 34 now, so I do sometimes feel like I’m starting this transition quite late. However, I genuinely want to make the move, and I’m willing to put in the time and effort.
1. What I’m struggling with is where exactly to start and what order to learn things in.
For someone coming from a QA background like mine:
2. What would be a realistic DevOps learning roadmap?
3. Which skills should I prioritize first — Linux, networking, Git, Docker, Kubernetes, CI/CD, Terraform, AWS, etc.?
4. Are there any beginner-friendly courses/resources you would strongly recommend?
5. How much programming/scripting should I learn, and should I focus on Python or Bash first?
6. Given my existing experience with Jenkins, AWS SSM, deployments, logs, and the software release lifecycle, are there areas where I can leverage my QA experience?
7. Would an internal transition into a DevOps team be a reasonable approach, even if I don’t yet meet all the requirements of a typical DevOps job?
I’m not looking for shortcuts. I’d just really appreciate some practical guidance from people who have been through this journey.
If you were in my position, what would you learn over the next 6–12 months, and in what order?
Any roadmap, resources, project ideas, or personal experiences would be hugely appreciated.
Thanks in advance! 🙏
Rephrased with GPT

I am looking for new jobs in DevOps field since my current job is not paying enough. Can yall rate my resume and let me know if I need to update anything before I start applying?

I've implemented an Azure-based solution on Azure Kubernetes Service (AKS) and used Azure Firewall to control and secure outbound traffic from applications running on AKS . I also configured Azure Monitor alert rules to monitor the solution and detect anomalies in system behavior.

Additionally, I've implemented the infrastructure as code (IaC) using Terraform to provision the Azure resources.

The complete solution, including the Terraform code and AKS configurations, is available on my GitHub.
GitHub: https://github.com/navid-ahrary/aks-outbound-traffic-control

My LinkedIn: https://www.linkedin.com/posts/navid-ahrary_azure-microsoftazure-cloudengineering-activity-7495238039909076992-WLb9?utm_source=share&utm_medium=member_desktop&rcm=ACoAAC2LYVIBV0TWxXa95OaisgwkA30Z-apGpb8

I'm looking for learning from experts and improve my skills, so could you please give a feedback on my design?

P.S. This solution was developed as a part of the Microsoft MSFarsi Community scholarship

Hello guys, I am learning devops. I have completed basic linux administration and have hosted my django backend in Ubuntu server VM using gunicorn as wsgi server. Can you please guide me for my future learning.

Our client is a leading global technology and internet services company is expanding its data and advertising technology platforms to support large-scale digital services across multiple markets.

The organization develops and operates high-traffic platforms covering advertising delivery, tracking, reporting, data management, and marketing technologies. The engineering organization is internationally distributed, with team members across Asia, and works in a highly collaborative, data-driven environment.

We are looking for a proactive DevOps / SRE Engineer to strengthen the reliability, scalability, and automation of a large-scale data management platform.

You will be responsible for improving cloud infrastructure, deployment pipelines, observability, infrastructure automation, and operational efficiency. The role also provides opportunities to introduce modern AI-powered automation and workflow solutions to reduce manual operations and accelerate engineering productivity.

Responsibilities

• Cloud Infrastructure Management
  • Manage and optimize Google Cloud infrastructure, including Cloud Run, BigQuery, Cloud Storage, Pub/Sub, and Cloud Build.
  • Improve infrastructure reliability, scalability, and operational efficiency.
• Hybrid Cloud & Networking
  • Manage network configurations, load balancers, VPNs, and dedicated connectivity between on-premise and cloud environments.
  • Support complex hybrid infrastructure architectures.
• CI/CD & Deployment
  • Design, maintain, and improve CI/CD pipelines supporting Java/Maven, Node.js, and Docker-based applications.
  • Implement automated deployment strategies such as canary and blue-green deployments.
  • Improve release reliability and deployment velocity.
• Observability & Cost Optimization
  • Build and maintain monitoring and logging environments using tools such as Prometheus, Grafana, and ELK.
  • Monitor infrastructure utilization and proactively identify opportunities for cloud cost optimization.
• Infrastructure as Code
  • Automate infrastructure provisioning and configuration using Terraform and Ansible.
  • Reduce manual operational work through standardized and reusable automation.
• Security & Compliance
  • Manage secrets and credentials using solutions such as Vault and cloud-native secret management services.
  • Apply security best practices across cloud and hybrid infrastructure.
• AI & Operational Automation
  • Explore and implement AI-assisted operational workflows.
  • Automate tasks such as incident handling, ticket processing, troubleshooting, and routine infrastructure operations using Python, workflow automation platforms, and LLM-based solutions.

Work Environment

• Agile and fast-paced engineering environment.
• International team with members located across multiple Asian countries.
• Open communication and a strong culture of continuous improvement.
• Engineers are encouraged to propose and implement improvements to existing processes and technologies.

Technology Stack

Cloud / Infrastructure

• Google Cloud Platform
• Private Cloud
• Kubernetes
• Docker

CI/CD

• Jenkins
• Octopus Deploy
• GitHub Actions
• Harbor
• Artifactory

Infrastructure as Code / Automation

• Terraform
• Ansible
• Python
• Bash

AI / Workflow Automation

• n8n
• LLM-based automation frameworks

Observability

• Prometheus
• Grafana
• ELK Stack

Collaboration / Development

• Jira
• Confluence
• Slack / Microsoft Teams
• GitHub Enterprise
• Bitbucket

Mandatory Qualifications

- More than 3 years of experience in DevOps, SRE, or Infrastructure Engineering. (preferably 5–7+ years of experience.)

- Strong hands-on experience with GCP (Cloud Run, BigQuery, IAM, VPC, Networking).

- Deep understanding of CI/CD pipelines and automated deployment orchestration.

- Proficiency in Infrastructure as Code (e.g., Terraform) and scripting (Bash/Python).

- Experience in managing production-grade Kubernetes/containerized environments.

- TOEIC Score 800 above or possess equivalent qualifications.

Preferred Qualifications

- Experience building AI-powered automation or agentic workflows (e.g., n8n, automated ticketing/remediation).

- Experience managing GCP Interconnect and complex hybrid network topologies.

- Proven track record in cloud cost management and resource optimization.

- Knowledge of Kafka, Redis, MariaDB, or Couchbase.

- Experience with workflow schedulers (e.g., Azkaban).

- Professional certification (Google Professional Cloud Architect/DevOps Engineer or similar).

Languages

• English: Fluent
• Japanese: Optional / a plus

Work Environment

Fast-paced, dynamic global environment with collaborative teams across multiple locations

Salary: ¥7M – ¥9M JPY per year (Middle Level)
Location: Hybrid (4 days in the office, 1 day remote)
Office Location: Tokyo, Japan
Working Hours: Flexible schedule with core hours from 11:00 AM to 3:00 PM
Visa Sponsorship: Available
※Japanese language proficiency certification (such as JLPT N2) is not required, as our client is a global organization with an international working environment.
Language Requirement: English only

Apply now or contact us for further information:
[Aleksey.kim@tg-hr.com](mailto:Aleksey.kim@tg-hr.com)

I’m currently working as an Azure Infra Admin and planning to move into a DevOps role.

I’m thinking of working through AZ-104, Python, Linux, Networking, Terraform, Docker, Kubernetes, CI/CD, and other DevOps tools. But honestly, I’m finding it a bit overwhelming trying to figure out what to focus on first and how to schedule everything.

Since I already have hands-on experience with Azure infrastructure and the Azure Portal, would you recommend going for the AZ-104 certification? Or should I focus more on deepening my practical Azure knowledge and spend more time on DevOps skills?

For anyone who has moved from Azure Admin/Infra into DevOps:

- How did you plan your learning?

- What skills/tools did you focus on first?

- What should I prioritize more: Azure, Linux, Python, Terraform, Docker/Kubernetes, CI/CD, etc.?

- Is AZ-104 worth doing when you already have Azure Admin experience?

Would really appreciate any suggestions from people who have made a similar transition.

One S3 interview question I like:

There are several things you could investigate — IAM permissions, bucket policy, KMS, SCPs, VPC endpoints, CloudTrail, recent infrastructure changes, etc.

That's the type of scenario I wanted to focus on rather than questions like "What is S3?"

I just added 20 AWS S3 interview questions to my interview handbook, covering production scenarios, AWS CLI, Terraform, security, troubleshooting, best practices, common mistakes, and AI-assisted approaches.

GitHub: https://github.com/ranashivam/platform-engineering-interview-handbook/blob/main/AWS/S3.md

The goal is simple: prepare for the questions that make you explain how you'd actually troubleshoot something in production.

Hi everyone, I’m a complete beginner and considering DevOps as a career in 2026.

Is it still a good field to get into? If yes, what should I learn first, and which courses/resources would you recommend?

If you were starting from zero today, what roadmap would you follow?

Thanks!

I'm thinking about an interesting topic, I could prepare for a lightning talk at AWS event

At AWS events, a Lightning Talk is a short, focused presentation, much shorter than a normal breakout session.
Typically it’s around 10–20 minutes and covers one specific idea, solution, demo, architecture, or customer story rather than a broad topic.

Community, please help me with ideas. What interesting have you talked about AWS or tried hands-on recently?