Site Reliability Engineer
Innovature is hiring a Site Reliability Engineer to manage observability platforms and improve system reliability. Responsibilities include incident response, L2 support, automation, and implementing SRE best practices. The ideal candidate has 2-3 years of experience with Python, AWS, Kubernetes, and monitoring tools. The role involves hands-on coding for reliability and active participation in an on-call rotation.
50k new jobs listed every day. Install TAL to find more jobs like this.
Experience
2-3 years
Function
Engineering
Work mode
Onsite, India
Company
Tier 2
What you will work on
Innovature is hiring a Site Reliability Engineer to manage observability platforms and improve system reliability. Responsibilities include incident response, L2 support, automation, and implementing SRE best practices. The ideal candidate has 2-3 years of experience with Python, AWS, Kubernetes, and monitoring tools. The role involves hands-on coding for reliability and active participation in an on-call rotation.
TAL's take
Solid technical requirements and well-defined scope for a mid-level SRE role at a tier-2 company.
Very clear responsibilities, tech stack, and expectations provided in the job description.
Must haves
- 2+ years experience in SRE, DevOps, or cloud engineering
- Intermediate to advanced skills in Python and Linux
- Experience with Terraform and Infrastructure as Code
- Expertise in AWS and Kubernetes
- Proficient in production on-call and incident management
- Business level English skills
Tools and skills
Nice to have: slo monitoring, disaster recovery planning, chaos testing, capacity planning, automation, toil reduction, apm solutions, gcp monitoring, gcp, kubernetes certifications, aws certifications.
About the company
Unfamiliar company, default mid-tier.
Posts mentioning Innovature
Developer needed for Innovative app project
Kind of agree with this take on types of PM
https://sachinrekhi.com/3-types-of-product-managers-builders-tuners-innovators
Work Pattern - Routine vs Innovation - Do you really have a choice
Being part of software engineering fraternity, I always had this introspective phase where I would question the work / development I am presently doing whether it's interesting/innovative or a routine feature development. Few dilemmas and discourses are as follows 1. I am building a product feature which basically requires me to copy paste most of my routine modules like creating similar entities in DB or creating the same services. It really feels mundane and a routine drill work. 2. But let's question first point, do we really have no way to have the innovative spectre in routine work. This is where a proactive engineer has an opportunity to stand out. It totally depends how they bring in innovative sparkle. This contribution may be on any domain be it security, data handling, analytics or UI. 3. So concluding remarks, it's just not the product and it's scale that makes the software engineering enticing but it's also the other way round where engineering can also play a leading role making the product interesting. Be the change you want to see