Previous Job
Site Reliability Engineer
Ref No.: 18-08054
Location: Framingham, Massachusetts
Position Type:Contract
Experience Level: 5 Years
Digital Site Reliability Engineering
8 month contract
Framingham, MA

Client's Digital Solution Delivery organization is need of Site Reliability Engineers to participate on one or multiple projects to ensure the new features are operationally ready for implementation.
In this role the Site Reliability Engineer represents the IT Operations Team on projects identifying the operational risk the new feature presents and the appropriate non-functional requirements (NFR) to implement reducing that risk. The goal is a minimum viable product (MVP) that meets both the functional and operational requirements to implement the feature.

Qualified individuals will have experience on projects and IT operations. They will have demonstrated experience in site reliability and IT operations roles in the past. While they don't need deep experts in these operational categories, they must understand them, their purpose and tease out the requirements as part of the project:

• Implementation planning and Hypercare (a.k.a. warranty period or early life support)
• Availability
• Resiliency
• Data – Retention, backup, privacy, archiving and purging
• Operability – Routine activities, corrective action plans, etc.
• Capacity and Performance
• Security, Compliance and Fraud
• Vendor Management and Licensing
• Usability – Browser, desktop, geography, accessibility, etc.

Individuals in this role must be able to work with project managers and stakeholders to put together task plans to perform these project activities.

Qualified Site Reliability Engineers will have experience in many tools supporting these capabilities:
• Agile – Confluence, Jira, etc.
• DevOps – Bitbucket, SVN, Jenkins, SonarCube
• Monitoring Tools – AppDynamics, Dynatrace, Gomez, Keynote, Splunk, AlertSite, New Relic
• Performance Testing – Client LoadRunner, Soasta Cloud Test etc., JMeter, etc.
• IT Service Management Tools - ServiceNow

Primary Responsibility
The Site Reliability Engineer will be responsible for the Service Transition Checklist, non-functional requirements and technical debt of each project.

The Service Transition Checklist is used to create a risk profile the project presents to operations and the reduce risk profile the project must meet to implement a minimum viable product from an operations perspective. The Site Reliability Engineer will work with key operations and project stakeholders to negotiate the target operational risk score the project must meet. The risk score will be agreed to by the Business Sponsor, IT Project Sponsor and IT Operations Sponsor and tracked as part of the go-live entrance criteria.

The non-functional requirements are those specific items that must be met to meet the target risk. The Site Reliability Engineer will work with IT Operations and project stakeholders to define specific requirements, owners, validators and approvers. The Site Reliability Engineer takes on a technical lead role for some of these non-functional requirements driving the activities and/or consulting and providing feedback on the design and implementation of them.

Technical debt are those non-functional requirements deemed out of scoped of the project, but that IT Operations needs to seek funding and implement at a later time. Technical debt is agreed to by the Business Sponsor, IT Project Sponsor and IT Operations Sponsor

Qualified individuals demonstrate critical thinking, inquisitiveness, initiative, independence and collaboration. They socialize their work and seek feedback for different perspectives they may not have considered. They have good written and verbal communication skills.

Domain Expertise
Experience in Retail and/or e-Commerce is preferred.

What does success in the role look like?
Successful candidates will have comprehensively identified and communicated the IT operational risk of the project, negotiated a project target risk score sponsors are satisfied with and enthusiastically drove the implementation of the corresponding non-functional requirements.