Eric Dobbs

Boulder, Colorado

PDF version

Ask me how I can help you grow and continuously improve a world-class resilience engineering practice fueled by deep learning from incidents and chaos engineering. I love cultivating reliability in complex systems: resilience in software teams & robustness in their services. Half software engineering and half relationship building. Demonstrated ability to identify & deliver systemic improvements & culture change.

Principal SRE—Resilience Engineering




Founded the Incident Management & Resilience Engineering team. Defined mission, vision, and roadmap. Wrote an effective job description. Successfully recruited and hired a Principal Resilience Engineer to join the team.


Developed relationships widely across the organization including diverse teams: Learning & Delivery, Product & Technology Excellence, Application Infrastructure, Software Delivery, Architecture Advisory Group, Security, Customer Success, Mobile Development and Product.

Learning From Incidents

Engaged Adaptive Capacity Labs to train a cohort of a dozen people across the organization. Developed the business case. Identified participants. Supported logistics and communication. Supported contract negotiations.

Led or contributed to six learning reports surfacing a dozen themes. Organized and iterated on an information architecture for themes and reports.

Senior Software Engineer—Reliability

New Relic



Pioneered chaos engineering practices to build skills and confidence across teams. Identified enabling infrastructure and features to allow safer experimentation in staging and production—e.g. traffic shaping, traffic mirroring, and advanced canary deployments. Balanced improvement of code & components and individual skills & teamwork.


Actively coached across skill levels: from a college intern, to lead engineers including security, tech support, devops, and software devs.

Apprenticed myself to a shihan in programming, mentoring, and community organizing to study closely how he supports and encourages growth and independence.

Cross-team Coordination

Led chaos engineering experiments (including the first in production), from developing experience across the organization, negotiating organizational buy-in, and synthesizing cross-team expertise into concrete experiment design.

Resolved gnarly, entangled design problems, integrating tooling with production systems and requiring buy-in from multiple teams.

Thought Leadership

Developed professional relationships with leaders in learning from incidents and chaos engineering. Participated in Supported learning from incidents workshop at Velocity San José 2019.

Wrote extensively in internal blogs. Actively participated in informal Slack conversations. Gave formal presentations and lightning talks in many communities of practice: Reliability, Chaos Engineering, Kubernetes, Ruby, Javascript, and others.

Code, Runbooks, Process, and Training

Incident chat ops: for example, used TDD to bootstrap test scaffolding and implement a micro-rules engine that automated escalation and paging during incidents.

Social engineering and evangelism for changes to policy around incident tracking, metrics collection and reporting, team health, and incident retros.

Helped write and organize Service Level Objectives documentation and tooling.

Principal Software Engineer

Itron, Inc. (was Comverge)



Applied diplomacy and role-modeling to streamline communications and increase collaboration between QA, Development, IT, and Solutions Delivery.

Increased productivity for 20 developers and 4 technicians. Reduced build times and deploy times while also increasing reliability.

Lead adoption of Docker throughout the organization.


Fostered deep respect and trust from my team. The director received repeated requests to remain on my team and several senior devs expressed specific interest in joining me.

Nurtured emotional safety and courage. Established weekly retros and bi-weekly one-on-ones focused on social-emotional parts of software development. Spoke hard truths and admissions of failure. Gave specific and concrete applause frequently. Other managers followed my lead.


Encouraged professional development in all levels of expertise: high-school intern, junior dev fresh out of a code school, intermediate dev transitioning from QA to engineering, and two senior developers. One exceeded her own goals in a well-received talk at Rocky Mountain Ruby 2015.


Reduced build times from 8 hours to 30 minutes by expanding the jenkins cluster from 20 to 70 VMs, and finding and fixing the worst-offenders in the test suite.

Improved whole software delivery life-cycle. Instituted standardized deploy process, team-wide runbooks, and semi-automated deploys that increased repeatability and reduced time required from one month to a few hours.

Social and technical engineering of Docker adoption. Enabled early adopters to experiment. Deployed first containers into CI. Created first containerized tests and deploys. Designed and evangelized effective patterns. Planned, negotiated, persuaded, and executed deployment in stages from dev, to test, QA, UAT, and production.

Senior Software Engineer




Fostered a culture of continuous improvement through honest and courageous communication, by speaking hard truths, and applauding when others did the same.

Emergent Design

Refactored all outbound messaging into a delivery service while maintaining existing message flows. This abstraction only two weeks later enabled us to improve throughput just in time for a customer's campaign messaging over 330,000 numbers.

Created a foundation for modularized html, css, and javascript enabling migration UI from home-grown CSS-soup to Bootstrap.

Refactored one particularly messy controller with just a handful of method extractions. A few weeks later those changes enabled a colleague to clarify the routing and models and complete the cleanup without me.


Profiled outbound messaging performance and throughput. Identified garbage collection and IO as primary bottlenecks.

Threaded message delivery for an immediate twelvefold increase in SMS message throughput. Introduced retries and fallbacks to ensure message logging and persistence and expand the ability to identify and diagnose failures.

Enabled message workers to run under JRuby as a strategic move to open other performance opportunities via JVM based tools and languages.

Front-end Engineering

Streamlined unit testing of javascript front end code using Jasmine.

Created dynamic and thoroughly customizable fundraising thermometer and pledge wall for use in high-profile gala events. Produced the SVG graphic for dynamic display and employed Ember.js for updates.


Full-stack agile methodologies including continuous integration, full-time pair-programming, retrospectives, etc.

Software Engineer

Pivotal Labs



Initiated an informal usability analysis for Groupon's editorial tools via direct observation of editors and deal creators.

Consequently created dramatic improvements in deal creation and editorial workflows. Streamlined communications between sales and editorial teams by integrating with Salesforce.


Mastered Ruby within a month. Immediately effective maintaining and updating existing Rails application for Groupon Merchant Center team.


Refactored Groupon's merchant analytics into an independent service-oriented architecture. Improved largest deal analytics reports from a query time of 7 minutes down to 15 seconds.


Full-time pair-programming, behavior-driven design (BDD), continuous integration, collective ownership, small releases, planning game, retrospectives, on-site customer.

Aikido Instructor

University of Colorado Recreation Center



Three students gave unsolicited feedback that my teaching changed their lives.

Increased typical class enrollment by 50%. Inspired many students to join Boulder Aikikai.

Forth Degree Black Belt

Boulder Aikikai

November 2019

Bachelor's of Environmental Design, emphasizing computer methods in design

College of Architecture and Planning, University of Colorado at Boulder

May 1994