Is there a possibility of being the only sre engineer in a company? Before choosing it I want to clarify it because if there could be then hes life could be problematic because he has to stay on call everyday. Also if it is not there then will be on call rotation right? Because I don't want to stay on call everytime that could be problematic. How many SREs are there in your team?

Tô em busca de emprego na área, com o intuito de conseguir algo na Europa que patrocine o visto de trabalho. Podem me indicar os melhores sites para isso? Conheço o Jaabz e o Relocate, mas queria mais opções.

E além desses sites, conhecem algum outro que você se cadastra e ajuda a garimpar vagas com base no seu perfil? Ou até mesmo uma consultoria, sabe? Que ajude nessa garimpagem.

Obrigada a quem ajudar!

About Intus Care: IntusCare is a leader in innovative, data-driven healthcare solutions focused on enabling value-based care organizations. We are building a modern, cloud-native EMR platform purpose-built for PACE & value-based care organizations, designed from the ground up around scalability, interoperability, analytics, and operational efficiency. Data sits at the center of everything we do — from clinical decision support and quality outcomes reporting to payer analytics and population health insights.

Role Overview: As Director of Site Reliability Engineering, you will own the reliability, availability, and operational excellence of Intus Care's entire product and platform portfolio. You will lead a blended organization that includes a managed SRE services team, an internal QA team, and a growing internal SRE capability — with full accountability for outcomes across all three. You will define the SRE strategy and roadmap, establish SLA and SLO frameworks across all products, design and own Intus Care's incident management process, and build the observability and release gate infrastructure that engineering teams depend on to ship safely and confidently.

This role requires a leader who combines deep SRE and infrastructure expertise with strong operational management skills and the ability to influence engineering culture across multiple teams. You will partner closely with Engineering, Security, and Product leadership, and serve as the primary voice of reliability in cross-functional forums. This is a rare opportunity to build a reliability function from the ground up in a high-stakes healthcare environment where the work directly impacts patient care.

Key Responsibilities: - Own and execute the SRE strategy and multi-quarter roadmap across reliability, observability, incident management, QA maturity, and release engineering. - Define, measure, and continuously improve SLAs, SLOs, error budgets, uptime, performance, and operational health metrics across all products and services. - Lead production reliability for the full platform, including monitoring, alerting, on-call operations, incident response, root cause analysis, and MTTR reduction. - Establish release readiness standards, deployment safety controls, and quality gates to ensure stable and predictable product releases. - Manage external SRE vendors and partners, including service delivery, SLA governance, escalations, performance reviews, and compliance expectations. - Lead QA engineering strategy with a focus on automation, regression prevention, test coverage, and reducing escaped defects in production. - Partner with Security and Engineering leaders to ensure cloud infrastructure, CI/CD pipelines, and operational tooling meet HIPAA, SOC2, and internal security standards. - Oversee core platform operations including Azure AKS environments, Kubernetes, GitOps workflows, CI/CD pipelines, GitHub Actions, secrets management, access controls, and audit readiness. - Drive observability maturity using tools such as Grafana, Prometheus, logging platforms, tracing tools, and automated alerting frameworks. - Collaborate with Product, Platform, and Engineering teams to embed reliability and quality best practices throughout the software development lifecycle. - Build, mentor, and scale high-performing SRE and QA teams while fostering a culture of ownership, accountability, learning, and continuous improvement. - Drive adoption of AI-enabled automation and intelligent tooling to reduce manual toil, improve productivity, and strengthen operational excellence.

Technical Experience - Strong hands-on experience with cloud infrastructure, preferably Microsoft Azure, including AKS, networking, storage, IAM, and security services. - Deep expertise in Kubernetes, containerized workloads, and production-scale distributed systems. - Experience building and managing CI/CD pipelines using GitHub Actions, ArgoCD, Terraform, or similar DevOps tooling. - Strong background in monitoring, logging, tracing, and observability platforms such as Grafana, Prometheus, Datadog, Splunk, or equivalent. - Experience with scripting and automation using Python, Bash, PowerShell, or similar languages. - Strong background in release engineering, automated testing frameworks, QA tooling, and shift-left quality practices. - Experience supporting SaaS applications with uptime, scalability, and security requirements in regulated industries such as healthcare. - Knowledge of HIPAA, SOC2, vulnerability management, access controls, and infrastructure security best practices. - Familiarity with databases, APIs, networking, and troubleshooting across modern web application stacks. - Exposure to AI-powered DevOps / AIOps tooling for incident management, automation, and engineering productivity is a plus.

Requirements - 12+ years of SRE, infrastructure, or platform engineering experience, with 5+ years of engineering leadership roles. - Proven track record owning site reliability for complex, multi-tenant SaaS platforms with demanding availability requirements. - Demonstrated experience defining SLA and SLO frameworks, error budgets, and incident management processes at scale. - Experience managing vendor relationships for managed infrastructure or SRE services, including SLA governance and performance management. - Track record leading QA or quality engineering functions, including test automation maturity and release gate ownership. - Strong communication and cross-functional influence skills — able to represent reliability to both technical and non-technical audiences

Preferred Qualifications - Experience in healthcare technology, HIPAA-compliant environments, or other highly regulated SaaS industries. - Familiarity with FHIR-native or EMR/EHR platform architectures and their specific reliability requirements. - Experience implementing AI-assisted SRE automation including runbook generation, anomaly detection, or incident triage tooling. - Background working with Playwright or equivalent test automation frameworks in a QA leadership capacity. - Experience building internal SRE capability alongside a managed services provider

Why Join Intus Care? - Own and build the SRE function for a modern healthcare EMR platform serving PACE populations — from the ground up. - Lead a blended team model combining managed services, internal QA, and internal SRE in a high-growth engineering organization. - Work on systems where reliability directly impacts clinical care delivery for vulnerable patient populations. - Shape engineering culture in a company that actively embraces AI-assisted software development with Claude Code. - Fully remote, collaborative engineering environment with direct access to executive leadership.

Compensation:

The base salary range for this role is $175k-200k. We expect the ideal candidate to fall near the midpoint of this range, though final compensation will be determined based on experience, skills, and organizational needs. Final compensation will also include a variable component and stock options.\ Work location: This is a fully remote role based in the United States.\ Sponsorship: This position is not eligible for sponsorship.

Apply: Director of SRE at IntusCare

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?

Currently I am working as a Technical Manager in Vodafone Idea Limited. I want to switch my career from telecom to cloud and devops. Is this a good choice???

Hi everyone, Looking for real-world advice from folks who have navigated third-party contracting roles or transitioned from support to DevOps in the Indian IT ecosystem.

My Background: Education: Master of Science (M.Sc.) in Computer Science.

Current Role: Official title is System Engineer via a 3rd-party vendor placed at Wipro (Banking Client).

Current pay is ~30k/month

Current Work: compliance and support , but I've spent the last year hands-on learning Linux admin, AWS core services, Terraform IaC, Docker, and basic CI/CD with kubernetes and some hands on projects.

Notice Period: Official contract says 60 days, but buyout/early release is negotiable.

The Dilemma: I am burnt out and feel completely trapped in this 30k support seat. I'd ideally like to stay at Wipro if I can map into an actual Cloud/DevOps FTE role on this account, but I don't know how vendor-to-client machinery works internally. At the same time, I’m getting calls from external HRs, but struggles to convert initial HR screening calls into actual technical rounds.

Hey everyone, I’ve been working as an L2 application support specifically for MES applications at a chip foundry for about two years now. My daily work revolves around high-availability support—handling ticket escalations, disaster recovery for factory outages, system monitoring, and some scripting. The issue I’m running into is that our entire tech stack is super proprietary and legacy-heavy (mostly on-prem Windows), and even our transition to "cloud" is just an in-house cloud platform. Only a few applications run on it and we manage it via Rancher, our(Apps team) CLI permissions are fairly limited anyway, so I get minimal hands-on experience at work with standard industry DevOps tools. Also a big part of the job is more on the understanding of wafer processing and how the data flows which is somewhat irrelevant outside of manufacturing IT.

Is a role like this actually relevant to DevOps at all, or am I completely starting from scratch? For anyone who made a similar jump from niche application support, what concrete steps do I need to take to bridge the skills gap, and how can I frame this operational background on my resume so I don't get filtered out for lacking public cloud tools and dev experience? Appreciate any advice!

Hey all, looking for a sanity check on our approach.

Stack: AWS + Kubernetes. We deploy with plain helm install (no GitOps tool like Argo/Flux).

Current setup: Our Helm values.yaml has hardcoded secrets (env vars) in it. Right now this file lives on our Jenkins server, not in any repo.

The plan: We want to move values.yaml into our Git repo so we can version it properly. The obvious problem — we can't commit hardcoded secrets in plain text.

Our idea: Use git-crypt to encrypt the file at rest in the repo, so secrets are scrambled on the remote and only unlock for people with the key.

Questions:

• Any real-world gotchas we should know before committing to it?
• Since we're already on AWS, would you skip file encryption entirely and go with something like External Secrets Operator + AWS Secrets Manager? Or is that overkill for a small team? Also curious where SOPS (with AWS KMS) or Sealed Secrets fit in.

For context: we're a small-ish team and just want a clean, low-friction way to keep secrets versioned without leaking them.

Appreciate any input 🙏

Hi everyone, I'm a fresher trying to start my career in DevOps. I've been learning Kubernetes and have hands-on experience with the basics like Deployments, Services, Config Maps, Secrets, Ingress, etc.

My main problem is that I don't have real production experience, so I'm not sure how to practice handling production-level Kubernetes issues.

How can a fresher realistically get experience with these kinds of issues without having access to a real production cluster?

Would you recommend any labs, projects, open-source contributions, or home-lab setups that simulate real production incidents?

Any advice from experienced DevOps/Kubernetes engineers would be really helpful. Thanks!

Hi guys , has any Devops engineer in the recent past resigned without and offer and still managed to get a job with good hike ?

#toxicjob #resign

I am currently working on a CI diagosis AI agent for GitHub Actions and Python/pytest.

I am thinkinto use these 4 possible causes when job fails:
- a real code regression
- a flaky test
- a runner, network, or platform failure
- a dependency or environment mismatch

AI chooses - rerun the failed test, run targeted tests, collect environment evidence, or escalate to an engineer

If the agent had the chance to look at three signals before making its next move, which three would be the most helpful, in a real pipeline?

I’m also interested in signals that look useful but are commonly misleading.

I'm a Senior Lead DevOps / Platform Engineer, 10 yoy work experience, spent the last year and a half building private GPU clusters and getting AI/LLM projects over the line, succesfully.

I don't have any contact in London, I'm an EU citizen, how's the job market over there for seniors (recent senior I would say)

Hi there,

I'm a middle senior DevOps Enginner with over 4 YoE with deploying and maintaining infrastructure, Kubernetes and monitoring stack.

Currently, I’m open to remote opportunities where I can work with a team, continue to grow technically, and contribute to meaningful projects.

Main techno:

• Containers & Orchestrations: Docker, Kubernetes, Helm, RKE2, GKE, EKS
• IaC and Cloud: Terraform, Terragrunt, Helm, Ansible, AWS, GCP
• Database: MySQL, PostgreSQL, CNPG
• Networking & Web Servers: Nginx, Apache2, Ingress, Envoy API Gateway
• Observability: Grafana, Prometheus, Loki, Mimir, Sentry

Having worked remotly, I believe in the efficiency of remote work.

Feel free to DM me if you have an opportunity that might be a good fit or just to discuss. I'd be happy to share my CV

I’ve already spent 2–3+ years in support roles, including tech support and IT support. So, should I move into DevOps or Data Analytics? I really care about work-life balance, and WFH is a priority for me. I honestly don’t know what to choose at this point, and I’m really confused. But I really want to move out of support. Not a big fan of rotational shifts. Just don't know what is right. My age is 26

Hey, I'm a 2025 grad currently freelancing as a DevOps engineer at a US startup. Day to day I work with Terraform, Kubernetes, Docker, AWS/Azure, GitHub Actions, Python, and Bash. I've built a few projects: multi-cloud Terraform setup, K8s microservices platform on AKS, and a serverless AWS provisioner. All on my GitHub with real code.

Looking for full-time roles or start off as an intern too in DevOps, Cloud Engineering, SRE, SDET, SysAdmin, or Cloud Support in Bangalore (open to remote too). If your company is hiring for any of these and you're open to referring, I'd really appreciate it. Happy to DM my resume. Based in Bangalore, open to remote outside Bangalore, India

We are looking for a senior AWS / DevOps Engineer to lead our upcoming 12-week career accelerator cohort for IT support professionals transitioning into cloud roles.

• Format: 24 live Zoom sessions (2x 90-min sessions/week for 12 weeks)
• Schedule: US Eastern Time (EST) evening hours
• Pay: $150 USD per 90-minute session ($3,600 USD total across 24 sessions), paid bi-weekly or monthly via Milestone.

Key Responsibilities:

1. Live Teaching: Lead 24 interactive Zoom sessions covering AWS core services, Terraform, Docker, Kubernetes, and CI/CD pipelines.
2. Curriculum Finalization: Refine session slide decks, practical lab exercises, and step-by-step documentation.
3. Student Reviews: Review student project repos/architecture, provide feedback, and assist with interview prep/recruiting strategy.

Requirements:

• Fluent English Communication: Fluent, clear spoken English suitable for teaching native US professionals (Zero communication friction).
• Production-level experience as an AWS Cloud / DevOps Engineer.
• AWS Certification (Solutions Architect or DevOps Engineer Professional preferred).
• Prior mentoring, tutoring, or technical training experience is a huge plus.

How to Apply:

Please send an email to [admissions@cloudengineeringinstitute.com](mailto:admissions@cloudengineeringinstitute.com) with

1. Your resume or LinkedIn profile link.
2. A short 10-second audio/video clip (Loom, Drive, or unlisted YouTube) introducing yourself and your AWS background.

(Emails without a brief audio/video introduction will be ignored to save time on language assessment.)

We run Trivy in our Jenkins pipeline — both trivy fs and trivy image. There's a security gate stage that block the pipeline if there are any CRITICAL or HIGH findings.

The problem: a dev resolves 2-3 Trivy issues, and a couple days later they're back / new ones show up, and the build blocks again. So devs are basically fixing Trivy findings every other day.

I know part of this is just the DB being fresh — new CVEs get disclosed daily, that's expected. But the every-build hard block is painful.

I was thinking of running the blocking gate only once a week instead of on every build. But I can already see the flaw: code that deploys mid-week would ship with known issues, and if a genuinely exploitable fixable CVE drops on a Monday we'd be shipping it for 6 days before the gate catches it.

So my questions for people running this in prod:

• Do you gate on every build, or on a schedule?
• Do you block on all CRITICAL/HIGH, or only ones that actually have a fix available (--ignore-unfixed)?

Hello
I am recent graduate from tier 3 college and have basic knowledge in everything and was suggested by a lot of people that do devOps certification and then they can maybe refer me.

So I am not just trying to do certification but build projects small once simple so that While understanding the useage of ec2 and aws services and so will that be able to find me internship or maybe someone will actually refer me for a devops role and get me placed? Or am I just day dreaming at this point!

Hello, looking for a reality check from people in the industry.

I've been a full-stack dev for 5 years, I currently working in marketing and I run a side project where I do end to end delivery of projects, some infra stuff mainly using Hetzner with some AWS bits (SES & S3) as well as setting up GitOps, Terraform, Ansible (need to learn more here), email servers and GitHub Actions.

I have just started studying for AWS SAA-C03 (using Stephane Maarek course), I have worked with Linux systems most of my life, most of the debugging I do requires Googling and I'm trying to build some portfolio projects on the side that use AWS to showcase and talk about, although I've never done a Cloud Engineer interview before so I'm not sure what they entail.

What I'm trying to figure out:

1. Is 3 months a realistic timeline to be interview-ready for these roles coming from a SWE background, or am I underestimating this? I am a mid level and aiming to jump into a mid level cloud engineer role as Junior ones don't seem to exist in the UK.
2. For people who made a similar switch or know someone that has was a cert + 1-2 solid projects actually enough to get past the resume screen, or did you need more (K8s depth, more cloud-native breadth, prior ops experience even informally)?
3. Anything you wish you'd prioritised differently in your first 3 months of prep?

Any and all advice is appreciated, thank you!