Privacy Notice

This site can enable Google Analytics to measure visits and traffic patterns after you opt in. Declining keeps Google Analytics off.

Read the privacy policy

Resume

Experience

Backend and platform work shaped by years of QA, systems troubleshooting, and cross-functional delivery.

Garrett Gehle

Backend / Platform Engineer

Summary

Professional Summary

Backend and platform-minded engineer with 10 years in tech spanning QA, internal systems, web development, and product-adjacent delivery.

Experienced investigating production issues, reproducing defects, improving release reliability, and building tooling that helps teams move faster with less guesswork.

Strong at working across support, engineering, and product to turn vague incidents into clear technical action.

Work History

Professional Experience

Senior Premium Support Advisor | Internal Tools & Systems Specialist

Docebo

Dec 2023 – Present
Remote

Investigate complex production issues for enterprise clients, reproduce platform defects, and build internal tools that improve support and triage workflows.

  • Investigate complex production issues reported by enterprise clients and reproduce defects for engineering teams
  • Document issues with clear reproduction steps and system context
  • Coordinate between support, engineering, and product teams to resolve platform issues
  • Develop internal tools to improve troubleshooting and issue triage workflows
Support SystemsInternal ToolsPlatform DebuggingEnterprise SaaS

Backend Developer | Product Manager | System Test Specialist

SAVI Controls

Jul 2022 – Oct 2023
Texas

Worked across backend development, product work, and system validation for distributed AV control software integrated with hardware, mobile devices, and server environments.

  • Led QA validation across 20+ software release versions for distributed AV systems
  • Identified defects, documented reproduction steps, and coordinated fixes with engineering teams
  • Designed automated test frameworks that reduced recurring regression bugs
  • Supported testing across server environments, Android devices, and networked hardware
BackendProductQAAutomation

QA Engineer

Charged Particles

Sep 2021 – Jul 2022
Remote

Built automated QA workflows and validated release stability across multiple application iterations.

  • Built automated QA workflows using Jest, Puppeteer, and Selenium
  • Identified and reproduced defects across multiple application releases
  • Performed regression testing to validate release stability
JestPuppeteerSeleniumRegression Testing

Web Developer

Genuinely Great Information Technology

2016 – Jul 2022
Remote

Delivered full-stack web applications and backend systems across e-commerce and education projects.

  • Delivered full-stack web applications across e-commerce and education sectors
  • Built APIs and backend systems supporting automation workflows
  • Investigated and resolved software issues across production environments
Web DevelopmentAPIsAutomationProduction Support

Additional Roles

Additional Experience

Marketing Manager & Technical Support

Real Geeks

2018–2021

Remote Technical Support

TeleNetwork / OneSupport

2017–2018

Team Lead – Customer Service

24-7 In-Touch

2015–2016

Education

University of North Texas

Information Science

QA Case Study

A QA Win I'm Proud Of

One QA experience I am particularly proud of came at SAVI Controls, where I tested software that managed complex audio and video systems connected to both proprietary hardware and commercially available AV equipment.

Failures could originate from several layers at once, including server software, device communication, network behavior, or third-party hardware compatibility. That made root cause analysis less about guesswork and more about disciplined reproduction and consistent test methodology.

I focused on structured QA processes with clear defect documentation and repeatable test scenarios across different hardware configurations, then helped introduce automated workflows to validate system behavior and catch regressions before release.

The result was more stable releases and fewer post-deployment incidents. What matters most to me is that the framework and QA practices we introduced became part of the standard release validation workflow.