{"id":15971176,"url":"https://github.com/dolph/cv","last_synced_at":"2026-03-18T17:21:21.721Z","repository":{"id":141850688,"uuid":"88410563","full_name":"dolph/cv","owner":"dolph","description":"My curriculum vitæ.","archived":false,"fork":false,"pushed_at":"2025-01-24T13:33:51.000Z","size":170,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2025-07-30T12:01:35.039Z","etag":null,"topics":["cv","resume"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/dolph.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-04-16T12:04:03.000Z","updated_at":"2025-03-11T14:43:31.000Z","dependencies_parsed_at":null,"dependency_job_id":"d2e8ce56-1ecf-4972-a862-173e09e434e8","html_url":"https://github.com/dolph/cv","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/dolph/cv","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dolph%2Fcv","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dolph%2Fcv/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dolph%2Fcv/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dolph%2Fcv/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/dolph","download_url":"https://codeload.github.com/dolph/cv/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dolph%2Fcv/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29270908,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-09T13:47:44.167Z","status":"ssl_error","status_checked_at":"2026-02-09T13:47:43.721Z","response_time":56,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cv","resume"],"created_at":"2024-10-07T20:20:19.382Z","updated_at":"2026-02-09T15:33:11.033Z","avatar_url":"https://github.com/dolph.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Dolph Mathews\n\n![Lint](https://github.com/dolph/cv/actions/workflows/markdown-lint.yml/badge.svg)\n![Links](https://github.com/dolph/cv/actions/workflows/markdown-links.yml/badge.svg)\n\nI am a highly experienced software engineer with a passion for automating\nsolutions and creating reliable, intuitive systems. My background includes\ndeveloping web applications, web services, and commandline tools. I enjoy\nwriting tests, publishing documentation, and optimizing processes.\n\n- Email: [dolph.mathews@gmail.com](mailto:dolph.mathews@gmail.com)\n- GitHub: [github.com/dolph](https://github.com/dolph/)\n- LinkedIn: [Profile](https://www.linkedin.com/in/dolphmathews/)\n- Location: Remote (USA)\n\n## Education\n\n### University of Texas at Austin (2005 \u0026mdash; 2009)\n\nBachelor of Science, **Electrical \u0026 Computer Engineering**\n\n## Experience\n\n### *Lead Reliability Engineer*, IBM Quantum (2023 \u0026mdash; present)\n\nAs IBM Quantum has grown in maturity from a research project to a\npublicly-accessible product offering, I've advocated for the reliability of our\nsoftware services to become a key objective for the organization. I established\na reliability practice within the organization, leading the use of Grafana as a\nbroadly accessible tool for observability of system metrics and near-realtime\ndebugging of internal components for development teams and internal users\nalike.\n\nI measured and led the improvement of Quantum's job success rate year over year\nfrom 96.17% in 2023 to 99.30% in 2024, and demonstrated that we can maintain a\njob success rate as high as 99.85% over a 7-day period. I also discovered and\nmeasured an internal system efficiency metric, and drove it up from 50.4% when\nI first measured it in June 2023, to \u003e90% in Q4 2024. These two achievements\nhave unlocked tens of millions of dollars of quantum compute capacity that was\notherwise being lost.\n\nI formalized 24/7 incident management policies and organized a volunteer team\nof subject matter experts to respond to software incidents within the\norganization. By driving improvements through alerting, I reduced our Mean Time\nto Detect customer impacting events from 368 minutes in 2023 to 58 minutes in\n2024. This team also achieved a Mean Time to Acknowledgement of all SEV-1\nincidents in 2024 of 9 minutes 10 seconds, which was previously estimated in\nterms of hours. As a result, this team directly helped improve our US service\navailability year over year from 97.0% in 2023 to 98.8% in 2024.\n\nCore technology stack: [Grafana](https://grafana.com/),\n[PostgreSQL](https://www.postgresql.org/), [Sysdig (statsd,\nPrometheus)](https://sysdig.com/), [LogDNA](https://www.logdna.com/),\n[Jaeger Tracing (OpenTelemetry)](https://www.jaegertracing.io/),\n[PagerDuty](https://www.logdna.com/)\n\nPrimary development tools: [vim](http://www.vim.org/),\n[git](https://git-scm.com/), [GitHub](https://www.github.com/),\n[Fedora](https://getfedora.org/)\n\n### *Technical Lead, Infrastructure*, IBM Quantum (2021 \u0026mdash; 2023)\n\nAs Technical Lead for a team of 10+ engineers, I am responsible for\nprioritizing the classical infrastructure work required to deploy and maintain\nQuantum hardware at 9 physical sites, the surrounding compute infrastructure,\nand the cloud services fronting them. We maintain dozens of\nKubernetes/OpenShift clusters, and hundreds of baremetal devices. The scope and\nscale of the team's responsibilities would not be possible to manage without a\nheavy reliance on automation, primarily using Ansible and Terraform.\n\nMy team supports hundreds of software engineers and researchers continuously\ndeveloping, deploying, and operating dozens of applications in multiple\nenvironments. Our primary challenge is keeping up with rapidly evolving\nbusiness goals by helping prototypes mature into reliable production services.\n\nCore technology stack: [Ansible](https://www.ansible.com/), [Concourse\nCI](https://concourse-ci.org/), [Red Hat Enterprise Linux 8\n(RHEL8)](https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux),\n[Dell iDRAC](https://www.dell.com/en-us/dt/solutions/openmanage/idrac.htm),\n[bash](https://www.gnu.org/software/bash/), [YAML](http://yaml.org/), [Sysdig\n(statsd, Prometheus)](https://sysdig.com/), [LogDNA](https://www.logdna.com/),\n[PagerDuty](https://www.logdna.com/), [Terraform](https://www.terraform.io/),\n[Atlantis](https://www.runatlantis.io/), [Python 3](https://www.python.org/),\n[TravisCI](https://travis-ci.org/)\n\nPrimary development tools: [vim](http://www.vim.org/),\n[git](https://git-scm.com/), [GitHub](https://www.github.com/),\n[Fedora](https://getfedora.org/)\n\n### *Senior DevOps Engineer*, IBM Quantum (2019 \u0026mdash; 2021)\n\nAs part of [IBM Quantum](https://www.ibm.com/quantum-computing/), I am\nresponsible for the entire lifecycle of backend infrastructure running both\nproduction and research \u0026 development workloads.\n\nI have led the deployment automation effort for all backend Linux systems,\nwhich was previously done manually from docs with a handful of bash snippets to\na variety of different hardware configurations, operating systems, and\nplatforms. After I converted all available documentation to Ansible playbooks,\nwhich I tested in Vagrant \u0026 VirtualBox, I helped standardize hardware and\noperating system configuration by automating the provisioning process from\nbaremetal. I later introduced Concourse CI to provide a continuous integration\nand continuous deployment platform, meeting business needs across multiple\ngeographically-distributed private networks while delivering changes across all\nproduction devices multiple times per day without human intervention.\n\nI have led the modernization of monitoring and alerting from backend\ninfrastructure from local log files to centralized logging via LogDNA, system\nmonitoring via Sysdig (which is built on Prometheus and `statsd`), and alerting\nvia PagerDuty.\n\nI have also led the full operations lifecycle of geographically distributed Red\nHat OpenShift/Kubernetes clusters from baremetal and virtualized provisioning\nto running clusters as part of [IBM Cloud\nSatellite](https://www.ibm.com/cloud/satellite), primarily for neartime quantum\ncompute workloads.\n\n- *Squad Lead*: As squad lead, I run daily standups, weekly backlog grooming,\n  biweekly retrospectives, and biweekly sprint planning for a team responsible\n  for backend infrastructure and Quantum control systems software. I also have\n  worked to help other teams adopt agile practices.\n\n- *Security Owner*: As security owner for almost all baremetal Linux systems in\n  IBM Quantum, I leverage our continuous deployment capability to rapidly\n  improve our security posture, mitigate and resolve vulnerabilities, and\n  manage authorization for internal users.\n\nCore technology stack: [Ansible](https://www.ansible.com/), [Concourse\nCI](https://concourse-ci.org/), [CentOS 7](https://www.centos.org/), [Red Hat\nEnterprise Linux 8\n(RHEL8)](https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux),\n[Dell iDRAC](https://www.dell.com/en-us/dt/solutions/openmanage/idrac.htm),\n[bash](https://www.gnu.org/software/bash/), [YAML](http://yaml.org/), [Sysdig\n(statsd, Prometheus)](https://sysdig.com/), [LogDNA](https://www.logdna.com/),\n[PagerDuty](https://www.logdna.com/), [Terraform](https://www.terraform.io/),\n[Python 3](https://www.python.org/)\n\nPrimary development tools: [vim](http://www.vim.org/),\n[git](https://git-scm.com/), [GitHub](https://www.github.com/),\n[Fedora](https://getfedora.org/), [Vagrant](https://www.vagrantup.com/),\n[VirtualBox](https://www.virtualbox.org/)\n\n### *Senior Developer Advocate*, IBM Developer (2017 \u0026mdash; 2019)\n\nAs part of [IBM Developer](https://developer.ibm.com/), I worked on a team\nresponsible for creating and managing developer advocacy content such as\ntutorials, articles, and code patterns covering topics including IBM Watson and\nIBM Cloud. A code pattern is an open source example demonstrating how\ndevelopers can leverage specific IBM services in their projects and are\npresented by developer advocates in labs, workshops, and presentations.\n\nSeveral of my accomplishments with IBM Developer focus on allowing a small team\nof developer advocates to build, deliver, and maintain thousands of pieces of\ntechnical content spread across hundreds of git repositories in a scalable\nmanner. For example:\n\n- automatically identifying and updating broken and outdated links,\n- building a tool to interactively validate Markdown frontmatter in YAML (using\n  JSON Schema),\n- automating the conversion of a legacy documentation format (XML to Markdown),\n- updating branding of IBM products and services, and\n- writing Selenium tests to exercise previously-untested workflows in the IBM\n  Cloud console.\n\n\u003e Dolph has gone out of his way to help the editorial team with several special\n  projects. His help has been invaluable and has saved our team hours of work.\n  He's streamlined and updated processes to make tools easier to use and to\n  offload work from us. \u0026mdash; Jill Amaya\n\nI was also entrusted to serve as an administrator of IBM's open source presence\non GitHub, [github.com/IBM](https://github.com/ibm/), managing the creation of\nopen source projects and the integration with 3rd party services.\n\nCore technology stack: [Python](https://www.python.org),\n[bash](https://www.gnu.org/software/bash/), [JSON](http://www.json.org/),\n[YAML](http://yaml.org/),\n[Markdown](https://daringfireball.net/projects/markdown/syntax), [JSON\nSchema](https://json-schema.org/)\n\nPrimary development tools: [vim](http://www.vim.org/),\n[git](https://git-scm.com/), [GitHub](https://www.github.com/),\n[TravisCI](https://travis-ci.org/), [Ubuntu Linux](https://www.ubuntu.com/)\n\n### *Principal Software Engineer*, Rackspace (2011 \u0026mdash; 2017)\n\nAt [Rackspace](https://www.rackspace.com/), I worked as an open source\n[Python](https://www.python.org/) developer on a globally distributed team in\nthe [OpenStack](https://www.openstack.org/) community. After being hired as a\n**Software Engineer**, I was promoted to **Principal Engineer** in November\n2014.\n\nDuring that time, I became a core contributor of [OpenStack\nKeystone](http://github.com/openstack/keystone), the identity service for\nOpenStack-based clouds, and I was subsequently elected by my peers as the\nProject Technical Lead (PTL) and a member of the [OpenStack Technical\nCommittee](https://www.openstack.org/foundation/tech-committee/) (TC). Later, I\nhelped launch the OpenStack Innovation Center (OSIC), a joint partnership\nbetween [Rackspace](https://www.rackspace.com/) and [Intel](https://01.org/),\nas a technical lead and cross-project liaison. I also helped lead the broader\nOpenStack technical strategy at Rackspace via the OpenStack Technical\nLeadership Team and the Rackspace Private Cloud architecture group.\n\nReviewing code from other contributors was one of my most satisfying endeavors.\nIn the early days of OpenStack, I helped kickstart OpenStack's code review\ndiscipline via [Gerrit](https://www.gerritcodereview.com/). Since then, I've\nstrived to provide other contributors with high-value constructive criticism,\nwith an eye towards fostering the community of new contributors, core\nreviewers, and technical leads both within Rackspace and beyond.\n\nI developed a rigorous appetite for a documentation-first approach (which\npushes developers to think through the user experience before diving into an\nimplementation), thorough automated testing (particularly important when\nworking with thousands of fellow technical contributors), and comprehensive\ncontinuous integration (from `git push` to shipping release artifacts).\n\n- *[Project Technical\n  Lead](https://docs.openstack.org/project-team-guide/ptl.html)*: As PTL, I\n  coordinated weekly team meetings via\n  [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat), conducted [thousands\n  of code\n  reviews](https://www.stackalytics.com/?release=all\u0026project_type=all\u0026user_id=dolph)\n  via [Gerrit](https://www.gerritcodereview.com/), triaged hundreds of issues\n  via [LaunchPad](https://launchpad.net/keystone), and fostered \u0026 mentored a\n  team of [core\n  reviewers](https://docs.openstack.org/doc-contrib-guide/docs-review.html)\n  from among dozens monthly active contributors in our open source community.\n\n- *[Technical Committee](https://governance.openstack.org/tc/)*: As a TC\n  member, I helped to govern the OpenStack community's structure, principles,\n  values, scope, goals, and licensing.\n\n- *[Stable Maintenance team\n  member](https://docs.openstack.org/project-team-guide/stable-branches.html)*:\n  As a stable maintenance team member, I was responsible for code reviewing\n  commits, backporting patches via cherry picks, and producing tagged releases\n  of stable branches.\n\n- *[Vulnerability Management team\n  member](https://security.openstack.org/vmt-process.html)*: As a vulnerability\n  management team member, I was responsible for triaging, reproducing,\n  documenting (via [CVE](https://cve.mitre.org/) processes), and patching\n  vulnerabilities on supported stable branches.\n\nCore technology stack: [Python](https://www.python.org),\n[bash](https://www.gnu.org/software/bash/), [JSON](http://www.json.org/),\n[YAML](http://yaml.org/), [Ansible](https://www.ansible.com/),\n[MySQL](https://www.mysql.com/), [memcached](https://memcached.org/)\n\nPrimary development tools: [vim](http://www.vim.org/),\n[git](https://git-scm.com/), [LaunchPad](https://launchpad.net/~dolph),\n[Trello](https://trello.com/), [Gerrit](https://www.gerritcodereview.com/),\n[Jenkins](https://jenkins.io/),\n[Wercker](https://devcenter.wercker.com/overview-and-core-concepts/wercker-features/),\n[TravisCI](https://travis-ci.org/), [Debian Linux](https://www.debian.org/),\n[Ubuntu Linux](https://www.ubuntu.com/), [OS X](https://www.apple.com/macos/)\n\n### *Software Engineer*, Akimeka (2009 \u0026mdash; 2011)\n\nAt [Akimeka](http://www.akimeka.com/), I worked on a project for the Department\nof Defense (DoD) Defense Healthcare Management System (DHMS) while holding a\nSecret security clearance.\n\nCore technology stack: [Java\nEE](http://www.oracle.com/technetwork/java/javaee/overview/index.html),\n[XML](https://en.wikipedia.org/wiki/XML), [JBoss\nAS](https://en.wikipedia.org/wiki/WildFly) (now known as\n[WildFly](http://wildfly.org/)), [JBoss\nSeam](https://en.wikipedia.org/wiki/JBoss_Seam), [JavaServer\nFaces](https://en.wikipedia.org/wiki/JavaServer_Faces) (JSF),\n[Hibernate](http://hibernate.org/orm/), [Oracle\nSQL](http://www.oracle.com/technetwork/database/), [XML-based\nsneakernet](https://en.wikipedia.org/wiki/Sneakernet)\n\nPrimary development tools: [Eclipse](https://eclipse.org/), [IntelliJ\nIDEA](https://www.jetbrains.com/idea/), [Perforce](https://www.perforce.com/),\n[FogBugz](https://www.fogcreek.com/fogbugz/), [Code\nCollaborator](https://smartbear.com/product/collaborator/overview/),\n[Windows](https://www.microsoft.com/en-us/windows/)\n\n## Side projects\n\nI've had many more side projects, but this is a handful I enjoy talking about.\n\n- [find-replace](https://github.com/dolph/find-replace): A fast find \u0026 replace\n  shell command written in Go.\n\n  Core technology stack: [Go](https://go.dev/)\n\n- [dotfiles](https://github.com/dolph/dotfiles): I've been version controlling\n  my desktop configuration files since 2013, across operating systems (OS X,\n  Ubuntu Linux, and Fedora Linux), and across multiple desktop environments\n  (Gnome, Xfce and i3). I now use Ansible to keep configuration across multiple\n  workstations in sync.\n\n  Core technology stack: [Ansible](https://www.ansible.com/),\n  [bash](https://www.gnu.org/software/bash/)\n\n- [github.com/dolph/recipes](https://github.com/dolph/recipes): I love to cook,\n  and I version control my recipe collection.\n\n  Core technology stack: [Github-flavored\n  Markdown](https://guides.github.com/features/mastering-markdown/)\n\n- [git-ready](https://github.com/dolph/git-ready): I found OpenStack's Gerrit\n  workflow to be a little cumbersome and (ironically) anti-social, so I built a\n  [Python](https://www.python.org/)-based CLI tool to eliminate that pain and\n  promote positive social interactions.\n\n  Core technology stack: [Python\n  2](https://www.python.org/download/releases/2.0/),\n  [bash](https://www.gnu.org/software/bash/)\n\n- [pasteraw](http://github.com/dolph/pasteraw): Frustrated by slow pastebin\n  services with poor CLI support, I built a fast, lightweight plaintext\n  pastebin service that pushes content directly to a CDN-enabled object store.\n  A few members of the OpenStack community adopted it, as well. Pastes are\n  still available today via CDN, but the frontend has been shutdown.\n\n  Core technology stack: [Python\n  2](https://www.python.org/download/releases/2.0/),\n  [Flask](https://flask.palletsprojects.com/en/2.0.x/), [OpenStack Swift\n  (Object\n  Storage)](https://docs.rackspace.com/docs/user-guides/infrastructure/cloud-config/storage/cloud-files-product-concepts/object-storage)\n  [Vagrant](https://www.vagrantup.com/)\n\n- [poker-hand-evaluator](https://github.com/dolph/poker-hand-evaluator): I\n  found that evaluating and comparing poker hands to be an incredibly\n  interesting and multifaceted problem. As a fun exercise, I built a command\n  line tool in [Go](https://golang.org/), mostly using bitwise operations, to\n  efficiently identify the best 5-card poker hand of a 7-card set. The result\n  is a unique integer that represents the strength of the hand, allowing the\n  hand to be compared to other 5- and 7-card hands to determine a winner.\n\n  Core technology stack: [Go](https://go.dev/)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdolph%2Fcv","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdolph%2Fcv","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdolph%2Fcv/lists"}