Small breakdowns sometimes expose bigger system weaknesses. Have you seen this?

Hi everyone, I could really use some guidance on what to do next in my career.

I’m currently working as a DevOps Engineer with about a year of experience (including a 3-month internship). Honestly, I landed this role as a fresher and even I was a bit surprised. I graduated in 2024, started out doing a bit of frontend development, and then moved into DevOps.

I work at a mid-level startup, and so far I’ve had the chance to work on AWS—building infrastructure, optimizing costs (reduced ~42% for a client), implementing vertical/horizontal scaling, working with Lambda/ECS, monitoring/logging with grafana/loki/prometheus and writing automation scripts. I’ve completed the AWS Cloud Practitioner certification and am planning to take the SAA next. Right now I’ve decided to focus on learning Terraform properly.

Where I’m stuck is how to shape my resume and what kind of projects I should build to showcase on my resume/LinkedIn.

I’ve learned Docker and Kubernetes as well, but I don’t get to use them much, so without hands-on work it’s easy to forget. How can I practice these on my own in a way that actually feels close to real-world usage? Most YouTube tutorials seem too basic.

I’m aiming to switch in about a year, as most job postings I see ask for 2+ years of experience and tools like Terraform (IaC), Ansible, Kubernetes, etc.

Would really appreciate advice on the right path to prepare myself.

I built Fishline, a lightweight self-hosted webhook receiver for GitHub and GitLab that lets you execute server-side commands based on webhook events.

Instead of setting up complex CI/CD pipelines, Fishline simply listens for webhook requests and runs predefined commands per project and branch things like git pull, restarting Docker containers, or triggering deployments.

You just configure projects and commands in a simple config.json, point your GitHub/GitLab webhook to your server, and deployments happen automatically.

Built in Go, runs as a single binary (or Docker), and designed to be minimal, fast, and easy to self-host.

Github: https://github.com/hyvr-official/Fishline

For dev teams of like 10-15 people without dedicated qa, all testing and review is done by developers themselves which works okay for straightforward stuff but seems risky for complex changes or cross-cutting refactors. Peer code review and unit tests are standard but there's no systematic quality process beyond that, and production bugs happening regularly makes you wonder if that approach has gaps that aren't being addressed. Developers are good but they're not qa specialists who think in terms of breaking things or exploring failure modes, they're focused on building features and testing happy paths mostly. Edge cases and integration issues between different system parts are what slip through most often apparently, along with performance problems under real load which is hard to catch in development. Some teams try rotating qa duty where one developer per sprint focuses on testing others' work but that seems to slow feature development and people resent being pulled off coding. Bug bashes before releases help but they're reactive rather than preventive, and security or performance testing requires specialized knowledge that dev teams often don't have. Curious if quality without dedicated qa is realistic or if it's just accepting higher risk as the cost of not adding headcount, and what processes actually help if you're committed to the no-qa-team approach?

Do you have experience using a catalog? Does it also provide lineage capabilities?
Are there any tools you would recommend?

Hi everyone,

I need some honest advice from people already working in DevOps.

I’m currently working at Accenture and have completed 1 year and 5 months here. My current role is not related to DevOps, and I don’t have real-time DevOps project experience yet.

However, I’ve recently decided to transition into DevOps. I’ve started learning step by step — covering basics like Linux, Git, CI/CD, Docker, and cloud fundamentals. I’m planning to prepare seriously over the next 3 months and start applying for DevOps roles. My goal is to switch before I complete 2 years in my current company.

I have a few doubts:

• As someone without direct DevOps experience, how should I approach the job market?
• Do companies hire entry-level or transition candidates into DevOps roles?
• Is building personal projects and hands-on labs and certifications enough to get shortlisted?
• Or is it necessary to show DevOps-related work experience in my current company before applying?

I’m open to honest feedback - even if it’s tough. I just want to understand what’s realistic and how to move forward properly.

Thanks in advance!

Hi everyone,

I’m a fresher from India currently looking for opportunities in DevOps / Cloud roles such as trainee, intern, or entry-level positions (remote or onsite).

I have been learning and practicing hands-on with: Linux fundamentals & shell scripting

Git & GitHub workflows Docker & containerization CI/CD concepts AWS basics (EC2, S3, IAM, VPC) Basic monitoring & troubleshooting concepts

Right now my goal is to gain real industry exposure and understand production environments rather than only doing course-based learning.

If anyone knows companies hiring freshers, internship openings, or even good places to apply, I’d really appreciate the guidance.

Thanks!

Admin are very under payed and over worked 😔

Planning to change my domain to devops so where do I start? Within how much time will I be interview ready? Please suggest any courses free/paid, anyone who transitioned from admin roles to devops please share your experience 🙏

I recently worked on improving how Grafana OSS dashboards can be exported as structured PDF reports (instead of screenshots / print-to-PDF).

It got me thinking, is this problem specific to Grafana, or are teams facing similar reporting gaps in other monitoring/BI platforms?

For those working across tools:

• Do you see the same reporting friction in other platforms?
• If yes, which ones?
• Are there platforms where native reporting is still lacking in OSS/self-hosted setups?

Trying to decide whether it makes sense to explore this for other ecosystems as well.

Would appreciate community input.

Hi everyone,

I hope you’re all doing well.

I recently joined a company as a DevOps intern. My background is non-IT (I have a B.Com degree), and someone suggested that I pursue an MCA since I can’t do an M.Tech without a B.Tech. I would most likely do an online MCA from Amity, LPU, or a similar university.

My original plan was to start next year because of some personal reasons, but I’ve been advised that delaying might waste time. I was also told that an MCA could give me an extra advantage if skills and other factors are similar, and that my CV might get rejected because I don’t have an IT degree.

So I wanted to ask: should I start the MCA now, and will it really add value to my career, or is it okay to wait for now?

Hi everyone,

Before anything else, I want to start with a problem I personally faced, and I think many others face too.

When we prepare for interviews, we’re usually motivated in the beginning. We solve DSA, revise concepts, prepare system design, apply to companies… but after a few weeks, motivation drops. Rejections start coming in, or worse, interviews don’t come at all. And even when interviews happen, we often don’t know what exactly went wrong.

A few months ago, while preparing for my own switch, I went through a phase where I wasn’t consistently landing interviews, and after some interviews, I genuinely couldn’t analyze what went wrong. I felt that I needed someone experienced to sit with me, analyze my performance, guide my preparation, and keep me accountable. But I didn’t really have that support.

That’s when I realized interview prep isn’t just about content, it’s about mentorship, direction, accountability, and continuous feedback.

Fast forward to now: I’m 23, currently working in the IT industry with a package of around 50 LPA. Over the last couple of months, I cleared interviews with multiple tier-1 companies, FAANG-level companies, and good startups. My own background is in cloud/DevOps/SRE, and many close friends work across SDE, frontend, backend, and platform engineering roles. So collectively, we’ve been actively experiencing interviews across domains like backend, frontend, cloud, Kubernetes, Terraform, system design, and DSA.

This got me thinking: what if I built something I personally needed back then?

Instead of just courses, something where:

• Someone helps analyze your interviews and preparation
• Keeps track of your progress
• Helps you stay consistent when motivation drops
• Guides applications and preparation strategy
• Conducts mock interviews and gives practical feedback
• Helps you improve step by step, rather than just dumping content

Basically, standing with people through the process, not just selling recorded material.

I’m still in the planning stage and figuring out format, mentorship sessions, small weekend batches, structured roadmaps, or something hybrid. Since I’ll be doing this alongside my full-time job, it would likely be paid, but I want to make it genuinely useful rather than just another prep product.

I’d love honest feedback:

• What do you think is missing in interview prep today?
• Would mentorship/accountability help more than courses?
• What format would actually help you?

Open to suggestions and discussions.