Urgent Requirement - Site Reliability Engineer - Cincinnati, OH

Hello, Hope you are having a wonderful day!!! My name is Praveen Kumar and I am a part of recruitment team at IDC Technologies INC. I came across your profile and wanted to see if you would be interested in Position Site Reliability Engineer with one of our customer located in Cincinnati, OH. Please let me know your thoughts on this exciting opportunity with us.      Role: Site Reliability Engineer Location: Cincinnati, OH Duration of Project: 12+ Months C2C & W2.                           Job Details: Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operationsproblems. The main goals are to create ultra-scalableand highly reliable software systems. According to Ben Treynor, founder of Googles Site Reliability Team, SRE is "what happens when a software engineer is tasked with what used to be called operations."A site reliability engineer (SRE) will spend up to 50% of their time doing "ops" related work such as issues, on-call, and manual intervention. Since the softwaresystem that an SRE oversees is expected to be highly automatic and self-healing, the SRE should spend the other 50% of their time on development tasks such as new features, scaling or automation. The ideal SRE candidate is a highly skilled system administrator with knowledge of code and automation.DevOps is a philosophy of cross team empathy and business alignment. Its also been associated with a practice that encompasses automation of manual tasks, continuous integration and continuous delivery. SRE and DevOps share the same foundational principles. SRE is viewed by many (as cited in the Google SRE book) as a "specific implementation of DevOps with some idiosyncratic extensions." SREs, being developers themselves, will naturally bring solutions that help remove the barriers between development teams and operations teams.SRE satisfies the DevOps pillars as follows:1.          Reduce organizational silos •      SRE shares ownership with developers to create shared responsibility•  SREs use the same tools that developers use, and vice versa2.   Accept failure as normal •            SREs embrace risk•   SRE quantifies failure and availability in a prescriptive manner using SLIs and SLOs•          SRE mandates blameless post mortems3.          Implement gradual changes •    SRE encourages developers and product owners to move quickly by reducing the cost of failure4. Leverage tooling and automation • SREs have a charter to automate menial tasks (called "toil") away5.      Measure everything •   SRE defines prescriptive ways to measure values•           SRE fundamentally believes that systems operation is a software problem       Thanks & Regards, Praveen Kumar IDC Technologies Inc. 1851 McCarthy Blvd, Suite 112 to 118 Milpitas, CA 95035 Desk: 408-637-5156 Phone: 732-708-3245 E: praveen.kumar1@idctechnologies.com

To unsubscribe from future emails or to update your email preferences click here .