One of the things I struggled with as an SRE was being able really grok what non-engineers/non-devs like my manager, whomever they reported to, and various chains in my employer’s business cared about most when it came time to select tools. Depending on the size of the employer, startup to enterprise, there are increasing numbers of non-engineering folks who have decision making power over the team’s tools. Thus, as devs, ops, etc. we cannot keep our focus on just the technical aspects of different tools and frameworks or we’ll miss the opportunity to appropriately make our case to these other stakeholders. In this session, I’ll be discussing what these other groups need to know to help them make a decision in your best interest.
KEYNOTE: PagerDuty -- How to Advocate to Not You: Non-technical Considerations for Our Technical Tools
Quintessence is a DevOps Advocate at PagerDuty. Prior to working at PagerDuty she was a Developer Advocate / Technical Evangelist at Logzio and then AppDynamics (part of Cisco). Her main area of focus is DevOps - tooling, cultural shifts, best practices, etc. Quintessence has been working in the IT industry for over a decade. Prior to Developer advocacy, she started out in Technical Support (now referred to as Customer Success), then dabbled as a Database Administrator, before becoming a “Cloud Engineer” / “DevOps Engineer” (or whatever the cool titles are these days) specializing in AWS. Outside of work, Quintessence ran Inclusive Tech Buffalo (formerly the Buffalo chapter of Girl Develop It) for 5 years and is staying on as a local mentor.